[
  {
    "path": "LICENSE",
    "content": "The MIT License (MIT)\n\nCopyright (c) 2015 Bitrise\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n\n"
  },
  {
    "path": "PULL_REQUEST_TEMPLATE.md",
    "content": "### What to do if the build fails?\n\nAt the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.\n\n### New Pull Request Checklist\n\n*Please mark the points which you did / accept.*\n\n- [ ] __I will not move an already shared step version's tag to another commit__\n- [ ] I read the [Step Development Guideline](https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md)\n- [ ] I have a test for my Step, which can be run with `bitrise run test` (in the step's repository)\n- [ ] I did run `bitrise run audit-this-step` (in the step's repository - note, if you don't have this workflow in your `bitrise.yml`, [you can copy it from the step template](https://github.com/bitrise-steplib/step-template/blob/master/bitrise.yml).)\n- [ ] I read and accept the [Abandoned Step policy](https://github.com/bitrise-io/bitrise-steplib#abandoned-step-policy)\n"
  },
  {
    "path": "README.md",
    "content": "# Bitrise StepLib\n\nYou can find the collection of all [Bitrise integrations](https://www.bitrise.io/integrations) in this repository under [/steps](https://github.com/bitrise-io/bitrise-steplib/tree/master/steps).\n\n## Contribution\n\nIf you find something missing from the steps, you can drop us an issue, or [create your own step](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step.html#ot-fltr-modal). See our example for creating & sharing a new step under [/step-template](https://github.com/bitrise-steplib/step-template).\n\n### Important\n\nOne PR should contain only one file (except the icon), and one change.\n\nWe require to create a new PR after addressing review concerns. This is needed to guarantee that the last (correct) tag/version of the step source repository is referenced.\n\nOne PR should contain only one step.\n\n### Install Bitrise CLI\n\nInstall the [Bitrise CLI](https://www.bitrise.io/cli) to run `bitrise` on your machine locally.\n\nYou can install it via Homebrew:\n\n`brew update && brew install bitrise`\n\nOr check the latest release with instructions at: [https://github.com/bitrise-io/bitrise/releases](https://github.com/bitrise-io/bitrise/releases)\n\n### Share your step\n\nAfter implementing your own step, you can share it with other Bitrisers using this StepLib via [`stepman`](https://github.com/bitrise-io/stepman).\n\nIf you are ready, just run `stepman share` and follow the instructions.\n\nFollow [@bitrise](https://twitter.com/bitrise) on Twitter for #status and step updates 🚀.\n\n\n## Abandoned Step policy\n\nWe try to keep this Step Library up-to-date and active. Steps shared in this collection have to be actively maintained to receive fixes / updates when required (e.g. security issue fixes or general usability fixes).\n\n**If you're a Step maintainer** you're not required to accept every Pull Request sent to your Step **but you should be reachable within a reasonable timeframe**. If we try to contact you several times regarding an important fix/update in your Step and you refuse to answer for several weeks *we might deprecate, remove or replace your Step* in the collection. Abandoned Steps can be a threat for those who use it, please keep this in mind if you decide to share your Step with others!\n\n**If you shared a Step but you're no longer able to or you don't want to maintain it** please create a GitHub issue in this repository (https://github.com/bitrise-io/bitrise-steplib).\n\n**If you're a user of a Step which has critical (security or functionality) issues** please create a ticket in the Step's Issue Tracker (every Step declares the preferred way of reporting issues with the `support_url` attribute - [see](https://github.com/bitrise-io/bitrise-steplib/blob/master/steps/activate-ssh-key/3.1.0/step.yml#L15)) first. If you don't get a response from the Step's maintainer for an extended period (reasonably, in general, for more than a couple of weeks) please create a GitHub issue in this repository (https://github.com/bitrise-io/bitrise-steplib) and we'll try to resolve the issue, following the Abandoned Step policy. *Please be patient* and keep in mind that everyone who contribute to this collection does that with an intention to help You by providing a Step for you to use, don't be rude to Step maintainers!\n"
  },
  {
    "path": "steplib.yml",
    "content": "---\nformat_version: 1.0.0\nsteplib_source: https://github.com/bitrise-io/bitrise-steplib.git\nassets_download_base_uri: https://bitrise-steplib-collection.s3.amazonaws.com/steps\ndownload_locations:\n  - type: zip\n    src: https://bitrise-steplib-collection.s3.amazonaws.com/step-archives/\n  - type: git\n    src: source/git\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.0.0/step.yml",
    "content": "title: Activate Bitrise Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2024-03-19T13:54:48.081077+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 77c5bb89d3c255f6961b944b60184d23e74d4225\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.0.1/step.yml",
    "content": "title: Activate Bitrise Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2024-07-03T08:53:25.668504731Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: bf80b3428b635ab201102eba89250c963a0e713f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.0.2/step.yml",
    "content": "title: Activate Bitrise Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2024-07-04T09:19:51.560238447Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: d357c44fb74e9022218301c1a75d0a1a7ccb1fe2\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.0.3/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2024-12-09T12:36:03.79513556Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 8067cbd719844ecdf1fb89519df7a812b995d633\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.0/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-01-27T08:26:13.220270491Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 75de4455768ca25f4d9a8e1d4f00622338d062c0\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.1/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-01-29T08:55:05.915263935Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: c2ce2ebe4e0b51352855253910458d1227b90430\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.2/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-01-31T11:24:13.001627088Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 3b9aee467b5aaf275f49f7cafc256514eec08e86\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.3/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-03-18T15:00:31.506191721Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: ad6897bb16c9b8d4fbd6c5cb026e03c74fba678e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.4/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-03-31T11:52:37.746466323Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 4f0906e6d72fe539e8ceb3dd85b043c06c586554\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.5/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-04-15T08:47:39.308757923Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 709710f2ef136c769d92a1b62c58198ea41acd95\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.1.6/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-04-24T14:00:28.354662174Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 44e1f07d1e195c1391b9f8453f5fd266d636d4ab\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: When enabled, this sets up Bazel to add timestamps to log messages\n      during the build.\n    is_required: true\n    summary: Add timestamps to build messages\n    title: Add timestamps to build messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"true\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.2.1/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-07-10T13:09:19.671854113Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 1f7f5fc10e48420c43135bdaa521386d8ea6f8d8\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: When enabled, this sets up Bazel to add timestamps to log messages\n      during the build.\n    is_required: true\n    summary: Add timestamps to build messages\n    title: Add timestamps to build messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"true\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.2.2/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-07-10T16:02:17.381418513Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: bd8a485fe83f8026ad15c8e24ae6ed53bdce167f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: When enabled, this sets up Bazel to add timestamps to log messages\n      during the build.\n    is_required: true\n    summary: Add timestamps to build messages\n    title: Add timestamps to build messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"true\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/1.2.3/step.yml",
    "content": "title: Build Cache for Bazel\nsummary: |\n  Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Bazel executions in the workflow.\n\n  After this Step executes, Bazel builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel/issues\npublished_at: 2025-07-31T09:09:50.701591125Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-bazel.git\n  commit: 3ca1551056267e3c80354a90ccd1e05c8fe853d2\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- enable_rbe: \"false\"\n  opts:\n    description: When enabled, this sets up Bazel to use Bitrise's Remote Build Execution\n      (RBE) service to execute builds.\n    is_required: true\n    summary: Enable Bazel Remote Build Execution (RBE)\n    title: Enable Bazel RBE\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: When enabled, this sets up Bazel to add timestamps to log messages\n      during the build.\n    is_required: true\n    summary: Add timestamps to build messages\n    title: Add timestamps to build messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"true\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-bazel/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/1.0.0/step.yml",
    "content": "title: Activate Bitrise Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2023-04-24T15:17:29.28468+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 8d9cd958ca84ad07975b29604b77b919175d7e42\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/1.0.1/step.yml",
    "content": "title: Activate Bitrise Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2023-06-30T14:22:20.837998-07:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 1b8642ecfa4f10e10ac9b0e91f497b95dbaf5663\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/1.0.2/step.yml",
    "content": "title: Activate Bitrise Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2023-07-14T14:38:27.979936064Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: a1a0c3ef5539cea632d292346d69da80e4a5f51b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/1.1.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2023-09-08T14:03:40.31439796Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: e9c8658a4a1f6a140fd11cfd3c6e7c2c85782088\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/1.1.1/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2023-10-25T12:43:51.151505012Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 6fc8b9b2d3f66ab2d4912603e2c01774a33467db\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.0.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-01-31T12:16:00.810062208Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 3004cc7a460c040fc2a5dc483317b6c02d97afbb\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.0.1/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-01-31T15:43:03.944679Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: f51a7a13595b63c68f3267e3245c1b4e011deac7\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.0.2/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-02-16T12:01:12.010942635Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 053cc4d95da4844fa2b8fd68185765e4e7be655f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.0.3/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-02-20T12:52:04.447191065Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 336ea8d9551862c8ecede3f9fc5795b852fd108c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.1.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-02-27T16:06:40.938850215Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 1f568f218c135875d221a9eec58dcac89c7de994\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.10.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-02-24T15:08:02.57752264Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 6148670db99dd04cbb90c548a41d975e3b3571d2\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.11.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-02T12:44:33.858012234Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: b85164292b694066b2407281b0cc8573d7cf6f4d\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.12.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-03T13:01:26.925457776Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 8dcceef71a141b63fcdfde200f7760c67b3a4e3d\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-11T14:42:24.789308701Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 624913294a6cd4ff12a512e8332daf89194016aa\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-13T15:14:46.589979577Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 6ab962f5da483873e893dd957003032e1d1cd067\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.2/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-13T16:31:24.478397077Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 050dfd7ed0eb9412c68079664e90759dcef6e55f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.3/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-17T11:22:55.083749123Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: f50deddf01f697e70c1a4927056e2119b9212ada\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.4/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-18T12:17:31.651174254Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 4e82b60844b7875ac763ffa08e0d752e6530b222\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.5/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-30T09:41:32.260992358Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 96d9116eb2513ccedf4845e78b5c509bf3bdde55\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.6/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-30T10:05:43.831457356Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: bdc91bcf15da9aefbb20642d2af6a0544f0255ea\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.7/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-03-31T11:39:38.23492577Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 900d7227b374c70e6fd0b9d8e374310880438de3\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.8/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-01T19:35:20.109273158Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: b94987a8565d2f12d3216df67421e43e06ba7e17\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.13.9/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-02T16:40:41.61240077Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 753d7ff388b9823a2e91db65f4a4e1b36588f740\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.14.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-10T14:18:34.827132064Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 7385a1e2a6b93319ea97c15182020c2f142de57d\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.14.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-14T15:04:37.841827942Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 7385a1e2a6b93319ea97c15182020c2f142de57d\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.15.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-21T07:32:46.800593292Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9d45fb0015f0b9b49a26dee35d4da111fffb8a55\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.16.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-21T11:44:34.422078783Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 0614e45c0ea5a0e3e8bddaa27d531bf09a4cbbb8\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.16.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-22T13:38:56.652732243Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: a89de7a9dc27fd8f27ca9dd60ed6863122c1f7a0\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.16.2/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-23T12:22:49.251129197Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9b76e1aa1ab3a07654e8f5d93694d20baec0d917\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.17.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-27T13:32:15.194250203Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: d55bf98a4223b6386f6abbc4962b1a278b897a12\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.17.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-28T16:40:57.314753469Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: a09457c1750923598fe96215f218d5254a9d1022\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.17.2/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-28T18:38:22.691892897Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 5e14417a153a0f2242d1d54abe7eac1bf8b6a5b9\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-29T11:09:50.844038312Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 08a7078abbfebb26cc5ecb7369d642db28665478\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-29T11:50:21.947087014Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 54d7e33686d036e0d6113ad6f53906f5e2c9f86c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.2/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-29T12:32:49.490739664Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 0c14d7586fbe4bf4f1a49ba882ef8033ac69cbc6\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.3/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-29T14:48:54.169815665Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: b018e2a161ede13fba41e862b352d0d61a2ec980\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.4/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-30T07:10:01.769287809Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: a99f5ab5a272dfd0e5707a91881d69c87aad121a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.5/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-30T09:39:06.885242964Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: bebeac0566ec3b1afc366dc55c271a9ef30cb6d0\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.6/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-30T11:37:32.992596109Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: aea5db5585fa3f1d5da68f93561ed49ef9eda038\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.7/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-30T12:01:19.928739389Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 266e2708c0d60ae8ce54e61eb52c183126151b7c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.8/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-30T15:21:27.406571371Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 181eac6385e4775102c8e72ae7f87b3b47c23b1b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.18.9/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-04-30T15:57:52.694564218Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: b26a9e613fee0db28f532b882936fcd34716fc3e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.19.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-05-05T12:06:30.505645616Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 65c095748df31573fd3af5cad027c52978b04335\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.2.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-03-26T12:27:16.004266382Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 2edfc038a41d3b42cec12f8234a7d733e548d1cc\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.20.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-05-05T14:45:21.731114537Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: cb3e6bde4d0b6d79819ba1cb8865dbdf2a9f3d64\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.20.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-05-12T08:58:55.856730738Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 94373df17d7d34cfe982070b80a6cd1cf6583037\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.3.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-04-03T12:56:44.890103211Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: efbe378d7817ea3559f5739799b0cc5e96a4b2b1\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"false\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.4.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-04-17T11:17:11.35146825Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 2fe9df1797c3ed4c05627d00670ae320cb057356\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.5.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-04-23T13:30:58.940201096Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: a9eb8f5d9e2868b9488f3ce896e5be8bbe5a71e9\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.6.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-05-09T06:49:25.539591955Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9d232a62bbf02e8ad3cd7818ef90eb4fabbbf8b2\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.0/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-05-14T08:54:06.286353106Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: fc1308fdc697651077655b6419f59173d6791211\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.1/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-05-16T07:25:51.701672831Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 5fe5746e06c97d3bed1431c0a1a682f429774ac5\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.10/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-12-09T13:46:25.722045301Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 3013c09aa89795912af26160cb900f428d0f4673\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.11/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-12-09T15:49:56.860632332Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 5b19ba43f97628884bff493f94c7032d65c9e5ee\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.12/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-12-12T10:03:19.31376549Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: c28102b1016b8b251af02e1c895086ef09828763\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.13/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-14T08:50:41.564279659Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 672b3deebab7ac0b613d42a3d11498d38bdaa2a7\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.14/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-16T10:14:19.667361302Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 1a66cdc623df7261514a18abe820d32d51019a65\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.15/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-20T11:05:36.8709771Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: dd7cd01193c4059260773c153ef4c65a822d8e55\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.16/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-21T10:20:39.157509331Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9cbf5d355f8d555cb81baedee7bf2ba7046950d4\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.17/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-27T15:28:58.842828325Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 62ff5a1e0f41d99a158bdaff05d565d264c9ab31\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.18/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-29T09:32:42.891262216Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 33d46171f76d737f76eae3a73257a97098f5da2a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.19/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-30T14:06:49.723702633Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 5d69be8fa0d5f36f6c1fd21b1bb0c52917a09800\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.2/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-05-17T14:55:57.451818696Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 7759efa0a099ed29e7500b3246c28c27977bb638\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.20/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-01-31T10:30:53.215411656Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 01979fbb712a2c4c83808c39f23990b6e8fe8409\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.21/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-02-06T14:00:07.341253501Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 2e43e9027383e8e6694551fe5f72676235c044b3\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.22/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-03-04T12:38:43.323862743Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 45214800122383f444549bcc75e79f9c0e66219a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.23/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-03-18T14:59:46.967995125Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 68b7cea844b00b7aa1dea8bc349898e106b5687d\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.24/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-03-25T08:40:54.613556685Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: e47a3ef3f2b8ad3cfa946369f5c338e9e45354ca\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.25/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-03-26T12:48:40.131895624Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 72d57cb5caf14287efe4fdd226279bffbb04f420\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.26/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-04-01T15:21:50.585546919Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: cc842c6db5f4fe10e751df3cd273af575b26e100\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.27/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-04-04T08:25:51.292878312Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 2626100fcb85d75347013bfca8f3eddedf13280b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.28/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-04-04T14:06:59.253832316Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 23cc6f6c6937d63de2102427735fc3b78bc4db73\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.29/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-04-09T09:31:43.676939974Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 3e19606fd9d4df5ec93d75b32869a78f243f8a9c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.3/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-05-29T17:00:04.205838589Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: d7de0df25d2f225ef91ededd0be9db474739fafd\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.30/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-04-10T07:58:22.710228407Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: faa772199b0b435e0bcd54683549c3f28f0a0d1a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.31/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-04-30T10:21:57.299470118Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 8591e8cd8de0d8b76b20713d3f0b8474a21ab850\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.32/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-05-08T13:02:41.371014847Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 44eb8f9fdbcaa1f333bce94399a2eac7c9cb6126\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.33/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-05-09T09:22:54.005022695Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 670dd19dc91e4887ffb0e504eb77f9f27af9e834\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.34/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-05-13T09:21:44.194859884Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 3083f11afbfee25848f960d5b6966de1ada7d8a9\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.35/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-03T11:02:05.718513443Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: b89a2bf54bc0ba7e8f08fe3b104b6b428c1e33fd\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.36/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-04T16:30:03.502635703Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 6cfb6304c6e7604f6fd0db14f00c22208009233a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.37/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-11T13:20:13.608073809Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 2332358e965bfb6216a4c437bf15d92f272ac77e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.38/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-11T15:03:42.074003661Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: e66112f6242b4e413822020966d66b97bd8f745e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.39/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-11T16:50:17.259953437Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: ba879d9c6415891af8a21c407f9af26ce70ea0dc\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.4/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-07-01T14:05:53.681179295Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 873fd0c62b7742461089babf2fa965cdcd0b4e7a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.40/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-17T09:40:05.957496929Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 0f1a598a9be3a25ba8af71c098ddcf99ac288dea\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.41/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-17T11:25:09.801489854Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 4be4deacde6961b06a10d2f29fe89d4aa61fe6a0\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.42/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-19T08:09:00.892845101Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 2b9de7f8dc0ed623eda3c1c4290d8fc72bdf872e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.43/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-25T10:53:58.653095031Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 0918df815326d1cd302a90c09cca0e62dccf44ba\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.44/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-06-26T13:40:47.404201394Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 3b714a7a7434be319f3ee58cdb62da6806299838\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.46/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-07-01T09:55:06.868121756Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 7c8036da167b6ad36374be9988b5cbdbba2c946f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.47/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-07-01T14:43:04.969363494Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 57a214f3ecfab20a28e38fd92ff571ec973fc5aa\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.48/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-07-08T09:34:10.0088445Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 48d0472c1efdc1d008ddce7955433057e2c13942\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.49/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-07-08T15:25:01.303980877Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 8116b48b3a51c835a743c1810ae1bba596eda025\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.5/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-07-04T09:18:58.387289938Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: de3d2babae03acd712d3134ade7a7342c5cc445e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.50/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-07-29T14:06:25.913097146Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 894aaf01727b2ff22e7bef8df932f44eb27f78fe\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.52/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-07-31T07:28:28.458151421Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 6857ca8432484b2360e2379e629df602fb314a80\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.53/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-09-02T15:52:33.65792468Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 3cd3e6c5d7ee7ccb0e1caea8750d9f3d6312163e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.54/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-09-04T12:16:04.593911938Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 60b3656c12b9396ee2f97a47e6cfacac4aa9512f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.55/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-10-01T13:19:36.586873122Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 03f357faf37d047f3aa3dc9fb69e0ded5b8a3869\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.56/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-10-28T09:47:57.802185467Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: bb366b50428ee744b492c2a92867858b655ae663\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.57/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-10-28T19:11:05.744948966Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: df49e07ac71d5239a74705e8389b911df05184c8\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.58/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-10-29T10:32:48.4981106Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 818395ceb854dd569e3b0c9ec55af1167e5441f6\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.59/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-04T14:16:06.495338021Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 4d90e2d58e971b2f116ef89fad5fc1f2444874cb\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.6/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-08-05T07:49:08.197071046Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9d3291505f347526b5f4adddd82d27e5042a8b92\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.60/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-05T12:41:12.759570793Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 075d9e2c117d6432960316ca74a693483fd4f21b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.7/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-09-30T11:07:17.51029294Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 15f878aef22cebab1489c7426c61d48b25c6efc3\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.8/step.yml",
    "content": "title: Activate Bitrise Build Cache Add-On for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-12-03T10:52:17.608486736Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9201ae9c6dc325380d720243907802971269ab54\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.7.9/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2024-12-09T09:48:17.734324726Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 5012c78400278f3cec07be0e77dfefc6049bad2d\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-13T12:27:56.912517408Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 4747543148fe67268816a7875dac6eec852380ca\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.1/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-19T10:04:45.773021477Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: dddeacd373c69a0d8393d9d0d757aff1e8cf62d1\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.2/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-20T14:43:53.284040504Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: d9c0ab87c8ab9a28ad622b3276b43e1c3258d1cb\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.3/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-26T12:00:13.90558941Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 5b0530e6b9525a00f47a056b2e8504206a544f6b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.4/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2025-11-28T09:49:28.522401001Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: a83c6fc8591502650d840e395d9c1056fda09601\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.7/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-01-12T13:56:29.425853921Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: aa978433873857ce3963c1dfa9847f97ac0270d0\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.8.8/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-01-13T13:57:11.549370392Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: f51c2ae4556087478577f336479f9de3a6eb2212\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/2.9.0/step.yml",
    "content": "title: Build Cache for Gradle\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds\n  in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Gradle executions in the workflow.\n\n  After this Step executes, Gradle builds will automatically read from the remote cache and push new entries if it's enabled.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache\npublished_at: 2026-02-12T16:14:03.515880643Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache.git\n  commit: 9a283fb4ef6ab4b268fde69976ae42458189ac7c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    description: |-\n      Level of cache entry validation for both uploads and downloads.\n\n      Levels:\n      - `none`: no validation.\n      - `warning`: print a warning about invalid cache entries, but don't interrupt the build\n      - `error`: print an error about invalid cache entries and interrupt the build\n    is_required: true\n    summary: Level of cache entry validation for both uploads and downloads.\n    title: Validation level\n    value_options:\n    - none\n    - warning\n    - error\n  validation_level: warning\n- collect_metrics: \"true\"\n  opts:\n    description: When enabled, this sets up Gradle build metrics collection for the\n      subsequent Gradle invocations in the workflow. Metrics are sent to [Bitrise\n      Insights](https://app.bitrise.io/insights).\n    is_required: true\n    summary: Collect build metrics in subsequent Gradle executions\n    title: Collect Gradle build metrics\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-gradle/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.1.0/step.yml",
    "content": "title: Activate React Native Features\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\n\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-09T12:00:00.000000000Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: e96ada56a66bb11c74d923afa2ac662a5235758c\n\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\n\nrun_if: .IsCI\nis_skippable: true\n\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\n\ninputs:\n# -------------------------------------------------------------------------------\n# Xcode cache\n# -------------------------------------------------------------------------------\n- xcode_cache_enabled: \"true\"\n  opts:\n    title: Enable Xcode cache\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    is_required: true\n    value_options:\n    - \"true\"\n    - \"false\"\n    description: |-\n      Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate and starts the Xcelerate proxy in the background.\n\n# -------------------------------------------------------------------------------\n# Gradle cache\n# -------------------------------------------------------------------------------\n- gradle_cache_enabled: \"true\"\n  opts:\n    title: Enable Gradle cache\n    summary: Enables Bitrise Build Cache for Gradle\n    is_required: true\n    value_options:\n    - \"true\"\n    - \"false\"\n    description: |-\n      Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle cache with analytics and remote cache plugins.\n\n# -------------------------------------------------------------------------------\n# Debugging\n# -------------------------------------------------------------------------------\n- verbose: \"false\"\n  opts:\n    title: Verbose logging\n    summary: Enable logging additional information for troubleshooting\n    is_required: true\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.2.0/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\n\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-15T07:28:02.846206874Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 8f6a31e16cfbd94c5256c2687c2b8720b77e7c25\n\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\n\nrun_if: .IsCI\nis_skippable: true\n\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\n\ninputs:\n# -------------------------------------------------------------------------------\n# Xcode cache\n# -------------------------------------------------------------------------------\n- xcode_cache_enabled: \"true\"\n  opts:\n    title: Enable Xcode cache\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    is_required: true\n    value_options:\n    - \"true\"\n    - \"false\"\n    description: |-\n      Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate and starts the Xcelerate proxy in the background.\n\n# -------------------------------------------------------------------------------\n# Gradle cache\n# -------------------------------------------------------------------------------\n- gradle_cache_enabled: \"true\"\n  opts:\n    title: Enable Gradle cache\n    summary: Enables Bitrise Build Cache for Gradle\n    is_required: true\n    value_options:\n    - \"true\"\n    - \"false\"\n    description: |-\n      Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle cache with analytics and remote cache plugins.\n\n# -------------------------------------------------------------------------------\n# Debugging\n# -------------------------------------------------------------------------------\n- verbose: \"false\"\n  opts:\n    title: Verbose logging\n    summary: Enable logging additional information for troubleshooting\n    is_required: true\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.3.0/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-27T11:19:33.07437196Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 32761b808cb4fdecc9fa5c1655aedc7d150cb5f7\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.3.0/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-8d7faad73d8d8f408945910bdb5b0e3f75ed7cdb86464af51351097096c1578f\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.3.0/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-fe4fdeed4f95fceb5a9ff23718621de8753fa7a4057b2462f4398aca584e0ebb\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.3.0/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-ae24ba0323bfc23cba5b8acaf370d3bb37f713b30be9c2be3c2faf38b1fbd6d3\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.3.0/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-7110058b0ab42bfe081eda0348f24ea8885ed1f7ccaf2a01d52d1815b7031480\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.4.0/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-27T14:00:52.952754191Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 838e67f4bb0a4c908e19e7355fd79466ee586a7a\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.0/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-c2ec9d0abd14153028efe2e12fd8e33d67a029ef797c9bbff285c3e121b5234e\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.0/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-4f262071a8bcb935ee71947de684889f7702c15990180d4d9b7a41d99aa72d42\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.0/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-ff5029e3e2ad262ecda24482caa3524e963366eaf6ca11dc11a61819938a91ff\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.0/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-6478fea860d2a3a3367d202025b40f018af1f3067e591bb6ba52a2689f6cfa0f\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.4.1/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-28T20:36:27.860435976Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 34387e1657a8fffa1b7495bf3da4d91531f30cb5\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.1/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-73497c5acbc9dc4dbf4289ee4f80b8e7bc01da8b73c06f8a269a1fc7b36e11d8\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.1/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-ec5e6fa440482fbe4c44269dd1f06145b2ca942906bb63a77b01cd79a207b193\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.1/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-d5f4ce531265a16da57c1ab3d05c8bebc2906f252c67125ff4ff2533f9f1dd32\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.4.1/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-d3b73f81fed3723fb0201835f0870adbe5d6cf2622f4b9caad2f41c926446565\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.0/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-29T11:05:48.40610511Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 12bf93750d3e053b50666a17c6e1c627a5f2dfde\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.0/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-b6cd564952d011ff94a5e5f3cbc6951df887ca3dceac0efc2b595c0fc8c6220f\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.0/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-2b06b766005b3a9f66471fc862d49881e7c649f8be014148118ae2e5118dd0d4\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.0/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-5a0e64c7d73e57a60260347cef30260d2fe14987b39ae95ed7076f251b0ff285\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.0/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-37e37fb5b3a9929d78225838d31f0caa51ddeb82202c4f84eceb88c55d64b698\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.1/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-29T11:35:26.909590062Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: bc60f70040df9a3f058aad09c9dd243edfd59319\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.1/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-8a118fac51c54c25c4198b6501353a80a9dda0c3809681ec03e4ea5a3080117b\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.1/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-d976e08285212b18d863607687164395d1537a42f0234aba360cd5574626ee9b\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.1/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-d1209fd80e26f260e5ccbec6fe339e5bcb9e6e015829316f3cb2cee81445dc6f\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.1/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-73407793b691008a008987705b5669ad7a0909b98db5d35ecf4019fe0c02251e\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.2/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-29T12:33:32.525784686Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 9c39597c45aa2695663a3174507a42291a8eeb14\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.2/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-204e5870c6538b1ec068c55a3302b35c8bba3e749e485f5f0cf33764a7251666\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.2/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-a8b0f5160eca2aa275a0846c8869ed28fdcfa57d4aee09919675945867ec47f5\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.2/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-0f2f38b739a662132e5d6358ad5682977a5f4f736d4818ce6bd96cf00b511cba\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.2/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-4d2221e2a003351a8acdeb5cdd6be6b5ae1e88c33183f81f0ef654820fd6ca6c\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.3/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-29T14:49:38.034274161Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 1d5c25cf68541ad4f4e5ab93706f455f9abade33\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.3/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-0c1996c7833ee4f9ceb1a86588e31402991bf6e573c3d63b81ccc24b3bf5498c\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.3/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-3e251ae7f7634bdf46e52eca62ae04e3b6695c3af0a78b4ce734bf0342951dc0\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.3/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-8eeb91b054fa40b602e04f951f862363cbab4337dccca8b7adccb7a81531799e\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.3/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-24ded93173c2cd43875041fad3fc2c968ffc8f1766c01c9a97b13e3df87b3e9b\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.4/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-30T09:40:00.116917839Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 59a0e3e3489727caa4191423f4fd007fb4f93243\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.4/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-b358e13ab5ea448157070b27686345b4d041e9d4996c5e88ef59c753198f42f0\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.4/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-d63235fbd29128fdef7ca17299db3f12abf564fb484ca41c068c00e63f212f4f\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.4/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-ec7c04082cffecc10952b5c972dfa0c9545337cdcea35c6f450ddc2236d0dbd3\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.4/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-7ac883c412781b31cbfc7135d09996c2f8c53154fd91d57bf4039f44c7b538a0\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.5/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-30T12:02:01.494993698Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 1a1ebadc5c50ff527737f8e35fb285f4bc4eb48e\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.5/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-35342d4cc6c78abd5c5147f92a212f59824f05fe88b9e7f2f143ae45b311b2c5\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.5/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-80bb2c94f6ae7c8cc82296ddaceea2b4729c67a73d22bfdaf8a42fffd97304d1\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.5/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-fc17b0dddb236d908142effe669822ff877dbad0a907e76030cfb73e5cb03c94\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.5/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-8b42a82a730f99eb060f87a3bc63501a4c893be07aa298c7757a7982119076ad\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.6/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-30T15:22:31.689356115Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: c5aae7ba287664a9aa076025743d86f754af471d\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.6/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-ca57dd1b26def487d8c236e81ccf13effab09e8572dff3f137fb8ab83b85fd12\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.6/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-f329bdd74ef9479f415e4122c4d224038ab2ec17459847e114c634bb22a26ee7\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.6/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-d9e0b97a181e2caf2f4d90821048b226b98e4f8a9e3e90f195ff5861d1213f0d\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.6/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-a18c700945c4a4a6f00fa5d995139a5a320fc631fe581b4b7563ded9e807d450\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.5.7/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-04-30T15:58:46.21636056Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 500bc61d5aa65d30c7f34edc2c1841428ad953a1\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.7/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-43f21698534e32efa4d37f483a973ee61c1d08ccb8a9ec23a7d909c5ec2a6df6\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.7/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-a8afc563a2d38ac1f87536824fa07707b8fb193a868b60d073284ad6c90ca988\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.7/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-b0c11ff6bd7714e84dca6b6ecf359704fbe66706a20bd779d74390d1c18f2be2\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.5.7/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-a37bd032f8dfba44fda8c7ae3c55be2399f73d2c1239daf87c6290e22895cdb0\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.6.0/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-05-05T12:08:18.103659759Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 4e26411bc72002d9a1377589af39490f604c363d\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.6.0/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-9debe0909aa80e8da3ef2d840e7ae2072d3b6af80e19410165bd34be2ca3040a\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.6.0/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-020965c25885dd95c9ffa862ffa59b32c2bbe202c32afbc6e4556fc182d759f3\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.6.0/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-cfe1c1521fc2c59da8652a1d395bc4ce1734bcc1b88621fe04eea6cd718a6a5c\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.6.0/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-0191b60fcb18adef34667994e5219888b41cc87a9b377014437904ea56bfc868\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.7.0/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-05-05T14:46:23.968272196Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 7c1680a1d96c9a3a7d803172d4fbee70ffa8ca76\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.0/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-a144c109bdabb83ac764215e65da9aeb475cd3f9a6beecaba6a411c411e13a5d\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.0/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-a0663f9d17f969545b5e5e7b5d1f63a109715e372ddcfc0413af62330cf13b8b\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.0/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-d922d92705482f3cb7c102e488f090593dd177ffb89f962b42af380d95f28d2c\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.0/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-f57b5669aebac5ea186c54cb9979411861421ff4b8a595e211936501231a9f51\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/0.7.1/step.yml",
    "content": "title: Build Cache for React Native\nsummary: Activates Bitrise Build Cache features for React Native projects\ndescription: |\n  This Step activates Bitrise Build Cache for all build systems used in a React Native project.\n\n  After this Step executes,\n  - enabling Xcode cache will result in: iOS builds will use the Bitrise Build Cache for Xcode via Xcelerate, with a background proxy started automatically.\n  - enabling Gradle cache will result in: Android Gradle builds will automatically read from and push entries to the remote cache. C++ native modules will also be compiled using ccache, with a background storage helper started automatically.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features\npublished_at: 2026-05-12T08:59:31.815907543Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-react-native-features.git\n  commit: 34ba6b685d3f9bd0d38dff152bce6ffb2e233562\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.1/bin/activate-build-cache-for-react-native-darwin-amd64\n    hash: sha256-3288fd95d5731206840e31bcf3c4a4517be4105323269c67be44d1265dee60df\n  darwin-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.1/bin/activate-build-cache-for-react-native-darwin-arm64\n    hash: sha256-ad3f03ac7f277b7e0016a34ba3d1cace01e53bbdb2bd7af42620c9ee9d8141cb\n  linux-amd64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.1/bin/activate-build-cache-for-react-native-linux-amd64\n    hash: sha256-175870eeed216dbcef7429e91f6fb7475585f92d2a477c28be8aa6e4b63c3502\n  linux-arm64:\n    storage_uri: steps/activate-build-cache-for-react-native/0.7.1/bin/activate-build-cache-for-react-native-linux-arm64\n    hash: sha256-d669d7ae021c8f259d2491cbf3d79312fa9291951e7a0cbc908e4609442c41f4\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-react-native-features\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Enables Bitrise Build Cache for Xcode. When enabled, activates Xcelerate\n      and starts the Xcelerate proxy in the background.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Xcode using Xcelerate\n    title: Enable Xcode cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  xcode_cache_enabled: \"true\"\n- gradle_cache_enabled: \"true\"\n  opts:\n    description: Enables Bitrise Build Cache for Gradle. When enabled, activates Gradle\n      cache with analytics and remote cache plugins.\n    is_required: true\n    summary: Enables Bitrise Build Cache for Gradle\n    title: Enable Gradle cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-react-native/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.0/step.yml",
    "content": "title: Activate Remote Tuist Cache\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-04-24T14:52:39.28671+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: 7876e59a47b92ab10de2a8cc09d12fcc58d28393\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.1/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-06-06T15:53:06.752511+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: 4bb0c8fae6a9a7afaa9afc0c60e9aac4a0c29436\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.2/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in\n  the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-06-30T20:36:14.699365+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: 1ec62acc47d6aa64960797fc2cb7e4c41c70ce70\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.3/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in\n  the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-07-14T16:36:41.930027+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: 4f46a8497048315ca3f0170f480ea07ad0d96528\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.4/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in\n  the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-07-25T09:58:01.891891+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: d8a26682256ef71b5ee0669c82935f02c9711391\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.5/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in\n  the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-08-03T15:47:46.012332+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: 434e8d2095cd63dce55127605cc1bfcaa674bebb\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.6/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in\n  the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-10-04T12:02:33.510826-04:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: d2a30d8fec48ebe9798e5281ae1a02aecbb0bed4\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/1.0.7/step.yml",
    "content": "title: Activate Bitrise Build Cache for Tuist\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Tuist builds in\n  the workflow\ndescription: |\n  This Step activates Bitrise's remote build cache add-on for subsequent Tuist executions in the workflow.\n\n  After this Step executes, Tuist builds will automatically read from the remote cache and push new entries.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache\npublished_at: 2023-10-04T14:11:45.96548-04:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-tuist-cache.git\n  commit: 5c17ce8e8593ab132a87756c87642d08dd0d3408\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\nis_skippable: true\nrun_if: .IsCI\n"
  },
  {
    "path": "steps/activate-build-cache-for-tuist/step-info.yml",
    "content": "maintainer: bitrise\ndeprecate_notes: \"This step is deprecated. For more information please see: https://bitrise.io/blog/post/tuist-bitrise-build-cache-update\"\nremoval_date: \"2024-03-31\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.0.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-xcode-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-xcode-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-xcode-remote-cache\npublished_at: 2025-09-12T14:41:09.542658+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: eee2ff0639cf8d9b135cc96881b01fb783bfac8a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.0.2/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-xcode-remote-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-xcode-remote-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-xcode-remote-cache\npublished_at: 2025-09-16T09:58:03.433296+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 4bac0e037cb2a91a0d19626f3302cf731600f968\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.0.3/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-09-16T10:49:00.305809+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 6c541d013e88ae8c37d626c83d2c5b1d8f3be12e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.0.4/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-09-18T07:24:32.676998975Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 94346b920bbcdfd048f9f50f700fd1f995fc7851\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.10.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-29T11:04:06.557704677Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 62daed5152db18e90d8c6a6ba4f6eabc4038dd9e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.10.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-29T11:34:41.506786508Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: f66f5c2ede52975906712c4f104a1965c29e69d4\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.10.2/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-30T09:39:13.240741999Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: b739e329c73424190b3796a4f4642dee21c0a9a0\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.10.3/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-30T12:01:16.669716177Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 6df27adf7554bd27ef8eec05b29a11fcee0f0c50\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.11.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-05-05T12:07:33.317274355Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 1d7ecb1446626fb9be93867b343174f3f48346a2\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.12.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-05-05T14:45:27.984878743Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 5f5e882493451122fffe98df772d92f5b7340305\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.2.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-09-24T07:18:10.506908925Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 5ded1c235fac99f2536effa7c8cc4b82d14e8c1a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the Verbose logging option.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.2.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-09-25T09:54:10.572274595Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: a94294250bdfdb63e1410984bd2e6ace17713f6e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the Verbose logging option.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.3.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-09-29T12:46:58.427174749Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 7ba32cda5ce9240288707a57f03527bdce9b823b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.3.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-10-14T08:46:28.00262386Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: fde9dbf94af906af8c489422f00c687034875e49\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.3.2/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-10-28T14:49:03.626139186Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: ce7d4b560b22fc5f76a9de5146244bfa8e7e9f1c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.3.3/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-10-31T09:52:01.821292646Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 1e22f4480ec546d66ce83fa9b07afe8309cac383\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-11-19T13:36:51.201673272Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 6fb844707437ce369ac7128375dd2d1c93d1958f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-11-19T15:33:23.193277318Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 711b8663e34f4383ca881cdc41cdc8d98e6bd5b6\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.2/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-12-02T13:05:50.078086376Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: cd3168c746e435c3b2582d73fa6600f12cc1dc4f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.3/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2025-12-08T15:35:14.205828811Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: d18b3d15931b1c44a6124134e24edcde937c0410\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.4/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-01-23T10:28:57.53333754Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: ba4c0d3047d0d3c04901370ab1871b90a00d475a\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.5/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-01-27T09:34:12.809933807Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 8cb70fd92918ca4f0572840d36553d3bcf075a25\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.6/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-02-03T15:55:26.290266147Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 9eacee8582cddef7dc79a6e11e73cde5e68611d3\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.7/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-03-10T15:36:27.842406326Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: dc1ecee50016b997105ea20a71ff14189af0cbe8\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.4.8/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-03-23T08:59:24.837665944Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: f84c4809634b58a5b40e0b7abf4939fd88cc802c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.5.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-03-26T15:08:21.119821401Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: bc2e151305eb4f6cd79cd004533f0d3c4870326f\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.5.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-03-30T11:59:11.681063144Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: f58dceaec1b0d089c6dfe2ac2366b75d59c5673b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.5.2/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-03-31T11:39:41.339260329Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 26a4e44bd6e70f49bd6603eed8e00f314bb5f1a9\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.5.3/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-02T16:40:49.809777506Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 6cf9516153a5cb1412cf13546a6778f30b2c08e7\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.6.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-10T14:18:29.919214388Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: d5d552b3988538412492cb2edc889006d05a7b39\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.6.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-14T15:04:47.184499236Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: d5d552b3988538412492cb2edc889006d05a7b39\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.7.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-21T07:32:46.775542252Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: fb2c23348968cd9fa4a1b20b0bc2ffe713fe763b\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.8.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-21T11:44:38.048841858Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 09d983542c8d39d1062e1b1f48667323104d950e\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.8.1/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-22T13:38:56.877363543Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 9593a9e67f7b25048f6f4a2148d31edc15f72c06\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.8.2/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-23T12:22:49.280370061Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: 27da8a811a9a910e51bf6f665220543b189d1577\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/0.9.0/step.yml",
    "content": "title: Build Cache for Xcode\nsummary: Activates Bitrise Remote Build Cache add-on for subsequent Xcode builds in\n  the workflow\ndescription: |\n  This Step enables Bitrise's Build Cache Add‑On for Xcode by configuring the environment with the Build Cache CLI.\n\n  After this Step runs, Xcode builds invoked via xcodebuild in subsequent workflow steps will automatically read from the remote cache and push new entries when applicable.\n\n  The Step adds an alias to ~/.zshrc and ~/.bashrc so the wrapper is available in all following steps; from that point all xcodebuild calls are wrapped to enable compilation caching.\n  Analytical data (command, duration, cache information, environment) is collected and sent to Bitrise and is available on the Build cache page: https://app.bitrise.io/build-cache\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode\npublished_at: 2026-04-27T13:32:17.524457722Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode.git\n  commit: fee71c33bcb2aca9911031699435127c9cd83cf1\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- cache: \"true\"\n  opts:\n    is_required: true\n    summary: Whether the build uses the remote cache\n    title: Use cache\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Whether the build can not only read, but write new entries to the remote\n      cache\n    title: Push new cache entries\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n- opts:\n    is_required: true\n    summary: |-\n      Whether Bitrise components should not log anything except the underlying xcodebuild output.\n      Takes precedence over the 'Verbose logging' and 'Add timestamps' options.\n    title: Silence all extra Bitrise logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  silent: \"false\"\n- opts:\n    description: When enabled, the analytics wrapper adds timestamps to xcodebuild\n      output log messages during the build.\n    is_required: true\n    summary: Add timestamps to xcodebuild messages\n    title: Add timestamps to xcodebuild messages\n    value_options:\n    - \"true\"\n    - \"false\"\n  timestamps: \"false\"\n- cache_skip_flags: \"false\"\n  opts:\n    description: |-\n      Skip passing cache flags to xcodebuild except the COMPILATION_CACHE_REMOTE_SERVICE_PATH.\n\n      Cache will have to be enabled manually in the Xcode project settings. More information can be found at the FAQ\n      document: https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html\n    is_required: true\n    summary: Skip passing cache flags to xcodebuild\n    title: Skip passing cache flags to xcodebuild\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-build-cache-for-xcode/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/0.1.0/step.yml",
    "content": "title: Activate Gradle Mirrors\nsummary: Activates Bitrise repository mirrors for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This step installs a Gradle init script that redirects repository requests to\n  Bitrise-hosted mirrors for faster, more reliable dependency resolution in\n  subsequent Gradle invocations.\n\n  The step is gated by the `BITRISE_MAVENCENTRAL_PROXY_ENABLED` environment\n  variable and only activates when run in a Bitrise datacenter that has a\n  mirror deployment. In every other case it logs an info message and exits\n  successfully.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\npublished_at: 2026-04-29T15:26:38.700397+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors.git\n  commit: 365f296d6df30cfef52ab593fea3ca83d4dfb588\nproject_type_tags:\n- android\n- kotlin-multiplatform\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/0.1.1/step.yml",
    "content": "title: Activate Gradle Mirrors\nsummary: Activates Bitrise repository mirrors for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This step installs a Gradle init script that redirects repository requests to\n  Bitrise-hosted mirrors for faster, more reliable dependency resolution in\n  subsequent Gradle invocations.\n\n  The step is gated by the `BITRISE_MAVENCENTRAL_PROXY_ENABLED` environment\n  variable and only activates when run in a Bitrise datacenter that has a\n  mirror deployment. In every other case it logs an info message and exits\n  successfully.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\npublished_at: 2026-04-30T07:23:52.790472639Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors.git\n  commit: c9068b5bfec2594d897aa6238491183c235c1554\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.1/bin/activate-gradle-mirrors-darwin-amd64\n    hash: sha256-073e7ae122e1368ada3d14c7de79dbe95c9265f95d7f1fbdecc15ddbacd91c53\n  darwin-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.1/bin/activate-gradle-mirrors-darwin-arm64\n    hash: sha256-22e91ff20e4b94e7e79e584aadee15ad2555ff8ccf9c9493a0a58f7462b523b0\n  linux-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.1/bin/activate-gradle-mirrors-linux-amd64\n    hash: sha256-356698c4f40dd26287d3bc0d7aa50892e416a687d06369e0b35217066d12fdd6\n  linux-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.1/bin/activate-gradle-mirrors-linux-arm64\n    hash: sha256-019e3f7e477b6bf2e32062b6bd3c05d0c18d59da6a742671a87527de04cbcd09\nproject_type_tags:\n- android\n- kotlin-multiplatform\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/0.1.2/step.yml",
    "content": "title: Activate Gradle Mirrors\nsummary: Activates Bitrise repository mirrors for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This step installs a Gradle init script that redirects repository requests to\n  Bitrise-hosted mirrors for faster, more reliable dependency resolution in\n  subsequent Gradle invocations.\n\n  The step is gated by the `BITRISE_MAVENCENTRAL_PROXY_ENABLED` environment\n  variable and only activates when run in a Bitrise datacenter that has a\n  mirror deployment. In every other case it logs an info message and exits\n  successfully.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\npublished_at: 2026-04-30T10:43:01.056392735Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors.git\n  commit: b4431c1ad7faca0795adde5451e842c7e7bf5902\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.2/bin/activate-gradle-mirrors-darwin-amd64\n    hash: sha256-c1e1d62b292eec340a49da27dd3acdab4ab9d06e0187a0c13db3f422b51b1a3d\n  darwin-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.2/bin/activate-gradle-mirrors-darwin-arm64\n    hash: sha256-e8bf9c6bba7aa713e0077a856e6780653f5735d89390c03df2431703e9e3a8db\n  linux-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.2/bin/activate-gradle-mirrors-linux-amd64\n    hash: sha256-d0482b3e772414f318b19b894c803d09e4878c6261d90c5fac4b0637c5e3e0e6\n  linux-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.2/bin/activate-gradle-mirrors-linux-arm64\n    hash: sha256-14e10b6776ef67515c38f8f217eb1d33e6eb66c0aaf3e4fc73b33260ec789d01\nproject_type_tags:\n- android\n- kotlin-multiplatform\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/0.1.3/step.yml",
    "content": "title: Activate Gradle Mirrors\nsummary: Activates Bitrise repository mirrors for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This step installs a Gradle init script that redirects repository requests to\n  Bitrise-hosted mirrors for faster, more reliable dependency resolution in\n  subsequent Gradle invocations.\n\n  The step is gated by the `BITRISE_MAVENCENTRAL_PROXY_ENABLED` environment\n  variable and only activates when run in a Bitrise datacenter that has a\n  mirror deployment. In every other case it logs an info message and exits\n  successfully.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\npublished_at: 2026-04-30T12:21:45.558967734Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors.git\n  commit: 09f80545433eb6fd05e80f1c464af8da8dd7e55c\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.3/bin/activate-gradle-mirrors-darwin-amd64\n    hash: sha256-8f07ec8b5b87d8ea42f160d74f174e214599e97c0d18a2466048f0658d1abf2f\n  darwin-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.3/bin/activate-gradle-mirrors-darwin-arm64\n    hash: sha256-03206f737a1b14f1ceb20bb3f88542a86bd75ca9156eaf9fb1a7dc1f70735caa\n  linux-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.3/bin/activate-gradle-mirrors-linux-amd64\n    hash: sha256-71af5b0313c5a36b1bf97b3f81ddf59fdbacfdfc0fecc51bfeaf4f43bafb1c4c\n  linux-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.3/bin/activate-gradle-mirrors-linux-arm64\n    hash: sha256-4d03646185a5369c62b331536c209463d5ce4c369ec9e2f3bb8849c2ed84e37f\nproject_type_tags:\n- android\n- kotlin-multiplatform\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/0.1.4/step.yml",
    "content": "title: Activate Gradle Mirrors\nsummary: Activates Bitrise repository mirrors for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This step installs a Gradle init script that redirects repository requests to\n  Bitrise-hosted mirrors for faster, more reliable dependency resolution in\n  subsequent Gradle invocations.\n\n  The step is gated by the `BITRISE_MAVENCENTRAL_PROXY_ENABLED` environment\n  variable and only activates when run in a Bitrise datacenter that has a\n  mirror deployment. In every other case it logs an info message and exits\n  successfully.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\npublished_at: 2026-04-30T15:57:56.529606051Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors.git\n  commit: 7d81db43fc5d41d176faab06497ea54e18805c67\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.4/bin/activate-gradle-mirrors-darwin-amd64\n    hash: sha256-888b9fa199649efa4f374ad8d1f03cb12080d896aa3a3ee2204f0fe47bc92491\n  darwin-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.4/bin/activate-gradle-mirrors-darwin-arm64\n    hash: sha256-7e908cd67d5ac7a1de4e67b61a56047b12337eb8965ad96867c66e4f129ebc02\n  linux-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.4/bin/activate-gradle-mirrors-linux-amd64\n    hash: sha256-b48f9084a617b4607a6ec3e1c75ac72edb8bc8263ea05d902e9979d1ffb9a6a4\n  linux-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.1.4/bin/activate-gradle-mirrors-linux-arm64\n    hash: sha256-b589792e599e3d53e64dc69eff530446ef63b8c67478f1d68ae8d20991bf42e5\nproject_type_tags:\n- android\n- kotlin-multiplatform\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/0.2.0/step.yml",
    "content": "title: Activate Gradle Mirrors\nsummary: Activates Bitrise repository mirrors for subsequent Gradle builds in the\n  workflow\ndescription: |\n  This step installs a Gradle init script that redirects repository requests to\n  Bitrise-hosted mirrors for faster, more reliable dependency resolution in\n  subsequent Gradle invocations.\n\n  The step is gated by the `BITRISE_MAVENCENTRAL_PROXY_ENABLED` environment\n  variable and only activates when run in a Bitrise datacenter that has a\n  mirror deployment. In every other case it logs an info message and exits\n  successfully.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\npublished_at: 2026-05-05T13:21:46.012673614Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors.git\n  commit: 212cee71bed8c302e1584c421f3103234547b47c\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.2.0/bin/activate-gradle-mirrors-darwin-amd64\n    hash: sha256-90b42d8a4c958f4195317668dded9078d0ed9f1df3975bc4e29194311693c5c4\n  darwin-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.2.0/bin/activate-gradle-mirrors-darwin-arm64\n    hash: sha256-7b7784c92fbac58c07f5d235c22f60fdc5192b0c444d48bac003f4000de4f8f8\n  linux-amd64:\n    storage_uri: steps/activate-gradle-mirrors/0.2.0/bin/activate-gradle-mirrors-linux-amd64\n    hash: sha256-d5f2275eab0ecde0d47a3da85c0926bf31ad9dfe79c734b6e8e731dc6004eab1\n  linux-arm64:\n    storage_uri: steps/activate-gradle-mirrors/0.2.0/bin/activate-gradle-mirrors-linux-arm64\n    hash: sha256-7f487edc1a4344c8e071a69c7f0b3137f1143e246f24bca065e7b44f69ebdd23\nproject_type_tags:\n- android\n- kotlin-multiplatform\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-activate-gradle-mirrors\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/activate-gradle-mirrors/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/activate-ssh-key/3.0.2/step.yml",
    "content": "title: Activate SSH key (RSA private key)\ndescription: |-\n  Saves the provided **RSA private SSH key** to file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The key should not have a passphrase** (should have an empty passphrase).\n\n  *Warning: the provided key will overwrite an existing key at\n  the provided path (if another key at the path already exists).*\n\n  It will start the ssh-agent if it can't connect to the agent.\nsummary: Setup the SSH Key to use with the current workflow\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2015-09-03T19:21:14.9231203+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: d4d437de5d7de7cdb4e25116c12fd0344a03923e\nhost_os_tags:\n- osx-10.9\nproject_type_tags:\n- ios\ntype_tags:\n- ssh\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other, previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-ssh-key/3.0.3/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: |-\n  Saves the provided **RSA private SSH key** to file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The key should not have a passphrase** (should have an empty passphrase).\n\n  *Warning: the provided key will overwrite an existing key at\n  the provided path (if another key at the path already exists).*\n\n  It will start the ssh-agent if it can't connect to the agent.\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2015-10-29T12:00:32.481457224+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: 5c42e6fe8642d8416faac742b0e137053f9ac9f3\nhost_os_tags:\n- osx-10.9\nproject_type_tags:\n- ios\ntype_tags:\n- ssh\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other, previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/activate-ssh-key/3.1.0/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: |-\n  Saves the provided **RSA private SSH key** to file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The key should not have a passphrase** (should have an empty passphrase).\n\n  *Warning: the provided key will overwrite an existing key at\n  the provided path (if another key at the path already exists).*\n\n  It will start the ssh-agent if it can't connect to the agent.\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2015-11-26T13:01:12.547208148+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: ca5c5aec19e237f2394e6a9fa2e9f625d15dd647\nhost_os_tags:\n- osx-10.9\nproject_type_tags:\n- ios\ntype_tags:\n- ssh\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other, previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled the no accessible\n      ssh-agent if found this Step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socker info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/3.1.1/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: |-\n  Saves the provided **RSA private SSH key** to file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The key should not have a passphrase** (should have an empty passphrase).\n\n  *Warning: the provided key will overwrite an existing key at\n  the provided path (if another key at the path already exists).*\n\n  It will start the ssh-agent if it can't connect to the agent.\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2016-08-01T12:03:18.249227437+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: ba111960d4ef6616a00c162195129e0134e410e6\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other, previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled the no accessible\n      ssh-agent if found this Step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.0.1/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: |-\n  Saves the provided **RSA private SSH key** to file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The key should not have a passphrase** (should have an empty passphrase).\n\n  *Warning: the provided key will overwrite an existing key at\n  the provided path (if another key at the path already exists).*\n\n  It will start the ssh-agent if it can't connect to the agent.\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2018-06-01T16:28:25.6312952+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: af23332f74c46f529a54cbdd546c93b70e92c3ae\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other, previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled the no accessible\n      ssh-agent if found this Step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.0.2/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: |-\n  Saves the provided **RSA private SSH key** to file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The key should not have a passphrase** (should have an empty passphrase).\n\n  *Warning: the provided key will overwrite an existing key at\n  the provided path (if another key at the path already exists).*\n\n  It will start the ssh-agent if it can't connect to the agent.\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2018-06-08T09:45:40.790981574+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: 6888940bf5c8dbae7f93f3782b5c8fb339319e16\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other, previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - true\n    - false\n  verbose: false\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled the no accessible\n      ssh-agent if found this Step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.0.3/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: |-\n  This step saves the provided **RSA private SSH key** to a file\n  and then loads it into the user's ssh-agent with `ssh-add`.\n\n  **The SSH key should not have a passphrase but an empty passphrase**.\n\n  *Warning: the provided key will overwrite an existing key at\n  the specified path (if another key at the path already exists).*\n\n  The step will start the ssh-agent if it can't connect to the agent.\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2018-08-22T09:43:08.222832748Z\nsource:\n  git: https://github.com/bitrise-io/steps-activate-ssh-key.git\n  commit: 29e73e8056a05ecf681ddac659afcfe9f3385a9e\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other or previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - true\n    - false\n  verbose: false\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled, and no accessible\n      ssh-agent is found, the step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.0.5/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: \"This Step makes sure Bitrise has access to your repository and thus\n  able to clone your code to our virtual machines. The Step saves the provided private\n  key of your SSH keypair to a file and then loads it into the user's ssh-agent with\n  `ssh-add`.\\n\\n### Configuring the Step\\n\\nBy default, you do not have to change\n  anything about the Step's configuration. All you need to do is make sure that you\n  registered your key pair on Bitrise and the public key at your Git provider. You\n  can generate and register an SSH keypair in two ways.\\n\\n- Automatically during\n  the [app creation process](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys).\\n-\n  Manually during the app creation process or at any other time. You [generate your\n  own SSH keys](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/) and\n  register them on Bitrise and at your Git provider. The SSH key should not have a\n  passphrase! \\n\\nOptionally, you can save the private key on the virtual machine.\n  If a key already exists on the path you specified in the **(Optional) path to save\n  the private key** input, it will be overwritten.\\n\\n### Troubleshooting\\n\\nIf the\n  Step fails, check the public key registered to your Git repository and compare it\n  to the public key registered on Bitrise. The most frequent issue is that someone\n  deleted or revoked the key on your Git provider's website.\\n\\nYou can also set the\n  **Enable verbose logging** input to `true`. This provides additional information\n  in the log.\\n\\n### Useful links\\n\\n[Setting up SSH keys](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys)\\n[How\n  can I generate an SSH key pair?](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/)\\n\\n###\n  Related Steps\\n\\n[Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2019-12-12T15:21:30.601101962Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-activate-ssh-key.git\n  commit: bf00bf4957c6e0a8e205da9f4601a15fc868144d\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other or previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: false\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled, and no accessible\n      ssh-agent is found, the step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.0.6/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: \"This Step makes sure Bitrise has access to your repository and thus\n  able to clone your code to our virtual machines. The Step saves the provided private\n  key of your SSH keypair to a file and then loads it into the user's ssh-agent with\n  `ssh-add`.\\n\\n### Configuring the Step\\n\\nBy default, you do not have to change\n  anything about the Step's configuration. All you need to do is make sure that you\n  registered your key pair on Bitrise and the public key at your Git provider. You\n  can generate and register an SSH keypair in two ways.\\n\\n- Automatically during\n  the [app creation process](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys).\\n-\n  Manually during the app creation process or at any other time. You [generate your\n  own SSH keys](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/) and\n  register them on Bitrise and at your Git provider. The SSH key should not have a\n  passphrase! \\n\\nOptionally, you can save the private key on the virtual machine.\n  If a key already exists on the path you specified in the **(Optional) path to save\n  the private key** input, it will be overwritten.\\n\\n### Troubleshooting\\n\\nIf the\n  Step fails, check the public key registered to your Git repository and compare it\n  to the public key registered on Bitrise. The most frequent issue is that someone\n  deleted or revoked the key on your Git provider's website.\\n\\nYou can also set the\n  **Enable verbose logging** input to `true`. This provides additional information\n  in the log.\\n\\n### Useful links\\n\\n- [Setting up SSH keys](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys)\\n-\n  [How can I generate an SSH key pair?](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/)\\n\\n###\n  Related Steps\\n\\n- [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2021-05-05T14:19:45.125786875Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-activate-ssh-key.git\n  commit: 17c9d33e3da625774824f1ab1942569b59fcd6dd\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other or previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: false\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled, and no accessible\n      ssh-agent is found, the step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.1.0/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Setup the SSH Key to use with the current workflow\ndescription: \"This Step makes sure Bitrise has access to your repository and thus\n  able to clone your code to our virtual machines. The Step saves the provided private\n  key of your SSH keypair to a file and then loads it into the user's ssh-agent with\n  `ssh-add`.\\n\\n### Configuring the Step\\n\\nBy default, you do not have to change\n  anything about the Step's configuration. All you need to do is make sure that you\n  registered your key pair on Bitrise and the public key at your Git provider. You\n  can generate and register an SSH keypair in two ways.\\n\\n- Automatically during\n  the [app creation process](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys).\\n-\n  Manually during the app creation process or at any other time. You [generate your\n  own SSH keys](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/) and\n  register them on Bitrise and at your Git provider. The SSH key should not have a\n  passphrase! \\n\\nOptionally, you can save the private key on the virtual machine.\n  If a key already exists on the path you specified in the **(Optional) path to save\n  the private key** input, it will be overwritten.\\n\\n### Troubleshooting\\n\\nIf the\n  Step fails, check the public key registered to your Git repository and compare it\n  to the public key registered on Bitrise. The most frequent issue is that someone\n  deleted or revoked the key on your Git provider's website.\\n\\nYou can also set the\n  **Enable verbose logging** input to `true`. This provides additional information\n  in the log.\\n\\n### Useful links\\n\\n- [Setting up SSH keys](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys)\\n-\n  [How can I generate an SSH key pair?](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/)\\n\\n###\n  Related Steps\\n\\n- [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-io/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-io/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-io/steps-activate-ssh-key/issues\npublished_at: 2021-08-25T12:38:21.03700457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-activate-ssh-key.git\n  commit: 9f0fc00b7a2483a283c0d82106d6816638ac7d41\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    title: (Optional) path to save the private key.\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      (Optional) Remove other or previously loaded keys and restart ssh-agent?\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_dont_change_value: true\n    is_expand: false\n    title: Remove other identities?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: false\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled, and no accessible\n      ssh-agent is found, the step will start a new ssh-agent.\n\n      This output environment variable will contain the path of the\n      SSH Auth Socket, which can be used to access the started ssh-agent.\n    title: SSH Auth Socket info, in case the ssh-agent was started by this step\n"
  },
  {
    "path": "steps/activate-ssh-key/4.1.1/step.yml",
    "content": "title: Activate SSH key (RSA private key)\nsummary: Add your SSH key to the build machine to access private repositories\ndescription: |-\n  This Step makes sure Bitrise has access to your repository when cloning SSH URLs. The Step saves the provided private key of your SSH keypair to a file and then loads it into the SSH agent.\n\n  ### Configuring the Step\n\n  By default, you do not have to change anything about the Step's configuration.\n\n  The step downloads the SSH key defined in your App Settings, so most of the time it's the only thing you need to configure ([more info](https://devcenter.bitrise.io/en/connectivity/configuring-ssh-keys).\n\n   All you need to do is make sure that you registered your key pair on Bitrise and the public key at your Git provider. You can generate and register an SSH keypair in two ways.\n\n  - Automatically during the [app creation process](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys).\n  - Manually during the app creation process or at any other time. You [generate your own SSH keys](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/) and register them on Bitrise and at your Git provider. The SSH key should not have a passphrase!\n\n  Note: if you configure to use HTTPS instead of SSH git access, you don't need to use this Step.\n\n  ### Troubleshooting\n\n  If the Step fails, check the public key registered to your Git repository and compare it to the public key registered on Bitrise. The most frequent issue is that someone deleted or revoked the key on your Git provider's website.\n\n  You can also set the **Enable verbose logging** input to `true`. This provides additional information in the log.\n\n  ### Useful links\n\n  - [Setting up SSH keys](https://devcenter.bitrise.io/getting-started/adding-a-new-app/#setting-up-ssh-keys)\n  - [How can I generate an SSH key pair?](https://devcenter.bitrise.io/faq/how-to-generate-ssh-keypair/)\n\n  ### Related Steps\n\n  - [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\nwebsite: https://github.com/bitrise-steplib/steps-activate-ssh-key\nsource_code_url: https://github.com/bitrise-steplib/steps-activate-ssh-key\nsupport_url: https://github.com/bitrise-steplib/steps-activate-ssh-key/issues\npublished_at: 2024-02-15T10:28:29.203495657Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-activate-ssh-key.git\n  commit: 78dae4ddaa4a2c3eddb35a3fc620b5fdf29fc82c\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-activate-ssh-key\ndeps:\n  apt_get:\n  - name: expect\n  - name: git\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: The private key of the SSH keypair in RSA format.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key content\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Path where the private key should be saved\n    is_dont_change_value: true\n    is_expand: true\n    title: SSH key save path\n  ssh_key_save_path: $HOME/.ssh/bitrise_step_activate_ssh_key\n- is_remove_other_identities: \"true\"\n  opts:\n    description: |-\n      When the step detects a running SSH agent and this input is true, it removes all loaded identities and restarts the agent before loading the configured key.\n\n      When there is no running SSH agent, this input has no effect.\n\n      Note: this only affects the in-memory SSH agent data, keys on disk are not touched.\n\n      Options:\n\n      * \"true\"\n      * \"false\"\n    is_expand: false\n    title: Remove other identities from SSH agent\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- SSH_AUTH_SOCK: null\n  opts:\n    description: |-\n      If the `is_should_start_new_agent` option is enabled, and no accessible ssh-agent is found, the step will start a new ssh-agent.\n\n      This output contains the path of the socket created by ssh-agent, which can be used to access the started ssh-agent ([learn more](https://www.man7.org/linux/man-pages/man1/ssh-agent.1.html))\n    title: SSH agent socket path\n"
  },
  {
    "path": "steps/activate-ssh-key/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/add-trace-sdk/1.0.1/step.yml",
    "content": "title: Add Trace SDK\nsummary: Add the Trace SDK during the Xcode build process.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\nAndroid:\\n  TBA.\\n  \\nOnce the\n  app has been deployed, developers can view the results of the app in the Trace addon.\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2020-07-14T13:41:09.21052+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: e01ae342db229d45eaa93cff53bc205b1bed3b54\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app.\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.0.3/step.yml",
    "content": "title: Add Trace SDK\nsummary: Add the Trace SDK during the Xcode build process.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\nAndroid:\\n  TBA.\\n  \\nOnce the\n  app has been deployed, developers can view the results of the app in the Trace addon.\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2020-07-24T13:36:50.662578+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 4bfdd2381519881fc9dde40961df68b0a7131653\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app.\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.0.4/step.yml",
    "content": "title: Add Trace SDK\nsummary: Add the Trace SDK during the Xcode build process.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\nAndroid:\\n  TBA.\\n  \\nOnce the\n  app has been deployed, developers can view the results of the app in the Trace addon.\\n\\nTrace:\n  https://trace.bitrise.io\\nWhat's Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting\n  started guide: https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2020-08-14T10:11:06.110439+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 0889135a9fb9ef1fc6d87cdaf7b736c77e8d9026\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app.\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.1.0/step.yml",
    "content": "title: Add Trace SDK\nsummary: Add the Trace SDK during the Xcode build process.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\nAndroid:\\n  TBA.\\n  \\nOnce the\n  app has been deployed, developers can view the results of the app in the Trace addon.\\n\\nTrace:\n  https://trace.bitrise.io\\nWhat's Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting\n  started guide: https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2020-10-28T09:59:12.765071Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 8438a8de7a3be903dcadf9b8d7d396d858809d37\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: \"The version of the Bitrise Trace SDK to link into the app. \\n\\nList\n      of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\"\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app.\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.1.1/step.yml",
    "content": "title: Add Trace SDK\nsummary: Add the Trace SDK during the Xcode build process.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\n  Supported stack: Xcode 11 and\n  12\\n\\nAndroid:\\n  TBA.\\n  \\nOnce the app has been deployed, developers can view\n  the results of the app in the Trace addon.\\n\\nTrace: https://trace.bitrise.io\\nWhat's\n  Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting started guide:\n  https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2020-11-03T14:23:51.16195Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 11578ad77bc1a70c1649bfeab1d8a85108f43ff3\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: \"The version of the Bitrise Trace SDK to link into the app. \\n\\nList\n      of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\"\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app.\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.2.1/step.yml",
    "content": "title: Add Trace SDK\nsummary: Add the Trace SDK during the Xcode build process.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\n  Supported stack: Xcode 11 and\n  12\\n\\nAndroid:\\n  TBA.\\n  \\nOnce the app has been deployed, developers can view\n  the results of the app in the Trace addon.\\n\\nTrace: https://trace.bitrise.io\\nWhat's\n  Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting started guide:\n  https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2020-11-19T10:07:48.32947Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 2c53c4257c59637f6a846346ec86e628ca92bc3a\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app. Use `latest` to always download the most recent stable release.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app. See more https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.2.2/step.yml",
    "content": "title: Add Trace SDK\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\n  Supported stack: Xcode 11 and\n  12\\n\\nAndroid:\\nFor Android, please find the details below.\\n**Source for Android\n  step:**\\n[https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android](https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android)\\n\\n\n  \\ \\nOnce the app has been deployed, developers can view the results of the app in\n  the Trace addon.\\n\\nTrace: https://trace.bitrise.io\\nWhat's Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting\n  started guide: https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2021-02-08T12:30:46.172739Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 7fd0a48ded1ba7af2c5286d5c3f835c28e613002\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app. Use `latest` to always download the most recent stable release.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app. See more https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.2.3/step.yml",
    "content": "title: Add Trace SDK\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\n  Supported stack: Xcode 11 and\n  12\\n\\nAndroid:\\nFor Android, please find the details below.\\n**Source for Android\n  step:**\\n[https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android](https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android)\\n\\n\n  \\ \\nOnce the app has been deployed, developers can view the results of the app in\n  the Trace addon.\\n\\nTrace: https://trace.bitrise.io\\nWhat's Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting\n  started guide: https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2021-03-19T16:49:24.874462Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: 5406d6337b2a7ab727b3fa8c9e1ec75503729e68\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path. Must be a relative path\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app. Use `latest` to always download the most recent stable release.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app. See more https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/1.2.4/step.yml",
    "content": "title: Add Trace SDK iOS\nsummary: |\n  ** Add the Trace SDK before the build process **\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: \"Adds the Trace SDK static library during the Xcode build process into\n  the resulting app artifact.\\n\\niOS:\\n  The step works by linking and modifying the\n  relevant Xcode project descriptor files to include necessary configurations in `other\n  linker flags`. These are the following:\\n    - Trace static library path\\n    -\n  System libraries: `C` and `C++` \\n    - System Framework `SystemConfiguration.framework`\\n\n  \\ \\n  System libraries and frameworks are linked if they are not present. It’s recommended\n  to add this step just before the Xcode build and archive step. \\n  This step is\n  compatible with all Xcode projects that use Swift only, interoperability (mixed)\n  and Objective-C only languages. \\n\\n  Source code for the iOS SDK can be found here:\n  https://github.com/bitrise-io/trace-cocoa-sdk\\n\\n  Supported stack: Xcode 11 and\n  12\\n\\nAndroid:\\nFor Android, please find the details below.\\n**Source for Android\n  step:**\\n[https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android](https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android)\\n\\n\n  \\ \\nOnce the app has been deployed, developers can view the results of the app in\n  the Trace addon.\\n\\nTrace: https://trace.bitrise.io\\nWhat's Trace? https://www.bitrise.io/add-ons/trace-mobile-monitoring\\nGetting\n  started guide: https://trace.bitrise.io/o/getting-started\\n\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk/issues\npublished_at: 2021-05-12T10:07:10.552605+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk.git\n  commit: f9da3d25560d7f393dbc1d8c662787e463e86d71\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nis_requires_admin_user: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path. Must be a relative path\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use. For Apple related platforms only\n    is_required: true\n    summary: The Scheme to use. For Apple related platforms only\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- lib_version: latest\n  opts:\n    description: |-\n      The version of the Bitrise Trace SDK to link into the app. Use `latest` to always download the most recent stable release.\n\n      List of available releases for Apple related platforms: https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    is_required: true\n    summary: The version of the Bitrise Trace SDK to link into the app. See more https://github.com/bitrise-io/trace-cocoa-sdk/releases\n    title: Library version\n"
  },
  {
    "path": "steps/add-trace-sdk/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2022-08-26\"\ndeprecate_notes: |\n  This step is deprecated as it is not supported anymore.\n"
  },
  {
    "path": "steps/add-trace-sdk-android/0.0.1/step.yml",
    "content": "title: Add Trace SDK Android\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: |\n  # Overview\n\n  Ensures that Trace is added to a given Android application project. Adds the required\n  dependency (trace-sdk) and applies plugin (trace-gradle-plugin) if the project not already have them.\n  This step is needed, when you have not added Trace manually to your project. For manual\n  installation see the documentation below.\n\n  **Use this step before your application is built/assembled with Gradle**\n\n  For the known limitations of trace-android-sdk please see the\n  [README.md](https://github.com/bitrise-io/trace-android-sdk/blob/main/README.md) file.\n\n  # Documentation\n\n  www.bitrise.io:\n  [https://devcenter.bitrise.io/monitoring/getting-started-with-trace/](https://devcenter.bitrise.io/monitoring/getting-started-with-trace/)\n\n  # About Trace\n\n  **Trace:** [https://trace.bitrise.io](https://trace.bitrise.io)\n\n  **What's Trace?** [https://www.bitrise.io/add-ons/trace-mobile-monitoring](https://www.bitrise.io/add-ons/trace-mobile-monitoring)\n\n  **Getting started guide:** [https://trace.bitrise.io/o/getting-started](https://trace.bitrise.io/o/getting-started)\n\n  # iOS\n\n  **For iOS, please check this step:**\n  [https://www.bitrise.io/integrations/steps/add-trace-sdk](https://www.bitrise.io/integrations/steps/add-trace-sdk)\n\n  **Source for iOS step:**\n  [https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk](https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk)\nwebsite: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsource_code_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsupport_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android/issues\npublished_at: 2021-02-03T12:48:18.987844+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android.git\n  commit: a7bcb1a899bb054915bf3692385bf3a113287737\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-add-trace-sdk-android\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path for the root project. By default it will be the source directory, but in some cases (for example if you\n      have a monorepo) you may want to specify which directory should be used for this step.\n\n      Example: $BITRISE_SOURCE_DIR/myproject1/\n    is_required: true\n    summary: Path of the root project\n    title: Path of the root project\n  project_path: $BITRISE_SOURCE_DIR\n- gradle_options: null\n  opts:\n    description: |\n      Step uses a Gradle task called \"injectTrace\" to add the required dependencies to the project. Also uses\n      \"verifyTrace\" to verify Trace has been applied successfully to the project. For debugging\n      purposes you may want to add additional flags to them, it would display useful information\n      if you have any issue with the step.\n\n      Examples: \"--stactrace\", \"--info\" or \"--debug\" (without the quote marks).\n\n      Note: Multiple entries should be separated with a whitespace character.\n\n      Example: \"--stacktrace --info\" (without the quote marks).\n    is_required: false\n    summary: Additional task options for \"injectTrace\" and \"verifyTrace\" tasks\n    title: Gradle Task Options\n"
  },
  {
    "path": "steps/add-trace-sdk-android/0.0.2/step.yml",
    "content": "title: Add Trace SDK Android\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: |\n  # Overview\n\n  Ensures that Trace is added to a given Android application project. Adds the required\n  dependency (trace-sdk) and applies plugin (trace-gradle-plugin) if the project not already have them.\n  This step is needed, when you have not added Trace manually to your project. For manual\n  installation see the documentation below.\n\n  **Use this step before your application is built/assembled with Gradle**\n\n  For the known limitations of trace-android-sdk please see the\n  [README.md](https://github.com/bitrise-io/trace-android-sdk/blob/main/README.md) file.\n\n  # Documentation\n\n  www.bitrise.io:\n  [https://devcenter.bitrise.io/monitoring/getting-started-with-trace/](https://devcenter.bitrise.io/monitoring/getting-started-with-trace/)\n\n  # About Trace\n\n  **Trace:** [https://trace.bitrise.io](https://trace.bitrise.io)\n\n  **What's Trace?** [https://www.bitrise.io/add-ons/trace-mobile-monitoring](https://www.bitrise.io/add-ons/trace-mobile-monitoring)\n\n  **Getting started guide:** [https://trace.bitrise.io/o/getting-started](https://trace.bitrise.io/o/getting-started)\n\n  # iOS\n\n  **For iOS, please check this step:**\n  [https://www.bitrise.io/integrations/steps/add-trace-sdk](https://www.bitrise.io/integrations/steps/add-trace-sdk)\n\n  **Source for iOS step:**\n  [https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk](https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk)\nwebsite: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsource_code_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsupport_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android/issues\npublished_at: 2021-02-08T14:13:07.022897+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android.git\n  commit: 4ab403a6ad3b605f54fc3b41706af1f2bbc993ef\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-add-trace-sdk-android\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path for the root project. By default it will be the source directory, but in some cases (for example if you\n      have a monorepo) you may want to specify which directory should be used for this step.\n\n      Example: $BITRISE_SOURCE_DIR/myproject1/\n    is_required: true\n    summary: Path of the root project\n    title: Path of the root project\n  project_path: $BITRISE_SOURCE_DIR\n- gradle_options: null\n  opts:\n    description: |\n      Step uses a Gradle task called \"injectTrace\" to add the required dependencies to the project. Also uses\n      \"verifyTrace\" to verify Trace has been applied successfully to the project. For debugging\n      purposes you may want to add additional flags to them, it would display useful information\n      if you have any issue with the step.\n\n      Examples: \"--stactrace\", \"--info\" or \"--debug\" (without the quote marks).\n\n      Note: Multiple entries should be separated with a whitespace character.\n\n      Example: \"--stacktrace --info\" (without the quote marks).\n    is_required: false\n    summary: Additional task options for \"injectTrace\" and \"verifyTrace\" tasks\n    title: Gradle Task Options\n"
  },
  {
    "path": "steps/add-trace-sdk-android/0.0.3/step.yml",
    "content": "title: Add Trace SDK Android\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: |\n  # Overview\n\n  Ensures that Trace is added to a given Android application project. Adds the required\n  dependency (trace-sdk) and applies plugin (trace-gradle-plugin) if the project not already have them.\n  This step is needed, when you have not added Trace manually to your project. For manual\n  installation see the documentation below.\n\n  **Use this step before your application is built/assembled with Gradle**\n\n  # Documentation\n\n  www.bitrise.io:\n  [https://devcenter.bitrise.io/monitoring/getting-started-with-trace/](https://devcenter.bitrise.io/monitoring/getting-started-with-trace/)\n\n  # About Trace\n\n  **Trace:** [https://trace.bitrise.io](https://trace.bitrise.io)\n\n  **What's Trace?** [https://www.bitrise.io/add-ons/trace-mobile-monitoring](https://www.bitrise.io/add-ons/trace-mobile-monitoring)\n\n  **Getting started guide:** [https://trace.bitrise.io/o/getting-started](https://trace.bitrise.io/o/getting-started)\n\n  # iOS\n\n  **For iOS, please check this step:**\n  [https://www.bitrise.io/integrations/steps/add-trace-sdk](https://www.bitrise.io/integrations/steps/add-trace-sdk)\n\n  **Source for iOS step:**\n  [https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk](https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk)\nwebsite: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsource_code_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsupport_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android/issues\npublished_at: 2021-02-10T17:38:34.717958+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android.git\n  commit: 64d26a3304df849f06e49e8d16eb0388d094280e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path for the root project. By default it will be the source directory, but in some cases (for example if you\n      have a monorepo) you may want to specify which directory should be used for this step.\n\n      Example: $BITRISE_SOURCE_DIR/myproject1/\n    is_required: true\n    summary: Path of the root project\n    title: Path of the root project\n  project_path: $BITRISE_SOURCE_DIR\n- gradle_options: null\n  opts:\n    description: |\n      Step uses a Gradle task called \"injectTrace\" to add the required dependencies to the project. Also uses\n      \"verifyTrace\" to verify Trace has been applied successfully to the project. For debugging\n      purposes you may want to add additional flags to them, it would display useful information\n      if you have any issue with the step.\n\n      Examples: \"--stactrace\", \"--info\" or \"--debug\" (without the quote marks).\n\n      Note: Multiple entries should be separated with a whitespace character.\n\n      Example: \"--stacktrace --info\" (without the quote marks).\n    is_required: false\n    summary: Additional task options for \"injectTrace\" and \"verifyTrace\" tasks\n    title: Gradle Task Options\n"
  },
  {
    "path": "steps/add-trace-sdk-android/0.0.4/step.yml",
    "content": "title: Add Trace SDK Android\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: |\n  # Overview\n\n  Ensures that Trace is added to a given Android application project. Adds the required\n  dependency (trace-sdk) and applies the plugin (trace-gradle-plugin) if the project does not already have them.\n  This step is needed, when you have not added Trace manually to your project. For manual\n  installation see the documentation below.\n\n  **Use this step before your application is built/assembled with Gradle**\n\n  # Documentation\n\n  www.bitrise.io:\n  [https://devcenter.bitrise.io/monitoring/getting-started-with-trace/](https://devcenter.bitrise.io/monitoring/getting-started-with-trace/)\n\n  # About Trace\n\n  **Trace:** [https://trace.bitrise.io](https://trace.bitrise.io)\n\n  **What's Trace?** [https://www.bitrise.io/add-ons/trace-mobile-monitoring](https://www.bitrise.io/add-ons/trace-mobile-monitoring)\n\n  **Getting started guide:** [https://trace.bitrise.io/o/getting-started](https://trace.bitrise.io/o/getting-started)\n\n  # iOS\n\n  **For iOS, please check this step:**\n  [https://www.bitrise.io/integrations/steps/add-trace-sdk](https://www.bitrise.io/integrations/steps/add-trace-sdk)\n\n  **Source for iOS step:**\n  [https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk](https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk)\nwebsite: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsource_code_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsupport_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android/issues\npublished_at: 2021-02-15T17:29:47.194001+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android.git\n  commit: 0b52859a2278551857aa72c116b46323fd7d838a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path for the root project. By default it will be the source directory, but in some cases (for example if you\n      have a monorepo) you may want to specify which directory should be used for this step.\n\n      Example: $BITRISE_SOURCE_DIR/monorepo/myproject1/\n    is_required: true\n    summary: Path of the root project\n    title: Path of the root project\n  project_path: $BITRISE_SOURCE_DIR/\n- gradle_options: null\n  opts:\n    description: |\n      Step uses a Gradle task called \"injectTrace\" to add the required dependencies to the project. Also uses\n      \"verifyTrace\" to verify Trace has been applied successfully to the project. For debugging\n      purposes you may want to add additional flags to them, it would display useful information\n      if you have any issue with the step.\n\n      Examples: \"--stactrace\", \"--info\" or \"--debug\" (without the quote marks).\n\n      Note: Multiple entries should be separated with a whitespace character.\n\n      Example: \"--stacktrace --info\" (without the quote marks).\n    is_required: false\n    summary: Additional task options for \"injectTrace\" and \"verifyTrace\" tasks\n    title: Gradle Task Options\n"
  },
  {
    "path": "steps/add-trace-sdk-android/0.0.5/step.yml",
    "content": "title: Add Trace SDK Android\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: |\n  # Overview\n\n  Ensures that Trace is added to a given Android application project. Adds the required\n  dependency (trace-sdk) and applies the plugin (trace-gradle-plugin) if the project does not already have them.\n  This step is needed, when you have not added Trace manually to your project. For manual\n  installation see the documentation below.\n\n  **Use this step before your application is built/assembled with Gradle**\n\n  # Documentation\n\n  www.bitrise.io:\n  [https://devcenter.bitrise.io/monitoring/getting-started-with-trace/](https://devcenter.bitrise.io/monitoring/getting-started-with-trace/)\n\n  # About Trace\n\n  **Trace:** [https://trace.bitrise.io](https://trace.bitrise.io)\n\n  **What's Trace?** [https://www.bitrise.io/add-ons/trace-mobile-monitoring](https://www.bitrise.io/add-ons/trace-mobile-monitoring)\n\n  **Getting started guide:** [https://trace.bitrise.io/o/getting-started](https://trace.bitrise.io/o/getting-started)\n\n  # iOS\n\n  **For iOS, please check this step:**\n  [https://www.bitrise.io/integrations/steps/add-trace-sdk](https://www.bitrise.io/integrations/steps/add-trace-sdk)\n\n  **Source for iOS step:**\n  [https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk](https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk)\nwebsite: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsource_code_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsupport_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android/issues\npublished_at: 2021-02-19T16:44:23.206359+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android.git\n  commit: 55f50b04a189b351cce7bc2d87bf4f359a0542d0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path for the root project. By default it will be the source directory, but in some cases (for example if you\n      have a monorepo) you may want to specify which directory should be used for this step.\n\n      Example: $BITRISE_SOURCE_DIR/monorepo/myproject1/\n    is_required: true\n    summary: Path of the root project\n    title: Path of the root project\n  project_path: $BITRISE_SOURCE_DIR/\n- gradle_options: null\n  opts:\n    description: |\n      Step uses a Gradle task called \"injectTrace\" to add the required dependencies to the project. Also uses\n      \"verifyTrace\" to verify Trace has been applied successfully to the project. For debugging\n      purposes you may want to add additional flags to them, it would display useful information\n      if you have any issue with the step.\n\n      Examples: \"--stactrace\", \"--info\" or \"--debug\" (without the quote marks).\n\n      Note: Multiple entries should be separated with a whitespace character.\n\n      Example: \"--stacktrace --info\" (without the quote marks).\n    is_required: false\n    summary: Additional task options for \"injectTrace\" and \"verifyTrace\" tasks\n    title: Gradle Task Options\n"
  },
  {
    "path": "steps/add-trace-sdk-android/0.1.0/step.yml",
    "content": "title: Add Trace SDK Android\nsummary: |\n  Add the Trace SDK before the build process\n\n  Important: Please read the Trace license terms in the SDK. By clicking here to add the Trace SDK, you are agreeing to those license terms.\ndescription: |\n  # Overview\n\n  Ensures that Trace is added to a given Android application project. Adds the required\n  dependency (trace-sdk) and applies the plugin (trace-gradle-plugin) if the project does not already have them.\n  This step is needed, when you have not added Trace manually to your project. For manual\n  installation see the documentation below.\n\n  **Use this step before your application is built/assembled with Gradle**\n\n  # Documentation\n\n  www.bitrise.io:\n  [https://devcenter.bitrise.io/monitoring/getting-started-with-trace/](https://devcenter.bitrise.io/monitoring/getting-started-with-trace/)\n\n  # About Trace\n\n  **Trace:** [https://trace.bitrise.io](https://trace.bitrise.io)\n\n  **What's Trace?** [https://www.bitrise.io/add-ons/trace-mobile-monitoring](https://www.bitrise.io/add-ons/trace-mobile-monitoring)\n\n  **Getting started guide:** [https://trace.bitrise.io/o/getting-started](https://trace.bitrise.io/o/getting-started)\n\n  # iOS\n\n  **For iOS, please check this step:**\n  [https://www.bitrise.io/integrations/steps/add-trace-sdk](https://www.bitrise.io/integrations/steps/add-trace-sdk)\n\n  **Source for iOS step:**\n  [https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk](https://github.com/bitrise-steplib/bitrise-step-add-trace-sdk)\nwebsite: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsource_code_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nsupport_url: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android/issues\npublished_at: 2021-04-16T14:25:34.46134+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-add-trace-sdk-android.git\n  commit: df0416a92023ffc1375f677c8b0ed364122b9acd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-add-trace-sdk-android\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path for the root project. By default it will be the source directory, but in some cases (for example if you\n      have a monorepo) you may want to specify which directory should be used for this step.\n\n      Example: $BITRISE_SOURCE_DIR/monorepo/myproject1/\n    is_required: true\n    summary: Path of the root project\n    title: Path of the root project\n  project_location: $BITRISE_SOURCE_DIR/\n- gradle_options: null\n  opts:\n    description: |\n      Step uses a Gradle task called \"injectTrace\" to add the required dependencies to the project. Also uses\n      \"verifyTrace\" to verify Trace has been applied successfully to the project. For debugging\n      purposes you may want to add additional flags to them, it would display useful information\n      if you have any issue with the step.\n\n      Examples: \"--stactrace\", \"--info\" or \"--debug\" (without the quote marks).\n\n      Note: Multiple entries should be separated with a whitespace character.\n\n      Example: \"--stacktrace --info\" (without the quote marks).\n    is_required: false\n    summary: Additional task options for \"injectTrace\" and \"verifyTrace\" tasks\n    title: Gradle Task Options\n"
  },
  {
    "path": "steps/add-trace-sdk-android/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2022-08-26\"\ndeprecate_notes: |\n  This step is deprecated as it is not supported anymore.\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.0.0/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2015-09-08T16:23:32.708148287+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 763999cd449f8d6817aafee5bd801895cb02e72a\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndependencies:\n- manager: brew\n  name: s3cmd\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_{app_slug}/{timestamp}_build_{build_slug}\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: \"\"\n- file_access_level: public_read\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.1.0/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2015-09-10T18:25:13.570266771+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: be125d5884ec40dce334ca155638f28a08d92169\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndependencies:\n- manager: brew\n  name: s3cmd\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_{app_slug}/{timestamp}_build_{build_slug}\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: \"\"\n- file_access_level: public_read\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.1.1/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2015-09-16T14:34:42.580482787+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: a3953cf444dbffb5fcf632d8cbbdf691585115b0\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndependencies:\n- manager: brew\n  name: s3cmd\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_{app_slug}/{timestamp}_build_{build_slug}\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: \"\"\n- file_access_level: public_read\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.2.0/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2015-10-20T12:49:19.364436458+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 0695e6a76c1a9e16ee7e3b6e98830b20109410cd\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndependencies:\n- manager: brew\n  name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_{app_slug}/{timestamp}_build_{build_slug}\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: \"\"\n- file_access_level: public_read\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.3.0/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2016-02-01T18:16:16.364194171+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: b0310698ca843b615c0f7fd1bcbc61ac33f43914\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_{app_slug}/{timestamp}_build_{build_slug}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: \"\"\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.4.0/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2016-02-15T14:13:54.589441417+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 85848a6fb73d328ce863e046ba1daef5f7e451eb\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_{app_slug}/{timestamp}_build_{build_slug}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: \"\"\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.0/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2016-03-09T16:38:47.576889058+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 53dd110f68976b23e1444354b665f91b96aa54f6\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- amazon\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.1/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2016-11-16T14:11:18.462804153+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: e5acd8b6e6ba8334740e2bec898891aad14fcb24\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.3/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: !!timestamp 2018-04-04T14:29:44.045971011+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 57dec28be8c19bc1dff8ba11f4764fda8bbb21a0\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.4/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: |-\n  Bitrise Step to Deploy an Xcode archive to Amazon S3.\n  Required: an Xcode Archive Step should run before this Step!\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2018-04-16T11:40:14.580837653+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 2f6ab262e0595a6bc2b4dcb6a4b343ae560e4887\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.6/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: \"This step deploys an Xcode archive to Amazon S3.\\nRequirements: An Xcode\n  Archive Step must run before this step and you must have an Amazon S3 account. \\nTo\n  register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\"\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2018-08-31T12:41:26.107542729Z\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: e67bc1a7a87199e78771a90e31e90b1a0e7ea983\nproject_type_tags:\n- ios\n- react-native\n- xamarin\n- cordova\n- ionic\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if there is no specified value, then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, for example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.7/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: \"This step deploys an Xcode archive to Amazon S3.\\nRequirements: An Xcode\n  Archive Step must run before this step and you must have an Amazon S3 account. \\nTo\n  register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\"\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2018-09-13T09:16:07.117061453Z\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-deploy.git\n  commit: 1561f7d7a99a730dba8aa4357cf87ff8a00b2e2f\nproject_type_tags:\n- ios\n- react-native\n- xamarin\n- cordova\n- ionic\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if there is no specified value, then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, for example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.8/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Upload your iOS Application to Amazon S3\ndescription: \"This step deploys an Xcode archive to Amazon S3.\\nRequirements: An Xcode\n  Archive Step must run before this step and you must have an Amazon S3 account. \\nTo\n  register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\"\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2019-10-15T09:12:50.778245022Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-amazon-s3-deploy.git\n  commit: 6065f531dfa1cccbd9cd08c13ff529e608515b3b\nproject_type_tags:\n- ios\n- react-native\n- xamarin\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if there is no specified value, then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, for example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/3.5.9/step.yml",
    "content": "title: Deploy to Amazon S3\nsummary: Uploads your iOS application to Amazon S3.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-amazon-s3-deploy) deploys an Xcode archive to [Amazon S3](https://aws.amazon.com/s3/).\n\n  ### Configuring the Step\n\n  Before you start:\n  - To deploy to S3 with this Step, you must have an Amazon S3 account with your credentials at hand. If you don't have one yet, go ahead and [create one](https://aws.amazon.com/s3/).\n\n  1. Add the **IPA path** in the respective field.\n  2. You can optionally add the **DSYM path** (debug symbols file) too.\n  3. The **BITRISE's App-Slug variable** and the **BITRISE's Build-Slug variable** are passed automatically on Bitrise.\n  5. Add the **Amazon AWS Access Key** and the **Amazon AWS Secret Access Key**. These were created [when you signed up for an AWS account](https://docs.aws.amazon.com/powershell/latest/userguide/pstools-appendix-sign-up.html). If you don't have these keys, you can create them through the [IAM console](https://signin.aws.amazon.com/signin?redirect_uri=https%3A%2F%2Fconsole.aws.amazon.com%2Fiam%2F%3Fstate%3DhashArgs%2523%26isauthcode%3Dtrue&client_id=arn%3Aaws%3Aiam%3A%3A015428540659%3Auser%2Fiam&forceMobileApp=0&code_challenge=Dm2ZFAI7S6azuYUUgSfUmQygOH0QNANyPFzDZ6FHeSc&code_challenge_method=SHA-256).\n  6. Add the **Amazon S3 Bucket Name**.\n  7. Add the **Amazon S3 Bucket Region** which you [specified when creating a bucket in AWS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingBucket.html). If you use the default s3 region (us-east-1), you can leave this field empty.\n  8. Add the **Amazon S3 File Path in Bucket** which is the URL of the bucket.\n  9. Select the **Amazon S3 file access level** which can be `public_read` or `private`.\n\n  ### Useful links\n  - [Deploying an iOS app](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n  - [Code signing an iOS app](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision with App Store Connect API](https://www.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  - [Amazon S3 Bucket Sync](https://www.bitrise.io/integrations/steps/amazon-s3-upload)\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-deploy\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-deploy/issues\npublished_at: 2021-06-25T08:12:03.089103471Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-amazon-s3-deploy.git\n  commit: 910a47002bb3944bd081df7cd456a0c9d953cbdf\nproject_type_tags:\n- ios\n- react-native\n- xamarin\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: DSYM path (optional)\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if there is no specified value, then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_DEPLOY_STEP_URL_IPA: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy IPA URL\n- S3_DEPLOY_STEP_URL_DSYM: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy DSYM URL\n- S3_DEPLOY_STEP_URL_PLIST: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n- S3_DEPLOY_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n- S3_DEPLOY_STEP_EMAIL_READY_URL: \"\"\n  opts:\n    description: |-\n      In a link-ready format, for example:\n\n          itms-services://?action=download-manifest&url=...\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy .plist URL\n"
  },
  {
    "path": "steps/amazon-s3-deploy/step-info.yml",
    "content": "maintainer: bitrise\ndeprecate_notes: |\n  This step is deprecated. Please use the build distribution feature: https://docs.bitrise.io/en/release-management/build-distribution/distributing-builds-to-testers.html\nremoval_date: \"2026-05-31\"\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.0.0/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Fill your Amazon S3 Bucket with contents from the VM\ndescription: |-\n  Syncs the given local folder with an S3 bucket.\n\n  This Step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  It will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local, input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2015-09-08T15:21:42.914704779+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-upload.git\n  commit: fa19800d9e5fe766cdf2ecbb2663807bd58a14b2\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- upload\n- uploader\n- amazon\ndependencies:\n- manager: brew\n  name: s3cmd\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder then you\n      should append a slash at the end of the path. Example: ./folder/\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.1.0/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Amazon S3 Bucket Sync\ndescription: |-\n  Syncs the given local folder with an S3 bucket.\n\n  This Step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  It will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local, input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2015-10-20T14:50:27.14371816+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-upload.git\n  commit: 282509840441eb26839e4226d9d84e9b07224e41\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- upload\n- uploader\n- amazon\ndependencies:\n- manager: brew\n  name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder then you\n      should append a slash at the end of the path. Example: ./folder/\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: |-\n      If set to \"true\" it'll only set ACL for changed objects, which is\n      way faster to do than to check and set every objects' ACL.\n\n      Generally, you can keep this option on \"yes\" to get a speed boost,\n      and you should only change it to \"false\" if you changed the\n      ACL option (in order to force set every object's ACL to the specified one).\n    title: Set ACL only on changed objects?\n    value_options:\n    - \"true\"\n    - \"false\"\n  set_acl_only_on_changed_objets: \"true\"\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.1.1/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Amazon S3 Bucket Sync\ndescription: |-\n  Syncs the given local folder with an S3 bucket.\n\n  This Step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  It will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local, input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2016-04-19T13:48:15.711316002+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-upload.git\n  commit: 36ed6ca8683e0b6a9e0b4cd74fa8c3fb9f2d03be\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- upload\n- uploader\n- amazon\ndeps:\n  brew:\n  - name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder then you\n      should append a slash at the end of the path. Example: ./folder/\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n- opts:\n    description: \"\"\n    is_required: true\n    summary: |-\n      If set to \"true\" it'll only set ACL for changed objects, which is\n      way faster to do than to check and set every objects' ACL.\n\n      Generally, you can keep this option on \"yes\" to get a speed boost,\n      and you should only change it to \"false\" if you changed the\n      ACL option (in order to force set every object's ACL to the specified one).\n    title: Set ACL only on changed objects?\n    value_options:\n    - \"true\"\n    - \"false\"\n  set_acl_only_on_changed_objets: \"true\"\n- aws_region: \"\"\n  opts:\n    description: |\n      If you want to specify a different AWS region of the bucket. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.1.2/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Amazon S3 Bucket Sync\ndescription: |-\n  Syncs the given local folder with an S3 bucket.\n\n  This Step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  It will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local, input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2016-06-16T12:45:13.485714232+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-upload.git\n  commit: 003a890a0fbb55628f1a1d87d362d46573cbb789\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- upload\n- uploader\n- amazon\ndeps:\n  brew:\n  - name: awscli\n  apt_get:\n  - name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder then you\n      should append a slash at the end of the path. Example: ./folder/\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n- opts:\n    description: \"\"\n    is_required: true\n    summary: |-\n      If set to \"true\" it'll only set ACL for changed objects, which is\n      way faster to do than to check and set every objects' ACL.\n\n      Generally, you can keep this option on \"yes\" to get a speed boost,\n      and you should only change it to \"false\" if you changed the\n      ACL option (in order to force set every object's ACL to the specified one).\n    title: Set ACL only on changed objects?\n    value_options:\n    - \"true\"\n    - \"false\"\n  set_acl_only_on_changed_objets: \"true\"\n- aws_region: \"\"\n  opts:\n    description: |\n      If you want to specify a different AWS region of the bucket. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.1.3/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Amazon S3 Bucket Sync\ndescription: |-\n  Syncs the given local folder with an S3 bucket.\n\n  This Step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  It will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local, input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2016-06-24T14:34:03.416955182+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-upload.git\n  commit: 7d3a0206d3ca99568e0ecd7866f987510a9748f8\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\n  apt_get:\n  - name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder then you\n      should append a slash at the end of the path. Example: ./folder/\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n- opts:\n    description: \"\"\n    is_required: true\n    summary: |-\n      If set to \"true\" it'll only set ACL for changed objects, which is\n      way faster to do than to check and set every objects' ACL.\n\n      Generally, you can keep this option on \"yes\" to get a speed boost,\n      and you should only change it to \"false\" if you changed the\n      ACL option (in order to force set every object's ACL to the specified one).\n    title: Set ACL only on changed objects?\n    value_options:\n    - \"true\"\n    - \"false\"\n  set_acl_only_on_changed_objets: \"true\"\n- aws_region: \"\"\n  opts:\n    description: |\n      If you want to specify a different AWS region of the bucket. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.1.4/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Amazon S3 Bucket Sync\ndescription: |-\n  Amazon S3 Bucket Sync step syncs the given local folder with an S3 bucket.\n\n  This step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  This step will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2018-08-31T11:12:40.418675898Z\nsource:\n  git: https://github.com/bitrise-io/steps-amazon-s3-upload.git\n  commit: 7690776dca854fe98edf0a5c52a81bb6a77d2a9a\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\n  apt_get:\n  - name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder, then you\n      should append a slash at the end of the path. For example: ./folder/\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n- opts:\n    description: \"\"\n    is_required: true\n    summary: |-\n      If it is set to \"true\", it'll only set ACL for changed objects, which is\n      way faster to do than to check and set every objects' ACL.\n\n      Generally, you can keep this option on \"yes\" to get a speed boost,\n      and you should only change it to \"false\" if you changed the\n      ACL option (to set every object's ACL to the specified one).\n    title: Set ACL only on changed objects?\n    value_options:\n    - \"true\"\n    - \"false\"\n  set_acl_only_on_changed_objets: \"true\"\n- aws_region: \"\"\n  opts:\n    description: |\n      Here you can specify a different AWS region of the bucket. You can leave\n      it empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/amazon-s3-upload/3.1.5/step.yml",
    "content": "title: Amazon S3 Bucket Sync\nsummary: Amazon S3 Bucket Sync\ndescription: |-\n  Amazon S3 Bucket Sync step syncs the given local folder with an S3 bucket.\n\n  This step requires an Amazon S3 registration.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\n\n  # Warning!\n\n  This step will perform a one-direction sync, removing every file and folder from\n  the bucket which is not present in the local input folder!\nwebsite: https://github.com/bitrise-io/steps-amazon-s3-upload\nsource_code_url: https://github.com/bitrise-io/steps-amazon-s3-upload\nsupport_url: https://github.com/bitrise-io/steps-amazon-s3-upload/issues\npublished_at: 2021-09-17T08:15:20.187953442Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-amazon-s3-upload.git\n  commit: 0b535b9624c4aa77e295c417936593edc5e9af09\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\n  apt_get:\n  - name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: S3 Bucket Name\n  upload_bucket: \"\"\n- opts:\n    description: |\n      If you want to sync only the content of\n      the folder but don't want to create the folder, then you\n      should append a slash at the end of the path. For example: ./folder/\n    is_required: true\n    summary: \"\"\n    title: Local path to upload\n  upload_local_path: \"\"\n- acl_control: private\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Access Control\n    value_options:\n    - public-read\n    - private\n- opts:\n    description: \"\"\n    is_required: true\n    summary: |-\n      If it is set to \"true\", it'll only set ACL for changed objects, which is\n      way faster to do than to check and set every objects' ACL.\n\n      Generally, you can keep this option on \"yes\" to get a speed boost,\n      and you should only change it to \"false\" if you changed the\n      ACL option (to set every object's ACL to the specified one).\n    title: Set ACL only on changed objects?\n    value_options:\n    - \"true\"\n    - \"false\"\n  set_acl_only_on_changed_objets: \"true\"\n- aws_region: \"\"\n  opts:\n    description: |\n      Here you can specify a different AWS region of the bucket. You can leave\n      it empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/amazon-s3-upload/step-info.yml",
    "content": "maintainer: bitrise\ndeprecate_notes: |\n  This step is deprecated. Please use the new official Amazon S3 step: https://bitrise.io/integrations/steps/aws-s3-upload\nremoval_date: \"2026-05-31\"\n"
  },
  {
    "path": "steps/amazon-s3-uploader/1.0.1/step.yml",
    "content": "title: Amazon S3 File uploader\nsummary: Upload a file to Amazon S3\ndescription: |-\n  Bitrise Step to upload a file to Amazon S3.\n\n  This Step requires an Amazon S3 account.\n  To register an Amazon S3 account, [click here](http://aws.amazon.com/s3/).\nwebsite: https://github.com/scruffyfox/bitrise-amazon-s3-uploader\nsource_code_url: https://github.com/scruffyfox/bitrise-amazon-s3-uploader\nsupport_url: https://github.com/scruffyfox/bitrise-amazon-s3-uploader/issues\npublished_at: 2016-09-16T16:24:30.382339161+01:00\nsource:\n  git: https://github.com/scruffyfox/bitrise-amazon-s3-uploader.git\n  commit: 2f622cb773b8a4f5dc5a16eac25579818b6a86a4\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  apt_get:\n  - name: awscli\n    bin_name: aws\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: Path to the file to be uploaded\n    title: File path\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's App-Slug variable (passed automatically on Bitrise)\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: BITRISE's Build-Slug variable (passed automatically on Bitrise)\n- aws_access_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Access Key\n- aws_secret_key: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon AWS Secret Access Key\n- bucket_name: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Bucket Name\n- bucket_region: \"\"\n  opts:\n    description: |\n      Amazon S3 Bucket Region\n\n      If you use default s3 region (us-east-1), you can leave it empty,\n      otherwise you should provide this input.\n    summary: \"\"\n    title: Amazon S3 Bucket Region\n- opts:\n    description: |-\n      Optional, if no value specified then the default will be:\n\n          bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n    summary: \"\"\n    title: Amazon S3 File Path In Bucket\n  path_in_bucket: bitrise_$BITRISE_APP_SLUG/${BITRISE_BUILD_TRIGGER_TIMESTAMP}_build_${BITRISE_BUILD_SLUG}\n- file_access_level: public_read\n  opts:\n    is_required: true\n    title: Amazon S3 file access level\n    value_options:\n    - private\n    - public_read\noutputs:\n- S3_UPLOAD_STEP_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: Url generated for the uploaded file\n    title: Amazon S3 Deploy URL\n- S3_UPLOAD_STEP_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Amazon S3 Deploy result ('success' or 'failed')\n"
  },
  {
    "path": "steps/amazon-s3-uploader/step-info.yml",
    "content": "maintainer: community\ndeprecate_notes: |\n  This step is deprecated. Please use the new official Amazon S3 step: https://bitrise.io/integrations/steps/aws-s3-upload\nremoval_date: \"2026-05-31\"\n"
  },
  {
    "path": "steps/android-build/0.10.0/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2019-05-24T14:37:28.600701733Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 4ba2a407db08bae27768cd1728823d1183e248ed\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patters with a newline.\n\n      **Note**<br/>\n      The step will export only the selected artifact type - `build type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - `depending on the build type input`\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- apk_path_pattern: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the App location pattern input instead\n\n\n      Will find the APK files with the given pattern.\n    summary: This input is **DEPRECATED** - use the App location pattern input instead\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.10.1/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2020-04-24T21:05:30.902538941Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 01c86abe34690c0fdf5c3f09213dde0acb5ff8da\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patters with a newline.\n\n      **Note**<br/>\n      The step will export only the selected artifact type - `build type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - `depending on the build type input`\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- apk_path_pattern: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the App location pattern input instead\n\n\n      Will find the APK files with the given pattern.\n    summary: This input is **DEPRECATED** - use the App location pattern input instead\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.10.2/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2020-09-02T09:59:16.604112066Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: ea67157a75f83a57fe5a338f73ed72a5a4264701\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patters with a newline.\n\n      **Note**<br/>\n      The step will export only the selected artifact type - `build type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - `depending on the build type input`\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- apk_path_pattern: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the App location pattern input instead\n\n\n      Will find the APK files with the given pattern.\n    summary: This input is **DEPRECATED** - use the App location pattern input instead\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.10.3/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: \"\\nThe Step builds your Android project on Bitrise with Gradle commands:\n  it installs all dependences that are listed in the project's `build.gradle` file,\n  and builds and exports either an APK or an AAB. \\nOnce the file is exported, it\n  is available for other Steps in your Workflow.\\n\\nYou can select the module and\n  the variant you want to use for the build.\\n\\n### Configuring the Step \\n\\n1. Make\n  sure the **Project Location** input points to the root directory of your Android\n  project.\\n1. In the **Module** input, set the module that you want to build.\\n   \\n\n  \\  You can find the available modules in Android Studio.\\n\\n1. In the **Variant**\n  input, set the variant that you want to build. \\n   \\n   You can find the available\n  variants in Android Studio.\\n   \\n1. In the **Build type** input, select the file\n  type you want to build. \\n\\n   The options are:\\n   - `apk`\\n   - `aab`\\n   \\n1.\n  In the **Options** input group, you can set more advanced configuration options\n  for the Step:\\n\\n   - In the **App artifact (.apk, .aab) location pattern** input,\n  you can tell the Step where to look for the APK or AAB files in your project to\n  export them. \\n   For the vast majority of Android projects, the default values\n  do NOT need to be changed.\\n   \\n   - In the **Additional Gradle Arguments**, you\n  can add additional command line arguments to the Gradle task. Read more about [Gradle's\n  Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\\n\n  \\  \\n   - The **Set the level of cache** input allows you to set what will be cached\n  during the build: everything, dependencies only, or nothing.\\n   \\n### Troubleshooting\n  \\n\\nBe aware that an APK or AAB built by the Step is still unsigned: code signing\n  is performed either in Gradle itself or by other Steps. To be able to deploy your\n  APK or AAB to an online store, you need code signing. \\n\\nIf you want to build a\n  custom module or variant, always check that the value you set in the respective\n  input is correct. A typo means your build will fail; if the module or variant does\n  not exist in Android Studio, the build will fail.\\n \\n### Useful links\\n\\n- [Getting\n  started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n-\n  [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\\n-\n  [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\\n\\n###\n  Related Steps \\n\\n- [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\\n- [Install missing\n  Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2020-12-10T08:43:04.365483747Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: c8661adc2e5a033205ce2c529a57ae87aa4469ba\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n      You can set multiple variants separated by `\\n` character. For instance: `- variant: myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- apk_path_pattern: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the App location pattern input instead\n\n      Will find the APK files with the given pattern.\n    summary: This input is **DEPRECATED** - use the App location pattern input instead\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.10.4/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: \"\\nThe Step builds your Android project on Bitrise with Gradle commands:\n  it installs all dependences that are listed in the project's `build.gradle` file,\n  and builds and exports either an APK or an AAB. \\nOnce the file is exported, it\n  is available for other Steps in your Workflow.\\n\\nYou can select the module and\n  the variant you want to use for the build.\\n\\n### Configuring the Step \\n\\n1. Make\n  sure the **Project Location** input points to the root directory of your Android\n  project.\\n1. In the **Module** input, set the module that you want to build.\\n   \\n\n  \\  You can find the available modules in Android Studio.\\n\\n1. In the **Variant**\n  input, set the variant that you want to build. \\n   \\n   You can find the available\n  variants in Android Studio.\\n   \\n1. In the **Build type** input, select the file\n  type you want to build. \\n\\n   The options are:\\n   - `apk`\\n   - `aab`\\n   \\n1.\n  In the **Options** input group, you can set more advanced configuration options\n  for the Step:\\n\\n   - In the **App artifact (.apk, .aab) location pattern** input,\n  you can tell the Step where to look for the APK or AAB files in your project to\n  export them. \\n   For the vast majority of Android projects, the default values\n  do NOT need to be changed.\\n   \\n   - In the **Additional Gradle Arguments**, you\n  can add additional command line arguments to the Gradle task. Read more about [Gradle's\n  Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\\n\n  \\  \\n   - The **Set the level of cache** input allows you to set what will be cached\n  during the build: everything, dependencies only, or nothing.\\n   \\n### Troubleshooting\n  \\n\\nBe aware that an APK or AAB built by the Step is still unsigned: code signing\n  is performed either in Gradle itself or by other Steps. To be able to deploy your\n  APK or AAB to an online store, you need code signing. \\n\\nIf you want to build a\n  custom module or variant, always check that the value you set in the respective\n  input is correct. A typo means your build will fail; if the module or variant does\n  not exist in Android Studio, the build will fail.\\n \\n### Useful links\\n\\n- [Getting\n  started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n-\n  [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\\n-\n  [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\\n\\n###\n  Related Steps \\n\\n- [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\\n- [Install missing\n  Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2021-05-28T07:51:31.99332069Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 84b5cbb44231b20e0490706a98956c6b664bb395\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n      You can set multiple variants separated by `\\n` character. For instance: `- variant: myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- apk_path_pattern: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the App location pattern input instead\n\n      Will find the APK files with the given pattern.\n    summary: This input is **DEPRECATED** - use the App location pattern input instead\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.0/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: !!timestamp 2018-03-29T11:30:43.460247665+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 534321783aba658c2b7c334b90f9d68618eed1c4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: APK Export Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.1/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: !!timestamp 2018-04-03T11:47:26.134777578+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 18de17bb9a720a7f45cf012b06518ae3612c3dc7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: APK Export Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.2/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2018-05-02T12:47:52.70496816+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 75e3f3d3daa8a9558518ce170d74ef7c30949be2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.3/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2018-05-09T15:33:45.48696137+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 041761f735f9b988c2120ed45addf781a621cdaf\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.4/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2018-05-23T15:14:12.225877854+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 9e4f55f0532997933c1df82928ba4638e51cc058\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.5/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2018-08-17T13:46:07.603768321Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: e209a75ea1cfaa24a836df7cd1408d63c9d424de\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/0.9.6/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with gradle.\ndescription: Builds your Android project with gradle.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2019-03-14T14:59:00.758256711Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: bd9b4143512019e1aaf21f885376f93c959be4f7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.0/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: \"\\nThe Step builds your Android project on Bitrise with Gradle commands:\n  it installs all dependences that are listed in the project's `build.gradle` file,\n  and builds and exports either an APK or an AAB. \\nOnce the file is exported, it\n  is available for other Steps in your Workflow.\\n\\nYou can select the module and\n  the variant you want to use for the build.\\n\\n### Configuring the Step \\n\\n1. Make\n  sure the **Project Location** input points to the root directory of your Android\n  project.\\n1. In the **Module** input, set the module that you want to build.\\n   \\n\n  \\  You can find the available modules in Android Studio.\\n\\n1. In the **Variant**\n  input, set the variant that you want to build. \\n   \\n   You can find the available\n  variants in Android Studio.\\n   \\n1. In the **Build type** input, select the file\n  type you want to build. \\n\\n   The options are:\\n   - `apk`\\n   - `aab`\\n   \\n1.\n  In the **Options** input group, you can set more advanced configuration options\n  for the Step:\\n\\n   - In the **App artifact (.apk, .aab) location pattern** input,\n  you can tell the Step where to look for the APK or AAB files in your project to\n  export them. \\n   For the vast majority of Android projects, the default values\n  do NOT need to be changed.\\n   \\n   - In the **Additional Gradle Arguments**, you\n  can add additional command line arguments to the Gradle task. Read more about [Gradle's\n  Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\\n\n  \\  \\n   - The **Set the level of cache** input allows you to set what will be cached\n  during the build: everything, dependencies only, or nothing.\\n   \\n### Troubleshooting\n  \\n\\nBe aware that an APK or AAB built by the Step is still unsigned: code signing\n  is performed either in Gradle itself or by other Steps. To be able to deploy your\n  APK or AAB to an online store, you need code signing. \\n\\nIf you want to build a\n  custom module or variant, always check that the value you set in the respective\n  input is correct. A typo means your build will fail; if the module or variant does\n  not exist in Android Studio, the build will fail.\\n \\n### Useful links\\n\\n- [Getting\n  started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n-\n  [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\\n-\n  [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\\n\\n###\n  Related Steps \\n\\n- [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\\n- [Install missing\n  Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2021-08-25T08:31:25.402721632Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 6930079046321080a933e7f599666b6b3d8bbcee\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n      You can set multiple variants separated by `\\n` character. For instance: `- variant: myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.1/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependences that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2021-11-09T13:15:16.553346237Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: ab02569279ab7cac49772cec4ed0a95dd2dd153d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n      You can set multiple variants separated by `\\n` character. For instance: `- variant: myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.2/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependencies that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2022-02-23T08:20:58.13153333Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 10926630dc97bd1c4722726c88a1c25d1841ed2e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n      You can set multiple variants separated by `\\n` character. For instance: `- variant: myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: |\n      Set the variant(s) that you want to build. To see your available variants, please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.3/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependencies that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2022-07-14T11:57:21.450658123Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 7e46991accbfc939719e9c77bc41b6a32299990c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants,  open your project in Android Studio and go in [Project Structure] -> variants section.\n\n      You can set multiple variants separated by a new line (`\\n`), such as `myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: Set the build variant you want to create, such as `debug` or `myflavorRelease`.\n      To see your available variants, open your project in Android Studio and go in\n      [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.4/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependencies that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2022-07-14T16:29:58.083630742Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: fe475b3da876a88e0f7a7db1bff6106533f96058\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant(s) that you want to build. To see your available variants,  open your project in Android Studio and go in [Project Structure] -> variants section.\n\n      You can set multiple variants separated by a new line (`\\n`), such as `myvariant1\\nmyvariant2`.\n    is_required: false\n    summary: Set the build variant you want to create, such as `debug` or `myflavorRelease`.\n      To see your available variants, open your project in Android Studio and go in\n      [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.5/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependencies that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2022-07-18T10:13:00.652404741Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 1f52f436a3be83d27917dac8a00b2e1b2a08331b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the build variants you want to create. To see your available variants,  open your project in Android Studio and go in [Project Structure] -> variants section.\n\n      This input also accepts multiple variants, separated by a line break.\n    is_required: false\n    summary: Set the build variants you want to create, such as `debug` or `myflavorRelease`.\n      To see your available variants, open your project in Android Studio and go in\n      [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - The Step will cache build cache and the dependencies\n      `only_deps` - The Step will cache dependencies only\n      `none` - The Step will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.0.6/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependencies that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2025-11-14T12:44:21.724936714Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: c3322b474c9549344344d6e90fb629632a609034\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the build variants you want to create. To see your available variants,  open your project in Android Studio and go in [Project Structure] -> variants section.\n\n      This input also accepts multiple variants, separated by a line break.\n    is_required: false\n    summary: Set the build variants you want to create, such as `debug` or `myflavorRelease`.\n      To see your available variants, open your project in Android Studio and go in\n      [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/1.1.0/step.yml",
    "content": "title: Android Build\nsummary: Builds your Android project with Gradle.\ndescription: |2-\n\n  The Step builds your Android project on Bitrise with Gradle commands: it installs all dependencies that are listed in the project's `build.gradle` file, and builds and exports either an APK or an AAB.\n  Once the file is exported, it is available for other Steps in your Workflow.\n\n  You can select the module and the variant you want to use for the build.\n\n  ### Configuring the Step\n\n  1. Make sure the **Project Location** input points to the root directory of your Android project.\n  1. In the **Module** input, set the module that you want to build.\n\n     You can find the available modules in Android Studio.\n\n  1. In the **Variant** input, set the variant that you want to build.\n\n     You can find the available variants in Android Studio.\n\n  1. In the **Build type** input, select the file type you want to build.\n\n     The options are:\n     - `apk`\n     - `aab`\n\n  1. In the **Options** input group, you can set more advanced configuration options for the Step:\n\n     - In the **App artifact (.apk, .aab) location pattern** input, you can tell the Step where to look for the APK or AAB files in your project to export them.\n     For the vast majority of Android projects, the default values do NOT need to be changed.\n\n     - In the **Additional Gradle Arguments**, you can add additional command line arguments to the Gradle task. Read more about [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html).\n\n     - The **Set the level of cache** input allows you to set what will be cached during the build: everything, dependencies only, or nothing.\n\n  ### Troubleshooting\n\n  Be aware that an APK or AAB built by the Step is still unsigned: code signing is performed either in Gradle itself or by other Steps. To be able to deploy your APK or AAB to an online store, you need code signing.\n\n  If you want to build a custom module or variant, always check that the value you set in the respective input is correct. A typo means your build will fail; if the module or variant does not exist in Android Studio, the build will fail.\n\n  ### Useful links\n\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n  - [Generating and deploying Android app bundles](https://devcenter.bitrise.io/deploy/android-deploy/generating-and-deploying-android-app-bundles/)\n  - [Gradle's Command Line Interface](https://docs.gradle.org/current/userguide/command_line_interface.html)\n\n  ### Related Steps\n\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build/issues\npublished_at: 2026-04-23T17:38:13.428737+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build.git\n  commit: 8af70c42dcf95d3142a52dcdfe561b35abb0c7ef\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to build. To see your available modules, please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the build variants you want to create. To see your available variants,  open your project in Android Studio and go in [Project Structure] -> variants section.\n\n      This input also accepts multiple variants, separated by a line break.\n    is_required: false\n    summary: Set the build variants you want to create, such as `debug` or `myflavorRelease`.\n      To see your available variants, open your project in Android Studio and go in\n      [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- build_type: apk\n  opts:\n    description: |\n      Set the build type that you want to build.\n    is_required: true\n    summary: |\n      Set the build type that you want to build.\n    title: Build type\n    value_options:\n    - apk\n    - aab\n- app_path_pattern: |-\n    */build/outputs/apk/*.apk\n    */build/outputs/bundle/*.aab\n  opts:\n    category: Options\n    description: |\n      Will find the APK or AAB files - depending on the **Build type** input - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The Step will export only the selected artifact type even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Will find the APK or AAB files - depending on the **Build type** input\n      - with the given pattern.\n    title: App artifact (.apk, .aab) location pattern\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n      If the build generates more than one APK which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB which fulfills the\n      filter inputs, this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB - after filtering.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths - after filtering.\n    title: List of the generated AAB paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in the project, this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/android-build/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.0/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with gradle with the belonging AndroidTest variant.\ndescription: Builds your Android project with gradle with the belonging AndroidTest\n  variant.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2019-01-11T11:33:11.886725521Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: 914037dbb2bf67e403faf0ce25d6506e4127ecb9\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.1/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with gradle with the belonging AndroidTest variant.\ndescription: Builds your Android project with gradle with the belonging AndroidTest\n  variant.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2019-03-14T14:58:35.456053745Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: 8a02f7acb3f2c1972b7207902dfba60367a7d536\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.2/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with gradle with the belonging AndroidTest variant.\ndescription: Builds your Android project with gradle with the belonging AndroidTest\n  variant.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2020-04-24T20:45:13.795565464Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: daa908208e5f854b35098dd24f90fff4de56adf0\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.3/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with gradle with the belonging AndroidTest variant.\ndescription: Builds your Android project with gradle with the belonging AndroidTest\n  variant.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2020-11-25T14:52:40.388696881Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: ffff234b0d635cce005becfca22f753b33adbd19\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.4/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with gradle with the belonging AndroidTest variant.\ndescription: Builds your Android project with gradle with the belonging AndroidTest\n  variant.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2021-05-28T12:52:59.366614897Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: 5023d0f4953924b23d60a4531b35ff564f929e98\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.5/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with Gradle with the belonging AndroidTest variant.\ndescription: \"[This Step](https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing)\n  generates all the APKs you need to run instrumentation tests for your Android app:\n  both an APK from your app and the belonging test APK, for example,  `:app:assembleDemoDebug`,\n  `:app:assembleDemoDebugAndroidTest`\\n \\n ### Configuring the Step\\n 1. Add the **Project\n  Location** which is the root directory of your Android project.\\n 2. Set the **Module**\n  you want to build. To see your available modules, open your project in Android Studio\n  and go to **Project Structure** and see the list on the left.\\n 3. Set the **Variant**\n  you want to build. To see your available variants, open your project in Android\n  Studio and go to **Project Structure** and then the **variants** section.\\n Under\n  **Options**:\\n 4. Set the **APK location pattern**: Once the build has run, the\n  Step finds the APK files with the given pattern.\\n 5. **Set the level of cache**\n  where `all` caches build cache and dependencies, `only_deps` caches dependencies\n  only, `none` does not cache anything.\\n 6. If you wish to pass any extra Gradle\n  arguments to the gradle task, you can add those in the **Additional Gradle Arguments**\n  input.\\n\\n ### Useful links\\n- [Testing with Bitrise](https://devcenter.bitrise.io/testing/testing-index/)\\n-\n  [Deploying an Android app with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2021-06-24T15:41:07.662994538Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: c85ab833f88b39cfa27abd5b84dafc6b879cbaef\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exist (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    description: Will find the APK files with the given pattern.\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.6/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with Gradle with the belonging AndroidTest variant.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing) generates all the APKs you need to run instrumentation tests for your Android app: both an APK from your app and the belonging test APK, for example,  `:app:assembleDemoDebug`, `:app:assembleDemoDebugAndroidTest`\n\n   ### Configuring the Step\n   1. Add the **Project Location** which is the root directory of your Android project.\n   2. Set the **Module** you want to build. To see your available modules, open your project in Android Studio and go to **Project Structure** and see the list on the left.\n   3. Set the **Variant** you want to build. To see your available variants, open your project in Android Studio and go to **Project Structure** and then the **variants** section.\n   Under **Options**:\n   4. Set the **APK location pattern**: Once the build has run, the Step finds the APK files with the given pattern.\n   5. **Set the level of cache** where `all` caches build cache and dependencies, `only_deps` caches dependencies only, `none` does not cache anything.\n   6. If you wish to pass any extra Gradle arguments to the gradle task, you can add those in the **Additional Gradle Arguments** input.\n\n   ### Useful links\n  - [Testing with Bitrise](https://devcenter.bitrise.io/testing/testing-index/)\n  - [Deploying an Android app with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2021-11-09T13:13:48.615405438Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: 05414286cf8ac74687de66884b0a5e1ee07344d6\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    is_required: true\n    summary: |\n      Set the module that you want to build. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.7/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with Gradle with the belonging AndroidTest variant.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing) generates all the APKs you need to run instrumentation tests for your Android app: both an APK from your app and the belonging test APK, for example,  `:app:assembleDemoDebug`, `:app:assembleDemoDebugAndroidTest`\n\n   ### Configuring the Step\n   1. Add the **Project Location** which is the root directory of your Android project.\n   2. Set the **Module** you want to build. To see your available modules, open your project in Android Studio and go to **Project Structure** and see the list on the left.\n   3. Set the **Variant** you want to build. To see your available variants, open your project in Android Studio and go to **Project Structure** and then the **variants** section.\n   Under **Options**:\n   4. Set the **APK location pattern**: Once the build has run, the Step finds the APK files with the given pattern.\n   5. **Set the level of cache** where `all` caches build cache and dependencies, `only_deps` caches dependencies only, `none` does not cache anything.\n   6. If you wish to pass any extra Gradle arguments to the gradle task, you can add those in the **Additional Gradle Arguments** input.\n\n   ### Useful links\n  - [Testing with Bitrise](https://devcenter.bitrise.io/testing/testing-index/)\n  - [Deploying an Android app with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2021-11-22T15:57:43.303035343Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: 88443b350d734172afcb3ee2099a098585c381f9\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module to build. Valid syntax examples: `app`, `feature:nested-module`\n\n      To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: 'Set the module to build. Valid syntax examples: `app`, `feature:nested-module`'\n    title: Module\n- opts:\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.8/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with Gradle with the belonging AndroidTest variant.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing) generates all the APKs you need to run instrumentation tests for your Android app: both an APK from your app and the belonging test APK, for example,  `:app:assembleDemoDebug`, `:app:assembleDemoDebugAndroidTest`\n\n   ### Configuring the Step\n   1. Add the **Project Location** which is the root directory of your Android project.\n   2. Set the **Module** you want to build. To see your available modules, open your project in Android Studio and go to **Project Structure** and see the list on the left.\n   3. Set the **Variant** you want to build. To see your available variants, open your project in Android Studio and go to **Project Structure** and then the **variants** section.\n   Under **Options**:\n   4. Set the **APK location pattern**: Once the build has run, the Step finds the APK files with the given pattern.\n   5. **Set the level of cache** where `all` caches build cache and dependencies, `only_deps` caches dependencies only, `none` does not cache anything.\n   6. If you wish to pass any extra Gradle arguments to the gradle task, you can add those in the **Additional Gradle Arguments** input.\n\n   ### Useful links\n  - [Testing with Bitrise](https://devcenter.bitrise.io/testing/testing-index/)\n  - [Deploying an Android app with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2025-10-31T10:00:24.545465935Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: 7b2605127f7698a2ee0af4b0eebcf68accb20c53\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module to build. Valid syntax examples: `app`, `feature:nested-module`\n\n      To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: 'Set the module to build. Valid syntax examples: `app`, `feature:nested-module`'\n    title: Module\n- opts:\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/0.1.9/step.yml",
    "content": "title: Android Build for UI Testing\nsummary: Builds your Android project with Gradle with the belonging AndroidTest variant.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing) generates all the APKs you need to run instrumentation tests for your Android app: both an APK from your app and the belonging test APK, for example,  `:app:assembleDemoDebug`, `:app:assembleDemoDebugAndroidTest`\n\n   ### Configuring the Step\n   1. Add the **Project Location** which is the root directory of your Android project.\n   2. Set the **Module** you want to build. To see your available modules, open your project in Android Studio and go to **Project Structure** and see the list on the left.\n   3. Set the **Variant** you want to build. To see your available variants, open your project in Android Studio and go to **Project Structure** and then the **variants** section.\n   Under **Options**:\n   4. Set the **APK location pattern**: Once the build has run, the Step finds the APK files with the given pattern.\n   5. **Set the level of cache** where `all` caches build cache and dependencies, `only_deps` caches dependencies only, `none` does not cache anything.\n   6. If you wish to pass any extra Gradle arguments to the gradle task, you can add those in the **Additional Gradle Arguments** input.\n\n   ### Useful links\n  - [Testing with Bitrise](https://devcenter.bitrise.io/testing/testing-index/)\n  - [Deploying an Android app with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing/issues\npublished_at: 2025-11-10T13:21:06.689090942Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing.git\n  commit: b46078d270aa7241b5587a0bafafaae1a0fc960d\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-build-for-ui-testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module to build. Valid syntax examples: `app`, `feature:nested-module`\n\n      To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: true\n    summary: 'Set the module to build. Valid syntax examples: `app`, `feature:nested-module`'\n    title: Module\n- opts:\n    is_required: true\n    summary: |\n      Set the variant that you want to build. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- apk_path_pattern: '*/build/outputs/apk/*.apk'\n  opts:\n    category: Options\n    is_required: true\n    summary: Will find the APK files with the given pattern.\n    title: APK location pattern\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK\n      after filtering based on the filter inputs.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n"
  },
  {
    "path": "steps/android-build-for-ui-testing/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/android-detekt/0.0.2/step.yml",
    "content": "title: Android Detekt\nsummary: |\n  This step runs detekt gradle task on your project.\ndescription: |\n  This step runs detekt gradle task on your project.\nwebsite: https://github.com/dzinek/bitrise-step-android-detekt\nsource_code_url: https://github.com/dzinek/bitrise-step-android-detekt\nsupport_url: https://github.com/dzinek/bitrise-step-android-detekt/issues\npublished_at: 2019-02-04T06:52:05.394754+01:00\nsource:\n  git: https://github.com/dzinek/bitrise-step-android-detekt.git\n  commit: 32358164f04f1996c577f6b581f5f1d244ea5990\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/dzinek/bitrise-step-android-detekt\ndeps:\n  apt_get:\n  - name: git\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to run detekt. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to run detekt. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/detekt/detekt*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/detekt/detekt*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/detekt/detekt*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-detekt/0.0.3/step.yml",
    "content": "title: Android Detekt\nsummary: |\n  This step runs detekt gradle task on your project.\ndescription: |\n  This step runs detekt gradle task on your project.\nwebsite: https://github.com/dzinek/bitrise-step-android-detekt\nsource_code_url: https://github.com/dzinek/bitrise-step-android-detekt\nsupport_url: https://github.com/dzinek/bitrise-step-android-detekt/issues\npublished_at: 2020-03-31T01:05:34.697406+02:00\nsource:\n  git: https://github.com/dzinek/bitrise-step-android-detekt.git\n  commit: 1c0a9f3a08f4100b036103775f67dcaa1a0b087c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/dzinek/bitrise-step-android-detekt\ndeps:\n  apt_get:\n  - name: git\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to run detekt. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to run detekt. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/detekt/detekt*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/detekt/detekt*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/detekt/detekt*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-detekt/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/android-instrumented-test/0.1.0/step.yml",
    "content": "title: Android Instrumented Test\nsummary: Runs Instrumented tests on an existing APK\ndescription: Runs Instrumented tests on an existing APK\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test/issues\npublished_at: 2022-06-28T08:38:59.19506-05:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test.git\n  commit: 30dd54e3850db8b804e5dcd3acae2cc19dbf924e\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-instrumented-test\ninputs:\n- main_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: The path to the app's main APK\n    is_required: true\n    summary: The path to the app's main APK\n    title: Main APK path\n- opts:\n    description: The path to the app's test APK\n    is_required: true\n    summary: The path to the app's test APK\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: The name of the test runner\n    is_required: true\n    summary: The name of the test runner\n    title: Test runner class\n  test_runner_class: androidx.test.runner.AndroidJUnitRunner\n- additional_testing_options: \"\"\n  opts:\n    description: |-\n      A space-delimited list of additional options to pass to the test runner\n\n      Example:\n\n      If a value of `KEY1 true KEY2 false` is passed to this input,\n      then it will be passed to the `adb` command like so:\n\n      ```shell\n      adb shell am instrument -e \"KEY1\" \"true\" \"KEY2\" \"false\" [...]\n      ```\n\n      See the [`adb` documentation](https://developer.android.com/studio/command-line/adb#am) for more info.\n    summary: A space-delimited list of additional options to pass to the test runner\n    title: Additional testing options\n"
  },
  {
    "path": "steps/android-instrumented-test/0.1.1/step.yml",
    "content": "title: Android Instrumented Test\nsummary: Runs Instrumented tests on an existing APK\ndescription: Runs Instrumented tests on an existing APK\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test/issues\npublished_at: 2023-07-24T13:32:30.362292292Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test.git\n  commit: 35984f7c637778c37f22a8d16e05af9ad76bdad4\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-instrumented-test\ninputs:\n- main_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: The path to the app's main APK\n    is_required: true\n    summary: The path to the app's main APK\n    title: Main APK path\n- opts:\n    description: The path to the app's test APK\n    is_required: true\n    summary: The path to the app's test APK\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: The name of the test runner\n    is_required: true\n    summary: The name of the test runner\n    title: Test runner class\n  test_runner_class: androidx.test.runner.AndroidJUnitRunner\n- additional_testing_options: \"\"\n  opts:\n    description: |-\n      A space-delimited list of additional options to pass to the test runner\n\n      Example:\n\n      If a value of `KEY1 true KEY2 false` is passed to this input,\n      then it will be passed to the `adb` command like so:\n\n      ```shell\n      adb shell am instrument -e \"KEY1\" \"true\" \"KEY2\" \"false\" [...]\n      ```\n\n      See the [`adb` documentation](https://developer.android.com/studio/command-line/adb#am) for more info.\n    summary: A space-delimited list of additional options to pass to the test runner\n    title: Additional testing options\n"
  },
  {
    "path": "steps/android-instrumented-test/0.1.2/step.yml",
    "content": "title: Android Instrumented Test\nsummary: Runs Instrumented tests on an existing APK\ndescription: Runs Instrumented tests on an existing APK\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test/issues\npublished_at: 2025-11-14T12:46:32.554922281Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-instrumented-test.git\n  commit: 26ef745d63863c7a072e4063fa5f08a60b288ef4\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-instrumented-test\ninputs:\n- main_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: The path to the app's main APK\n    is_required: true\n    summary: The path to the app's main APK\n    title: Main APK path\n- opts:\n    description: The path to the app's test APK\n    is_required: true\n    summary: The path to the app's test APK\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: The name of the test runner\n    is_required: true\n    summary: The name of the test runner\n    title: Test runner class\n  test_runner_class: androidx.test.runner.AndroidJUnitRunner\n- additional_testing_options: \"\"\n  opts:\n    description: |-\n      A space-delimited list of additional options to pass to the test runner\n\n      Example:\n\n      If a value of `KEY1 true KEY2 false` is passed to this input,\n      then it will be passed to the `adb` command like so:\n\n      ```shell\n      adb shell am instrument -e \"KEY1\" \"true\" \"KEY2\" \"false\" [...]\n      ```\n\n      See the [`adb` documentation](https://developer.android.com/studio/command-line/adb#am) for more info.\n    summary: A space-delimited list of additional options to pass to the test runner\n    title: Additional testing options\n"
  },
  {
    "path": "steps/android-instrumented-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/android-lint/0.9.0/step.yml",
    "content": "title: Android Lint\nsummary: Runs lint gradle task on your project.\ndescription: Runs lint gradle task on your project.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: !!timestamp 2018-03-22T14:31:26.216598122+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 0e89ce7f00a06ee57c54b074989c203410da8a74\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Report Export Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n"
  },
  {
    "path": "steps/android-lint/0.9.1/step.yml",
    "content": "title: Android Lint\nsummary: Runs lint gradle task on your project.\ndescription: Runs lint gradle task on your project.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2018-05-02T12:43:14.432324737+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: ea9b335bb05c7007d70fd001bc26baf047aea6f3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.10/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2021-11-08T09:56:34.10549279Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: de8726d7c43c2d3de51c23b0bcbe76ec42b120b1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.11/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2022-02-23T08:20:03.97327161Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 379c820c7713997eb706b7ff4e18b6642c720a8f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.12/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2025-11-18T09:15:23.162068754Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 2ea35ded0377ad1a9e2e2056807f5434d33c1bad\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.13/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2026-02-02T11:14:34.387799105Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 6d612b1000ffb820c1976430b77ac4e9a90b8b34\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.14/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2026-03-02T09:43:52.366748462Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 63b4b07b6f7cf04bcbc208818b5dca46b84642fd\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/android-lint/0.9.14/bin/android-lint-darwin-amd64\n    hash: sha256-8a1d00f7d740b4e7cf1981cd2094d76bffaab8831a4b04586f950fd4ee6fa197\n  darwin-arm64:\n    storage_uri: steps/android-lint/0.9.14/bin/android-lint-darwin-arm64\n    hash: sha256-652b30bee446aa28fdd81cc685b752d1e0997a412ffc0a50ba078bad4a072d90\n  linux-amd64:\n    storage_uri: steps/android-lint/0.9.14/bin/android-lint-linux-amd64\n    hash: sha256-84477435e62f546258a8522c9641024c3652b9d61cc25466ea9991afeec04114\n  linux-arm64:\n    storage_uri: steps/android-lint/0.9.14/bin/android-lint-linux-arm64\n    hash: sha256-34086ec9b01562c37cceadd05e4481dd5d577cadaa0eca21a1f6c8ac156bb6c0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.2/step.yml",
    "content": "title: Android Lint\nsummary: Runs lint gradle task on your project.\ndescription: Runs lint gradle task on your project.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2018-05-23T15:16:52.992466727+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 8b5597a0ea586579b6fd6698e2111ea13659a0f2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.4/step.yml",
    "content": "title: Android Lint\nsummary: Runs lint gradle task on your project.\ndescription: Runs lint gradle task on your project.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2018-06-29T14:43:34.144796202+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 61682434a650a82adf0aaddca2fa0a48f22b3182\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.5/step.yml",
    "content": "title: Android Lint\nsummary: This step runs lint gradle task on your project.\ndescription: This step runs lint gradle task on your project.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2018-10-29T13:39:24.293713488Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 8fdc72eb7f80638eeaf92c1bba9bbf06031dc28e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.6/step.yml",
    "content": "title: Android Lint\nsummary: This step runs lint gradle task on your project.\ndescription: This step runs lint gradle task on your project.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2019-03-14T14:58:53.356958732Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 960fc806a066bae5f8a38fd5e076f80dcc87b181\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.7/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2020-01-13T08:32:58.861993297Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 1ef53e35109f99b0e085ebd887567bebaa2af8dd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.8/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2020-11-25T14:48:35.844179195Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: 83326f5b7c81e8c1b27c53e03150ae22e9204b76\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/0.9.9/step.yml",
    "content": "title: Android Lint\nsummary: Runs Lint on your Android project source files and detects potential syntax\n  errors to keep your code error free.\ndescription: |-\n  It highlights the code line where the error is found, explains the type of error and suggests corrections. The Step does not make the build fail if it spots any structural errors in your code. If you have inserted the **Deploy to Bitrise.io** Step in the Workflow, the tes results will be available in a viewable or downloadable Lint Report HTML or XML file which you can access on the Build's APPS & ARTIFACTS page.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input which, by default, points to the root directory of your Android project.\n  2. Set the module and variant you wish to lint in the **Module** and **Variant** fields.\n\n  Optionally, you can modify these inputs:\n  1. You can specify where the Lint reports should be found once the Step has run if you overwrite the **Report location pattern** input.\n  2. You can set if the Step should cache build outputs and dependencies, only the dependencies or nothing at all in the **Set level of cache** input.\n  3. You can set any gradle argument to the gradle task in the **Additional Gradle Arguments** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before a build Step.\n  Make sure you type the correct module and variant names in the respective fields of the Step. If you are unsure about the exact names, you can check them in the **Project Structure** dialog of your project in Android Studio.\n\n  ### Useful links\n  - [Improve your code with lint checks](https://developer.android.com/studio/write/lint)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  - [[BETA] Virtual Device Testing for Android](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-android)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-lint\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-lint/issues\npublished_at: 2021-05-28T08:06:54.079258192Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-lint.git\n  commit: c9f79992f4ce8508274b825332d7f8f2b2a72d22\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-lint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to lint. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to lint. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Options\n    description: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    is_required: true\n    summary: |\n      Will find the report file with the given pattern. If you need the xml file then you can use: \"*/build/reports/lint-results*.xml\"\n    title: Report location pattern\n  report_path_pattern: '*/build/reports/lint-results*.html'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - will not cache anything\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n"
  },
  {
    "path": "steps/android-lint/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/android-manifest-info/1.0.0/step.yml",
    "content": "title: Android Manifest Info\nsummary: Extracts Android manifest attributes to environment variables.\ndescription: |-\n  Read Android manifest attriubtes from `AndroidManifest.xml` file,\n  then export that data to environment variables prefixed with **AMI_**.\n\n  After this you can use these environment variables in other steps.\nwebsite: https://github.com/tomcurran/bitrise-step-android-manifest-info\nsource_code_url: https://github.com/tomcurran/bitrise-step-android-manifest-info\nsupport_url: https://github.com/tomcurran/bitrise-step-android-manifest-info/issues\npublished_at: 2017-01-29T02:05:10.79863906Z\nsource:\n  git: https://github.com/tomcurran/bitrise-step-android-manifest-info.git\n  commit: 7a52b46c5dd4f14d9e3148b7e2ec6cccbf579ae2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\ntype_tags:\n- build\n- utils\n- versioning\nis_always_run: false\nis_skippable: false\ninputs:\n- manifest_file: $BITRISE_ANDROID_MANIFEST_PATH\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\noutputs:\n- AMI_VERSION_CODE: null\n  opts:\n    title: Version Code (versionCode from AndroidManifest.xml)\n- AMI_VERSION_NAME: null\n  opts:\n    title: Version Name (versionName from AndroidManifest.xml)\n- AMI_PACKAGE_NAME: null\n  opts:\n    title: Package Name (package from AndroidManifest.xml)\n- AMI_MIN_SDK_VERSION: null\n  opts:\n    title: Minimum SDK Version (minSdkVersion from AndroidManifest.xml)\n- TARGETSDKVERSION: null\n  opts:\n    title: Target SDK Version (targetSdkVersion from AndroidManifest.xml)\n"
  },
  {
    "path": "steps/android-manifest-info/1.0.1/step.yml",
    "content": "title: Android Manifest Info\nsummary: Extracts Android manifest attributes to environment variables.\ndescription: |-\n  Read Android manifest attriubtes from `AndroidManifest.xml` file,\n  then export that data to environment variables prefixed with **AMI_**.\n\n  After this you can use these environment variables in other steps.\nwebsite: https://github.com/tomcurran/bitrise-step-android-manifest-info\nsource_code_url: https://github.com/tomcurran/bitrise-step-android-manifest-info\nsupport_url: https://github.com/tomcurran/bitrise-step-android-manifest-info/issues\npublished_at: 2017-01-29T19:35:51.993488403Z\nsource:\n  git: https://github.com/tomcurran/bitrise-step-android-manifest-info.git\n  commit: 79b3826e8e584ccb6b8bceb21a97906bc684312b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_always_run: false\nis_skippable: false\ninputs:\n- manifest_file: $BITRISE_ANDROID_MANIFEST_PATH\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\noutputs:\n- AMI_VERSION_CODE: null\n  opts:\n    title: Version Code (versionCode from AndroidManifest.xml)\n- AMI_VERSION_NAME: null\n  opts:\n    title: Version Name (versionName from AndroidManifest.xml)\n- AMI_PACKAGE_NAME: null\n  opts:\n    title: Package Name (package from AndroidManifest.xml)\n- AMI_MIN_SDK_VERSION: null\n  opts:\n    title: Minimum SDK Version (minSdkVersion from AndroidManifest.xml)\n- AMI_TARGET_SDK_VERSION: null\n  opts:\n    title: Target SDK Version (targetSdkVersion from AndroidManifest.xml)\n"
  },
  {
    "path": "steps/android-manifest-info/1.0.2/step.yml",
    "content": "title: Android Manifest Info\nsummary: Extracts Android manifest attributes to environment variables.\ndescription: |-\n  Read Android manifest attriubtes from `AndroidManifest.xml` file,\n  then export that data to environment variables prefixed with **AMI_**.\n\n  After this you can use these environment variables in other steps.\nwebsite: https://github.com/tomcurran/bitrise-step-android-manifest-info\nsource_code_url: https://github.com/tomcurran/bitrise-step-android-manifest-info\nsupport_url: https://github.com/tomcurran/bitrise-step-android-manifest-info/issues\npublished_at: 2018-01-18T23:28:30.018621Z\nsource:\n  git: https://github.com/tomcurran/bitrise-step-android-manifest-info.git\n  commit: d85f7a37476f419390dec2459f1c80f99078a4bd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_always_run: false\nis_skippable: false\ninputs:\n- manifest_file: $BITRISE_ANDROID_MANIFEST_PATH\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\noutputs:\n- AMI_VERSION_CODE: null\n  opts:\n    title: Version Code (versionCode from AndroidManifest.xml)\n- AMI_VERSION_NAME: null\n  opts:\n    title: Version Name (versionName from AndroidManifest.xml)\n- AMI_PACKAGE_NAME: null\n  opts:\n    title: Package Name (package from AndroidManifest.xml)\n- AMI_MIN_SDK_VERSION: null\n  opts:\n    title: Minimum SDK Version (minSdkVersion from AndroidManifest.xml)\n- AMI_TARGET_SDK_VERSION: null\n  opts:\n    title: Target SDK Version (targetSdkVersion from AndroidManifest.xml)\n"
  },
  {
    "path": "steps/android-manifest-info/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/android-screenrecord-start/0.9.0/step.yml",
    "content": "title: Android Screenrecord Start\nsummary: Start recording an Android device's screen.\ndescription: Start recording an Android device's screen.\nwebsite: https://github.com/bitrise-steplib/steps-android-screenrecord-start\nsource_code_url: https://github.com/bitrise-steplib/steps-android-screenrecord-start\nsupport_url: https://github.com/bitrise-steplib/steps-android-screenrecord-start/issues\npublished_at: 2017-12-20T11:18:41.171970361+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-android-screenrecord-start.git\n  commit: 3e83238c5c6fb5d27a955e2f3b3d24c5120dd428\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-android-screenrecord-start\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: Make sure this input's value is unique. This ID will be included\n      in the recorded file's name to be able to separate records, and also `Stop Screenrecord\n      Android` step will need this ID to know which record need to be stopped.\n    is_expand: true\n    is_required: true\n    summary: Make sure this input's value is unique. This ID will be included in the\n      recorded file's name to be able to separate records, and also `Stop Screenrecord\n      Android` step will need this ID to know which record need to be stopped.\n    title: Record ID\n  record_id: record0\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: The commands will be sent to the emulator that has the given serial.\n    is_expand: true\n    is_required: true\n    summary: The commands will be sent to the emulator that has the given serial.\n    title: Emulator serial\noutputs:\n- BITRISE_RECORD_ID: null\n  opts:\n    description: The started record's ID\n    summary: The started record's ID\n    title: Record ID\n"
  },
  {
    "path": "steps/android-screenrecord-start/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, android emulators no longer support screen recording\nmaintainer: bitrise\nremoval_date: \"2018-09-20\"\n"
  },
  {
    "path": "steps/android-screenrecord-stop/0.9.0/step.yml",
    "content": "title: Android Screenrecord Stop\nsummary: Stop an Android device's screen recording and pulls the recorded video under\n  BITRISE_DEPLOY_DIR\ndescription: Stop an Android device's screen recording and pulls the recorded video\n  under BITRISE_DEPLOY_DIR\nwebsite: https://github.com/bitrise-steplib/steps-android-screenrecord-stop\nsource_code_url: https://github.com/bitrise-steplib/steps-android-screenrecord-stop\nsupport_url: https://github.com/bitrise-steplib/steps-android-screenrecord-stop/issues\npublished_at: 2017-12-20T11:51:07.464074046+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-android-screenrecord-stop.git\n  commit: d5180e9ddd1bae5bb5cc61ae59ceb83d9e4ecd16\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-android-screenrecord-stop\ndeps:\n  brew:\n  - name: go\n  - name: ffmpeg\n  apt_get:\n  - name: ffmpeg\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: The record running with this ID will be stopped and the finished\n      video will be downloaded from the device.\n    is_expand: true\n    is_required: true\n    summary: The record running with this ID will be stopped and the finished video\n      will be downloaded from the device.\n    title: Record ID\n  record_id: $BITRISE_RECORD_ID\n- opts:\n    description: Remove sequentially duplicate frames with FFmpeg by dropping frames\n      that do not differ greatly from the previous frame in order to reduce frame\n      rate, video length and file size.\n    is_expand: true\n    is_required: true\n    summary: Remove sequentially duplicate frames with FFmpeg by dropping frames that\n      do not differ greatly from the previous frame in order to reduce frame rate,\n      video length and file size.\n    title: Remove Duplicate Frames\n    value_options:\n    - \"true\"\n    - \"false\"\n  remove_frames: \"false\"\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: The commands will be sent to the emulator that has the given serial.\n    is_expand: true\n    is_required: true\n    summary: The commands will be sent to the emulator that has the given serial.\n    title: Emulator serial\n"
  },
  {
    "path": "steps/android-screenrecord-stop/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, android emulators no longer support screen recording\nmaintainer: bitrise\nremoval_date: \"2018-09-20\"\n"
  },
  {
    "path": "steps/android-sdk-add-on-installer/0.0.1/step.yml",
    "content": "title: Android SDK Add-on Installer\nsummary: |\n  Step to install an Android SDK Add-on locally\ndescription: |\n  This step will download a specific version of the Android SDK Add-on into the Bitrise VM, allowing apps to build its code linking against this add-on code\nwebsite: https://github.com/FutureWorkshops/bitrise-step-android-sdk-add-on-installer\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-android-sdk-add-on-installer\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-android-sdk-add-on-installer\npublished_at: 2021-04-20T00:04:44.634593+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-android-sdk-add-on-installer.git\n  commit: e57e0115c2e2c2d000ab47d637d1c557429e7ec3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/FutureWorkshops/bitrise-step-android-sdk-add-on-installer\ndeps:\n  brew:\n  - name: go\n  - name: unzip\n  apt_get:\n  - name: golang\n    bin_name: go\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- android_sdk_path: $ANDROID_HOME\n  opts:\n    is_expand: true\n    is_required: true\n    title: Path to the Android SDK folders in the machine\n- add_on_url: null\n  opts:\n    description: |\n      The Android SDK Manager Add-on definition is a XML file that is responsible to define how an extra is added to the\n      $ANDROID_HOME path.\n    is_expand: true\n    is_required: true\n    summary: URL to the android Add-on XML definition\n    title: Add-on URL\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If enabled, the step will calculate the checksum of the downloaded file, based in the type specified in the XML. If the local file\n      do not match the XML data, the step will fail.\n    is_required: true\n    title: Validate downloaded file checksum?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  validate_checksum: \"no\"\noutputs:\n- ADD_ON_SDK_PATH: null\n  opts:\n    summary: Path to the installed SDK\n    title: Local Path of Addon\n"
  },
  {
    "path": "steps/android-sdk-add-on-installer/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/android-sdk-update/1.0.1/step.yml",
    "content": "title: Android SDK Update\nsummary: |-\n  Need to install or update a packge from Android SDK Manager?\n  Use this Step to install and update them as you wish!\ndescription: Install the necessary sdk tools to compile your application\nwebsite: https://github.com/guitcastro/steps-update-sdk\nsource_code_url: https://github.com/guitcastro/steps-update-sdk\nsupport_url: https://github.com/guitcastro/steps-update-sdk/issues\npublished_at: 2015-12-21T18:51:40.042362954-02:00\nsource:\n  git: https://github.com/guitcastro/steps-update-sdk.git\n  commit: 141c81917e966d8674904c042b0e5029c8880152\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- android\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Enable this option to update the Android SDK Tools.\n    summary: \"\"\n    title: Update Android SDK Tools\n    value_options:\n    - \"on\"\n    - \"off\"\n  tools: \"off\"\n- opts:\n    description: Select which version of Android SDK Platform-tools should be installed.\n    is_required: true\n    title: Android SDK Platform-tools version\n    value_options:\n    - stable\n    - preview\n    - both\n    - none\n  platform_tools: none\n- build_tools: \"\"\n  opts:\n    description: |-\n      Comma separated list of all Build-tools versions that should be installed.\n\n      Example: `23.0.2,22.0.1`\n\n      *Leave it empty if you don't want to install any Build tool.*\n    summary: 'Example: 23.0.2,22.0.1'\n    title: Android SDK Build-tools versions\n- opts:\n    description: |-\n      Comma separated list of all platform versions that should be installed.\n\n      Example: `23,22,17`\n\n      *Leave it empty if you don't want to install any SDK version.*\n    summary: 'Example: 23,22,17'\n    title: Android SDK Platform versions\n  sdk_version: \"\"\n- opts:\n    description: |-\n      Comma separated list of all system images that should be installed.\n      Use `android list --all -e` to get the names of all available SystemImages.\n\n      Example: `sys-img-armeabi-v7a-android-tv-23,sys-img-armeabi-v7a-android-22`\n\n      *Leave it empty if you don't want to install any System Image.*\n    summary: 'Example: sys-img-armeabi-v7a-android-tv-23,sys-img-armeabi-v7a-android-22'\n    title: System Images\n  system_images: \"\"\n"
  },
  {
    "path": "steps/android-sdk-update/1.0.2/step.yml",
    "content": "title: Android SDK Update\nsummary: |-\n  Need to install or update a packge from Android SDK Manager?\n  Use this Step to install and update them as you wish!\ndescription: Install the necessary sdk tools to compile your application\nwebsite: https://github.com/guitcastro/steps-update-sdk\nsource_code_url: https://github.com/guitcastro/steps-update-sdk\nsupport_url: https://github.com/guitcastro/steps-update-sdk/issues\npublished_at: 2017-03-18T00:33:48.816322159-03:00\nsource:\n  git: https://github.com/guitcastro/steps-update-sdk.git\n  commit: acc051f9d96d0987d1848b4578c5ed49f2d88b73\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Enable this option to update the Android SDK Tools.\n    summary: \"\"\n    title: Update Android SDK Tools\n    value_options:\n    - \"on\"\n    - \"off\"\n  tools: \"off\"\n- opts:\n    description: Select which version of Android SDK Platform-tools should be installed.\n    is_required: true\n    title: Android SDK Platform-tools version\n    value_options:\n    - stable\n    - preview\n    - both\n    - none\n  platform_tools: none\n- build_tools: \"\"\n  opts:\n    description: |-\n      Comma separated list of all Build-tools versions that should be installed.\n\n      Example: `23.0.2,22.0.1`\n\n      *Leave it empty if you don't want to install any Build tool.*\n    summary: 'Example: 23.0.2,22.0.1'\n    title: Android SDK Build-tools versions\n- opts:\n    description: |-\n      Comma separated list of all platform versions that should be installed.\n\n      Example: `23,22,17`\n\n      *Leave it empty if you don't want to install any SDK version.*\n    summary: 'Example: 23,22,17'\n    title: Android SDK Platform versions\n  sdk_version: \"\"\n- opts:\n    description: |-\n      Comma separated list of all system images that should be installed.\n      Use `android list --all -e` to get the names of all available SystemImages.\n\n      Example: `sys-img-armeabi-v7a-android-tv-23,sys-img-armeabi-v7a-android-22`\n\n      *Leave it empty if you don't want to install any System Image.*\n    summary: 'Example: system-images;android-20;android-wear;x86,system-images;android-20;android-tv;armeabi-v7a'\n    title: System Images\n  system_images: \"\"\n"
  },
  {
    "path": "steps/android-sdk-update/1.0.4/step.yml",
    "content": "title: Android SDK Update\nsummary: |-\n  Need to install or update a packge from Android SDK Manager?\n  Use this Step to install and update them as you wish!\ndescription: Install the necessary sdk tools to compile your application\nwebsite: https://github.com/guitcastro/steps-update-sdk\nsource_code_url: https://github.com/guitcastro/steps-update-sdk\nsupport_url: https://github.com/guitcastro/steps-update-sdk/issues\npublished_at: 2017-05-31T17:19:32.768808446-03:00\nsource:\n  git: https://github.com/guitcastro/steps-update-sdk.git\n  commit: 8cf06500b2b661930672d8e78ecc5fa4935a08fb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Enable this option to update the Android SDK Tools.\n    summary: \"\"\n    title: Update Android SDK Tools\n    value_options:\n    - \"on\"\n    - \"off\"\n  tools: \"off\"\n- opts:\n    description: Select which version of Android SDK Platform-tools should be installed.\n    is_required: true\n    title: Android SDK Platform-tools version\n    value_options:\n    - stable\n    - preview\n    - both\n    - none\n  platform_tools: none\n- build_tools: \"\"\n  opts:\n    description: |-\n      Comma separated list of all Build-tools versions that should be installed.\n\n      Example: `23.0.2,22.0.1`\n\n      *Leave it empty if you don't want to install any Build tool.*\n    summary: 'Example: 23.0.2,22.0.1'\n    title: Android SDK Build-tools versions\n- opts:\n    description: |-\n      Comma separated list of all platform versions that should be installed.\n\n      Example: `23,22,17`\n\n      *Leave it empty if you don't want to install any SDK version.*\n    summary: 'Example: 23,22,17'\n    title: Android SDK Platform versions\n  sdk_version: \"\"\n- opts:\n    description: |-\n      Comma separated list of all system images that should be installed.\n      Use `android list --all -e` to get the names of all available SystemImages.\n\n      Example: `sys-img-armeabi-v7a-android-tv-23,sys-img-armeabi-v7a-android-22`\n\n      *Leave it empty if you don't want to install any System Image.*\n    summary: 'Example: system-images;android-20;android-wear;x86,system-images;android-20;android-tv;armeabi-v7a'\n    title: System Images\n  system_images: \"\"\n"
  },
  {
    "path": "steps/android-sdk-update/1.0.6/step.yml",
    "content": "title: Android SDK Update\nsummary: |-\n  Need to install or update a packge from Android SDK Manager?\n  Use this Step to install and update them as you wish!\ndescription: Install the necessary sdk tools to compile your application\nwebsite: https://github.com/guitcastro/steps-update-sdk\nsource_code_url: https://github.com/guitcastro/steps-update-sdk\nsupport_url: https://github.com/guitcastro/steps-update-sdk/issues\npublished_at: 2017-07-18T16:40:00.250198428-03:00\nsource:\n  git: https://github.com/guitcastro/steps-update-sdk.git\n  commit: fb76af2d0e6137bc09b7c432ce22d119d1f9e754\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Enable this option to update the Android SDK Tools.\n    summary: \"\"\n    title: Update Android SDK Tools\n    value_options:\n    - \"on\"\n    - \"off\"\n  tools: \"off\"\n- opts:\n    description: Select which version of Android SDK Platform-tools should be installed.\n    is_required: true\n    title: Android SDK Platform-tools version\n    value_options:\n    - stable\n    - preview\n    - both\n    - none\n  platform_tools: none\n- build_tools: \"\"\n  opts:\n    description: |-\n      Comma separated list of all Build-tools versions that should be installed.\n\n      Example: `23.0.2,22.0.1`\n\n      *Leave it empty if you don't want to install any Build tool.*\n    summary: 'Example: 23.0.2,22.0.1'\n    title: Android SDK Build-tools versions\n- opts:\n    description: \"Comma separated list of all platform versions that should be installed.\\n\\nExample:\n      `23,22,17`\\n\\n*Leave it empty if you don't want to install any SDK version.*\n      \\     \"\n    summary: 'Example: 23,22,17'\n    title: Android SDK Platform versions\n  sdk_version: \"\"\n- opts:\n    description: |-\n      Comma separated list of all system images that should be installed.\n      Use `android list --all -e` to get the names of all available SystemImages.\n\n      Example: `sys-img-armeabi-v7a-android-tv-23,sys-img-armeabi-v7a-android-22`\n\n      *Leave it empty if you don't want to install any System Image.*\n    summary: 'Example: extras;google;googlee_play_services,extras;google;m2repository,extras;android;m2repository,add-ons;addon-google_apis-google-15,system-images;android-20;android-wear;x86,system-images;android-20;android-tv;armeabi-v7a'\n    title: System Images and others\n  system_images: \"\"\n"
  },
  {
    "path": "steps/android-sdk-update/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/android-unit-test/0.10.0/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2019-05-10T15:12:00.52861022Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 55470cf914e07f5bfffe25f5d73cb72dfdffff3e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n"
  },
  {
    "path": "steps/android-unit-test/0.11.0/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2019-05-31T13:20:45.384381408Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 428918d36f02330b62c83cdbe2e968784e9dac1b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/0.11.1/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2019-06-04T15:36:08.714263749Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: dd2535d711f8515202beb3f02ef43c9b2c268b5b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/0.9.0/step.yml",
    "content": "title: Android Unit Test\nsummary: Runs your Android project's unit tests.\ndescription: Runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: !!timestamp 2018-04-04T12:46:14.69292473+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 7c41a81d35e8d3d8502b7a25a2028ed723e0ca23\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- opts:\n    category: Export Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Export Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n"
  },
  {
    "path": "steps/android-unit-test/0.9.2/step.yml",
    "content": "title: Android Unit Test\nsummary: Runs your Android project's unit tests.\ndescription: Runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2018-04-23T10:14:43.932928818+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 3d89f92d6f4cff8aa2a07de986cfdd7935eb69a8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n"
  },
  {
    "path": "steps/android-unit-test/0.9.3/step.yml",
    "content": "title: Android Unit Test\nsummary: Runs your Android project's unit tests.\ndescription: Runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2018-05-23T15:26:42.968819074+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: f8d54c03abe3e2b09c3ec11d71c8dfa45b6e181c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'The root directory of your android project, e.g.: where your root\n      build gradle file exist (also gradlew, settings.gradle, etc...)'\n    is_required: true\n    summary: 'The root directory of your android project, e.g.: where your root build\n      gradle file exist (also gradlew, settings.gradle, etc...)'\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules please open your project in Android Studio and go in [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants please open your project in Android Studio and go in [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n"
  },
  {
    "path": "steps/android-unit-test/0.9.4/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2018-10-24T10:26:11.028083639Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: ab10871cdde264bd3716ebc7ffadb944784e2f70\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n"
  },
  {
    "path": "steps/android-unit-test/0.9.5/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2018-10-29T11:49:53.412800334Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: b066992f1bb47fbcd9c2d17c7be772f3966fdf19\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n"
  },
  {
    "path": "steps/android-unit-test/0.9.6/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2019-03-14T14:58:18.911376758Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: d2fd457bb55fbb962c10392ce323f51085b7c2af\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: Will find the report dir with the given pattern.\n    is_required: true\n    summary: Will find the report dir with the given pattern.\n    title: Report location pattern\n  report_path_pattern: '*build/reports'\n- opts:\n    category: Options\n    description: Will find test-results dir with the given pattern.\n    is_required: true\n    summary: Will find the test-results dir with the given pattern.\n    title: Test results location pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n"
  },
  {
    "path": "steps/android-unit-test/1.0.0/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2019-08-30T13:17:52.665032945Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 9d5c1d4e8630a28a5d0d4a23fd29f15b02d45d75\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.0.1/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2020-04-24T21:04:02.756435284Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 76e5f6b0dd8d00ccae20a010cd44a6f80716bd11\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.0.2/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2020-09-02T10:00:21.25275027Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 0fa88871b67a43bf43d31e6cf6d37729559f375e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    is_required: false\n    summary: |\n      Set the module that you want to test. To see your available modules, please open your project in Android Studio and go to [Project Structure] and see the list on the left.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    is_required: false\n    summary: |\n      Set the variant that you want to test. To see your available variants, please open your project in Android Studio and go to [Project Structure] -> variants section.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.0.3/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2021-04-07T07:46:54.862092587Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: f9e6c6cf664ff7b4e2a02b8cfac5297b63bc6fde\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: \"Set the module that you want to test.  \\nTo see your available modules,\n      please open your project in Android Studio, go to **Project Structure** and\n      see the list on the left.  \\nLeave this input blank to test all modules.\\n\"\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: \"Set the variant that you want to test.  \\nTo see your available\n      variants, please open your project in Android Studio, go to **Project Structure**,\n      then to the **variants** section.  \\nLeave this input blank to test all variants.\\n\"\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.0.4/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2021-05-28T08:33:46.788663638Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 15e66bf3dd9cc5cf7fd3e53043dee229edbca28c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: \"Set the module that you want to test.  \\nTo see your available modules,\n      please open your project in Android Studio, go to **Project Structure** and\n      see the list on the left.  \\nLeave this input blank to test all modules.\\n\"\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: \"Set the variant that you want to test.  \\nTo see your available\n      variants, please open your project in Android Studio, go to **Project Structure**,\n      then to the **variants** section.  \\nLeave this input blank to test all variants.\\n\"\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.0.5/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2021-11-09T13:17:14.597945447Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: ca1455796fbb1e09325b4ad910b197a91935dc6c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: \"Set the module that you want to test.  \\nTo see your available modules,\n      please open your project in Android Studio, go to **Project Structure** and\n      see the list on the left.  \\nLeave this input blank to test all modules.\\n\"\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: \"Set the variant that you want to test.  \\nTo see your available\n      variants, please open your project in Android Studio, go to **Project Structure**,\n      then to the **variants** section.  \\nLeave this input blank to test all variants.\\n\"\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.0.6/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2022-02-23T08:18:53.194059419Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: f6fe0b870df5c43925cc713c2ea72a08f792149b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: \"Set the module that you want to test.  \\nTo see your available modules,\n      please open your project in Android Studio, go to **Project Structure** and\n      see the list on the left.  \\nLeave this input blank to test all modules.\\n\"\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: \"Set the variant that you want to test.  \\nTo see your available\n      variants, please open your project in Android Studio, go to **Project Structure**,\n      then to the **variants** section.  \\nLeave this input blank to test all variants.\\n\"\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test HTML\n      results__.  \\nThe whole HTML results directory will be zipped and moved to the\n      `$BITRISE_DEPLOY_DIR`.\\n\\nYou need to override this input if you have custom\n      output dir set for Local unit test HTML results.  \\nThe pattern needs to be\n      relative to the selected module's directory.\\n\\nExample 1: app module and debug\n      variant is selected and the HTML report is generated at:\\n\\n- `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n\\nthis\n      case use: `*build/reports/tests/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the HTML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/reports/tests` pattern.\"\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: \"The step will use this pattern to export __Local unit test XML results__.\n      \\ \\nThe whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      \\ \\nand the result files will be deployed to the Ship Addon.\\n\\nYou need to\n      override this input if you have custom output dir set for Local unit test XML\n      results.  \\nThe pattern needs to be relative to the selected module's directory.\\n\\nExample\n      1: app module and debug variant is selected and the XML report is generated\n      at:\\n\\n- `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n\\nthis\n      case use: `*build/test-results/testDebugUnitTest` pattern.\\n\\nExample 2: app\n      module and NO variant is selected and the XML reports are generated at:\\n\\n-\n      `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\\n- `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\\n\\nto\n      export every variant's reports use: `*build/test-results` pattern.\"\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- cache_level: only_deps\n  opts:\n    category: Options\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/android-unit-test/1.1.0/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2025-08-04T07:39:40.000403613Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 3019f21819f5599f801025e3f507735c97af9722\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/1.2.0/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2025-09-30T13:45:03.70192349Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 41045b1268ad551dfdcf97442108bc0c1b019f43\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/1.2.1/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2025-11-10T13:52:40.678714154Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 612d8564242be44d7b4c886129f8f97bdc86034a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/1.2.2/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2026-02-02T11:14:49.745543538Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 72f46d000aed21753f9c2b43eddecb7445b01ddc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/1.2.3/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2026-02-13T14:53:26.157019013Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 4b799ec38fa555acf295ff0ed17b46962def2671\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/android-unit-test/1.2.3/bin/android-unit-test-darwin-amd64\n    hash: sha256-5d38d4d3ca4f58e92d59e4aad339197a47b91eaa6a06b8bb956acf7d3c199054\n  darwin-arm64:\n    storage_uri: steps/android-unit-test/1.2.3/bin/android-unit-test-darwin-arm64\n    hash: sha256-dde38c8fa7032a6d2383aa0eb189e226dfc8576fe1dd21e7e3c7e554bb09f504\n  linux-amd64:\n    storage_uri: steps/android-unit-test/1.2.3/bin/android-unit-test-linux-amd64\n    hash: sha256-1d9d945effb24303aebdad75896fbd4703670ba8ebaeaaaad004d8050017877d\n  linux-arm64:\n    storage_uri: steps/android-unit-test/1.2.3/bin/android-unit-test-linux-arm64\n    hash: sha256-41f87a2ebac9b43c46d72a96ae38d50665b8624e85298a5efafecde649f82c3c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/1.2.4/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2026-03-09T13:27:51.153207087Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 7fe00a907b7db49a1685496bbe1f466dac402a92\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/android-unit-test/1.2.4/bin/android-unit-test-darwin-amd64\n    hash: sha256-2e455a3aa3e5593c3406af975ae71bc139d624b3b6953e36c334a046821bac95\n  darwin-arm64:\n    storage_uri: steps/android-unit-test/1.2.4/bin/android-unit-test-darwin-arm64\n    hash: sha256-fef43e5a7f1fc7fad8a56e2842021483e854681fdd1042610ebe5bced635f719\n  linux-amd64:\n    storage_uri: steps/android-unit-test/1.2.4/bin/android-unit-test-linux-amd64\n    hash: sha256-8353f606f8e0100766621fbe4575906b8a6a66b6678dcb2c677b7573c8917c8f\n  linux-arm64:\n    storage_uri: steps/android-unit-test/1.2.4/bin/android-unit-test-linux-arm64\n    hash: sha256-35c7f6e1c60f7510df739d86bd7bb9915de14817c7b35acc520f8b9af4305464\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/1.2.5/step.yml",
    "content": "title: Android Unit Test\nsummary: This step runs your Android project's unit tests.\ndescription: This step runs your Android project's unit tests.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-android-unit-test/issues\npublished_at: 2026-03-26T13:12:13.575411912Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-android-unit-test.git\n  commit: 805f654006f2939d9a28d9370b4f66fc53dc7a56\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/android-unit-test/1.2.5/bin/android-unit-test-darwin-amd64\n    hash: sha256-d77edd0cd6464322bdc9a607c8d403763c7422933b8676bb9b69e1d23a4defe6\n  darwin-arm64:\n    storage_uri: steps/android-unit-test/1.2.5/bin/android-unit-test-darwin-arm64\n    hash: sha256-7565e4168e29ce65dd971d0f0d493cf53ea547678f2dd4a38fca9d1ab8db42a3\n  linux-amd64:\n    storage_uri: steps/android-unit-test/1.2.5/bin/android-unit-test-linux-amd64\n    hash: sha256-87837c5ee3e977d2617654ea51614c505d8c80526aec6a84f28f413fd6827a7a\n  linux-arm64:\n    storage_uri: steps/android-unit-test/1.2.5/bin/android-unit-test-linux-arm64\n    hash: sha256-8b92df152b8a4ee86fa348a930c6d44fcdd5c9ddfa8f8e5b32126e1bc1187f61\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-android-unit-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root directory of your android project, for example, where your\n      root build gradle file exists (also gradlew, settings.gradle, etc...)\n    is_required: true\n    summary: The root directory of your android project, for example, where your root\n      build gradle file exists (also gradlew, settings.gradle, etc...)\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- module: \"\"\n  opts:\n    description: |\n      Set the module that you want to test.\n      To see your available modules, please open your project in Android Studio, go to **Project Structure** and see the list on the left.\n      Leave this input blank to test all modules.\n    is_required: false\n    summary: |\n      Set the module that you want to test.\n    title: Module\n- opts:\n    description: |\n      Set the variant that you want to test.\n      To see your available variants, please open your project in Android Studio, go to **Project Structure**, then to the **variants** section.\n      Leave this input blank to test all variants.\n    is_required: false\n    summary: |\n      Set the variant that you want to test.\n    title: Variant\n  variant: \"\"\n- arguments: null\n  opts:\n    category: Options\n    description: Extra arguments passed to the gradle task\n    is_required: false\n    summary: Extra arguments passed to the gradle task\n    title: Additional Gradle Arguments\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test HTML results__.\n      The whole HTML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`.\n\n      You need to override this input if you have custom output dir set for Local unit test HTML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the HTML report is generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n\n      this case use: `*build/reports/tests/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the HTML reports are generated at:\n\n      - `<path_to_your_project>/app/build/reports/tests/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/reports/tests/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/reports/tests` pattern.\n    is_required: true\n    title: Local unit test HTML result directory pattern\n  report_path_pattern: '*build/reports/tests'\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export __Local unit test XML results__.\n      The whole XML results directory will be zipped and moved to the `$BITRISE_DEPLOY_DIR`\n      and the result files will be deployed to the Ship Addon.\n\n      You need to override this input if you have custom output dir set for Local unit test XML results.\n      The pattern needs to be relative to the selected module's directory.\n\n      Example 1: app module and debug variant is selected and the XML report is generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n\n      this case use: `*build/test-results/testDebugUnitTest` pattern.\n\n      Example 2: app module and NO variant is selected and the XML reports are generated at:\n\n      - `<path_to_your_project>/app/build/test-results/testDebugUnitTest`\n      - `<path_to_your_project>/app/build/test-results/testReleaseUnitTest`\n\n      to export every variant's reports use: `*build/test-results` pattern.\n    is_required: true\n    title: Local unit test XML result directory pattern\n  result_path_pattern: '*build/test-results'\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/android-unit-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/apispotter-test-runner/0.0.1/step.yml",
    "content": "title: ApiSpotter Test Group Runner\nsummary: |\n  Run your ApiSpotter tests and get the test result to your Bitrise build.\ndescription: |\n  ApiSpotter (https://apispotter.com) is an online tool for testing, monitoring and documenting your API systems.\n  It makes you sure that your API's are up and running as they should.\n\n  Use this step to run your test groups on APISpotter and retrieve their results.\n  Make sure your API's are working before build complete.\nwebsite: https://github.com/loopdigital/bitrise-step-apispotter-test-runner\nsource_code_url: https://github.com/loopdigital/bitrise-step-apispotter-test-runner\nsupport_url: https://github.com/loopdigital/bitrise-step-apispotter-test-runner/issues\npublished_at: 2018-08-16T14:55:41.386017695+03:00\nsource:\n  git: https://github.com/loopdigital/bitrise-step-apispotter-test-runner.git\n  commit: 8ece866dd6372940318520b97d430b928e8135b5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apispotter_api_token: null\n  opts:\n    description: |\n      Your user API token from ApiSpotter.\n      You can get it from your account settings page.\n    is_expand: true\n    is_required: true\n    title: ApiSpotter User API Token\n- apispotter_test_group_id: null\n  opts:\n    description: |\n      The ID of the test group you would like to run.\n    is_expand: true\n    is_required: true\n    title: Test Group ID\n- abort_build: \"no\"\n  opts:\n    description: \"Abort the current build if we detect that your API's having some\n      troubles.\\n\\nWith this option set to 'no', build will not be aborted if the\n      test result is false, it will only abort when a fatal error occur. (Like internal\n      errors or exceptions, if we can't run the test group.) \\nIf you set this option\n      to 'yes', build will be aborted when the retrieved test result is false too.\n      \\n\"\n    summary: Abort the current build if we detect that your API's having some troubles.\n    title: Abort The Current Build\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- AS_RUN_RESULT: null\n  opts:\n    description: |\n      Boolean value of the requested test group run result.\n    title: Test Group Run Result\n- AS_ERROR_MESSAGE: null\n  opts:\n    description: \"If any type of error occurs in the process, you can retrieve the\n      error message with this variable. \\n\"\n    title: Error Message\n"
  },
  {
    "path": "steps/apispotter-test-runner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/apk-info/1.0.4/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2016-10-19T15:35:00.882498804+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 104e26a8800fc9363658b5837cf4747e5f26b032\nproject_type_tags:\n- android\ntype_tags:\n- android\n- apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.1.0/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2016-10-20T09:55:26.379142783+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: d38bd460cc5070d16885ece2eceb96184e8cd3ef\nproject_type_tags:\n- android\ntype_tags:\n- android\n- apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.1.1/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2016-10-20T16:15:52.183384837+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 6079303ef24037208fb6437ecd6af1f4ea4bd439\nproject_type_tags:\n- android\ntype_tags:\n- android\n- apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.2.0/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2017-01-03T20:39:11.298726262+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: ea19668e5088dc517d5631941026347e78e7173f\nproject_type_tags:\n- android\ntype_tags:\n- android\n- apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.2.1/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2017-01-04T10:06:25.318699526+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 9dda88ddbea00c03deb973576f716abbf1c55e9e\nproject_type_tags:\n- android\ntype_tags:\n- android\n- apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.2.2/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2017-01-13T15:44:35.290816965+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 053af0b89c101ab87de1db9fd70d9b78430974ce\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- \"artifact info\"\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.2.3/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2017-06-29T10:57:06.839233486+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 8aa691f70c60416b3c3d30002797a3775875a351\nproject_type_tags:\n- android\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.3.0/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2017-08-18T13:28:30.970744569+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: db6870adc885e1eb25433a1ef6a5e7b3081b7f20\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.0/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2018-02-03T21:09:29.224001+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 5d5d3cd0155b868cf10a754adf4cbb7aee461dba\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.1/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2018-08-27T08:46:03.274386929+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 7b402d3fcf60cd844a4641dfc248c8868e036a10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.2/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2018-09-12T09:40:47.241293411+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 57774f6c167a3db9d0b4ef1eb412bbb92221eb29\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.4/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2019-04-17T15:07:28.566349757+02:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-apk-info.git\n  commit: 50026bd18253adca731b5b752cfbb01082081c23\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.5/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2020-04-16T09:44:38.920347+02:00\nsource:\n  git: https://github.com/futuredapp/bitrise-step-apk-info.git\n  commit: fce22a7a9cbf3c4c42e1afff1032c8d8981edacc\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.6/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2021-06-02T20:24:31.688097+02:00\nsource:\n  git: https://github.com/futuredapp/bitrise-step-apk-info.git\n  commit: 2897c74e1af045467695842ff1d84622848d9079\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/1.4.7/step.yml",
    "content": "title: APK info\nsummary: APK Android info provider\ndescription: Provides all possible Android APK information as package name, version\n  name or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-apk-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-apk-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues\npublished_at: 2025-12-01T11:27:03.389818+01:00\nsource:\n  git: https://github.com/futuredapp/bitrise-step-apk-info.git\n  commit: fab654713ec1327dc68106bbf023a35e1f01ebd3\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      File path to APK file to get info from.\n    is_required: true\n    title: APK file path\noutputs:\n- ANDROID_APP_PACKAGE_NAME: null\n  opts:\n    description: Android application package name, ex. com.package.my\n    title: Android application package name\n- ANDROID_APK_FILE_SIZE: null\n  opts:\n    description: Android APK file size, in bytes\n    title: Android APK file size\n- ANDROID_APP_NAME: null\n  opts:\n    description: Android application name from APK\n    title: Android application name\n- ANDROID_APP_VERSION_NAME: null\n  opts:\n    description: Android application version name from APK, ex. 1.0.0\n    title: Android application version name\n- ANDROID_APP_VERSION_CODE: null\n  opts:\n    description: Android application version code from APK, ex. 10\n    title: Android application version code\n- ANDROID_ICON_PATH: null\n  opts:\n    description: File path to android application icon\n    title: File path to icon\n"
  },
  {
    "path": "steps/apk-info/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/app-center-launch-test-android/1.0.0/step.yml",
    "content": "title: App Center Launch Test Android\nsummary: |\n  Run App Center launch test for android\ndescription: |\n  Verify that your build works on a real device by running a launch test on a real device\nwebsite: https://github.com/tomcurran/bitrise-step-app-center-launch-test-android\nsource_code_url: https://github.com/tomcurran/bitrise-step-app-center-launch-test-android\nsupport_url: https://github.com/tomcurran/bitrise-step-app-center-launch-test-android/issues\npublished_at: 2018-01-28T12:01:08.598154Z\nsource:\n  git: https://github.com/tomcurran/bitrise-step-app-center-launch-test-android.git\n  commit: 818a3fc0a61c2de7e1ecdd06570365f86dd51a30\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: npm\n  apt_get:\n  - name: npm\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      App file path, for example to an APK file for Android.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: App path\n- app_center_app: $APP_CENTER_APP\n  opts:\n    description: |\n      Get all available apps using cli \"appcenter apps list\".\n    is_expand: true\n    is_required: true\n    summary: username/app_name or org/app_name\n    title: App Center app\n- app_center_token: $APP_CENTER_TOKEN\n  opts:\n    description: |\n      Create API token using cli \"appcenter tokens create\".\n    is_expand: true\n    is_required: true\n    summary: App Ceneter APK token with access to app specified in app_center_app\n    title: App Center API token\n"
  },
  {
    "path": "steps/app-center-launch-test-android/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/app-gallery-deploy/1.0.0/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: |\n  Uploads APK to Huawei App Gallery\ndescription: |\n  This step is based on [Huawei Publishing API](https://developer.huawei.com/consumer/en/service/hms/catalog/AGCConnectAPI.html?page=hmssdk_appGalleryConnect_getstarted)\nwebsite: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution\nsource_code_url: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution\nsupport_url: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution/issues\npublished_at: 2020-01-20T13:19:43.423533+01:00\nsource:\n  git: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution.git\n  commit: f79d0b1208466246453a8edada218b4eba556775\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: Path to generated APK file to deploy.\n    is_expand: true\n    is_required: true\n    title: APK path\n- huawei_filename: build_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    description: Unique name of APK file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    description: App ID can be found in App information tab.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    description: Client ID generated in `Users and permissions -> Api Key -> AppGalleryConnect\n      API`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    description: Client Secret generated in `Users and permissions -> Api Key -> AppGalleryConnect\n      API`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Client Secret\n- lang: en-EN\n  opts:\n    description: For more languages refer to [Language Types](https://developer.huawei.com/consumer/en/service/hms/catalog/AGCConnectAPI.html?page=hmssdk_appGalleryConnect_api_reference_language_type)\n    is_expand: true\n    is_required: true\n    title: Language Type\n"
  },
  {
    "path": "steps/app-gallery-deploy/1.0.1/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: |\n  Uploads APK to Huawei App Gallery\ndescription: |\n  This step is based on [Huawei Publishing API](https://developer.huawei.com/consumer/en/service/hms/catalog/AGCConnectAPI.html?page=hmssdk_appGalleryConnect_getstarted)\nwebsite: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution\nsource_code_url: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution\nsupport_url: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution/issues\npublished_at: 2020-07-14T13:09:41.3999029+02:00\nsource:\n  git: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution.git\n  commit: dc099afb0e871eea5c70dff738cb6e401e3fbe9c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK file to deploy.\n    is_expand: true\n    is_required: true\n    title: APK path\n- huawei_filename: build_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in App information tab.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `Users and permissions -> Api Key -> AppGalleryConnect\n      API`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Client Secret generated in `Users and permissions -> Api Key -> AppGalleryConnect\n      API`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Client Secret\n- lang: en-EN\n  opts:\n    category: Config\n    description: For more languages refer to [Language Types](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-reference-langtype)\n    is_expand: true\n    is_required: true\n    title: Language Type\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/app-gallery-deploy/1.1.0/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: |\n  Uploads APK/AAB to Huawei App Gallery\ndescription: |\n  This step is based on [Huawei Publishing API](https://developer.huawei.com/consumer/en/service/hms/catalog/AGCConnectAPI.html?page=hmssdk_appGalleryConnect_getstarted)\nwebsite: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution\nsource_code_url: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution\nsupport_url: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution/issues\npublished_at: 2020-07-23T09:18:35.3690867+02:00\nsource:\n  git: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution.git\n  commit: d0541f53aa8b4bd6895e69b8f6ac0ddff03a775a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: build_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in App information tab.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `Users and permissions -> Api Key -> AppGalleryConnect\n      API`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Client Secret generated in `Users and permissions -> Api Key -> AppGalleryConnect\n      API`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Client Secret\n- lang: en-EN\n  opts:\n    category: Config\n    description: For more languages refer to [Language Types](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-reference-langtype)\n    is_expand: true\n    is_required: true\n    title: Language Type\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/app-gallery-deploy/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/app-ray-mobile-security/1.3.9/step.yml",
    "content": "title: App-Ray Mobile Security\nsummary: |\n  Mobile application security testing with App-Ray's engine via API\ndescription: |\n  Fully automated mobile application security testing identifies vulnerabilities, mitigate risks, comply with regulations whether you are developer, CISO, CEO.\nwebsite: https://app-ray.co/\nsource_code_url: https://github.com/App-Ray/bitrise-step-app-ray-mobile-security\nsupport_url: https://github.com/App-Ray/bitrise-step-app-ray-mobile-security/issues\npublished_at: 2021-01-11T19:17:36.637764711+01:00\nsource:\n  git: https://github.com/App-Ray/bitrise-step-app-ray-mobile-security.git\n  commit: dd94f3e7af0b91ebdd0f12a8cc594449729fa1cd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- base_url: null\n  opts:\n    description: |-\n      Your App-Ray base URL\n      Example https://demo.app-ray.co/\n      URL MUST end with /\n    is_required: true\n    summary: \"Your App-Ray base URL \\nExample https://demo.app-ray.co/\"\n    title: AppRay instance base URL\n- app_path: null\n  opts:\n    description: Path to the app file you want to upload, generated by Bitrise, usually\n      like $BITRISE\\_APK\\_PATH or $BITRISE\\_IPA\\_PATH. AAB is also supported\n    is_expand: true\n    is_required: true\n    summary: The app file you want to upload, usually like $BITRISE\\_APK\\_PATH or\n      $BITRISE\\_IPA\\_PATH\n    title: APK, AAB or IPA file path\n- appray_api_token: null\n  opts:\n    description: Your App-Ray authentication token, it can be a one time token or\n      a permanent token\n    is_required: true\n    is_sensitive: true\n    summary: App-Ray API authentication token\n    title: App-Ray API token\n- opts:\n    description: Score from 0 to 100\n    is_required: true\n    summary: |-\n      Risk Score treshold of which to decide if the analysis was succesful on the application\n      Value 0-100, where 100 is the highest risk\n    title: Risk Score treshold\n  score_treshold: null\n- opts:\n    category: Options\n    description: |-\n      The step will use this pattern to export security analysis XML results.\n      The pattern needs to be relative to the selected module's directory.\n      The pattern MUST end with /\n    is_expand: true\n    is_required: false\n    summary: Step will use this directory pattern to export test XML results. If left\n      blank no results will be saved\n    title: Test XML result directory pattern\n  result_path: '*build/test-results/'\noutputs:\n- APP_RAY_RISK_SCORE: null\n  opts:\n    description: |\n      Analysis result risk score\n    summary: App-Ray analysis result risk score\n    title: App-Ray Risk Score\n"
  },
  {
    "path": "steps/app-ray-mobile-security/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/appaloosa/1.0.0/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS IPA to Appaloosa-Store.\n\n  Required: an Xcode Archive Step should run before this Step!\n\n  This step requires an Appaloosa-Store account or an email address to create your account\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2015-10-26T09:49:37.761092326+01:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: 7a549a1dcfc8c6b9961d59c3fd4e76a911a5b389\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- appaloosa\n- appaloosa-store\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the variable of your IPA path on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA PATH\n- opts:\n    description: |-\n      ***Only if you haven't created an account on Appaloosa yet.***\n\n      You'll receive an email with your credentials to access your private store.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: If you don't have an account we'll automatically create one for you.\n      At the end of the step you'll receive an email with your credentials to access\n      your store, and install your application. For all future runs of this step,\n      remove your email address and setup this step as a registered user.\n    title: User Email Address\n  user_email: null\n- appaloosa_api_key: null\n  opts:\n    description: '***Only if you are already registered on Appaloosa***'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is your unique Appaloosa API Key that can be found in your user's\n      profile on Appaloosa\n    title: User API Key\n- opts:\n    description: |-\n      ***Only if you are already registered on Appaloosa***\n\n      This is the store id of the store you want your application uploaded to.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description or changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- group_ids: null\n  opts:\n    description: |-\n      ***Only for registered users. ***\n\n      Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs\n"
  },
  {
    "path": "steps/appaloosa/1.1.0/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS IPA to Appaloosa-Store.\n\n  Required: an Xcode Archive Step should run before this Step!\n\n  This step requires an Appaloosa-Store account or an email address to create your account\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2015-12-07T18:46:02.426518391+01:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: ab2f0a9f075027d3b25d44f1b66da1ac66fb25e3\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- appaloosa\n- appaloosa-store\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the variable of your IPA path on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA PATH\n- opts:\n    description: |-\n      ***Only if you haven't created an account on Appaloosa yet.***\n\n      You'll receive an email with your credentials to access your private store.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: If you don't have an account we'll automatically create one for you.\n      At the end of the step you'll receive an email with your credentials to access\n      your store, and install your application. For all future runs of this step,\n      remove your email address and setup this step as a registered user.\n    title: User Email Address\n  user_email: null\n- appaloosa_api_key: null\n  opts:\n    description: '***Only if you are already registered on Appaloosa***'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is your unique Appaloosa API Key that can be found in your user's\n      profile on Appaloosa\n    title: User API Key\n- opts:\n    description: |-\n      ***Only if you are already registered on Appaloosa***\n\n      This is the store id of the store you want your application uploaded to.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description or changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- group_ids: null\n  opts:\n    description: |-\n      ***Only for registered users. ***\n\n      Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs\n"
  },
  {
    "path": "steps/appaloosa/1.2.0/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS IPA to Appaloosa-Store.\n\n  Required: an Xcode Archive Step should run before this Step!\n\n  This step requires an Appaloosa-Store account or an email address to create your account\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2016-10-13T14:27:48.012057922+02:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: daa18c207fb0a6c00cd586fd071bc559c1a6946a\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- appaloosa\n- appaloosa-store\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the variable of your IPA path on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA PATH\n- opts:\n    description: |-\n      ***Only if you haven't created an account on Appaloosa yet.***\n\n      You'll receive an email with your credentials to access your private store.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: If you don't have an account we'll automatically create one for you.\n      At the end of the step you'll receive an email with your credentials to access\n      your store, and install your application. For all future runs of this step,\n      remove your email address and setup this step as a registered user.\n    title: User Email Address\n  user_email: null\n- appaloosa_api_key: null\n  opts:\n    description: '***Only if you are already registered on Appaloosa***'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is your unique Appaloosa API Key that can be found in your user's\n      profile on Appaloosa\n    title: User API Key\n- opts:\n    description: |-\n      ***Only if you are already registered on Appaloosa***\n\n      This is the store id of the store you want your application uploaded to.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- changelog: null\n  opts:\n    description: Changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the changelog for your application. You can have a different\n      changelog for each version for your application.\n    title: Changelog\n- group_ids: null\n  opts:\n    description: |-\n      ***Only for registered users. ***\n\n      Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs\n"
  },
  {
    "path": "steps/appaloosa/1.2.1/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS IPA to Appaloosa-Store.\n\n  Required: an Xcode Archive Step should run before this Step!\n\n  This step requires an Appaloosa-Store account or an email address to create your account\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2016-10-14T14:24:27.089688+02:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: a15d9815b44e8d33269778e3c67cef60934b49a2\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- appaloosa\n- appaloosa-store\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the variable of your IPA path on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA PATH\n- opts:\n    description: |-\n      ***Only if you haven't created an account on Appaloosa yet.***\n\n      You'll receive an email with your credentials to access your private store.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: If you don't have an account we'll automatically create one for you.\n      At the end of the step you'll receive an email with your credentials to access\n      your store, and install your application. For all future runs of this step,\n      remove your email address and setup this step as a registered user.\n    title: User Email Address\n  user_email: null\n- appaloosa_api_key: null\n  opts:\n    description: '***Only if you are already registered on Appaloosa***'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is your unique Appaloosa API Key that can be found in your user's\n      profile on Appaloosa\n    title: User API Key\n- opts:\n    description: |-\n      ***Only if you are already registered on Appaloosa***\n\n      This is the store id of the store you want your application uploaded to.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- changelog: null\n  opts:\n    description: Changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the changelog for your application. You can have a different\n      changelog for each version for your application.\n    title: Changelog\n- group_ids: null\n  opts:\n    description: |-\n      ***Only for registered users. ***\n\n      Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs\n"
  },
  {
    "path": "steps/appaloosa/1.2.3/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS IPA to Appaloosa-Store.\n\n  Required: an Xcode Archive Step should run before this Step!\n\n  This step requires an Appaloosa-Store account or an email address to create your account\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2016-10-19T13:12:18.714797437+02:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: 38d2d6132fc1365c3650159a758bf495305372fe\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- appaloosa\n- appaloosa-store\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the variable of your IPA path on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA PATH\n- opts:\n    description: |-\n      ***Only if you haven't created an account on Appaloosa yet.***\n\n      You'll receive an email with your credentials to access your private store.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: If you don't have an account we'll automatically create one for you.\n      At the end of the step you'll receive an email with your credentials to access\n      your store, and install your application. For all future runs of this step,\n      remove your email address and setup this step as a registered user.\n    title: User Email Address\n  user_email: null\n- appaloosa_api_key: null\n  opts:\n    description: '***Only if you are already registered on Appaloosa***'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is your unique Appaloosa API Key that can be found in your user's\n      profile on Appaloosa\n    title: User API Key\n- opts:\n    description: |-\n      ***Only if you are already registered on Appaloosa***\n\n      This is the store id of the store you want your application uploaded to.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- changelog: null\n  opts:\n    description: Changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the changelog for your application. You can have a different\n      changelog for each version for your application.\n    title: Changelog\n- group_ids: null\n  opts:\n    description: |-\n      ***Only for registered users. ***\n\n      Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs\n"
  },
  {
    "path": "steps/appaloosa/1.3.0/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS .ipa or Android .apk to Appaloosa-Store.\n\n  Required:\n    For iOS: an Xcode Archive Step should run before this Step!\n    For Android: an apk should exist\n\n  This step requires an Appaloosa-Store account or an email address to create your account\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2016-11-15T15:00:39.505566497+01:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: 30664f05e6f05ae94d5d0f448835a5000c3a412e\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the path to your binary on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BINARY PATH\n- opts:\n    description: |-\n      ***Only if you haven't created an account on Appaloosa yet.***\n\n      You'll receive an email with your credentials to access your private store.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: If you don't have an account we'll automatically create one for you.\n      At the end of the step you'll receive an email with your credentials to access\n      your store, and install your application. For all future runs of this step,\n      remove your email address and setup this step as a registered user.\n    title: User Email Address\n  user_email: null\n- appaloosa_api_key: null\n  opts:\n    description: '***Only if you are already registered on Appaloosa***'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is your unique Appaloosa API Key that can be found in your user's\n      profile on Appaloosa\n    title: User API Key\n- opts:\n    description: |-\n      ***Only if you are already registered on Appaloosa***\n\n      This is the store id of the store you want your application uploaded to.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- changelog: null\n  opts:\n    description: Changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the changelog for your application. You can have a different\n      changelog for each version for your application.\n    title: Changelog\n- group_ids: null\n  opts:\n    description: |-\n      ***Only for registered users. ***\n\n      Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs\n"
  },
  {
    "path": "steps/appaloosa/1.4.0/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS .ipa or Android .apk to Appaloosa-Store.\n\n  Required:\n    For iOS: an ipa should have been generated before running this step.\n    For Android: an apk should have been generated before running this step.\n\n  This step requires an Appaloosa-Store account.\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2016-11-15T15:00:39.505566497+01:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: 30664f05e6f05ae94d5d0f448835a5000c3a412e\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the path to your binary on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BINARY PATH\n- appaloosa_api_key: null\n  opts:\n    description: 'This is your unique Appaloosa API Key that can be found in your settings'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: You can find this value in your store settings\n    title: User API Key\n- opts:\n    description: 'This is the store id of the store you want your application uploaded to.'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- changelog: null\n  opts:\n    description: Changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the changelog for your application. You can have a different\n      changelog for each version for your application.\n    title: Changelog\n- group_ids: null\n  opts:\n    description: 'Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs"
  },
  {
    "path": "steps/appaloosa/1.5.0/step.yml",
    "content": "title: Publish to Appaloosa Store\nsummary: This step allows you to publish your application to your private app store\n  on Appaloosa Store\ndescription: |\n  Bitrise Step to Deploy an iOS .ipa or Android (.apk, .aab) to Appaloosa-Store.\n\n  Required:\n    For iOS: an ipa should have been generated before running this step.\n    For Android: an apk or aab should have been generated before running this step.\n\n  This step requires an Appaloosa-Store account.\nwebsite: https://www.appaloosa-store.com\nsource_code_url: https://github.com/appaloosa-store/bitrise_appaloosa\nsupport_url: https://github.com/appaloosa-store/bitrise_appaloosa/issues\npublished_at: 2016-11-15T15:00:39.505566497+01:00\nsource:\n  git: https://github.com/appaloosa-store/bitrise_appaloosa.git\n  commit: 2d776f2b7bc7a87f5f3e0a95b0ac6480d6e0ddf9\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: This is the path to your binary on Bitrise\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: BINARY PATH\n- appaloosa_api_key: null\n  opts:\n    description: 'This is your unique Appaloosa API Key that can be found in your settings'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: You can find this value in your store settings\n    title: User API Key\n- opts:\n    description: 'This is the store id of the store you want your application uploaded to.'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can find this value in your store settings\n    title: Store ID\n  store_id: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your first screenshot\n    title: SCREENSHOT 1\n  screenshot1: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your second screenshot\n    title: SCREENSHOT 2\n  screenshot2: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your third screenshot\n    title: SCREENSHOT 3\n  screenshot3: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fourth screenshot\n    title: SCREENSHOT 4\n  screenshot4: null\n- opts:\n    description: URL (jpg or png)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Enter the url of your fifth screenshot\n    title: SCREENSHOT 5\n  screenshot5: null\n- description: null\n  opts:\n    description: Description for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the description for your application. You can have a different\n      description for each version for your application.\n    title: Description\n- changelog: null\n  opts:\n    description: Changelog for your application\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: This is the changelog for your application. You can have a different\n      changelog for each version for your application.\n    title: Changelog\n- group_ids: null\n  opts:\n    description: 'Groups ids of the groups you want your application published to. If you do not specify at least one group id, you will have to change the visibility directly on Appaloosa website.'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: You can target specific groups on Appaloosa and publish your application\n      only to the users of these groups.\n    title: Group IDs"
  },
  {
    "path": "steps/appaloosa/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/appcenter-apk-upload/0.0.1/step.yml",
    "content": "title: Deploy to AppCenter - apk & mapping\nsummary: |\n  Upload apk and mapping.txt to Microsoft AppCenter\ndescription: |\n  This step is upload Android apk archive file to AppCenter support mapping.txt.\nwebsite: https://github.com/kanari3/bitrise-step-appcenter-apk-upload\nsource_code_url: https://github.com/kanari3/bitrise-step-appcenter-apk-upload\nsupport_url: https://github.com/kanari3/bitrise-step-appcenter-apk-upload/issues\npublished_at: 2019-07-25T00:12:17.685785+09:00\nsource:\n  git: https://github.com/kanari3/bitrise-step-appcenter-apk-upload.git\n  commit: 8fd5f903714eba07ef2451c27de74607528e3c4c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: curl\n  apt_get:\n  - name: jq\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_id: $APP_CENTER_RELEASE_NOTE\n  opts:\n    description: |\n      Doesn't support markdown format.\n    is_required: false\n    summary: for AppCenter Release Note Message\n    title: AppCenter Release Note\n- app_id: $APP_PROJECT_NAME\n  opts:\n    description: |\n      Target project inclued by setting.gradle\n    is_required: true\n    summary: Application Project file name.\n    title: App Project Name\n- app_id: $APP_CENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name\n      and an Application Name.\n      For example: \"MyOrganization/MyApplication\"\n    is_required: true\n    summary: AppCenter application identifier (Owner + App Name).\n    title: Application Identifier\n- api_token: $APP_CENTER_ACCESS_TOKEN\n  opts:\n    description: |\n      [Obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- distribution_group: $APP_CENTER_DISTRIBUTION_GROUP\n  opts:\n    description: |\n      For example and default: \"Collaborators\"\n    is_required: true\n    title: AppCenter Distribution Group Name\n"
  },
  {
    "path": "steps/appcenter-apk-upload/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appcenter-app-release/1.0.0/step.yml",
    "content": "title: AppCenter App Release\nsummary: |\n  Release an application on Microsoft AppCenter\ndescription: |\n  Release an application on Microsoft AppCenter\nwebsite: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsource_code_url: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsupport_url: https://github.com/fileformat/bitrise-step-appcenter-app-release/issues\npublished_at: 2019-07-01T10:50:42.111187111-04:00\nsource:\n  git: https://github.com/fileformat/bitrise-step-appcenter-app-release.git\n  commit: e064d73405ff8c29ffaaf712fd7002083e8113ca\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: curl\n  apt_get:\n  - name: jq\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appcenter_api_token: $APPCENTER_API_TOKEN\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- appcenter_name: $APPCENTER_NAME\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Application Name\n- appcenter_org: $APPCENTER_ORG\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Organization\n- artifact_path: $ARTIFACT_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    title: path to the built application file (.ipa or .apk)\n"
  },
  {
    "path": "steps/appcenter-app-release/1.0.1/step.yml",
    "content": "title: AppCenter App Release\nsummary: |\n  Release an application on Microsoft AppCenter\ndescription: |\n  Release an application on Microsoft AppCenter\nwebsite: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsource_code_url: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsupport_url: https://github.com/fileformat/bitrise-step-appcenter-app-release/issues\npublished_at: 2019-09-04T15:29:27.480646-04:00\nsource:\n  git: https://github.com/fileformat/bitrise-step-appcenter-app-release.git\n  commit: 6e49525cb88bec3f4e098b314c4586d57b4b7274\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: curl\n  apt_get:\n  - name: jq\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appcenter_api_token: $APPCENTER_API_TOKEN\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- appcenter_name: $APPCENTER_NAME\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Application Name\n- appcenter_org: $APPCENTER_ORG\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Organization\n- artifact_path: $ARTIFACT_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    title: path to the built application file (.ipa or .apk)\n- distribution_groups: $DISTRIBUTION_GROUPS\n  opts:\n    description: Groups should be comma separated e.g. group1, group2. If not specified,\n      artifact will be sent to all distribution groups\n    is_expand: true\n    is_required: false\n    title: AppCenter distribution groups\n- opts:\n    is_expand: true\n    is_required: false\n    title: Uploaded build related release notes\n  release_notes: $RELEASE_NOTES\n"
  },
  {
    "path": "steps/appcenter-app-release/1.0.3/step.yml",
    "content": "title: AppCenter App Release\nsummary: |\n  Release an application on Microsoft AppCenter\ndescription: |\n  Release an application on Microsoft AppCenter\nwebsite: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsource_code_url: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsupport_url: https://github.com/fileformat/bitrise-step-appcenter-app-release/issues\npublished_at: 2019-10-01T11:02:36.233008-04:00\nsource:\n  git: https://github.com/fileformat/bitrise-step-appcenter-app-release.git\n  commit: 347097e2f25e382e34119e8ee919355986dbcd1f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: curl\n  apt_get:\n  - name: jq\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appcenter_api_token: $APPCENTER_API_TOKEN\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- appcenter_name: $APPCENTER_NAME\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Application Name\n- appcenter_org: $APPCENTER_ORG\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Organization\n- artifact_path: $ARTIFACT_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    title: path to the built application file (.ipa or .apk)\n- distribution_groups: $DISTRIBUTION_GROUPS\n  opts:\n    description: Groups should be comma separated e.g. group1, group2. If not specified,\n      artifact will be sent to all distribution groups\n    is_expand: true\n    is_required: false\n    title: AppCenter distribution groups\n- notify_testers: $NOTIFY_TESTERS\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Do you want to notify testers of a new release (default = true)\n    title: Notify testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_expand: true\n    is_required: false\n    title: Uploaded build related release notes\n  release_notes: $RELEASE_NOTES\n"
  },
  {
    "path": "steps/appcenter-app-release/1.0.5/step.yml",
    "content": "title: AppCenter App Release\nsummary: |\n  Release an application on Microsoft AppCenter\ndescription: |\n  Release an application on Microsoft AppCenter\nwebsite: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsource_code_url: https://github.com/fileformat/bitrise-step-appcenter-app-release\nsupport_url: https://github.com/fileformat/bitrise-step-appcenter-app-release/issues\npublished_at: 2019-11-22T11:09:49.651925-05:00\nsource:\n  git: https://github.com/fileformat/bitrise-step-appcenter-app-release.git\n  commit: caa8294515c2902721a1d72b831446d2ea89bd1c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: curl\n  apt_get:\n  - name: jq\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appcenter_api_token: $APPCENTER_API_TOKEN\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- appcenter_name: $APPCENTER_NAME\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Application Name\n- appcenter_org: $APPCENTER_ORG\n  opts:\n    is_expand: true\n    is_required: true\n    title: AppCenter Organization\n- artifact_path: $ARTIFACT_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    title: path to the built application file (.ipa or .apk)\n- distribution_groups: $DISTRIBUTION_GROUPS\n  opts:\n    description: Groups should be comma separated e.g. group1, group2. If not specified,\n      artifact will be sent to all distribution groups\n    is_expand: true\n    is_required: false\n    title: AppCenter distribution groups\n- mandatory_update: $MANDATORY_UPDATE\n  opts:\n    description: Whether this release is a mandatory update (default = false)\n    is_expand: true\n    is_required: false\n    title: AppCenter Mandatory Update flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- notify_testers: $NOTIFY_TESTERS\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Do you want to notify testers of a new release (default = true)\n    title: Notify testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_expand: true\n    is_required: false\n    title: Uploaded build related release notes\n  release_notes: $RELEASE_NOTES\noutputs:\n- APPCENTER_DOWNLOAD_URL: $APPCENTER_DOWNLOAD_URL\n  opts:\n    title: Download URL from AppCenter\n"
  },
  {
    "path": "steps/appcenter-app-release/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2022-11-06\"\ndeprecate_notes: |\n  This step is no longer maintained by its author.\n  \n  It's recommended to use the new AppCenter steps created and maintained by Bitrise:\n  - For iOS, use the [AppCenter iOS Deploy](https://github.com/bitrise-steplib/steps-appcenter-deploy-ios) Step instead\n  - For Android, use the [AppCenter Android Deploy](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) Step instead\n"
  },
  {
    "path": "steps/appcenter-codepush-release-react-native/0.0.1/step.yml",
    "content": "title: AppCenter CodePush Release React Native\nsummary: |\n  Release a React Native update to AppCenter CodePush\ndescription: |\n  Utilise appcenter-cli command appcenter codepush release-react to release an update\nwebsite: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native\nsource_code_url: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native\nsupport_url: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native/issues\npublished_at: !!timestamp 2018-03-21T03:24:18.183703631+08:00\nsource:\n  git: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native.git\n  commit: bdbfa011fc1469fd2cb583f3cc732cfc01e013b8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path where the React Native project is located.\n    is_required: true\n    title: React Native Project Root\n  react_native_project_root: $REACT_NATIVE_PROJECT_ROOT\n- app_id: $APPCENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name and an Application Name.\n      For example: \"Upstack-Studio/bitrise-android\"\n    is_required: true\n    summary: AppCenter application identifier (Organization/Owner Name + App Name).\n    title: AppCenter App ID\n- api_token: $APPCENTER_API_TOKEN\n  opts:\n    description: |\n      AppCenter API Token can be obtained from [here]](https://appcenter.ms/settings/apitokens).\n      New API Token > Enter a description for the token > Select Full Access > Add New API Token\n    is_required: true\n    title: AppCenter API Token\n- env: 'prod'\n  opts:\n    description: |\n      Choices for environments [here](https://github.com/Microsoft/appcenter-cli/blob/61bd72c1dcabeb876ee14fcaa316fd6b367b49a6/src/commands/codepush/lib/environment.ts#L18)\n    is_required: true\n    title: Environment\n- options:\n  opts:\n    description: |\n      Any extra options that you would like to concat to the release-react command\n    is_required: false\n    title: Extra Options\n"
  },
  {
    "path": "steps/appcenter-codepush-release-react-native/0.0.2/step.yml",
    "content": "title: AppCenter CodePush Release React Native\nsummary: |\n  Release a React Native update to AppCenter CodePush\ndescription: |\n  Utilise appcenter-cli command appcenter codepush release-react to release an update\nwebsite: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native\nsource_code_url: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native\nsupport_url: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native/issues\npublished_at: 2018-07-24T12:10:48.971190291+08:00\nsource:\n  git: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native.git\n  commit: c6cb21acbdefcc8f230d459bcdb940d17fa58135\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path where the React Native project is located.\n    is_required: true\n    title: React Native Project Root\n  react_native_project_root: $REACT_NATIVE_PROJECT_ROOT\n- app_id: $APPCENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name and an Application Name.\n      For example: \"Upstack-Studio/bitrise-android\"\n    is_required: true\n    summary: AppCenter application identifier (Organization/Owner Name + App Name).\n    title: AppCenter App ID\n- api_token: $APPCENTER_API_TOKEN\n  opts:\n    description: |\n      AppCenter API Token can be obtained from [here]](https://appcenter.ms/settings/apitokens).\n      New API Token > Enter a description for the token > Select Full Access > Add New API Token\n    is_required: true\n    title: AppCenter API Token\n- deployment: Staging\n  opts:\n    description: |\n      This specifies which deployment you want to release the update to. This defaults to Staging, but when you're ready to deploy to Production, or one of your own custom deployments, just explicitly set this argument. See [here](https://docs.microsoft.com/en-us/appcenter/distribution/codepush/cli#deployment-name-parameter) for details.\n    is_required: true\n    title: Deployment\n- options: null\n  opts:\n    description: |\n      Any extra options that you would like to concat to the release-react command. Eg. \"-m --disable-duplicate-release-error\"\n    is_required: false\n    title: Extra Options\n"
  },
  {
    "path": "steps/appcenter-codepush-release-react-native/0.0.3/step.yml",
    "content": "title: AppCenter CodePush Release React Native\nsummary: |\n  Release a React Native update to AppCenter CodePush\ndescription: |\n  Utilise appcenter-cli command appcenter codepush release-react to release an update\nwebsite: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native\nsource_code_url: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native\nsupport_url: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native/issues\npublished_at: 2021-03-24T17:24:07.835473+08:00\nsource:\n  git: https://github.com/adrianchinghc/bitrise-step-appcenter-codepush-release-react-native.git\n  commit: dc8cee3b16aaf5ae2ca377422cb74f3bff1e7dff\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path where the React Native project is located.\n    is_required: true\n    title: React Native Project Root\n  react_native_project_root: $REACT_NATIVE_PROJECT_ROOT\n- app_id: $APPCENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name and an Application Name.\n      For example: `Upstack-Studio/bitrise-android`\n    is_required: true\n    summary: AppCenter application identifier (Organization/Owner Name + App Name).\n    title: AppCenter App ID\n- api_token: $APPCENTER_API_TOKEN\n  opts:\n    description: |\n      AppCenter API Token can be obtained from [here](https://appcenter.ms/settings/apitokens). `New API Token` > `Enter a description for the token` > `Select Full Access` > `Add New API Token`\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- deployment: Staging\n  opts:\n    description: |\n      This specifies which deployment you want to release the update to. This defaults to Staging, but when you're ready to deploy to Production, or one of your own custom deployments, just explicitly set this argument. See [here](https://docs.microsoft.com/en-us/appcenter/distribution/codepush/cli#deployment-name-parameter) for details.\n    is_required: true\n    title: Deployment\n- description: null\n  opts:\n    description: |\n      Specify an optional \"change log\" for the deployment.\n    is_required: false\n    title: Description\n- options: null\n  opts:\n    description: |\n      Any extra options that you would like to concat to the release-react command. Eg. \"-m --disable-duplicate-release-error\"\n    is_required: false\n    title: Extra Options\n"
  },
  {
    "path": "steps/appcenter-codepush-release-react-native/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appcenter-deploy-android/1.0.0/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2019-11-26T14:38:45.813756844Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 0c5eb1ad4f7f7ca9bce75a819894e0c9241ec0cd\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/1.0.1/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2019-12-10T15:16:51.146344226Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 1947d021cba299356fb6fe8a8c2a979c608ef6f4\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/1.0.2/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2020-09-02T10:36:06.638925259Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 3c0ca221d52f3262c2010b8809107de15a08853c\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/1.1.0/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2020-09-25T09:24:01.531290521Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 6408133236abf61f266d53f0d3563c56d4edf301\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.0.0/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2020-12-16T12:42:08.970623593Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 29195d883bc9b3b650f06ac9c32882ae3d73da39\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    is_required: true\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.0.1/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2021-01-12T12:23:34.413069704Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 17c3521aedb18274a7cae73e26ac9dcc8b0622a1\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    is_required: true\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.0.2/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2021-01-13T09:59:12.992816851Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: a416c2ba131027775756abb847f182a9d76e9900\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    is_required: true\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.1.0/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Deploy your awesome Android app to AppCenter.\ndescription: Deploy an Android application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2021-05-12T14:42:53.059706067Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 412c3c60260dcfdd37efc06ffb5114867f6b95f8\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.1.1/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Distribute your Android app through [Microsoft App Center](https://appcenter.ms/).\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **APP path** which points to a binary file.\n   2. Add the **mapping.txt file path**.\n   3. Add the App Center **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n\n  ### Useful links\n  - [About Android deployment with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n  - [About Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to Huawei App Gallery](https://www.bitrise.io/integrations/steps/app-gallery-deploy)\n  - [Google Play Deploy](https://www.bitrise.io/integrations/steps/google-play-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2021-06-25T07:14:11.674056296Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 7abb6cd5a561d7af8be91a9603693323fd6f5e85\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.1.2/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Distribute your Android app through [Microsoft App Center](https://appcenter.ms/).\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **APP path** which points to a binary file.\n   2. Add the **mapping.txt file path**.\n   3. Add the App Center **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n\n  ### Useful links\n  - [About Android deployment with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n  - [About Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to Huawei App Gallery](https://www.bitrise.io/integrations/steps/app-gallery-deploy)\n  - [Google Play Deploy](https://www.bitrise.io/integrations/steps/google-play-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2021-12-09T13:39:59.147780768Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 0b97fa8454360060fcc9c66668deff0e0bb64a3c\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.2.0/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Distribute your Android app through [Microsoft App Center](https://appcenter.ms/).\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **APP path** which points to a binary file.\n   2. Add the **mapping.txt file path**.\n   3. Add the App Center **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n\n  ### Useful links\n  - [About Android deployment with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n  - [About Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to Huawei App Gallery](https://www.bitrise.io/integrations/steps/app-gallery-deploy)\n  - [Google Play Deploy](https://www.bitrise.io/integrations/steps/google-play-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2022-01-21T14:54:23.145759439Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 3390b3e63e545a46ec0eb3004dfd5b0c5b4ba72c\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.2.1/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Distribute your Android app through [Microsoft App Center](https://appcenter.ms/).\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **APP path** which points to a binary file.\n   2. Add the **mapping.txt file path**.\n   3. Add the App Center **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n  ### Useful links\n  - [About Android deployment with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n  - [About Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to Huawei App Gallery](https://www.bitrise.io/integrations/steps/app-gallery-deploy)\n  - [Google Play Deploy](https://www.bitrise.io/integrations/steps/google-play-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2022-07-27T14:29:17.289340852Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: bb33fa4e3ab76222252eee6c4653c53804360dbb\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.2.2/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Distribute your Android app through [Microsoft App Center](https://appcenter.ms/).\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **APP path** which points to a binary file.\n   2. Add the **mapping.txt file path**.\n   3. Add the App Center **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n  ### Useful links\n  - [About Android deployment with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n  - [About Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to Huawei App Gallery](https://www.bitrise.io/integrations/steps/app-gallery-deploy)\n  - [Google Play Deploy](https://www.bitrise.io/integrations/steps/google-play-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2023-08-03T08:18:38.245095734Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: 32924202bdfd43c339e3cfef649fd2c1ac184357\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/2.2.3/step.yml",
    "content": "title: AppCenter Android Deploy\nsummary: Distribute your Android app through [Microsoft App Center](https://appcenter.ms/).\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-android) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **APP path** which points to a binary file.\n   2. Add the **mapping.txt file path**.\n   3. Add the App Center **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n  ### Useful links\n  - [About Android deployment with Bitrise](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n  - [About Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to Huawei App Gallery](https://www.bitrise.io/integrations/steps/app-gallery-deploy)\n  - [Google Play Deploy](https://www.bitrise.io/integrations/steps/google-play-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-android/issues\npublished_at: 2023-10-09T08:59:39.929529758Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-android.git\n  commit: de7c76ece787bab144e12ff79345ecdf60f7b995\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-android\nis_always_run: false\nis_skippable: false\ninputs:\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to binary file\n\n      For APKs, only single or universal APKs are supported: https://docs.microsoft.com/en-us/appcenter/build/react-native/android/#63-building-multiple-apks\n    is_required: true\n    summary: Path to binary file\n    title: APP path\n- mapping_path: null\n  opts:\n    description: Path to an Android mapping.txt file.\n    summary: Path to an Android mapping.txt file.\n    title: mapping.txt file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: |-\n      User groups you wish to distribute the app. One group name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: |-\n      Distribution stores you wish to distribute the app. One store name per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: |-\n      List of individual testers. One email per line.\n\n      Distribution of AAB is supported only for Google Play store deployment: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#android\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Additional notes for the deployed artifact.\n    summary: Release notes text\n    title: Release notes text\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment status: ''success'' or ''failed'''\n    summary: 'Deployment status: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: null\n  opts:\n    description: Install page URL of the newly deployed version.\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: null\n  opts:\n    description: Download URL of the newly deployed version.\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public install page URL of the latest version.\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_RELEASE_PAGE_URL: null\n  opts:\n    description: URL to the release page containing release notes, easily share with\n      business partners and QA for testing.\n    summary: URL to the release page containing release notes.\n    title: Release Page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-android/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/1.0.0/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Deploy your awesome iOS app to App Center.\ndescription: Deploy an iOS application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2019-11-26T14:37:36.373448806Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: a756aaa213dd51e6d6e25532ad22832b00970e36\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/1.1.0/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Deploy your awesome iOS app to App Center.\ndescription: Deploy an iOS application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2020-09-25T09:24:42.620639402Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: ad21da815b53fe75d581f0ce507b92827c67acbb\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.0.0/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Deploy your awesome iOS app to App Center.\ndescription: Deploy an iOS application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2020-12-16T12:42:44.450536761Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: eac9055034fd8103bbf1eeaa8682738027571af6\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    is_required: true\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.0.1/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Deploy your awesome iOS app to App Center.\ndescription: Deploy an iOS application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2021-01-12T12:23:51.845656713Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: d1dcd5a0247f0208f89d129ba507521fd79dcec2\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    is_required: true\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.0.2/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Deploy your awesome iOS app to App Center.\ndescription: Deploy an iOS application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2021-01-13T10:11:16.401356238Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: 9bd0610d9544b2b9052fddc7f96a3fd6a18dc820\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    is_required: true\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.1.0/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Deploy your awesome iOS app to App Center.\ndescription: Deploy an iOS application to [AppCenter](https://appcenter.ms).\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2021-05-13T08:28:34.697416698Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: 8aab34dac2e9ccc603cab02fef486cfd764b1f61\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.1.1/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Distribute your iOS app through Microsoft App Center.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-ios) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **IPA path** which points to a binary file.\n   2. Add the **DSYM.zip file path**.\n   3. Add the AppCenter **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory update** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n   ### Useful links\n  - [About iOS deployment with Bitrise]https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/()\n  - [About iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Deploy to iTunes Connect - Application Loader](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2021-06-24T15:55:13.221055708Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: 64ecbc696f2274baea2e744545d93afb344aaf87\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.1.2/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Distribute your iOS app through Microsoft App Center.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-ios) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **IPA path** which points to a binary file.\n   2. Add the **DSYM.zip file path**.\n   3. Add the AppCenter **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory update** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n   ### Useful links\n  - [About iOS deployment with Bitrise]https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/()\n  - [About iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Deploy to iTunes Connect - Application Loader](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2021-09-16T15:33:59.250468501Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: bce482a130c778c1d486b38568b6062a71f4148a\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.2.0/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Distribute your iOS app through Microsoft App Center.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-ios) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **IPA path** which points to a binary file.\n   2. Add the **DSYM.zip file path**.\n   3. Add the AppCenter **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory update** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n   ### Useful links\n  - [About iOS deployment with Bitrise]https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/()\n  - [About iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Deploy to iTunes Connect - Application Loader](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2022-01-25T10:08:12.925669492Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: 9521becda0f81f2491a7cd8155758e260b1563a7\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.2.1/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Distribute your iOS app through Microsoft App Center.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-ios) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **IPA path** which points to a binary file.\n   2. Add the **DSYM.zip file path**.\n   3. Add the AppCenter **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory update** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n   ### Useful links\n  - [About iOS deployment with Bitrise]https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/()\n  - [About iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Deploy to iTunes Connect - Application Loader](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2023-08-03T08:20:34.006542299Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: 5644edec67aec758dd5a152fad09f7fb114fad08\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/2.2.2/step.yml",
    "content": "title: AppCenter iOS Deploy\nsummary: Distribute your iOS app through Microsoft App Center.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-appcenter-deploy-ios) integrates with the [App Center](https://appcenter.ms/)'s Distribution service and enables you to distribute your apps seamlessly to different stores, for example, App Store, MS Intune, user groups or even individual testers.\n\n   ### Configuring the Step\n\n   Before you start:\n\n   The Step requires an active MS App Center account.\n\n   1. Add the **IPA path** which points to a binary file.\n   2. Add the **DSYM.zip file path**.\n   3. Add the AppCenter **API token**.\n   4. Add the **Owner name**, which means the owner of the App Center app. For an app owned by a user, the URL in App Center can look like this https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {ownername} is JoshuaWeber. For an app owned by an organization, the URL can be, for example, https://appcenter.ms/orgs/Microsoft/apps/APIExample where the {ownername} is Microsoft.\n   5. Add the **App name** which is the name of the App Center app. For an app owned by a user, the URL in App Center might look like this: https://appcenter.ms/users/JoshuaWeber/apps/APIExample where the {app_name} is APIExample.\n   6. Add the **Distribution groups** which means the user groups you wish to distribute the app to. Please add one group name per line.\n   7. Add the **Distribution stores** where you wish to distribute the app to. Please add one store name per line.\n   8. Add the **Testers** who you wish to send the app to via email. Please add one email address per line.\n   9. Add any **Release notes for the deployed artifact**.\n   10. Send notification emails to testers and distribution groups with the **Notify Testers** input.\n   11. You can enforce the installation of a distribution version with the **Mandatory update** input set to `yes`.\n   12. If you set the **Debug** input to `yes`, you can enable verbose logs.\n\n   ### Useful links\n  - [About iOS deployment with Bitrise]https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/()\n  - [About iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Deploy to iTunes Connect - Application Loader](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues\npublished_at: 2023-10-09T08:41:52.513899345Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-deploy-ios.git\n  commit: 574f77d1868f8da20ec36e882c8b134c8c0eda5f\nproject_type_tags:\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-deploy-ios\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path to a binary file\n    is_required: true\n    summary: Path to a binary file\n    title: IPA path\n- dsym_zip_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path to a DSYM.zip file\n    summary: Path to a DSYM.zip file\n    title: DSYM.zip file path\n- api_token: null\n  opts:\n    description: App Center API token\n    is_required: true\n    is_sensitive: true\n    summary: App Center API token\n    title: API Token\n- opts:\n    description: |-\n      Owner of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {owner_name} is JoshuaWeber. For an app owned by an org, the URL might be\n      https://appcenter.ms/orgs/Microsoft/apps/APIExample and the {owner_name} would be Microsoft\n    is_required: true\n    summary: Owner of the App Center app\n    title: Owner name\n  owner_name: null\n- app_name: null\n  opts:\n    description: |-\n      The name of the App Center app.\n\n      For an app owned by a user, the URL in App Center might look like https://appcenter.ms/users/JoshuaWeber/apps/APIExample.\n\n      Here, the {app_name} is ApiExample.\n    is_required: true\n    summary: The name of the App Center app\n    title: App name\n- distribution_group: null\n  opts:\n    description: User groups you wish to distribute the app. One group name per line.\n    summary: User groups you wish to distribute the app. One group name per line.\n    title: Distribution groups\n- distribution_store: null\n  opts:\n    description: Distribution stores you wish to distribute the app. One store name\n      per line.\n    summary: Distribution stores you wish to distribute the app. One store name per\n      line.\n    title: Distribution stores\n- distribution_tester: null\n  opts:\n    description: List of individual testers. One email per line.\n    summary: List of individual testers. One email per line.\n    title: Testers\n- opts:\n    description: Release notes text\n    summary: Release notes text\n    title: Release notes for the deployed artifact.\n  release_notes: Release notes\n- notify_testers: \"yes\"\n  opts:\n    description: Send notification email to testers and distribution groups.\n    is_required: true\n    summary: Send notification email to testers and distribution groups.\n    title: Notify Testers\n    value_options:\n    - \"yes\"\n    - \"no\"\n- mandatory: \"no\"\n  opts:\n    description: Enforce installation of distribution version. Requires SDK integration.\n    is_required: true\n    summary: Enforce installation of distribution version. Requires SDK integration.\n    title: Mandatory update\n    value_options:\n    - \"no\"\n    - \"yes\"\n- debug: \"no\"\n  opts:\n    description: Enable verbose logs\n    is_required: true\n    summary: Enable verbose logs\n    title: Debug\n    value_options:\n    - \"no\"\n    - \"yes\"\n- all_distribution_groups: \"no\"\n  opts:\n    description: Distribute the app to all user groups on that app. Enabling this\n      options makes it ignore distribution_group.\n    summary: Distribute the app to all user groups on that app.\n    title: All distribution groups\n    value_options:\n    - \"no\"\n    - \"yes\"\noutputs:\n- APPCENTER_DEPLOY_STATUS: null\n  opts:\n    description: 'Deployment result: ''success'' or ''failed'''\n    summary: 'Deployment result: ''success'' or ''failed'''\n    title: Deployment status\n- APPCENTER_DEPLOY_INSTALL_URL: \"\"\n  opts:\n    description: Install page URL of the newly deployed version\n    summary: Install page URL of the newly deployed version\n    title: Install page URL\n- APPCENTER_DEPLOY_DOWNLOAD_URL: \"\"\n  opts:\n    description: Download URL of the newly deployed version\n    summary: Download URL of the newly deployed version\n    title: Download URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URL: \"\"\n  opts:\n    description: Public install page URL of the latest version\n    summary: Public install page URL of the latest version\n    title: Public install page URL\n- APPCENTER_PUBLIC_INSTALL_PAGE_URLS: null\n  opts:\n    description: When a group is public the step will AppCenter provides and the step\n      exports a public install page URL.\n    summary: Comma-separated list of the public install pages URL.\n    title: Comma-separated public install pages by groups\n- APPCENTER_DEPLOY_RELEASE_ID: null\n  opts:\n    description: ID of the new release for later retrieval via App Center APIs.\n    summary: ID of the new release for later retrieval via App Center APIs.\n    title: Release ID\n"
  },
  {
    "path": "steps/appcenter-deploy-ios/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appcenter-dsym-upload/0.1.2/step.yml",
    "content": "title: AppCenter dSYM upload\nsummary: |\n  Upload dSYM to Microsoft AppCenter\ndescription: \"This step uploads dSYM to AppCenter using official CLI.\\nThe step is\n  relevant only for iOS projects (including Xamarin.iOS).\\n\\nBy default $BITRISE_DSYM_PATH\n  env used to lookup for dSYM file.\\nIf an archive step used as part of the workflow\n  then a default value can be used \\nfor `dsym_path` variable\\n\\nIt is important to\n  [obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\\nto use\n  this step.\\n\"\nwebsite: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload\nsource_code_url: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload\nsupport_url: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload/issues\npublished_at: 2017-12-18T13:20:30.338428+02:00\nsource:\n  git: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload.git\n  commit: c705e034afdadc7887e3458c9d8a8ae60a34b08a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      A path to dSYM file to upload.\n    is_required: true\n    title: dSYM path\n- app_id: $BITRISE_APPCENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name\n      and an Application Name.\n\n      For example: \"MyOrganization/MyApplication\"\n    is_required: true\n    summary: AppCenter application identifier (Owner + App Name).\n    title: Application Identifier\n- api_token: $BITRISE_APPCENTER_API_TOKEN\n  opts:\n    description: |\n      [Obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\n    is_required: true\n    title: AppCenter API Token\n"
  },
  {
    "path": "steps/appcenter-dsym-upload/0.1.3/step.yml",
    "content": "title: AppCenter dSYM upload\nsummary: |\n  Upload dSYM to Microsoft AppCenter\ndescription: \"This step uploads dSYM to AppCenter using official CLI.\\nThe step is\n  relevant only for iOS projects (including Xamarin.iOS).\\n\\nBy default $BITRISE_DSYM_PATH\n  env used to lookup for dSYM file.\\nIf an archive step used as part of the workflow\n  then a default value can be used \\nfor `dsym_path` variable\\n\\nIt is important to\n  [obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\\nto use\n  this step.\\n\"\nwebsite: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload\nsource_code_url: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload\nsupport_url: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload/issues\npublished_at: 2018-02-23T13:15:57.923773+02:00\nsource:\n  git: https://github.com/alexshikov/bitrise-step-appcenter-dsym-upload.git\n  commit: 42bb29ba2f557877bf8bea996452a60c2162d47c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      A path to dSYM file to upload.\n    is_required: true\n    title: dSYM path\n- app_id: $BITRISE_APPCENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name\n      and an Application Name.\n\n      For example: \"MyOrganization/MyApplication\"\n    is_required: true\n    summary: AppCenter application identifier (Owner + App Name).\n    title: Application Identifier\n- api_token: $BITRISE_APPCENTER_API_TOKEN\n  opts:\n    description: |\n      [Obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\n    is_required: true\n    title: AppCenter API Token\n"
  },
  {
    "path": "steps/appcenter-dsym-upload/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appcenter-ipa-upload/0.0.2/step.yml",
    "content": "title: AppCenter ipa upload\nsummary: |\n  Upload ipa to Microsoft AppCenter\ndescription: |\n  This step is upload iOS ipa archive file to AppCenter.\n  Using AppCenter CLI.\nwebsite: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload\nsource_code_url: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload\nsupport_url: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload/issues\npublished_at: 2019-07-15T21:29:09.119266+09:00\nsource:\n  git: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload.git\n  commit: 2e9810e71558b613a495c1169644d2038c51adca\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_id: $APP_CENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name\n      and an Application Name.\n      For example: \"MyOrganization/MyApplication\"\n    is_required: true\n    summary: AppCenter application identifier (Owner + App Name).\n    title: Application Identifier\n- api_token: $APP_CENTER_ACCESS_TOKEN\n  opts:\n    description: |\n      [Obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- distribution_group: $APP_CENTER_DISTRIBUTION_GROUP\n  opts:\n    description: |\n      For example and default: \"Collaborators\"\n    is_required: true\n    title: AppCenter Distribution Group Name\n"
  },
  {
    "path": "steps/appcenter-ipa-upload/0.0.3/step.yml",
    "content": "title: AppCenter ipa upload\nsummary: |\n  Upload ipa to Microsoft AppCenter\ndescription: |\n  This step is upload iOS ipa archive file to AppCenter.\n  Using AppCenter CLI.\nwebsite: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload\nsource_code_url: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload\nsupport_url: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload/issues\npublished_at: 2020-05-14T20:48:51.96485+09:00\nsource:\n  git: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload.git\n  commit: 3417e68a91b0305cd3a89cbd718107666dd4257d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_id: $APP_CENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name\n      and an Application Name.\n      For example: \"MyOrganization/MyApplication\"\n    is_required: true\n    summary: AppCenter application identifier (Owner + App Name).\n    title: Application Identifier\n- api_token: $APP_CENTER_ACCESS_TOKEN\n  opts:\n    description: |\n      [Obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- distribution_group: $APP_CENTER_DISTRIBUTION_GROUP\n  opts:\n    description: |\n      For example and default: \"Collaborators\"\n    is_required: true\n    title: AppCenter Distribution Group Name\n- build_message: $APP_CENTER_BUILD_MESSAGE\n  opts:\n    description: |\n      Build message that will appear under the build in AppCenter's list of builds.\n    is_required: true\n    title: AppCenter Build Message to share in the build.\n"
  },
  {
    "path": "steps/appcenter-ipa-upload/0.0.4/step.yml",
    "content": "title: AppCenter ipa upload\nsummary: |\n  Upload ipa to Microsoft AppCenter\ndescription: |\n  This step is upload iOS ipa archive file to AppCenter.\n  Using AppCenter CLI.\nwebsite: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload\nsource_code_url: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload\nsupport_url: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload/issues\npublished_at: 2021-10-07T04:12:37.337295+09:00\nsource:\n  git: https://github.com/kanari3/bitrise-step-appcenter-ipa-upload.git\n  commit: 258ec1c071f0577e2763429f1cbb95d5c9a16609\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_id: $APP_CENTER_APP_ID\n  opts:\n    description: |\n      AppCenter Application Identifier is a combination of your Organization/Owner Name\n      and an Application Name.\n      For example: \"MyOrganization/MyApplication\"\n    is_required: true\n    summary: AppCenter application identifier (Owner + App Name).\n    title: Application Identifier\n- api_token: $APP_CENTER_ACCESS_TOKEN\n  opts:\n    description: |\n      [Obtain API Token from AppCenter](https://appcenter.ms/settings/apitokens)\n    is_required: true\n    is_sensitive: true\n    title: AppCenter API Token\n- distribution_group: $APP_CENTER_DISTRIBUTION_GROUP\n  opts:\n    description: |\n      For example and default: \"Collaborators\"\n    is_required: true\n    title: AppCenter Distribution Group Name\n- build_message: $APP_CENTER_BUILD_MESSAGE\n  opts:\n    description: |\n      Build message that will appear under the build in AppCenter's list of builds.\n    is_required: false\n    title: (optional) AppCenter Build Message to share in the build.\n"
  },
  {
    "path": "steps/appcenter-ipa-upload/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appcenter-test/0.9.0/step.yml",
    "content": "title: App Center upload and schedule tests\nsummary: Uploads and schedules tests on Microsoft App Center\ndescription: |-\n  Uploads and schedules tests on Microsoft App Center.\n\n  Appium, Espresso, Calabash Xamarin.UITest and XCUITest tests can be uploaded.\n\n  Setup Instructions:\n\n  1. Prepare your test for upload: [https://docs.microsoft.com/en-us/appcenter/test-cloud/preparing-for-upload/](https://docs.microsoft.com/en-us/appcenter/test-cloud/preparing-for-upload/)\n  1. Create an App Center project: [https://appcenter.ms/apps](https://appcenter.ms/apps)\n  1. Navigate to Test runs tab and start a New test run:\n    - Select devices\n    - Configure test run\n    - On Submit tab you will find every required input for the step\n    - Click on Done\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-test\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-test\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-test/issues\npublished_at: 2018-04-26T14:00:51.279392903+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-test.git\n  commit: 913608ceb0cb9f507b831c6ffb05c35d7096f291\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: '[Install the appcenter-cli](https://github.com/Microsoft/appcenter-cli#installation)\n      and run `appcenter tokens create` to generate a new API token.'\n    is_expand: true\n    is_required: true\n    summary: API token\n    title: API token\n  token: null\n- app: null\n  opts:\n    description: Specify app in the <ownerName>/<appName> format\n    is_expand: true\n    is_required: true\n    summary: Specify app in the <ownerName>/<appName> format\n    title: Target App on App Center\n- framework: null\n  opts:\n    description: |-\n      The used testing framework name.\n\n      Available options:\n\n      - `appium` - for Appium tests\n      - `espresso` - for Espresso tests\n      - `calabash` - for Calabash tests\n      - `uitest` - for Xamarin.UITests\n      - `xcuitest` - for XCUITest\n    is_expand: true\n    is_required: true\n    summary: The used testing framework name\n    title: Test framework\n- devices: null\n  opts:\n    description: Device selection slug\n    is_expand: true\n    is_required: true\n    summary: Device selection slug\n    title: Device selection slug\n- opts:\n    description: Name of the test series.\n    is_expand: true\n    is_required: true\n    summary: Name of the test series\n    title: Name of the test series\n  series: null\n- locale: en_US\n  opts:\n    description: The system locale for the test run.\n    is_expand: true\n    is_required: true\n    summary: The system locale for the test run\n    title: The system locale for the test run\n- app_path: null\n  opts:\n    description: |-\n      Path to an application file.\n      Can be an .ipa or .apk file.\n    is_expand: true\n    is_required: true\n    summary: Path to an application file\n    title: Path to an application file\n- dsym_dir: null\n  opts:\n    description: Path to the directory with iOS symbol files.\n    is_expand: true\n    summary: Path to the directory with iOS symbol files\n    title: Path to the directory with iOS symbol files\n- opts:\n    description: |-\n      Path to the test directory.\n\n      - For Appium tests: path to the directory with the Appium tests (usually <project>/target/upload)\n      - For Espresso tests: path to the Espresso output directory (usually <project>/build/outputs/apk)\n      - For Calabash tests: path to the Calabash workspace directory (usually <project>/features)\n      - For Xamarin.UITest tests: path to the directory with the built test assemblies (usually <project>/bin/<configuration>)\n      - For XCUITest tests: path to the build output directory (usually <project>/Build/Products/Debug-iphoneos)\n    is_expand: true\n    is_required: true\n    summary: Path to the test directory\n    title: Path to the test directory\n  test_dir: null\n"
  },
  {
    "path": "steps/appcenter-test/0.9.1/step.yml",
    "content": "title: App Center upload and schedule tests\nsummary: Uploads and schedules tests on Microsoft App Center\ndescription: |-\n  Uploads and schedules tests on Microsoft App Center.\n\n  Appium, Espresso, Calabash Xamarin.UITest and XCUITest tests can be uploaded.\n\n  Setup Instructions:\n\n  1. Prepare your test for upload: [https://docs.microsoft.com/en-us/appcenter/test-cloud/preparing-for-upload/](https://docs.microsoft.com/en-us/appcenter/test-cloud/preparing-for-upload/)\n  1. Create an App Center project: [https://appcenter.ms/apps](https://appcenter.ms/apps)\n  1. Navigate to Test runs tab and start a New test run:\n    - Select devices\n    - Configure test run\n    - On Submit tab you will find every required input for the step\n    - Click on Done\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-test\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-test\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-test/issues\npublished_at: 2018-05-30T11:09:25.312167837+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-test.git\n  commit: 0479c92f1552a983d5ae7511c62568e9a7b54e07\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: '[Install the appcenter-cli](https://github.com/Microsoft/appcenter-cli#installation)\n      and run `appcenter tokens create` to generate a new API token.'\n    is_expand: true\n    is_required: true\n    summary: API token\n    title: API token\n  token: null\n- app: null\n  opts:\n    description: Specify app in the <ownerName>/<appName> format\n    is_expand: true\n    is_required: true\n    summary: Specify app in the <ownerName>/<appName> format\n    title: Target App on App Center\n- framework: null\n  opts:\n    description: |-\n      The used testing framework name.\n\n      Available options:\n\n      - `appium` - for Appium tests\n      - `espresso` - for Espresso tests\n      - `calabash` - for Calabash tests\n      - `uitest` - for Xamarin.UITests\n      - `xcuitest` - for XCUITest\n    is_expand: true\n    is_required: true\n    summary: The used testing framework name\n    title: Test framework\n- devices: null\n  opts:\n    description: Device selection slug\n    is_expand: true\n    is_required: true\n    summary: Device selection slug\n    title: Device selection slug\n- opts:\n    description: Name of the test series.\n    is_expand: true\n    is_required: true\n    summary: Name of the test series\n    title: Name of the test series\n  series: null\n- locale: en_US\n  opts:\n    description: The system locale for the test run.\n    is_expand: true\n    is_required: true\n    summary: The system locale for the test run\n    title: The system locale for the test run\n- app_path: null\n  opts:\n    description: |-\n      Path to an application file.\n      Can be an .ipa or .apk file.\n    is_expand: true\n    is_required: true\n    summary: Path to an application file\n    title: Path to an application file\n- dsym_dir: null\n  opts:\n    description: Path to the directory with iOS symbol files.\n    is_expand: true\n    summary: Path to the directory with iOS symbol files\n    title: Path to the directory with iOS symbol files\n- opts:\n    description: |-\n      Path to the test directory.\n\n      - For Appium tests: path to the directory with the Appium tests (usually <project>/target/upload)\n      - For Espresso tests: path to the Espresso output directory (usually <project>/build/outputs/apk)\n      - For Calabash tests: path to the Calabash workspace directory (usually <project>/features)\n      - For Xamarin.UITest tests: path to the directory with the built test assemblies (usually <project>/bin/<configuration>)\n      - For XCUITest tests: path to the build output directory (usually <project>/Build/Products/Debug-iphoneos)\n    is_expand: true\n    is_required: true\n    summary: Path to the test directory\n    title: Path to the test directory\n  test_dir: null\n- additional_options: null\n  opts:\n    description: |-\n      Options added to the end of the test run.\n\n      You can use multiple options, separated by a space\n      character. Example `--include-category A|B|C --exclude-cataegory D`\n    is_expand: true\n    is_required: false\n    summary: Additional options for test run\n    title: Additional options for test run\n"
  },
  {
    "path": "steps/appcenter-test/0.9.2/step.yml",
    "content": "title: App Center upload and schedule tests\nsummary: This step uploads and schedules tests on Microsoft App Center.\ndescription: |-\n  This step uploads and schedules tests on Microsoft App Center.\n\n  Appium, Espresso, Calabash Xamarin.UITest and XCUITest tests can be uploaded.\n\n  Setup instructions:\n\n  1. Prepare your test for upload: [https://docs.microsoft.com/en-us/appcenter/test-cloud/preparing-for-upload/](https://docs.microsoft.com/en-us/appcenter/test-cloud/preparing-for-upload/)\n  1. Create an App Center project: [https://appcenter.ms/apps](https://appcenter.ms/apps)\n  1. Navigate to Test runs tab and start a New test run:\n    - Select devices\n    - Configure test run\n    - On the Submit tab, you will find every required input for the step\n    - Click Done\nwebsite: https://github.com/bitrise-steplib/steps-appcenter-test\nsource_code_url: https://github.com/bitrise-steplib/steps-appcenter-test\nsupport_url: https://github.com/bitrise-steplib/steps-appcenter-test/issues\npublished_at: 2018-08-31T11:05:44.472286611Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appcenter-test.git\n  commit: 85a0aa10c73c56f1dc82564415dcdc1c87d02ee6\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appcenter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: '[Install the appcenter-cli](https://github.com/Microsoft/appcenter-cli#installation)\n      and run `appcenter tokens create` to generate a new API token.'\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API token\n    title: API token\n  token: null\n- app: null\n  opts:\n    description: Specify app in the <ownerName>/<appName> format\n    is_expand: true\n    is_required: true\n    summary: Specify app in the <ownerName>/<appName> format\n    title: Target App on App Center\n- framework: null\n  opts:\n    description: |-\n      The used testing framework name.\n\n      Available options:\n\n      - `appium` - for Appium tests\n      - `espresso` - for Espresso tests\n      - `calabash` - for Calabash tests\n      - `uitest` - for Xamarin.UITests\n      - `xcuitest` - for XCUITest\n    is_expand: true\n    is_required: true\n    summary: The used testing framework name\n    title: Test framework\n- devices: null\n  opts:\n    description: Device selection slug\n    is_expand: true\n    is_required: true\n    summary: Device selection slug\n    title: Device selection slug\n- opts:\n    description: Name of the test series.\n    is_expand: true\n    is_required: true\n    summary: Name of the test series\n    title: Name of the test series\n  series: null\n- locale: en_US\n  opts:\n    description: The system locale for the test run.\n    is_expand: true\n    is_required: true\n    summary: The system locale for the test run\n    title: The system locale for the test run\n- app_path: null\n  opts:\n    description: |-\n      Path to an application file.\n      Can be an .ipa or an .apk file.\n    is_expand: true\n    is_required: true\n    summary: Path to an application file\n    title: Path to an application file\n- dsym_dir: null\n  opts:\n    description: Path to the directory with iOS symbol files.\n    is_expand: true\n    summary: Path to the directory with iOS symbol files\n    title: Path to the directory with iOS symbol files\n- opts:\n    description: |-\n      Path to the test directory.\n\n      - For Appium tests: path to the directory with the Appium tests (usually <project>/target/upload)\n      - For Espresso tests: path to the Espresso output directory (usually <project>/build/outputs/apk)\n      - For Calabash tests: path to the Calabash workspace directory (usually <project>/features)\n      - For Xamarin.UITest tests: path to the directory with the built test assemblies (usually <project>/bin/<configuration>)\n      - For XCUITest tests: path to the build output directory (usually <project>/Build/Products/Debug-iphoneos)\n    is_expand: true\n    is_required: true\n    summary: Path to the test directory\n    title: Path to the test directory\n  test_dir: null\n- additional_options: null\n  opts:\n    description: |-\n      Options added to the end of the test run.\n\n      You can use multiple options, separated by a space\n      character. Example `--include-category A|B|C --exclude-cataegory D`\n    is_expand: true\n    is_required: false\n    summary: Additional options for test run\n    title: Additional options for test run\n"
  },
  {
    "path": "steps/appcenter-test/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2026-08-08\"\ndeprecate_notes: |\n  App Center is deprecated.\n\n  We recommend to use [Bitrise Release Management](https://docs.bitrise.io/en/release-management.html) and [Bitrise CodePush](https://docs.bitrise.io/en/release-management/codepush/about-codepush.html).\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/1.0.12/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2023-06-27T16:03:13.933774+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: ed3e54bea3dd0be05e5d2693bfd9780d9e4f8fda\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing?\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/1.0.5/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2023-05-09T11:27:43.406105+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: bacf66f4a8dae4f03daca821a2de1260ca04078b\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"true\"\n  opts:\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/1.0.7/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2023-05-21T18:14:24.326262+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: 5f67a7a9eb2c5eadee63c0267f5f5e4b3cdeeb1e\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/2.0.0/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2023-07-12T10:53:07.558334+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: 3454e77f745fe74de2659b67b203d26aa0e5f780\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - Bitbar\n    - Browserstack\n    - Saucelabs\n    - Lambdatest\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (Appdome_Universal.apk). Available if Secondary Output is set to 'true' and the original app is .aab type.\n    summary: Local path of the secured secondary output file (Appdome_Universal.apk)\n    title: Secured secondary output file path (Appdome_Universal.apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/3.0.0/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2023-08-13T12:15:36.722066+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: 6933e473dcd17ae5274068c9a9ac8241c8897ee2\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name. The file extension (aab/apk) will be the same as\n      the original app. If not specified, the default output file will be same as\n      the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - Bitbar\n    - Browserstack\n    - Saucelabs\n    - Lambdatest\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (universal apk). Available if Secondary Output is set to 'true' and the original app is .aab type\n    summary: Local path of the secured secondary output file\n    title: Secured secondary output file path (universal apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/3.2.0/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2024-08-19T13:49:51.361285+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: b38a88f644eea60308aa458de0d3ffdc087764e9\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name. The file extension (aab/apk) will be the same as\n      the original app. If not specified, the default output file will be same as\n      the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS device farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (universal apk). Available if Secondary Output is set to 'true' and the original app is .aab type\n    summary: Local path of the secured secondary output file\n    title: Secured secondary output file path (universal apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/3.3.1/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2024-10-31T21:59:47.773733+02:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: e80589f229be29724f1ec848b7d0cee9ca595450\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name. The file extension (aab/apk) will be the same as\n      the original app. If not specified, the default output file will be same as\n      the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS_device_farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\n- opts:\n    is_required: false\n    summary: File name of the workflow logs.\n    title: Workflow output logs file name\n  workflow_output_logs: null\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (universal apk). Available if Secondary Output is set to 'true' and the original app is .aab type\n    summary: Local path of the secured secondary output file\n    title: Secured secondary output file path (universal apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n- APPDOME_WORKFLOW_LOGS: null\n  opts:\n    summary: Local path of the Appdome workflow logs file\n    title: Appdome workflow logs file\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/3.4.1/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2025-03-20T11:03:46.939024+02:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: d74ab90bd5a960402543d2a8bf419052d0c1545c\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name. The file extension (aab/apk) will be the same as\n      the original app. If not specified, the default output file will be same as\n      the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- download_deobfuscation: \"true\"\n  opts:\n    category: Deobfuscation Options\n    description: Select 'true' to download Appdome deobfuscation mapping zip file\n      to the Artifacts section.\n    is_required: false\n    summary: Select 'true' to download Appdome deobfuscation mapping zip file to the\n      Artifacts section.\n    title: Download deobfuscation mapping file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- crashlytics_app_id: null\n  opts:\n    category: Deobfuscation Options\n    description: Crashlytics App ID as appears in the Firebase account, for auto upload\n      Appdome deobfuscation mapping file.\n    is_required: false\n    title: Crashlytics App ID\n- datadog_api_key: null\n  opts:\n    category: Deobfuscation Options\n    description: Datadog API Key, for auto upload Appdome deobfuscation mapping file.\n    is_required: false\n    title: Datadog API Key\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS_device_farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\n- opts:\n    is_required: false\n    summary: File name of the workflow logs.\n    title: Workflow output logs file name\n  workflow_output_logs: null\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (universal apk). Available if Secondary Output is set to 'true' and the original app is .aab type\n    summary: Local path of the secured secondary output file\n    title: Secured secondary output file path (universal apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n- APPDOME_WORKFLOW_LOGS: null\n  opts:\n    summary: Local path of the Appdome workflow logs file\n    title: Appdome workflow logs file\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/3.5.0/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2026-02-01T16:04:35.159228+02:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: 09c548a96cde19ed6f417be5db6b8152f8316b15\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name. The file extension (aab/apk) will be the same as\n      the original app. If not specified, the default output file will be same as\n      the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- multiple_trusted_signing_certs_path: null\n  opts:\n    category: Multiple Trusted Signing Certificates\n    description: 'Path to file containing multiple trusted signing certificates, or\n      an EnvVar representing its path (e.g. $MULTIPLE_TRUSTED_CERTS_PATH). Note: Multiple\n      Trusted Signing Certificates can''t work alongside ''Google Signing'' or ''Private/Auto-Dev-Signing''\n      categories.'\n    is_required: false\n    summary: Path to file containing multiple trusted signing certificates (or an\n      EnvVar representing the path)\n    title: Multiple Trusted Signing Certificates file path\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- download_deobfuscation: \"true\"\n  opts:\n    category: Deobfuscation Options\n    description: Select 'true' to download Appdome deobfuscation mapping zip file\n      to the Artifacts section.\n    is_required: false\n    summary: Select 'true' to download Appdome deobfuscation mapping zip file to the\n      Artifacts section.\n    title: Download deobfuscation mapping file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- crashlytics_app_id: null\n  opts:\n    category: Deobfuscation Options\n    description: Crashlytics App ID as appears in the Firebase account, for auto upload\n      Appdome deobfuscation mapping file.\n    is_required: false\n    title: Crashlytics App ID\n- datadog_api_key: null\n  opts:\n    category: Deobfuscation Options\n    description: Datadog API Key, for auto upload Appdome deobfuscation mapping file.\n    is_required: false\n    title: Datadog API Key\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS_device_farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\n- opts:\n    is_required: false\n    summary: File name of the workflow logs.\n    title: Workflow output logs file name\n  workflow_output_logs: null\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (universal apk). Available if Secondary Output is set to 'true' and the original app is .aab type\n    summary: Local path of the secured secondary output file\n    title: Secured secondary output file path (universal apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n- APPDOME_WORKFLOW_LOGS: null\n  opts:\n    summary: Local path of the Appdome workflow logs file\n    title: Appdome workflow logs file\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/3.6.0/step.yml",
    "content": "title: Appdome-Build-2Secure for Android\nsummary: |\n  Builds a mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android/issues\npublished_at: 2026-03-30T13:56:47.880158+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-android.git\n  commit: 78745644884ada60181d926689cf9b72826bf92b\nproject_type_tags:\n- android\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: null\n  opts:\n    is_required: true\n    summary: URL to app file (apk/aab) or an EnvVar representing its path (i.e. $BITRISE_APK_PATH\n      or $BITRISE_AAB_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name. The file extension (aab/apk) will be the same as\n      the original app. If not specified, the default output file will be same as\n      the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- android_keystore_url_env: null\n  opts:\n    category: On-Appdome Signing\n    description: Variable name from Project settings → Code Signing (no $). E.g. BITRISEIO_ANDROID_KEYSTORE_4_URL.\n      Leave empty for default primary or _1 keystore.\n    is_required: false\n    summary: Bitrise Code Signing keystore URL variable; password, alias, and key\n      password env names are derived from it.\n    title: Keystore URL — env var name\n- multiple_trusted_signing_certs_path: null\n  opts:\n    category: Multiple Trusted Signing Certificates\n    description: 'Path to file containing multiple trusted signing certificates, or\n      an EnvVar representing its path (e.g. $MULTIPLE_TRUSTED_CERTS_PATH). Note: Multiple\n      Trusted Signing Certificates can''t work alongside ''Google Signing'' or ''Private/Auto-Dev-Signing''\n      categories.'\n    is_required: false\n    summary: Path to file containing multiple trusted signing certificates (or an\n      EnvVar representing the path)\n    title: Multiple Trusted Signing Certificates file path\n- gp_signing: \"false\"\n  opts:\n    category: Google Signing\n    description: Sign the app for Google Play? If 'true', requires $SIGN_FINGERPRINT\n      in the Secrets tab.\n    is_required: true\n    title: Google Play Signing\n    value_options:\n    - \"true\"\n    - \"false\"\n- google_fingerprint: $GOOGLE_SIGN_FINGERPRINT\n  opts:\n    category: Google Signing\n    description: Google Sign Fingerprint for Google Play singing, or its Secret variable\n      name.\n    is_required: false\n    title: Google Sign Fingerprint\n- fingerprint: $SIGN_FINGERPRINT\n  opts:\n    category: Private/Auto-Dev Signing\n    description: Sign Fingerprint (not for Google Play singing), or its Secret variable\n      name.\n    is_required: false\n    title: Sign Fingerprint\n- download_deobfuscation: \"true\"\n  opts:\n    category: Deobfuscation Options\n    description: Select 'true' to download Appdome deobfuscation mapping zip file\n      to the Artifacts section.\n    is_required: false\n    summary: Select 'true' to download Appdome deobfuscation mapping zip file to the\n      Artifacts section.\n    title: Download deobfuscation mapping file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- crashlytics_app_id: null\n  opts:\n    category: Deobfuscation Options\n    description: Crashlytics App ID as appears in the Firebase account, for auto upload\n      Appdome deobfuscation mapping file.\n    is_required: false\n    title: Crashlytics App ID\n- datadog_api_key: null\n  opts:\n    category: Deobfuscation Options\n    description: Datadog API Key, for auto upload Appdome deobfuscation mapping file.\n    is_required: false\n    title: Datadog API Key\n- opts:\n    description: Select 'true' to create a Universal.apk file (applies to .aab app\n      types only).\n    is_required: false\n    title: Secondary Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  secondary_output: \"false\"\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS_device_farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\n- opts:\n    is_required: false\n    summary: File name of the workflow logs.\n    title: Workflow output logs file name\n  workflow_output_logs: null\noutputs:\n- APPDOME_SECURED_APK_PATH: null\n  opts:\n    description: |\n      Local path of the secured .apk file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .apk file\n    title: Secured .apk file path\n- APPDOME_SECURED_AAB_PATH: null\n  opts:\n    description: |\n      Local path of the secured .aab file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .aab file\n    title: Secured .aab file path\n- APPDOME_SECURED_SO_PATH: null\n  opts:\n    description: |\n      Local path of the secured secondary output file (universal apk). Available if Secondary Output is set to 'true' and the original app is .aab type\n    summary: Local path of the secured secondary output file\n    title: Secured secondary output file path (universal apk)\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n- APPDOME_WORKFLOW_LOGS: null\n  opts:\n    summary: Local path of the Appdome workflow logs file\n    title: Appdome workflow logs file\n"
  },
  {
    "path": "steps/appdome-build-2secure-android/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/1.0.12/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2023-06-27T16:05:25.418104+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: 33bc74d294a4e22295f826987e959bc6ba0adf80\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space), required for Auto-Dev-Singing\n      and On-Appdome Signing.\n    is_required: false\n    title: iOS Entitlement EnvVar/s\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/1.0.5/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2023-05-09T14:14:21.5537+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: 7de2a623cc5cd7dc3417acc9ee2e4f9fcdab6201\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space)\n    is_required: true\n    title: iOS Entitlement EnvVar/s\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/1.0.6/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2023-05-21T18:05:04.002205+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: dee73db1790b0b29068b733343e4d602065c5b9c\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space)\n    is_required: true\n    title: iOS Entitlement EnvVar/s\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/2.0.0/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2023-07-12T16:37:39.10928+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: b531b999f484193b96432755da9b1ee9e69a5938\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- certificate_file: null\n  opts:\n    description: Code signing cetificate file name (from the uploaded code signing\n      certificates) to use. If not provided, the LAST certificate among the uploaded\n      files to 'Code Signing & Files' section will be used. If you don't know the\n      file name of the certificate you want to use, download the certificate from\n      the Code Signing & Files section to your computer and type here its file name\n      and extension as was downloaded. Only ONE certificate file is supported.\n    is_required: false\n    title: Code signing cetificates (.p12) file name\n- opts:\n    description: List of provisioning profile file name/s (with no file extension,\n      separated by commas) from the uploaded provisioning profiles to use. If not\n      provided, all provisioning profiles uploaded to 'Code Signing & Files' section\n      will be used.\n    is_required: false\n    title: Provisioning profile file name/s\n  provisioning_profiles: null\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space), required for Auto-Dev-Singing\n      and On-Appdome Signing.\n    is_required: false\n    title: iOS Entitlement EnvVar/s\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - Bitbar\n    - Browserstack\n    - Saucelabs\n    - Lambdatest\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/3.0.0/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2023-08-11T09:36:54.586355+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: 634a0ddd6abfb9361940824f901e8d1a8be21b8b\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name (without extension). If not populated, the default\n      output file name will be the same as the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- certificate_file: null\n  opts:\n    description: Code signing cetificate file name (from the uploaded code signing\n      certificates) to use. If not provided, the LAST certificate among the uploaded\n      files to 'Code Signing & Files' section will be used. If you don't know the\n      file name of the certificate you want to use, download the certificate from\n      the Code Signing & Files section to your computer and type here its file name\n      and extension as was downloaded. Only ONE certificate file is supported.\n    is_required: false\n    title: Code signing cetificates (.p12) file name\n- opts:\n    description: List of provisioning profile file name/s (with no file extension,\n      separated by commas) from the uploaded provisioning profiles to use. If not\n      provided, all provisioning profiles uploaded to 'Code Signing & Files' section\n      will be used.\n    is_required: false\n    title: Provisioning profile file name/s\n  provisioning_profiles: null\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space), required for Auto-Dev-Singing\n      and On-Appdome Signing.\n    is_required: false\n    title: iOS Entitlement EnvVar/s\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - Bitbar\n    - Browserstack\n    - Saucelabs\n    - Lambdatest\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/3.1.0/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2024-08-19T13:23:28.948749+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: bd405ed42557ee19b4f3c52c0c583469b63122eb\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name (without extension). If not populated, the default\n      output file name will be the same as the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- certificate_file: null\n  opts:\n    description: Code signing cetificate file name (from the uploaded code signing\n      certificates) to use. If not provided, the LAST certificate among the uploaded\n      files to 'Code Signing & Files' section will be used. If you don't know the\n      file name of the certificate you want to use, download the certificate from\n      the Code Signing & Files section to your computer and type here its file name\n      and extension as was downloaded. Only ONE certificate file is supported.\n    is_required: false\n    title: Code signing cetificates (.p12) file name\n- opts:\n    description: List of provisioning profile file name/s (with no file extension,\n      separated by commas) from the uploaded provisioning profiles to use. If not\n      provided, all provisioning profiles uploaded to 'Code Signing & Files' section\n      will be used.\n    is_required: false\n    title: Provisioning profile file name/s\n  provisioning_profiles: null\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space), required for Auto-Dev-Singing\n      and On-Appdome Signing.\n    is_required: false\n    title: iOS Entitlement EnvVar/s\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS device farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/3.1.1/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2024-08-27T10:43:20.247755+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: 0571e76f16bcc45701d54464d5e2e4fb4b9df418\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name (without extension). If not populated, the default\n      output file name will be the same as the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- certificate_file: null\n  opts:\n    description: Code signing cetificate file name (from the uploaded code signing\n      certificates) to use. If not provided, the LAST certificate among the uploaded\n      files to 'Code Signing & Files' section will be used. If you don't know the\n      file name of the certificate you want to use, download the certificate from\n      the Code Signing & Files section to your computer and type here its file name\n      and extension as was downloaded. Only ONE certificate file is supported.\n    is_required: false\n    title: Code signing cetificates (.p12) file name\n- opts:\n    description: List of provisioning profile file name/s (with no file extension,\n      separated by commas) from the uploaded provisioning profiles to use. If not\n      provided, all provisioning profiles uploaded to 'Code Signing & Files' section\n      will be used.\n    is_required: false\n    title: Provisioning profile file name/s\n  provisioning_profiles: null\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space), required for Auto-Dev-Singing\n      and On-Appdome Signing.\n    is_required: false\n    title: iOS Entitlement EnvVar/s\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS_device_farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/3.2.0/step.yml",
    "content": "title: Appdome-Build-2Secure for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, building and signing mobile apps using Appdome's API. For details see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios/issues\npublished_at: 2024-10-15T18:05:12.882312+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: 1dbd0e62a3b6d637865cdbd10eb3653d8609e731\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step_init.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file (ipa) or an EnvVar representing its path (i.e. $BITRISE_IPA_PATH)\n    title: App file URL or EnvVar\n- opts:\n    is_required: false\n    summary: Output app file name (without extension). If not populated, the default\n      output file name will be the same as the original app but with Appdome_ prefix.\n    title: Output file name (without extension)\n  output_filename: null\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- certificate_file: null\n  opts:\n    description: Code signing cetificate file name (from the uploaded code signing\n      certificates) to use. If not provided, the LAST certificate among the uploaded\n      files to 'Code Signing & Files' section will be used. If you don't know the\n      file name of the certificate you want to use, download the certificate from\n      the Code Signing & Files section to your computer and type here its file name\n      and extension as was downloaded. Only ONE certificate file is supported.\n    is_required: false\n    title: Code signing cetificates (.p12) file name\n- opts:\n    description: List of provisioning profile file name/s (with no file extension,\n      separated by commas) from the uploaded provisioning profiles to use. If not\n      provided, all provisioning profiles uploaded to 'Code Signing & Files' section\n      will be used.\n    is_required: false\n    title: Provisioning profile file name/s\n  provisioning_profiles: null\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space), required for Auto-Dev-Singing\n      and On-Appdome Signing.\n    is_required: false\n    title: iOS Entitlement EnvVar/s\n- build_logs: \"false\"\n  opts:\n    description: Build the app with Appdome's Diagnostic Logs\n    is_required: true\n    title: Build With Diagnostic Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_to_test: None\n  opts:\n    description: Select a device cloud vendor this build will be ready for testing\n      on. Select None for a production build or for a vendor not in the list.\n    is_required: true\n    title: Build to test Vendor\n    value_options:\n    - None\n    - AWS_device_farm\n    - Bitbar\n    - Browserstack\n    - Firebase\n    - Katalon\n    - Kobiton\n    - Lambdatest\n    - Perfecto\n    - Tosca\n    - Saucelabs\n- opts:\n    is_required: false\n    summary: File name of the workflow logs.\n    title: Workflow output logs file name\n  workflow_output_logs: null\noutputs:\n- APPDOME_SECURED_IPA_PATH: null\n  opts:\n    description: |\n      Local path of the secured .ipa file. Available when 'Signing Method' set to 'On-Appdome' or 'Private-Signing'\n    summary: Local path of the secured .ipa file\n    title: Secured .ipa file path\n- APPDOME_PRIVATE_SIGN_SCRIPT_PATH: null\n  opts:\n    description: |\n      Local path of the .sh sign script file. Available when 'Signing Method' set to 'Auto-Dev-Signing'\n    summary: Local path of the .sh sign script file\n    title: .sh sign script file path\n- APPDOME_CERTIFICATE_PATH: null\n  opts:\n    summary: Local path of the Certified Secure Certificate .pdf file\n    title: Certified Secure Certificate .pdf file path\n- APPDOME_WORKFLOW_LOGS: null\n  opts:\n    summary: Local path of the Appdome workflow logs file\n    title: Appdome workflow logs file\n"
  },
  {
    "path": "steps/appdome-build-2secure-ios/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/appetize-deploy/0.1.3/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy the app to Appetize.io\ndescription: Deploy the app to Appetize.io\nwebsite: https://github.com/dag-io/appetize-deploy-step\nsource_code_url: https://github.com/dag-io/appetize-deploy-step.git\nsupport_url: https://github.com/dag-io/appetize-deploy-step/issues\npublished_at: 2016-06-02T17:29:18.851622215+02:00\nsource:\n  git: https://github.com/dag-io/appetize-deploy-step.git\n  commit: cce2b50b313197d23061197f3132163d30bb1a09\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- app_path: null\n  opts:\n    description: The full path to the application file (.app or .apk)\n    is_expand: true\n    is_required: true\n    summary: The full path to the application file (.app or .apk)\n    title: Application path\n- opts:\n    description: Is your app an Android or iOS app ?\n    is_expand: true\n    is_required: true\n    summary: Is your app an Android or iOS app ?\n    title: Platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- appetize_token: null\n  opts:\n    description: The token provided by Appetize.io\n    is_expand: true\n    is_required: true\n    summary: The token provided by Appetize.io\n    title: Appetize.io token\n- opts:\n    description: The public key in case you want to deploy this to build to an existing\n      app\n    is_expand: true\n    is_required: false\n    summary: The public key in case you want to deploy this to build to an existing\n      app\n    title: Public key\n  public_key: null\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/0.10.0/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy your app to Appetize.io\ndescription: |-\n  The Step deploys your app to [Appetize.io](https://appetize.io/). This way you can run your app in your browser for app demos, training, customer support, development, testing, etc.\n\n  ### Configuring the Step\n\n  1. Specify the path of the application in the **Application path** input.\n     **NOTE:** For iOS, provide the `.app` bundle or `.zip` or a `.tar.gz` file containing your compressed .app bundle. For Android, provide the `.apk` containing your app.\n  2. Add your Appetize API token to the **Appetize.io API Token** input.\n     You can read about the Appetize REST API here: [Appetize REST API Overview](https://docs.appetize.io/rest-api/overview)\n  3. (Optional) Add the public key of an existing app to the **Public key** input if you want to deploy this build to an existing app.\n  4. Set the **Enable verbose logging** to `true` to enable extended logs for debugging.\n\n  ### Troubleshooting\n\n  * [Android Troubleshooting](https://docs.appetize.io/platform/uploading-apps/android#troubleshooting)\n  * [iOS Troubleshooting](https://docs.appetize.io/platform/uploading-apps/ios#troubleshooting)\n\n  ### Useful links\n\n  * [Appetize REST API Overview](https://docs.appetize.io/rest-api/overview)\n\n  ### Related Steps\n\n  * [Xcode Build for Simulator](https://bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy/issues\npublished_at: 2023-10-03T11:51:36.895004952Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appetize-io-deploy.git\n  commit: 8364b2ff12db5e0bafccce83b7b677baa9a9f8c2\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appetize-io-deploy\ninputs:\n- app_path: null\n  opts:\n    description: |-\n      The full path to the application file (.app, .zip, .tar.gz, or .apk)\n\n      **NOTE:** For iOS, provide the `.app` bundle or `.zip` or a `.tar.gz` file containing your compressed .app bundle. For Android, provide the `.apk` containing your app.\n    is_required: true\n    summary: The full path to the application file (.app, .zip, .tar.gz, or .apk)\n    title: Application path\n- appetize_token: null\n  opts:\n    description: |-\n      The token provided by Appetize.io\n\n      **NOTE:** All users with admin or developer roles may request an API token after logging in and navigating to your [Account Dashboard](https://appetize.io/account).\n    is_required: true\n    is_sensitive: true\n    summary: The API token provided by Appetize.io\n    title: Appetize.io API Token\n- opts:\n    description: The public key in case you want to deploy this build to an existing\n      app\n    is_required: false\n    summary: The public key in case you want to deploy this build to an existing app\n    title: Public key\n  public_key: null\n- appetize_api: '@api.appetize.io/v1/apps'\n  opts:\n    description: Allows for customized Appetize.io api endpoints, default is @api.appetize.io/v1/apps\n    is_required: true\n    summary: Allows for customized Appetize.io api endpoints, default is @api.appetize.io/v1/apps\n    title: Appetize.io api endpoint\n- appetize_host: appetize.io\n  opts:\n    description: Allows for customized Appetize.io hosts, default is appetize.io\n    is_required: true\n    summary: Allows for customized Appetize.io hosts, default is appetize.io\n    title: Appetize.io host\n- opts:\n    description: Enable verbose log option for better debugging\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/0.9.0/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy the app to Appetize.io\ndescription: \"Deploy your app to Appetize.io and run it in your browser.\\nFor app\n  demos, training, customer support, development, testing, and more.\\n\\n**NOTE:**\n  For iOS, provide a `.zip` or `.tar.gz` file containing your compressed .app bundle\n  or the `.app` bundle. For Android, provide the `.apk` containing your app. \"\nwebsite: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy/issues\npublished_at: 2018-06-08T10:13:42.715871756+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-appetize-io-deploy.git\n  commit: df109f715e013131cb47199949b5efdeb9bfa0d8\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appetize-io-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\ninputs:\n- app_path: null\n  opts:\n    description: \"The full path to the application file (.app, .zip, .tar.gz, or .apk)\\n\\n**NOTE:**\n      For iOS, provide a `.zip` or `.tar.gz` file containing your compressed .app\n      bundle or the `.app` bundle. For Android, provide the `.apk` containing your\n      app. \"\n    is_expand: true\n    is_required: true\n    summary: The full path to the application file (.app, .zip, .tar.gz, or .apk)\n    title: Application path\n- appetize_token: null\n  opts:\n    description: |-\n      The token provided by Appetize.io\n\n      **NOTE:** You can reaquest an api token for Appetioze.io here:\n      [Appetize.io/request-api-token](https://appetize.io/docs#request-api-token)\n    is_expand: true\n    is_required: true\n    summary: The token provided by Appetize.io\n    title: Appetize.io token\n- opts:\n    description: The public key in case you want to deploy this to build to an existing\n      app\n    is_expand: true\n    is_required: false\n    summary: The public key in case you want to deploy this to build to an existing\n      app\n    title: Public key\n  public_key: null\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - true\n    - false\n  verbose: false\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/0.9.1/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy the app to Appetize.io\ndescription: \"Deploy your app to Appetize.io and run it in your browser.\\nFor app\n  demos, training, customer support, development, testing, and more.\\n\\n**NOTE:**\n  For iOS, provide a `.zip` or `.tar.gz` file containing your compressed .app bundle\n  or the `.app` bundle. For Android, provide the `.apk` containing your app. \"\nwebsite: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy/issues\npublished_at: 2018-07-16T10:27:21.438395014+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-appetize-io-deploy.git\n  commit: da19cebf2a207a6c9f3db8e632ac518b262f02ad\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appetize-io-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\ninputs:\n- app_path: null\n  opts:\n    description: \"The full path to the application file (.app, .zip, .tar.gz, or .apk)\\n\\n**NOTE:**\n      For iOS, provide a `.zip` or `.tar.gz` file containing your compressed .app\n      bundle or the `.app` bundle. For Android, provide the `.apk` containing your\n      app. \"\n    is_expand: true\n    is_required: true\n    summary: The full path to the application file (.app, .zip, .tar.gz, or .apk)\n    title: Application path\n- appetize_token: null\n  opts:\n    description: |-\n      The token provided by Appetize.io\n\n      **NOTE:** You can reaquest an api token for Appetioze.io here:\n      [Appetize.io/request-api-token](https://appetize.io/docs#request-api-token)\n    is_expand: true\n    is_required: true\n    summary: The token provided by Appetize.io\n    title: Appetize.io token\n- opts:\n    description: The public key in case you want to deploy this to build to an existing\n      app\n    is_expand: true\n    is_required: false\n    summary: The public key in case you want to deploy this to build to an existing\n      app\n    title: Public key\n  public_key: null\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - true\n    - false\n  verbose: false\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/0.9.3/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy your app to Appetize.io\ndescription: \"Deploy your app to [Appetize.io](https://appetize.io/) and run it in\n  your browser.\\nFor app demos, training, customer support, development, testing,\n  and more.\\n\\n**NOTE:** For iOS, provide a `.zip` or a `.tar.gz` file containing\n  your compressed .app bundle or the `.app` bundle. For Android, provide the `.apk`\n  containing your app. \"\nwebsite: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy/issues\npublished_at: 2018-08-31T10:53:44.558425652Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appetize-io-deploy.git\n  commit: 6aa16b2880d1ee5bf80abc56614dbee6dd75b958\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appetize-io-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\ninputs:\n- app_path: null\n  opts:\n    description: \"The full path to the application file (.app, .zip, .tar.gz, or .apk)\\n\\n**NOTE:**\n      For iOS, provide a `.zip` or `.tar.gz` file containing your compressed .app\n      bundle or the `.app` bundle. For Android, provide the `.apk` containing your\n      app. \"\n    is_required: true\n    summary: The full path to the application file (.app, .zip, .tar.gz, or .apk)\n    title: Application path\n- appetize_token: null\n  opts:\n    description: |-\n      The token provided by Appetize.io\n\n      **NOTE:** You can reaquest an api token for Appetioze.io here:\n      [Appetize.io/request-api-token](https://appetize.io/docs#request-api-token)\n    is_required: true\n    is_sensitive: true\n    summary: The token provided by Appetize.io\n    title: Appetize.io token\n- opts:\n    description: The public key in case you want to deploy this to build to an existing\n      app\n    is_required: false\n    summary: The public key in case you want to deploy this to build to an existing\n      app\n    title: Public key\n  public_key: null\n- opts:\n    description: Enable verbose log option for better debug\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debug\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/0.9.4/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy your app to Appetize.io\ndescription: \"Deploy your app to [Appetize.io](https://appetize.io/) and run it in\n  your browser.\\nFor app demos, training, customer support, development, testing,\n  and more.\\n\\n**NOTE:** For iOS, provide a `.zip` or a `.tar.gz` file containing\n  your compressed .app bundle or the `.app` bundle. For Android, provide the `.apk`\n  containing your app. \"\nwebsite: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy/issues\npublished_at: 2019-12-17T09:27:06.889342486Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appetize-io-deploy.git\n  commit: d8af79622e3970e4efc22ee90e7f952bcbdbf704\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appetize-io-deploy\ninputs:\n- app_path: null\n  opts:\n    description: \"The full path to the application file (.app, .zip, .tar.gz, or .apk)\\n\\n**NOTE:**\n      For iOS, provide a `.zip` or `.tar.gz` file containing your compressed .app\n      bundle or the `.app` bundle. For Android, provide the `.apk` containing your\n      app. \"\n    is_required: true\n    summary: The full path to the application file (.app, .zip, .tar.gz, or .apk)\n    title: Application path\n- appetize_token: null\n  opts:\n    description: |-\n      The token provided by Appetize.io\n\n      **NOTE:** You can reaquest an api token for Appetize.io here:\n      [Appetize.io/request-api-token](https://appetize.io/docs#request-api-token)\n    is_required: true\n    is_sensitive: true\n    summary: The token provided by Appetize.io\n    title: Appetize.io token\n- opts:\n    description: The public key in case you want to deploy this build to an existing\n      app\n    is_required: false\n    summary: The public key in case you want to deploy this build to an existing app\n    title: Public key\n  public_key: null\n- opts:\n    description: Enable verbose log option for better debugging\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/0.9.5/step.yml",
    "content": "title: Appetize.io deploy\nsummary: Deploy your app to Appetize.io\ndescription: |-\n  The Step deploys your app to [Appetize.io](https://appetize.io/). This way you can run your app in your browser for app demos, training, customer support, development, testing, etc.\n\n  ### Configuring the Step\n\n  1. Specify the path of the application in the **Application path** input.\n     **NOTE:** For iOS, provide the `.app` bundle or `.zip` or a `.tar.gz` file containing your compressed .app bundle. For Android, provide the `.apk` containing your app.\n  1. Add your Appetize.io API token to the **Appetize.io token** input.\n     You can read about the Appetize.io API here: [Appetize.io API Overview](https://docs.appetize.io/api/overview)\n  1. (Optional) Add the public key of an existing app to the **Public key** input if you want to deploy this build to an existing app.\n  1. Set the **Enable verbose logging** to `true` to enable extended logs for debugging.\n\n  ### Troubleshooting\n\n  ### Useful links\n\n  * [Appetize.io API Overview](https://docs.appetize.io/api/overview)\n\n  ### Related Steps\n\n  * [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  * [Xcode Archive for Mac](https://github.com/bitrise-steplib/steps-xcode-archive-mac)\n  * [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-appetize-io-deploy/issues\npublished_at: 2023-10-03T11:50:22.92638014Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-appetize-io-deploy.git\n  commit: 34ad14f7e15bde89b5ffcb40b7e6ae301d549d65\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-appetize-io-deploy\ninputs:\n- app_path: null\n  opts:\n    description: |-\n      The full path to the application file (.app, .zip, .tar.gz, or .apk)\n\n      **NOTE:** For iOS, provide the `.app` bundle or `.zip` or a `.tar.gz` file containing your compressed .app bundle. For Android, provide the `.apk` containing your app.\n    is_required: true\n    summary: The full path to the application file (.app, .zip, .tar.gz, or .apk)\n    title: Application path\n- appetize_token: null\n  opts:\n    description: |-\n      The token provided by Appetize.io\n\n      **NOTE:** You can request an API token for Appetize.io here:\n      [Appetize.io/request-api-token](https://appetize.io/docs#request-api-token)\n    is_required: true\n    is_sensitive: true\n    summary: The token provided by Appetize.io\n    title: Appetize.io token\n- opts:\n    description: The public key in case you want to deploy this build to an existing\n      app\n    is_required: false\n    summary: The public key in case you want to deploy this build to an existing app\n    title: Public key\n  public_key: null\n- opts:\n    description: Enable verbose log option for better debugging\n    is_expand: true\n    is_required: true\n    summary: Enable verbose log option for better debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- APPETIZE_APP_URL: null\n  opts:\n    description: The public URL to use the app\n    is_expand: false\n    is_required: true\n    summary: The public URL to use the app\n    title: Public URL for the app\n"
  },
  {
    "path": "steps/appetize-deploy/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/appgallery-deploy/0.9.0/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads APK/AAB to Huawei App Gallery\ndescription: \"This step deploys a .apk/.aab file to Huawei App Gallery.\\nIt's based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted).\"\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2020-12-13T23:39:33+00:00\nsource:\n   git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n   commit: 6d0cc1649adf7ca185ce4c910b2f59d6227e835d\nhost_os_tags:\n  - osx-10.10\n  - ubuntu-16.04\nproject_type_tags:\n  - android\n  - xamarin\n  - react-native\n  - flutter \n\ntype_tags:\n  - deploy\n\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\n\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\n\n\ntoolkit:\n  bash:\n    entry_file: step.sh\n\n\ninputs:\n  - file_path: $BITRISE_APK_PATH\n    opts:\n      category: Config\n      title: File path\n      description: Path to generated APK/AAB file to deploy.\n      is_expand: true\n      is_required: true\n\n  - huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n    opts:\n      category: Config\n      title: File name\n      description: Unique name of APK/AAB file upload.\n      is_expand: true\n      is_required: true\n\n  - huawei_app_id:\n    opts:\n      category: Config\n      title: App ID\n      description: App ID can be found in the `App information` section in App Gallery Connect.\n      is_expand: true\n      is_required: true\n\n  - huawei_client_id:\n    opts:\n      category: Config\n      title: Client ID\n      description: Client ID generated in `AppGallery Connect -> Users and permissions -> API key -> Connect API -> API client`\n      is_expand: true\n      is_required: true\n\n  - huawei_client_secret:\n    opts:\n      category: Config\n      description: Key Secret generated in `AppGallery Connect -> Users and permissions -> API key -> Connect API -> API client`\n      title: Key\n      is_expand: true\n      is_required: true\n      is_sensitive: true\n\n  - lang: en-GB\n    opts:\n      category: Config\n      title: Language Type\n      description: For more languages refer to [Language Types](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-reference-langtype)\n      is_expand: true\n      is_required: false\n\n  - release_type: 1\n    opts:\n      category: Config\n      title: Release Type\n      description: App release mode (1 - on the entire network | 3 - by phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n      is_expand: true\n      is_required: false\n\n  - show_debug_logs: \"no\"\n    opts:\n      category: Debug\n      title: \"Show debug logs?\"\n      description: |\n        If debug=yes the step will print debug infos\n      value_options:\n        - \"no\"\n        - \"yes\""
  },
  {
    "path": "steps/appgallery-deploy/1.0.0/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-01-20T15:10:31.098379Z\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: abb6d03b8242d7baf1512df95f50c75e736c8f65\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- lang: en-GB\n  opts:\n    category: Config\n    description: For more languages refer to [Language Types](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-reference-langtype)\n    is_expand: true\n    is_required: false\n    title: Language Type\n- opts:\n    category: Config\n    description: App release mode (1 - on the entire network | 3 - by phase)[Release\n      Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: false\n    title: Release Type\n  release_type: 1\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.0/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-02-16T13:54:29.036326Z\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: 1ca84c79dc1cc0fa4556651875305eee6e2bbc87\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (true). Setting to false will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n  submit_for_review: true\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Scheduled Release Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase.Enter an integer or\n      decimal greater than 0 and less than 100. The value can contain up to two decimal\n      places. For a version released by phase, the release percentage must increase\n      gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.1/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-02-23T15:06:39.301374Z\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: a78aae58e21f29bd38068708813188d5ea74d946\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase.Enter an integer or\n      decimal greater than 0 and less than 100. The value can contain up to two decimal\n      places. For a version released by phase, the release percentage must increase\n      gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.2/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-02-24T00:13:08.968898Z\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: 85a1a415ed943218a803b57ed94e9c8d84612817\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase.Enter an integer or\n      decimal greater than 0 and less than 100. The value can contain up to two decimal\n      places. For a version released by phase, the release percentage must increase\n      gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.3/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-02-25T14:27:02.612966Z\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: 7b04772072d6f6ae79a21dfbd4e9791d29f59eb5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase.Enter an integer or\n      decimal greater than 0 and less than 100. The value can contain up to two decimal\n      places. For a version released by phase, the release percentage must increase\n      gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.4/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-08-07T13:50:16.273005+01:00\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: ef7f72862c80b8028c3e8ff50c5365b44cc3b232\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase.Enter an integer or\n      decimal greater than 0 and less than 100. The value can contain up to two decimal\n      places. For a version released by phase, the release percentage must increase\n      gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.5/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2021-08-09T15:34:25.744735+01:00\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: 5e35cedfa8fd2a5d46cb203114e8f8bacae1c88e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase. Enter an integer\n      or decimal greater than 0 and less than 100. The value can contain up to two\n      decimal places. For a version released by phase, the release percentage must\n      increase gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.6/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2023-10-02T10:07:24.329817+01:00\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: 569805655afd5e556935388beb3f77865a1901ba\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase. Enter an integer\n      or decimal greater than 0 and less than 100. The value can contain up to two\n      decimal places. For a version released by phase, the release percentage must\n      increase gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.7/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2023-10-12T11:01:51.611027+01:00\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: b58ef32e772f8cfef63c95b0ad94c4a87b216896\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase. Enter an integer\n      or decimal greater than 0 and less than 100. The value can contain up to two\n      decimal places. For a version released by phase, the release percentage must\n      increase gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.8/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2025-07-12T14:04:08.335762+01:00\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: 7a9e31e3981d2d32d2cd50c7a1f4c5789a2c84e4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`. For 19-digit Client IDs, wrap the\n      value in quotes to avoid precision issues.\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase. Enter an integer\n      or decimal greater than 0 and less than 100. The value can contain up to two\n      decimal places. For a version released by phase, the release percentage must\n      increase gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/1.5.9/step.yml",
    "content": "title: Deploy to Huawei App Gallery\nsummary: Uploads and releases apps to Huawei App Gallery\ndescription: |-\n  Uploads and releases apps to Huawei App Gallery.\n\n  This step is based on [AppGallery Connect API](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-getstarted)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-deploy\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-deploy\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-deploy/issues\npublished_at: 2025-07-16T22:06:34.652451+01:00\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-deploy.git\n  commit: c97a512508c886cefba3c494ce441aae0ca14f31\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    category: Config\n    description: Path to generated APK/AAB file to deploy.\n    is_expand: true\n    is_required: true\n    title: File path\n- huawei_filename: app_release_${BITRISE_BUILD_NUMBER}.apk\n  opts:\n    category: Config\n    description: Unique name of APK/AAB file upload.\n    is_expand: true\n    is_required: true\n    title: File name\n- huawei_app_id: null\n  opts:\n    category: Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`. For 19-digit Client IDs, wrap the\n      value in quotes to avoid precision issues.\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- opts:\n    category: Config\n    description: App release mode (Entire network | By phase)[Release Type](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-app-submit-with-file_v2)\n    is_expand: true\n    is_required: true\n    title: Release Type\n    value_options:\n    - Entire Network\n    - By Phase\n  release_type: Entire Network\n- opts:\n    category: Config\n    description: By default is marked as For Review (\"true\"). Setting to \"false\" will\n      submit the relase as a Draft.\n    is_expand: true\n    is_required: false\n    title: Submit for Review\n    value_options:\n    - \"true\"\n    - \"false\"\n  submit_for_review: \"true\"\n- opts:\n    category: Phase\n    description: Start time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-17T13:20:15\n    is_expand: true\n    is_required: false\n    title: Phase Release Start Time\n  phase_release_start_time: null\n- opts:\n    category: Phase\n    description: End time of the validity period of the release by phase. The value\n      is UTC time in the following format yyyy-MM-ddTHH:mm:ssZZ. Example:2021-02-20T07:05:15\n    is_expand: true\n    is_required: false\n    title: Phase Release End Time\n  phase_release_end_time: null\n- opts:\n    category: Phase\n    description: Percentage of target users of release by phase. Enter an integer\n      or decimal greater than 0 and less than 100. The value can contain up to two\n      decimal places. For a version released by phase, the release percentage must\n      increase gradually for different phases.\n    is_expand: true\n    is_required: false\n    title: Phase Release Percentage\n  phase_release_percentage: null\n- opts:\n    category: Phase\n    description: Remarks of the phased release, such as release features, with up\n      to 500 characters. The description is not displayed to users or Huawei reviewers.\n      It is displayed only on the version information page for your reference.\n    is_expand: true\n    is_required: false\n    title: Phase Description\n  phase_release_description: null\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\n"
  },
  {
    "path": "steps/appgallery-deploy/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/appium-server/0.0.2/step.yml",
    "content": "title: Run Appium Server\nsummary: |\n  Install and Run Appium Server\ndescription: |\n  Install and Run Appium Server on Bitrise to be able to run our mobile automated tests\nwebsite: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-appium-server/issues\npublished_at: 2021-08-18T23:06:40.395281+02:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-appium-server.git\n  commit: a42128594674b52114a883558124aad26af8f38f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: nodejs\n  apt_get:\n  - name: nodejs\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appium_version: v1.21.0\n  opts:\n    description: \"Specify the Appium version that you want to install for example\n      v1.21.0 \\n\"\n    is_expand: false\n    is_required: true\n    summary: Specify the Appium version that you want to install\n    title: Appium Version\n    value_options:\n    - v1.21.0\n    - v1.20.2\n"
  },
  {
    "path": "steps/appium-server/0.0.4/step.yml",
    "content": "title: Run Appium Server\nsummary: |\n  Install and Run Appium Server\ndescription: |\n  Install and Run Appium Server on Bitrise to be able to run our mobile automated tests\nwebsite: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-appium-server/issues\npublished_at: 2021-08-27T16:04:04.474263+02:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-appium-server.git\n  commit: 6a427500aee5a429f61d1bda9632a7e30ec455d0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: nodejs\n  apt_get:\n  - name: nodejs\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appium_version: v1.21.0\n  opts:\n    description: |\n      Specify the Appium version that you want to install for example v1.21.0.\n    is_expand: false\n    is_required: true\n    summary: Specify the Appium version that you want to install\n    title: Appium Version\n"
  },
  {
    "path": "steps/appium-server/0.0.5/step.yml",
    "content": "title: Run Appium Server\nsummary: |\n  Install and Run Appium Server\ndescription: |\n  Install and Run Appium Server on Bitrise to be able to run our mobile automated tests\nwebsite: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-appium-server/issues\npublished_at: 2022-11-11T15:37:52.793685+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-appium-server.git\n  commit: 06cee7a3276a99d324c17c092ff04a1c1a0a099b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: nodejs\n  apt_get:\n  - name: nodejs\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appium_version: next\n  opts:\n    description: |\n      Specify the Appium version that you want to install for example v1.21.0.\n    is_expand: false\n    is_required: true\n    summary: Specify the Appium version that you want to install\n    title: Appium Version\n"
  },
  {
    "path": "steps/appium-server/0.0.6/step.yml",
    "content": "title: Run Appium Server\nsummary: |\n  Install and Run Appium Server\ndescription: |\n  Install and Run Appium Server on Bitrise to be able to run our mobile automated tests\nwebsite: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-appium-server\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-appium-server/issues\npublished_at: 2023-01-31T12:47:30.187595+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-appium-server.git\n  commit: a5061208a33adf794534bfd6c09ee7e7c6d6292a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: nodejs\n  apt_get:\n  - name: nodejs\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- appium_version: next\n  opts:\n    description: |\n      Specify the Appium version that you want to install for example v1.21.0.\n    is_expand: false\n    is_required: true\n    summary: Specify the Appium version that you want to install\n    title: Appium Version\n"
  },
  {
    "path": "steps/appium-server/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/applivery-android/0.1.0/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android Application to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify testers.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *Account API Key* for you account and the *App Id* for the app.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2016-02-09T23:36:10.028033474+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: f76628cef4a36049026b74d0a96eabdc5d3f7e8e\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\n- Applivery\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- api_token: \"\"\n  opts:\n    description: |-\n      This is the API Key to access your account.\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Developers menu option from the left side menu and copy it from the\n      Account API Key section.\n    is_required: true\n    summary: \"\"\n    title: Account API Key\n- app_id: \"\"\n  opts:\n    description: |-\n      This is the App Id that identifies your App in Applivery.com\n\n      ## Where to get the App Id?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Applications menu option from the left side menu, click on the desired App.\n      You'll find the App Id inside the (i) information block (written in red).\n    is_required: false\n    summary: \"\"\n    title: 'Applivery: App ID'\n- notes: Deployed with Bitrise Applivery.com Android Deploy Step.\n  opts:\n    description: Additional build/release notes\n    summary: \"\"\n    title: Notes attached to the deploy\n- notify: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your testers vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Comma-separated list of tags\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  version_name: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.2.0/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android Application to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify testers.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *Account API Key* for you account and the *App Id* for the app.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2016-04-28T01:02:47.449031585+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: 89c14039fb7936d5557305586f621831f48969f5\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\n- Applivery\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- api_token: $APPLIVERY_API_TOKEN\n  opts:\n    description: |-\n      This is the API Key to access your account.\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Developers menu option from the left side menu and copy it from the\n      Account API Key section.\n    is_required: true\n    summary: \"\"\n    title: Account API Key\n- app_id: $APPLIVERY_APP_ID\n  opts:\n    description: |-\n      This is the App Id that identifies your App in Applivery.com\n\n      ## Where to get the App Id?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Applications menu option from the left side menu, click on the desired App.\n      You'll find the App Id inside the (i) information block (written in red).\n    is_required: false\n    summary: \"\"\n    title: 'Applivery: App ID'\n- notes: Deployed with Bitrise Applivery.com Android Deploy Step.\n  opts:\n    description: Additional build/release notes\n    summary: \"\"\n    title: Notes attached to the deploy\n- notify: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your testers vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Comma-separated list of tags\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  version_name: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.2.1/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android Application to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify testers.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *Account API Key* for you account and the *App Id* for the app.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2017-01-04T14:03:34.982420013+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: d464399d4454709804d3c9d347afa12d20ae7d8a\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- api_token: $APPLIVERY_API_TOKEN\n  opts:\n    description: |-\n      This is the API Key to access your account.\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Developers menu option from the left side menu and copy it from the\n      Account API Key section.\n    is_required: true\n    summary: \"\"\n    title: Account API Key\n- app_id: $APPLIVERY_APP_ID\n  opts:\n    description: |-\n      This is the App Id that identifies your App in Applivery.com\n\n      ## Where to get the App Id?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Applications menu option from the left side menu, click on the desired App.\n      You'll find the App Id inside the (i) information block (written in red).\n    is_required: false\n    summary: \"\"\n    title: 'Applivery: App ID'\n- notes: Deployed with Bitrise Applivery.com Android Deploy Step.\n  opts:\n    description: Additional build/release notes\n    summary: \"\"\n    title: Notes attached to the deploy\n- notify: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your testers vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- autoremove: \"true\"\n  opts:\n    description: Automatically remove the oldest build before uploading a new one\n      to prevent reaching your account limits.\n    is_required: false\n    summary: \"\"\n    title: Automatically remove the oldest build?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  version_name: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.3.0/step.yml",
    "content": "title: Applivery.com v3 Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2019-06-04T18:14:41.973346+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: 1f0215d8e5c934c2821b114ea488e9dd83295fa2\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.3.1/step.yml",
    "content": "title: Applivery.com v3 Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2019-06-14T12:33:24.455085+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: ee4d75cd1334830168fb2cd87d2ed3e7f38a52db\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.3.2/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2019-06-14T17:00:20.975236+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: 19012f619eda2a0cffe1cbae4f16507cb2f64dbf\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.3.3/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2020-03-26T16:25:05.770629+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: c135fabb437e4209acedaa99342e8affe5070449\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: APK file path\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: AAB file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/0.3.4/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2020-06-08T21:37:04.862208+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: c135fabb437e4209acedaa99342e8affe5070449\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: APK file path\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: AAB file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/1.0.0/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2021-01-31T23:05:14.478861+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: 033b9d477facdbb43c0bf88a64f341e01ccffc51\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: APK file path\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: AAB file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\n- filter: \"\"\n  opts:\n    description: 'Comma-separated list of groups that will be notified. i.e.: group1,group2|group3\n      = (group1 AND group2) OR (group3)'\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of groups that will be notified\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/1.0.1/step.yml",
    "content": "title: Applivery.com Android Deploy\nsummary: Deploy your awesome Android App to Applivery.com\ndescription: |-\n  Deploy an Android application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-android-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-android-deploy\nsupport_url: https://github.com/applivery/steps-applivery-android-deploy/issues\npublished_at: 2025-01-30T11:10:55.913686+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-android-deploy.git\n  commit: 9c1e292a034a8ac1464d0e437ce0ee779ef728ef\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: APK file path\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: \"\"\n    is_required: false\n    summary: \"\"\n    title: AAB file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\n- filter: \"\"\n  opts:\n    description: 'Comma-separated list of groups that will be notified. i.e.: group1,group2|group3\n      = (group1 AND group2) OR (group3)'\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of groups that will be notified\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-android/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/applivery-ios/0.1.1/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS Application to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify testers.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *Account API Key* for you account and the *App Id* for the app.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2016-02-08T21:08:30.248904107+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: e770b31324534126ba52a2ed84027dc86999e035\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- Applivery\n- iOS\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- api_token: \"\"\n  opts:\n    description: |-\n      This is the API Key to access your account.\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Developers menu option from the left side menu and copy it from the\n      Account API Key section.\n    is_required: true\n    summary: \"\"\n    title: Account API Key\n- app_id: \"\"\n  opts:\n    description: |-\n      This is the App Id that identifies your App in Applivery.com\n\n      ## Where to get the App Id?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Applications menu option from the left side menu, click on the desired App.\n      You'll find the App Id inside the (i) information block (written in red).\n    is_required: false\n    summary: \"\"\n    title: 'Applivery: App ID'\n- notes: Deployed with Bitrise Applivery.com iOS Deploy Step.\n  opts:\n    description: Additional build/release notes\n    summary: \"\"\n    title: Notes attached to the deploy\n- notify: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your testers vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Comma-separated list of tags\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  version_name: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/0.2.0/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS Application to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify testers.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *Account API Key* for you account and the *App Id* for the app.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2016-04-28T00:57:25.625748376+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: fcfa296d86595058db86ffdce7a1dfc26f017c52\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- Applivery\n- iOS\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- api_token: $APPLIVERY_API_TOKEN\n  opts:\n    description: |-\n      This is the API Key to access your account.\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Developers menu option from the left side menu and copy it from the\n      Account API Key section.\n    is_required: true\n    summary: \"\"\n    title: Account API Key\n- app_id: $APPLIVERY_APP_ID\n  opts:\n    description: |-\n      This is the App Id that identifies your App in Applivery.com\n\n      ## Where to get the App Id?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Applications menu option from the left side menu, click on the desired App.\n      You'll find the App Id inside the (i) information block (written in red).\n    is_required: false\n    summary: \"\"\n    title: 'Applivery: App ID'\n- notes: Deployed with Bitrise Applivery.com iOS Deploy Step.\n  opts:\n    description: Additional build/release notes\n    summary: \"\"\n    title: Notes attached to the deploy\n- notify: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your testers vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Comma-separated list of tags\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  version_name: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/0.2.1/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS Application to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify testers.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *Account API Key* for you account and the *App Id* for the app.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2017-01-04T14:02:04.895044503+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: d26536b4a5f2f148058aaf9623dc5c52c791a477\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- api_token: $APPLIVERY_API_TOKEN\n  opts:\n    description: |-\n      This is the API Key to access your account.\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Developers menu option from the left side menu and copy it from the\n      Account API Key section.\n    is_required: true\n    summary: \"\"\n    title: Account API Key\n- app_id: $APPLIVERY_APP_ID\n  opts:\n    description: |-\n      This is the App Id that identifies your App in Applivery.com\n\n      ## Where to get the App Id?\n\n      Sign in to your [Applivery.com](http://dashboard.applivery.com) account,\n      click on Applications menu option from the left side menu, click on the desired App.\n      You'll find the App Id inside the (i) information block (written in red).\n    is_required: false\n    summary: \"\"\n    title: 'Applivery: App ID'\n- notes: Deployed with Bitrise Applivery.com iOS Deploy Step.\n  opts:\n    description: Additional build/release notes\n    summary: \"\"\n    title: Release notes\n- notify: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your testers vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"true\"\n    - \"false\"\n- autoremove: \"true\"\n  opts:\n    description: Automatically remove the oldest build before uploading a new one\n      to prevent reaching your account limits.\n    is_required: false\n    summary: \"\"\n    title: (Optional) Automatically remove the oldest build?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  version_name: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/0.3.0/step.yml",
    "content": "title: Applivery.com v3 iOS Deploy\nsummary: Deploy your awesome iOS App to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery..com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2019-06-04T18:13:07.508147+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: 29d9bf9f15dd71010eccc1dab1239b6dd1830b9b\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- IPA_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/0.3.1/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS App to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery.com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2019-06-14T17:20:45.281533+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: 29d5d7a23a201cc363208650dcdd6c32cfcc9241\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\n- opts:\n    description: If you enable this option the step will download your code signing\n      files from Bitrise Code Signing Tab and it will upload it to Applivery.\n    is_required: true\n    summary: Applivery will use these files to help you fix installation issues with\n      your endusers by analyzing those files.\n    title: Enable to upload certificates and provisioning profiles to Applivery.\n    value_options:\n    - \"true\"\n    - \"false\"\n  uploadCodeSigning: \"false\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/0.3.2/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS App to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery.com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2020-06-08T21:41:42.464006+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: 13355a4fc2dda1a1297fb8a6ae6175ae4e814653\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\n- opts:\n    description: If you enable this option the step will download your code signing\n      files from Bitrise Code Signing Tab and it will upload it to Applivery.\n    is_required: true\n    summary: Applivery will use these files to help you fix installation issues with\n      your endusers by analyzing those files.\n    title: Enable to upload certificates and provisioning profiles to Applivery.\n    value_options:\n    - \"true\"\n    - \"false\"\n  uploadCodeSigning: \"false\"\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/1.0.0/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS App to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery.com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2021-01-31T23:28:08.574208+01:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: 8ebcd01013efeabf07ea53248da4d49b0a7c4825\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\n- opts:\n    description: If you enable this option the step will download your code signing\n      files from Bitrise Code Signing Tab and it will upload it to Applivery.\n    is_required: true\n    summary: Applivery will use these files to help you fix installation issues with\n      your endusers by analyzing those files.\n    title: Enable to upload certificates and provisioning profiles to Applivery.\n    value_options:\n    - \"true\"\n    - \"false\"\n  uploadCodeSigning: \"false\"\n- filter: \"\"\n  opts:\n    description: 'Comma-separated list of groups that will be notified. i.e.: group1,group2|group3\n      = (group1 AND group2) OR (group3)'\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of groups that will be notified\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/1.0.1/step.yml",
    "content": "title: Applivery.com iOS Deploy\nsummary: Deploy your awesome iOS App to Applivery.com\ndescription: |-\n  Deploy an iOS application to [Applivery](http://www.applivery.com),\n  add notes and notify Collaborators and Employees.\n\n  Register a Applivery account at [http://www.applivery.com/](http://www.applivery.com)\n  and create an App to utilize this step.\n\n  You also need to get your *App Token* of your App that can be found under your App Settings.\nwebsite: https://github.com/applivery/steps-applivery-ios-deploy\nsource_code_url: https://github.com/applivery/steps-applivery-ios-deploy\nsupport_url: https://github.com/applivery/steps-applivery-ios-deploy/issues\npublished_at: 2024-05-27T12:27:58.840935+02:00\nsource:\n  git: https://github.com/applivery/steps-applivery-ios-deploy.git\n  commit: 3d5f6e737d3ed2593cbb6685994fc8fb61bf0f84\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- appToken: $APPLIVERY_APP_TOKEN\n  opts:\n    description: |-\n      This is your App Token\n\n      ## Where to get the Applivery Account API Key?\n\n      Sign in to your [Applivery](http://dashboard.applivery.io) account,\n      click on your App and the navigate to the Settings menu option. Scroll down to the Integrations section and click on New Token button to generate a new token. Then, copy & paste it here. [Read more](https://www.applivery.com/docs/rest-api/authentication/)\n    is_required: true\n    summary: \"\"\n    title: App Token\n- changelog: \"\"\n  opts:\n    description: Additional build/release notes or changelog attached to the deploy\n    summary: \"\"\n    title: (Optional) Changelog or release notes\n- notifyCollaborators: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Collaborators\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Collaborators?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyEmployees: \"true\"\n  opts:\n    description: This flag allows you to automatically notify your project Employees\n      vía email.\n    is_required: true\n    summary: \"\"\n    title: Notify Employees?\n    value_options:\n    - \"true\"\n    - \"false\"\n- notifyMessage: \"\"\n  opts:\n    description: Notification message to be sent along with the email notification\n    summary: \"\"\n    title: (Optional) Notification message\n- opts:\n    description: Comma-separated list of tags to easily identify the build\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of tags\n  tags: \"\"\n- opts:\n    description: Human readable version name for this build.\n    summary: \"\"\n    title: (Optional) Human readable version name\n  versionName: \"\"\n- opts:\n    description: If you enable this option the step will download your code signing\n      files from Bitrise Code Signing Tab and it will upload it to Applivery.\n    is_required: true\n    summary: Applivery will use these files to help you fix installation issues with\n      your endusers by analyzing those files.\n    title: Enable to upload certificates and provisioning profiles to Applivery.\n    value_options:\n    - \"true\"\n    - \"false\"\n  uploadCodeSigning: \"false\"\n- filter: \"\"\n  opts:\n    description: 'Comma-separated list of groups that will be notified. i.e.: group1,group2|group3\n      = (group1 AND group2) OR (group3)'\n    is_required: false\n    summary: \"\"\n    title: (Optional) Comma-separated list of groups that will be notified\noutputs:\n- APPLIVERY_DEPLOY_STATUS: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n"
  },
  {
    "path": "steps/applivery-ios/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/apps-decompiler/1.0.1/step.yml",
    "content": "title: Mobile apps decompiler\nsummary: |\n  Decompile mobile APK and/or IPA to look inside\ndescription: |\n  Decompile mobile APK and/or IPA to look inside\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after the compilation step (\"Android Build\" for android, \"Xcode Archive\" for iOS)\n  - Launch \"Deploy to Bitrise.io\" step after this one to deploy report files to artifacts\nwebsite: https://github.com/odemolliens/bitrise-step-apps-decompiler\nsource_code_url: https://github.com/odemolliens/bitrise-step-apps-decompiler\nsupport_url: https://github.com/odemolliens/bitrise-step-apps-decompiler/issues\npublished_at: 2021-01-25T09:05:10.83394+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-apps-decompiler.git\n  commit: f34307a75dbe37cda5252dbf1c02a49f83972893\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: apktool\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- decompile_android: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Do you want decompile Android APK?\n    title: Decompile Android APK\n    value_options:\n    - \"yes\"\n    - \"no\"\n- decompile_ios: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Do you want decompile iOS IPA?\n    title: Decompile iOS IPA\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      You can use the artifacts from another bitrise build of the same project.\n      If you launch this step on the build where you launched Android build step eg. you don't have to set this key\n    is_expand: true\n    is_required: false\n    summary: Build slug of the build where you have the APK/IPA into artifacts\n    title: External Build slug\n  outside_build_slug: null\n- android_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      You have to set this key if you launch this step directly in the build where you generate your APK, in that case, be careful to launch it necessarily after these build steps\n          - `Android Build` for android\n      Otherwis, you can launch this step in another Bitrise build, in that case, you don't need to setup this key but `outside_build_slug` to download your APK to do quality checks\n    is_expand: true\n    is_required: true\n    title: APK path\n- ios_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      You have to set this key if you launch this step directly in the build where you generate your IPA, in that case, be careful to launch it necessarily after these build steps\n          - `Xcode Archive` for iOS\n      Otherwis, you can launch this step in another Bitrise build, in that case, you don't need to setup this key but `outside_build_slug` to download your IPA to do quality checks\n    is_expand: true\n    is_required: true\n    title: IPA path\n"
  },
  {
    "path": "steps/apps-decompiler/1.0.2/step.yml",
    "content": "title: Mobile apps decompiler\nsummary: |\n  Decompile mobile APK and/or IPA to look inside\ndescription: |\n  Decompile mobile APK and/or IPA to look inside\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after the compilation step (\"Android Build\" for android, \"Xcode Archive\" for iOS)\n  - Launch \"Deploy to Bitrise.io\" step after this one to deploy report files to artifacts\nwebsite: https://github.com/odemolliens/bitrise-step-apps-decompiler\nsource_code_url: https://github.com/odemolliens/bitrise-step-apps-decompiler\nsupport_url: https://github.com/odemolliens/bitrise-step-apps-decompiler/issues\npublished_at: 2021-01-28T12:06:32.492436+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-apps-decompiler.git\n  commit: c2b1259d1171cab5fbaea8463c4aae734a78dba6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: apktool\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- decompile_android: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Do you want decompile Android APK?\n    title: Decompile Android APK\n    value_options:\n    - \"yes\"\n    - \"no\"\n- decompile_ios: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Do you want decompile iOS IPA?\n    title: Decompile iOS IPA\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      You can use the artifacts from another bitrise build of the same project.\n      If you launch this step on the build where you launched Android build step eg. you don't have to set this key\n    is_expand: true\n    is_required: false\n    summary: Build slug of the build where you have the APK/IPA into artifacts\n    title: External Build slug\n  outside_build_slug: null\n- android_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      You have to set this key if you launch this step directly in the build where you generate your APK, in that case, be careful to launch it necessarily after these build steps\n          - `Android Build` for android\n      Otherwis, you can launch this step in another Bitrise build, in that case, you don't need to setup this key but `outside_build_slug` to download your APK to do quality checks\n    is_expand: true\n    is_required: true\n    title: APK path\n- ios_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      You have to set this key if you launch this step directly in the build where you generate your IPA, in that case, be careful to launch it necessarily after these build steps\n          - `Xcode Archive` for iOS\n      Otherwis, you can launch this step in another Bitrise build, in that case, you don't need to setup this key but `outside_build_slug` to download your IPA to do quality checks\n    is_expand: true\n    is_required: true\n    title: IPA path\n"
  },
  {
    "path": "steps/apps-decompiler/1.0.3/step.yml",
    "content": "title: Mobile apps decompiler\nsummary: |\n  Decompile mobile APK and/or IPA to look inside\ndescription: |\n  Decompile mobile APK and/or IPA to look inside\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after the compilation step (\"Android Build\" for android, \"Xcode Archive\" for iOS)\n  - Launch \"Deploy to Bitrise.io\" step after this one to deploy report files to artifacts\nwebsite: https://github.com/odemolliens/bitrise-step-apps-decompiler\nsource_code_url: https://github.com/odemolliens/bitrise-step-apps-decompiler\nsupport_url: https://github.com/odemolliens/bitrise-step-apps-decompiler/issues\npublished_at: 2021-02-04T13:51:59.397006+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-apps-decompiler.git\n  commit: d6cf3d7977fd440a9f964310348c1732d864c087\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: apktool\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- decompile_android: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Do you want decompile Android APK?\n    title: Decompile Android APK\n    value_options:\n    - \"yes\"\n    - \"no\"\n- decompile_ios: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Do you want decompile iOS IPA?\n    title: Decompile iOS IPA\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      You can use the artifacts from another bitrise build of the same project.\n      If you launch this step on the build where you launched Android build step eg. you don't have to set this key\n    is_expand: true\n    is_required: false\n    summary: Build slug of the build where you have the APK/IPA into artifacts\n    title: External Build slug\n  outside_build_slug: null\n- android_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      You have to set this key if you launch this step directly in the build where you generate your APK, in that case, be careful to launch it necessarily after these build steps\n          - `Android Build` for android\n      Otherwis, you can launch this step in another Bitrise build, in that case, you don't need to setup this key but `outside_build_slug` to download your APK to do quality checks\n    is_expand: true\n    is_required: true\n    title: APK path\n- ios_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      You have to set this key if you launch this step directly in the build where you generate your IPA, in that case, be careful to launch it necessarily after these build steps\n          - `Xcode Archive` for iOS\n      Otherwis, you can launch this step in another Bitrise build, in that case, you don't need to setup this key but `outside_build_slug` to download your IPA to do quality checks\n    is_expand: true\n    is_required: true\n    title: IPA path\n"
  },
  {
    "path": "steps/apps-decompiler/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/apptestai-test/0.1.0/step.yml",
    "content": "title: apptest.ai Test\nsummary: |\n  Bitrise step for apptest.ai test execution\ndescription: |\n  Bitrise step for apptest.ai test execution.\n\n  Input your apptest.ai Access Key, Project ID, Package file path\n  refer to more information from https://app.apptest.ai/#/main/integrations\n\n  We recommend to use Access Key using bitrise workflow secret variable.\nwebsite: https://github.com/forcemax/bitrise-step-apptestai-test\nsource_code_url: https://github.com/forcemax/bitrise-step-apptestai-test\nsupport_url: https://github.com/forcemax/bitrise-step-apptestai-test/issues\npublished_at: 2020-04-02T15:15:51.7726+09:00\nsource:\n  git: https://github.com/forcemax/bitrise-step-apptestai-test.git\n  commit: 0c74c431abce60886a627ebc023e970b33bf5208\nhost_os_tags:\n- osx-10.14\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/forcemax/bitrise-step-apptestai-test\ndeps: {}\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key:\n  opts:\n    description: 'Access key to use for apptest.ai test. (e.g.: ci_support:4b55ec5999ea636b0aafb402816ac50b)'\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: 'Access key to use for apptest.ai test.'\n- project_id:\n  opts:\n    description: 'Project ID to use for apptest.ai test. (e.g. 19049)'\n    is_expand: true\n    is_required: true\n    title: 'Project ID to use for apptest.ai test.'\n- binary_path:\n  opts:\n    description: 'Package file path. You can use $BITRISE_APK_PATH or $BITRISE_IPA_PATH or app file path. supported file type: apk,ipa,xapk'\n    is_expand: true\n    is_required: true\n    title: 'Package file path.'\n- testset_name:\n  opts:\n    description: 'Specify test set name.'\n    is_expand: true\n    is_required: false\n    title: 'Specify test set name.'\n- time_limit:\n  opts:\n    description: 'Specify test time limit (minutes) (range: 5 - 30). If the value is empty, it follows the time-limit saved in the project.'\n    is_expand: true\n    is_required: false\n    title: 'Specify test time limit.'\n- use_vo:\n  opts:\n    description: 'Whether AT&T Video Optimizer(ARO) is used. (true|false)'\n    is_expand: true\n    is_required: false\n    title: 'Whether AT&T Video Optimizer(ARO) is used.'\n- callback:\n  opts:\n    description: 'Callback URL to be called after test completion.'\n    is_expand: true\n    is_required: false\n    title: 'Callback URL to be called after test completion.'\n- login_id:\n  opts:\n    description: 'ID of the test account required to test the app. If the value is empty, it follows the time-limit saved in the project.'\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: 'ID of the test account required to test the app.'\n- login_pw:\n  opts:\n    description: 'Password of the test account required to test the app. If the value is empty, it follows the time-limit saved in the project.'\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: 'Password of the test account required to test the app.'\n"
  },
  {
    "path": "steps/apptestai-test/step-info.yml",
    "content": "maintainer: community"
  },
  {
    "path": "steps/apt-get-install/0.10.0/step.yml",
    "content": "title: apt-get install\nsummary: |\n  Install or upgrade packages with apt-get\ndescription: |\n  Install or upgrade packages with apt-get\nwebsite: https://github.com/bitrise-steplib/steps-apt-get-install\nsource_code_url: https://github.com/bitrise-steplib/steps-apt-get-install\nsupport_url: https://github.com/bitrise-steplib/steps-apt-get-install/issues\npublished_at: 2019-11-04T14:47:50.397507394Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-apt-get-install.git\n  commit: 44c9fe8318037f71b5ce21c17b854dcda2ced80a\nhost_os_tags:\n- ubuntu\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-apt-get-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Name of the packages to install/upgrade, separated with spaces\n    is_expand: true\n    is_required: true\n    summary: Name of the packages to install/upgrade, separated with spaces\n    title: Name of the packages to install/upgrade, separated with spaces\n    value_options: []\n  packages: null\n- options: null\n  opts:\n    description: |\n      Flags to pass to the apt-get install/upgrade command.\n\n      `apt-get install/upgrade -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Options for apt-get install/upgrade\n    title: Options for apt-get install/upgrade\n    value_options: []\n- opts:\n    description: |\n      If set the step will upgrade the defined packages by calling `apt-get upgrade -y [options] [packages]` command.\n\n      Otherwise the step calls `apt-get install -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Upgrade packages if previously installed\n    title: Upgrade packages if previously installed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- cache_level: all\n  opts:\n    category: Options\n    description: |-\n      Sets the level of cache.\n\n      'all' enables the caching of all files under /var/cache/apt/archives folder (default directory for apt cache).\n      'none' disables the caching for the step.\n    is_required: true\n    summary: Sets the level of cache\n    title: Cache level\n    value_options:\n    - all\n    - none\n"
  },
  {
    "path": "steps/apt-get-install/0.10.1/step.yml",
    "content": "title: apt-get install\nsummary: Install or upgrade packages on Ubuntu with apt-get.\ndescription: |-\n  [This Step](https://www.bitrise.io/integrations/steps/apt-get-install) integrates with the Advanced Package Tool (APT) command line tool to install and upgrade packages.\n\n  ### Configuring the Step\n  1. Add the **Name of the packages to install/upgrade, separated with spaces**.\n  2. Add flags to pass on to the `apt-get` command in the **Options for apt-get install/upgrade** input.\n  3. Allow upgrades to previously installed packages with the **Upgrade packages if previously installed** input.\n  Under **Options**:\n  4. Set the level of cache in the **Cache level** input.\n\n  ### Useful links\n  - [Installing any additional tools](https://devcenter.bitrise.io/tips-and-tricks/install-additional-tools/#apt-get-on-linux)\n\n  ### Related Steps\n  - [Brew Install](https://www.bitrise.io/integrations/steps/brew-install)\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\nwebsite: https://github.com/bitrise-steplib/steps-apt-get-install\nsource_code_url: https://github.com/bitrise-steplib/steps-apt-get-install\nsupport_url: https://github.com/bitrise-steplib/steps-apt-get-install/issues\npublished_at: 2021-07-21T10:11:55.028203785Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-apt-get-install.git\n  commit: 6c27f0d7f0dd51cfc67eec8c22fd9526a9523820\nhost_os_tags:\n- ubuntu\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-apt-get-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Name of the packages to install/upgrade, separated with spaces\n    is_expand: true\n    is_required: true\n    summary: Name of the packages to install/upgrade, separated with spaces\n    title: Name of the packages to install/upgrade, separated with spaces\n    value_options: []\n  packages: null\n- options: null\n  opts:\n    description: |\n      Flags to pass to the `apt-get install/upgrade` command.\n\n      `apt-get install/upgrade -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Options for apt-get install/upgrade\n    title: Options for apt-get install/upgrade\n    value_options: []\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `apt-get upgrade -y [options] [packages]` command.\n\n      Otherwise the step calls `apt-get install -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Upgrade packages if previously installed\n    title: Upgrade packages if previously installed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- cache_level: all\n  opts:\n    category: Options\n    description: |-\n      Sets the level of cache.\n\n      'all' enables the caching of all files under /var/cache/apt/archives folder (default directory for apt cache).\n      'none' disables the caching for the step.\n    is_required: true\n    summary: Sets the level of cache\n    title: Cache level\n    value_options:\n    - all\n    - none\n"
  },
  {
    "path": "steps/apt-get-install/0.9.0/step.yml",
    "content": "title: apt-get install\nsummary: |\n  Install or upgrade packages with apt-get\ndescription: |\n  Install or upgrade packages with apt-get\nwebsite: https://github.com/bitrise-steplib/steps-apt-get-install\nsource_code_url: https://github.com/bitrise-steplib/steps-apt-get-install\nsupport_url: https://github.com/bitrise-steplib/steps-apt-get-install/issues\npublished_at: 2017-10-30T13:48:44.706918231+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-apt-get-install.git\n  commit: 0561642b4ec224e02697e55636bc52631cd45c45\nhost_os_tags:\n- ubuntu\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-apt-get-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Name of the packages to install/upgrade\n    is_expand: true\n    is_required: true\n    summary: Name of the packages to install/upgrade\n    title: Name of the packages to install/upgrade\n    value_options: []\n  packages: null\n- options: null\n  opts:\n    description: |\n      Flags to pass to the apt-get install/upgrade command.\n\n      `apt-get install/upgrade -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Options for apt-get install/upgrade\n    title: Options for apt-get install/upgrade\n    value_options: []\n- opts:\n    description: |\n      If set the step will upgrade the defined packages by calling `apt-get upgrade -y [options] [packages]` command.\n\n      Otherwise the step calls `apt-get install -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Upgrade packages if previously installed\n    title: Upgrade packages if previously installed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n"
  },
  {
    "path": "steps/apt-get-install/0.9.1/step.yml",
    "content": "title: apt-get install\nsummary: |\n  Install or upgrade packages with apt-get\ndescription: |\n  Install or upgrade packages with apt-get\nwebsite: https://github.com/bitrise-steplib/steps-apt-get-install\nsource_code_url: https://github.com/bitrise-steplib/steps-apt-get-install\nsupport_url: https://github.com/bitrise-steplib/steps-apt-get-install/issues\npublished_at: 2019-06-26T14:42:19.040757125Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-apt-get-install.git\n  commit: 19f57b2aed33a964f96130ddaa02feb100ab6792\nhost_os_tags:\n- ubuntu\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-apt-get-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Name of the packages to install/upgrade, separated with spaces\n    is_expand: true\n    is_required: true\n    summary: Name of the packages to install/upgrade, separated with spaces\n    title: Name of the packages to install/upgrade, separated with spaces\n    value_options: []\n  packages: null\n- options: null\n  opts:\n    description: |\n      Flags to pass to the apt-get install/upgrade command.\n\n      `apt-get install/upgrade -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Options for apt-get install/upgrade\n    title: Options for apt-get install/upgrade\n    value_options: []\n- opts:\n    description: |\n      If set the step will upgrade the defined packages by calling `apt-get upgrade -y [options] [packages]` command.\n\n      Otherwise the step calls `apt-get install -y [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Upgrade packages if previously installed\n    title: Upgrade packages if previously installed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n"
  },
  {
    "path": "steps/apt-get-install/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/artifact-pull/1.0.0/step.yml",
    "content": "title: Artifact pull\nsummary: Step to pull artifacts of a pipeline\ndescription: |-\n  The step downloads build artifacts of a pipeline to a local folder.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded. This can be limited\n  by setting the `artifact_sources` input variable.\n\n  Please note that this step is designed to be executed on the CI only.\nwebsite: https://github.com/bitrise-steplib/steps-artifact-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-artifact-pull\nsupport_url: https://github.com/bitrise-steplib/steps-artifact-pull/issues\npublished_at: 2022-07-07T10:25:37.52419-05:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-artifact-pull.git\n  commit: 9991a40d2454eca425f8462a018409eaaf657443\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-artifact-pull\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma separated list of workflows and stage\n      paths, which can generate artifacts.\n      You need to use the `{stage}.{workflow}` syntax.\n      The \"dot\" character is the delimiter between\n      the stage and the workflow.\n      You can use regular expressions.\n      If you leave it empty, the default value\n      will be the \".*\" (star), which means, it will\n      get every artifact from every workflow.\n      Do not forget to escape the special chatacters.\n    summary: |-\n      The list of the stage and workflow\n      paths, which can generate artifacts.\n    title: Artifact source\n- export_map: \"\"\n  opts:\n    description: |-\n      Variable export map, use the following regular expression syntax to collect the downloaded file's locations into separated environment variables (do not forget to escape the special chatacters):\n      DOWNLOADED_APKS: .*\\.apk\n      DOWNLOADED_TEST_RESULTS: .*\\.result\n      DOCS: .*\\.txt,.*\\.doc\n    is_expand: false\n    is_required: true\n    title: Output variable export map\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\noutputs:\n- BITRISE_ARTIFACT_PATHS: null\n  opts:\n    summary: An absolute path list of the downloaded artifacts. The list is separated\n      with pipe (|) characters.\n    title: Pulled artifacts locations\n"
  },
  {
    "path": "steps/artifact-pull/1.0.1/step.yml",
    "content": "title: Artifact pull\nsummary: Step to pull artifacts of a pipeline\ndescription: |-\n  The step downloads build artifacts of a pipeline to a local folder.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded. This can be limited\n  by setting the `artifact_sources` input variable.\n\n  Please note that this step is designed to be executed on the CI only.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-artifact-pull\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-artifact-pull\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-artifact-pull/issues\npublished_at: 2022-08-04T14:18:02.468733819Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-artifact-pull.git\n  commit: 6f5a62f5636d4f167c0fe48868a673a63ae394e3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-artifact-pull\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma separated list of workflows and stage paths, which can generate artifacts.\n      You need to use the `{stage}.{workflow}` syntax.\n      The \"dot\" character is the delimiter between the stage and the workflow.\n\n      You can use regular expressions.\n      The default value (`.*`) means: get every artifact from every workflow.\n\n      Do not forget to escape the special characters.\n      If you want to match all workflow from a stage then you need to escape the `.` separator and the use the `.*` any characters regex like `{stage-name}\\..*`.\n    summary: |-\n      The list of the stage and workflow\n      paths, which can generate artifacts.\n    title: Artifact source\n- export_map: \"\"\n  opts:\n    description: |-\n      Variable export map, use the following regular expression syntax to collect the downloaded file's locations into separated environment variables (do not forget to escape the special chatacters):\n      DOWNLOADED_APKS: .*\\.apk\n      DOWNLOADED_TEST_RESULTS: .*\\.result\n      DOCS: .*\\.txt,.*\\.doc\n    is_expand: false\n    is_required: true\n    title: Output variable export map\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\noutputs:\n- BITRISE_ARTIFACT_PATHS: null\n  opts:\n    summary: An absolute path list of the downloaded artifacts. The list is separated\n      with pipe (|) characters.\n    title: Pulled artifacts locations\n"
  },
  {
    "path": "steps/artifact-pull/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2023-04-13\"\ndeprecate_notes: |\n  This Step is deprecated, please use the [Pull Intermediate Files](https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files) Step instead.\n  More info and a migration guide can be found [here](https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/releases/tag/1.0.0).\n"
  },
  {
    "path": "steps/ascii-generator/1.0.3/step.yml",
    "content": "title: ASCII art generator\nsummary: |\n  Add a random Bitrise ASCII art to your build log\ndescription: |\n  Add a random Bitrise ASCII art to your build log\nwebsite: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator/issues\npublished_at: 2018-12-20T17:12:45.860373785+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator.git\n  commit: 9c5977234bf30bac168f684c522ca8c281cb563a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-ascii-art-generator\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- addon_url: $BITRISE_SAMPLE_ADDON_URL\n  opts:\n    is_expand: true\n    is_required: true\n    summary: URL of the ASCII generator addon\n    title: URL of the ASCII generator addon\n    value_options: []\n- access_token: $BITRISE_SAMPLE_ADDON_ACCESS_KEY\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Access token for ASCII generator addon, which gets generated at the provisioning\n    title: Access token for the ASCII generator addon\n    value_options: []\noutputs:\n- BITRISE_ASCII_ART: null\n  opts:\n    summary: The Bitrise ASCII art fetched from the generator add-on\n    title: Generated random Bitrise ASCII art\n"
  },
  {
    "path": "steps/ascii-generator/1.0.4/step.yml",
    "content": "title: ASCII art generator\nsummary: |\n  Add a random Bitrise ASCII art to your build log\ndescription: |\n  Add a random Bitrise ASCII art to your build log\nwebsite: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator/issues\npublished_at: 2019-05-08T17:57:21.319301+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-ascii-art-generator.git\n  commit: 380f3c5374ec77592a762663483c36f47184ab0c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-ascii-art-generator\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- addon_url: $BITRISE_SAMPLE_ADDON_URL\n  opts:\n    is_expand: true\n    is_required: true\n    summary: URL of the ASCII generator addon\n    title: URL of the ASCII generator addon\n    value_options: []\n- access_token: $BITRISE_SAMPLE_ADDON_ACCESS_TOKEN\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Access token for ASCII generator addon, which gets generated at the provisioning\n    title: Access token for the ASCII generator addon\n    value_options: []\noutputs:\n- BITRISE_ASCII_ART: null\n  opts:\n    summary: The Bitrise ASCII art fetched from the generator add-on\n    title: Generated random Bitrise ASCII art\n"
  },
  {
    "path": "steps/ascii-generator/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.0/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication config to the .netrc file\ndescription: |-\n  Adds your authentication config to the .netrc file.\n\n  If you already has a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2017-04-13T16:07:01.842544289+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: 8d2b815fa92df234f854fb09b8eeeb43357a2ca4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where username and password will be used.\n      For example: github.com\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    is_required: true\n    summary: The username used for the host to authenticate.\n    title: Username\n  username: null\n- opts:\n    description: The password used for the host to authenticate.\n    is_required: true\n    title: Password\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.2/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication config to the .netrc file\ndescription: |-\n  Adds your authentication config to the .netrc file.\n\n  If you already has a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2018-02-13T13:48:40.21354024+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: 300fa060cc6699d748ca0a33836da6dd4e7e2d77\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where username and password will be used.\n      For example: github.com\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    is_required: true\n    summary: The username used for the host to authenticate.\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token / Access Token) used for the host to\n      authenticate.\n    is_required: true\n    title: Password / Auth Token / Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.3/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication config to the .netrc file\ndescription: |-\n  Adds your authentication config to the .netrc file.\n\n  If you already has a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: !!timestamp 2018-05-04T17:03:16.138150869+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: b112b2419e5000d94e33849a9855761a4c5a96d8\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where username and password will be used.\n      For example: github.com\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    is_required: true\n    summary: The username used for the host to authenticate.\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token / Access Token) used for the host to\n      authenticate.\n    is_required: true\n    title: Password / Auth Token / Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.4/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication config to the .netrc file\ndescription: |-\n  Adds your authentication config to the .netrc file.\n\n  If you already have a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2018-08-31T11:13:14.811353457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: 9acdb22de1c4825db6c46c29f7cfd25b9ed33f85\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where the username and password will be used.\n      For example: github.com\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    is_required: true\n    is_sensitive: true\n    summary: The username used for the host to authenticate.\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token/Access Token) used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Password/Auth Token/Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.5/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc) adds the authentication configuration (host name, login name and password string) to the `.netrc` file .\n  The Step lets you store your remote credentials on the build VM once so that later steps can use the credentials for authentication instead of requiring manual input. Examples include HTTPS git clone URLs with OAuth token-based authentication (instead of authenticating with SSH key).\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add the **Host** name, where the username and password will be used, for example, github.com.\n  2.Add the **Username**.\n  3.Add the password or the authentication token/ access token in the respective field which will be used by the host to authenticate you.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/flutter-installer)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2021-07-21T14:07:25.70325756Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: cfd20d42a5df681730a790e0e66f91f8b2135694\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where the username and password will be used.\n      For example: github.com\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    is_required: true\n    is_sensitive: true\n    summary: The username used for the host to authenticate.\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token/Access Token) used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Password/Auth Token/Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.6/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc) adds the authentication configuration (host name, login name and password string) to the `.netrc` file .\n  The Step lets you store your remote credentials on the build VM once so that later steps can use the credentials for authentication instead of requiring manual input. Examples include HTTPS git clone URLs with OAuth token-based authentication (instead of authenticating with SSH key).\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add the **Host** name, where the username and password will be used, for example, github.com.\n  2.Add the **Username**.\n  3.Add the password or the authentication token/ access token in the respective field which will be used by the host to authenticate you.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/flutter-installer)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2021-10-28T10:11:24.162751267Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: bd3986570f629ed6895016e8964ac283f81a8902\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where the username and password will be used.\n      For example: github.com\n    is_required: true\n    title: Host\n- opts:\n    description: The username used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token/Access Token) used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Password/Auth Token/Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.7/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc) adds the authentication configuration (host name, login name and password string) to the `.netrc` file .\n  The Step lets you store your remote credentials on the build VM once so that later steps can use the credentials for authentication instead of requiring manual input. Examples include HTTPS git clone URLs with OAuth token-based authentication (instead of authenticating with SSH key).\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add the **Host** name, where the username and password will be used, for example, github.com.\n  2.Add the **Username**.\n  3.Add the password or the authentication token/ access token in the respective field which will be used by the host to authenticate you.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/flutter-installer)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2023-02-16T10:56:27.535947167Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: 8cb845d52e28737766ca0fdf9e7d512ac1d25812\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where the username and password will be used.\n      For example: github.com\n    is_required: true\n    title: Host\n- opts:\n    description: The username used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token/Access Token) used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Password/Auth Token/Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.8/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc) adds the authentication configuration (host name, login name and password string) to the `.netrc` file .\n  The Step lets you store your remote credentials on the build VM once so that later steps can use the credentials for authentication instead of requiring manual input. Examples include HTTPS git clone URLs with OAuth token-based authentication (instead of authenticating with SSH key).\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add the **Host** name, where the username and password will be used, for example, github.com.\n  2.Add the **Username**.\n  3.Add the password or the authentication token/ access token in the respective field which will be used by the host to authenticate you.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/flutter-installer)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2023-07-11T08:44:41.341029103Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: 91fcd09b2017f5eccce2e3a850dec9336015a31f\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where the username and password will be used.\n      For example: github.com\n    is_required: true\n    title: Host\n- opts:\n    description: The username used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token/Access Token) used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Password/Auth Token/Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/0.9.9/step.yml",
    "content": "title: Authenticate host with netrc\nsummary: Adds your authentication configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc) adds the authentication configuration (host name, login name and password string) to the `.netrc` file .\n  The Step lets you store your remote credentials on the build VM once so that later steps can use the credentials for authentication instead of requiring manual input. Examples include HTTPS git clone URLs with OAuth token-based authentication (instead of authenticating with SSH key).\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add the **Host** name, where the username and password will be used, for example, github.com.\n  2.Add the **Username**.\n  3.Add the password or the authentication token/ access token in the respective field which will be used by the host to authenticate you.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/flutter-installer)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc/issues\npublished_at: 2025-06-04T12:28:07.086084037Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-host-with-netrc.git\n  commit: a21bc03a3ab4829294cdef6127710cc5d22ced7d\ntype_tags:\n- access-control\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-host-with-netrc\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- host: null\n  opts:\n    description: |-\n      The host where the username and password will be used.\n      For example: github.com\n    is_required: true\n    title: Host\n- opts:\n    description: The username used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Username\n  username: null\n- opts:\n    description: The password (or Auth Token/Access Token) used for the host to authenticate.\n    is_required: true\n    is_sensitive: true\n    title: Password/Auth Token/Access Token\n  password: null\n"
  },
  {
    "path": "steps/authenticate-host-with-netrc/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/authenticate-with-aws/0.0.1/step.yml",
    "content": "title: Authenticate with Amazon Web Services (AWS)\nsummary: The step authenticates with AWS using an OIDC token.\ndescription: |-\n  This step authenticates with Amazon Web Services (AWS) using an OpenID Connect (OIDC) token.\n\n  It retrieves an identity token from Bitrise, assumes the specified AWS role using the token, and generates temporary AWS credentials.\n\n  The generated AWS credentials are then set as environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, and `AWS_SESSION_TOKEN`) for use in subsequent steps.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-aws\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-aws\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-aws/issues\npublished_at: 2025-10-31T11:35:55.043551+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-aws.git\n  commit: 03e9a6319d4488d9c51f17f80f440cfcadfd5578\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-authenticate-with-aws\ninputs:\n- audience: null\n  opts:\n    category: Identity token\n    description: |-\n      The audience for the identity token.\n\n      This could be the URL of the service you want to access with the token or a specific identifier provided by the service.\n    is_required: true\n    summary: The audience for the identity token.\n    title: Token audience\n- opts:\n    category: Identity token\n    description: |-\n      The ARN of the AWS role to assume.\n\n      You can find the ARN in the AWS Management Console under IAM roles.\n    is_required: true\n    summary: The ARN of the AWS role to assume.\n    title: AWS Role ARN\n  role_arn: null\n- opts:\n    category: Identity token\n    description: The AWS region to use.\n    is_required: true\n    summary: The AWS region to use.\n    title: AWS Region\n  region: us-east-1\n- opts:\n    category: Identity token\n    description: |-\n      The session name for the assumed role.\n\n      If not provided, a default name will be generated with the format `bitrise-<build-number>`.\n    is_required: false\n    summary: The session name for the assumed role.\n    title: AWS Session Name\n  session_name: bitrise-$BITRISE_BUILD_NUMBER\n- docker_login: \"false\"\n  opts:\n    category: Docker\n    description: |-\n      Performs Docker login with an auth token.\n\n      It is supported only on the Linux stacks.\n    is_required: true\n    summary: Performs Docker login with an auth token.\n    title: Docker login\n    value_options:\n    - \"true\"\n    - \"false\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: |-\n      Unique build URL of this build on Bitrise.io.\n\n      By default the step will use the Bitrise API.\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io.\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: |-\n      The build's API Token for the build on Bitrise.io\n\n      This will be used to communicate with the Bitrise API\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise build token\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- AWS_ACCESS_KEY_ID: null\n  opts:\n    summary: The newly generated AWS access key ID.\n    title: AWS Access Key ID\n- AWS_SECRET_ACCESS_KEY: null\n  opts:\n    summary: The newly generated AWS secret access key.\n    title: AWS Secret Access Key\n- AWS_SESSION_TOKEN: null\n  opts:\n    summary: The newly generated AWS session token.\n    title: AWS Session Token\n"
  },
  {
    "path": "steps/authenticate-with-aws/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/authenticate-with-bitbucket-oauth/0.10.0/step.yml",
    "content": "title: Authenticate with Bitbucket OAuth\nsummary: Adds your Bitbucket OAuth config to the .netrc file\ndescription: |-\n  Adds your Bitbucket OAuth config to the .netrc file.\n\n  If you already have a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth/issues\npublished_at: 2018-08-31T08:10:11.499913905Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth.git\n  commit: 40e5e3ee730385da8ed5ef72ac5bd8550becf4d6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for Bitbucket to login.\n    title: Bitbucket username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your Bitbucket App Password, follow the instructions below:\n\n      1. Log into your Bitbucket account\n      2. In the upper-right corner of any page, click your profile photo, then click **Bitbucket Settings**.\n      3. In the left sidebar, click **App passwords**.\n      4. Click **Create app password**.\n      5. Give your password a descriptive label.\n      6. Select the permissions you'd like to grant to this token.\n      7. Click **Create**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: App Password\n"
  },
  {
    "path": "steps/authenticate-with-bitbucket-oauth/0.10.1/step.yml",
    "content": "title: Authenticate with Bitbucket OAuth\nsummary: Adds your Bitbucket OAuth configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth) adds the authentication configuration (Bitbucket username and App password) to the `.netrc` file .\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add your **Bitbucket username**.\n  2. Add your Bitbucket **App Password**.\n  To get your Bitbucket App Password, follow the instructions below:\n  1. Log into your Bitbucket account.\n  2. In the left sidebar, click **App passwords**.\n  3. Click **Create app password**.\n  4. Give your password a descriptive label.\n  5. Select the permissions you'd like to grant to this token.\n  6. Click **Create**.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/open-vpn)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth/issues\npublished_at: 2021-07-21T09:57:16.194029839Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth.git\n  commit: 867c641baa7af3ac4d24b03a834c77dfcbc3106b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for Bitbucket to login.\n    title: Bitbucket username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your Bitbucket App Password, follow the instructions below:\n\n      1. Log into your Bitbucket account\n      2. In the upper-right corner of any page, click your profile photo, then click **Bitbucket Settings**.\n      3. In the left sidebar, click **App passwords**.\n      4. Click **Create app password**.\n      5. Give your password a descriptive label.\n      6. Select the permissions you'd like to grant to this token.\n      7. Click **Create**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: App Password\n"
  },
  {
    "path": "steps/authenticate-with-bitbucket-oauth/0.10.2/step.yml",
    "content": "title: Authenticate with Bitbucket OAuth\nsummary: Adds your Bitbucket OAuth configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth) adds the authentication configuration (Bitbucket username and App password) to the `.netrc` file .\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1.Add your **Bitbucket username**.\n  2. Add your Bitbucket **App Password**.\n  To get your Bitbucket App Password, follow the instructions below:\n  1. Log into your Bitbucket account.\n  2. In the left sidebar, click **App passwords**.\n  3. Click **Create app password**.\n  4. Give your password a descriptive label.\n  5. Select the permissions you'd like to grant to this token.\n  6. Click **Create**.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/open-vpn)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth/issues\npublished_at: 2022-11-01T10:07:52.260023979Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth.git\n  commit: d189ec8e3344e64a3a47abb98348db517cc48d22\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for Bitbucket to login.\n    title: Bitbucket username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your Bitbucket App Password, follow the instructions below:\n\n      1. Log into your Bitbucket account\n      2. In the upper-right corner of any page, click your profile photo, then click **Bitbucket Settings**.\n      3. In the left sidebar, click **App passwords**.\n      4. Click **Create app password**.\n      5. Give your password a descriptive label.\n      6. Select the permissions you'd like to grant to this token.\n      7. Click **Create**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: App Password\n"
  },
  {
    "path": "steps/authenticate-with-bitbucket-oauth/0.10.3/step.yml",
    "content": "title: Authenticate with Bitbucket OAuth\nsummary: Adds your Bitbucket OAuth configuration to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth) adds the authentication configuration (Bitbucket username and App password) to the `.netrc` file .\n  Please note that if you already have a `.netrc` file, the Step will create a backup of the original, and appends the configs to the current one.\n\n  ### Configuring the Step\n  1. Add your **Bitbucket username**.\n  2. Add your Bitbucket **App Password**.\n\n  To get your Bitbucket App Password, follow the instructions below:\n  1. Log into your Bitbucket account.\n  2. In the left sidebar, click **App passwords**.\n  3. Click **Create app password**.\n  4. Give your password a descriptive label.\n  5. Select the permissions you'd like to grant to this token.\n  6. Click **Create**.\n\n  ### Useful links\n  - [Learn more what the .netrc file format comprises of](https://everything.curl.dev/usingcurl/netrc#the-netrc-file-format)\n\n  ### Related Steps\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Connect to OpenVPN Server](https://www.bitrise.io/integrations/steps/open-vpn)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth/issues\npublished_at: 2026-01-29T16:09:24.765354694Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth.git\n  commit: 33f32d030e43dc776d3768ab56825a1d2f105519\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for Bitbucket to login.\n    title: Bitbucket username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your Bitbucket App Password, follow the instructions below:\n\n      1. Log into your Bitbucket account\n      2. In the upper-right corner of any page, click your profile photo, then click **Bitbucket Settings**.\n      3. In the left sidebar, click **App passwords**.\n      4. Click **Create app password**.\n      5. Give your password a descriptive label.\n      6. Select the permissions you'd like to grant to this token.\n      7. Click **Create**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: App Password\n"
  },
  {
    "path": "steps/authenticate-with-bitbucket-oauth/0.9.0/step.yml",
    "content": "title: Authenticate with Bitbucket OAuth\nsummary: Adds your Bitbucket OAuth config to the .netrc file\ndescription: |-\n  Adds your Bitbucket OAuth config to the .netrc file.\n\n  If you already has a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth/issues\npublished_at: 2017-04-26T13:46:22.656723978+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth.git\n  commit: 55d79d4233845840c49d0673141b5d83fe5218dd\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-bitbucket-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: The username used for Bitbucket to login.\n    title: Bitbucket username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your Bitbucket App Password, follow the instructions below:\n      1) Login to yout Bitbucket account\n      2) In the upper-right corner of any page, click your profile photo, then click **Bitbucket Settings**.\n      3) In the left sidebar, click **App passwords**.\n      4) Click **Create app password**.\n      5) Give your password a descriptive label.\n      6) Select the permissions you'd like to grant this token.\n      7) Click **Create**.\n    is_required: true\n    title: App Password\n"
  },
  {
    "path": "steps/authenticate-with-bitbucket-oauth/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/authenticate-with-gcp/0.0.1/step.yml",
    "content": "title: Authenticate with Google Cloud Platform (GCP)\nsummary: The step authenticates with GCP using a service account key.\ndescription: |-\n  This step authenticates with Google Cloud Platform (GCP) using a service account key.\n\n  It generates a Google auth token and sets the `GOOGLE_APPLICATION_CREDENTIALS` environment variable.\n\n  The step can also log in to Docker to the supplied Artifact Registry locations.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp/issues\npublished_at: 2025-07-24T11:09:18.001509+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp.git\n  commit: f24aff6380913575e2fda8a36b611b5057ff88c2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp\ninputs:\n- opts:\n    description: |-\n      The service account key in JSON format.\n\n      You can generate a service account key in the Google Cloud Console. Make sure to grant the necessary permissions to the service account.\n\n      The step will use this key to authenticate with GCP and generate a Google auth token.\n    is_required: true\n    is_sensitive: true\n    summary: The service account key in JSON format.\n    title: Service account key\n  service_account_key: null\n- docker_login: \"false\"\n  opts:\n    category: Docker\n    description: |-\n      Performs Docker login with an auth token.\n\n      The step will log in to the Artifact Registry locations specified in the `artifact_registry_locations` input.\n\n      It is supported only on the Linux stacks.\n    is_required: true\n    summary: Performs Docker login with an auth token.\n    title: Docker login\n    value_options:\n    - \"true\"\n    - \"false\"\n- artifact_registry_locations: null\n  opts:\n    category: Docker\n    description: |-\n      A newline (`\\n`) separated list of Artifact Registry locations to log in to.\n\n      The step will log in to the specified locations using the Google auth token generated from the service account key.\n\n      These locations can point ot either the deprecated Container Registry or the new Artifact Registry.\n    summary: A newline (`\\n`) separated list of Artifact Registry locations to log\n      in to.\n    title: Artifact Registry locations\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- GOOGLE_AUTH_TOKEN: null\n  opts:\n    summary: |-\n      The generated Google auth token.\n\n      This token can be used to authenticate with GCP services.\n    title: Google auth token\n- GOOGLE_APPLICATION_CREDENTIALS: null\n  opts:\n    summary: |-\n      The path to the service account key file.\n\n      This file is used by GCP SDKs and libraries to authenticate with GCP services.\n    title: Google credentials path\n"
  },
  {
    "path": "steps/authenticate-with-gcp/0.0.4/step.yml",
    "content": "title: Authenticate with Google Cloud Platform (GCP)\nsummary: The step authenticates with GCP using a service account key.\ndescription: |-\n  This step authenticates with Google Cloud Platform (GCP) using a service account key.\n\n  It generates a Google auth token and sets the `GOOGLE_APPLICATION_CREDENTIALS` environment variable.\n\n  The step can also log in to Docker to the supplied Artifact Registry locations.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp/issues\npublished_at: 2025-11-19T13:07:07.260955266Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp.git\n  commit: b147cc0fc20ae38739dad8d90803e56490146f74\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-authenticate-with-gcp\ninputs:\n- opts:\n    category: Service account\n    description: |-\n      The service account key in JSON format.\n\n      You can generate a service account key in the Google Cloud Console. Make sure to grant the necessary permissions to the service account.\n\n      The step will use this key to authenticate with GCP and generate a Google auth token.\n    is_sensitive: true\n    summary: The service account key in JSON format.\n    title: Service account key\n  service_account_key: null\n- client_config: null\n  opts:\n    category: Identity token\n    description: |-\n      Client config in JSON format.\n\n      You can generate a client config in the Google Cloud Console. Make sure to grant the necessary permissions to the client.\n    is_sensitive: true\n    summary: Client config in JSON format.\n    title: Client config\n- audience: null\n  opts:\n    category: Identity token\n    description: |-\n      The audience for the identity token.\n\n      This could be the URL of the service you want to access with the token or a specific identifier provided by the service.\n    summary: The audience for the identity token.\n    title: Token audience\n- docker_login: \"false\"\n  opts:\n    category: Docker\n    description: |-\n      Performs Docker login with an auth token.\n\n      The step will log in to the Artifact Registry locations specified in the `artifact_registry_locations` input.\n\n      It is supported only on the Linux stacks.\n    is_required: true\n    summary: Performs Docker login with an auth token.\n    title: Docker login\n    value_options:\n    - \"true\"\n    - \"false\"\n- artifact_registry_locations: null\n  opts:\n    category: Docker\n    description: |-\n      A newline (`\\n`) separated list of Artifact Registry locations to log in to.\n\n      The step will log in to the specified locations using the Google auth token generated from the service account key.\n\n      These locations can point ot either the deprecated Container Registry or the new Artifact Registry.\n    summary: A newline (`\\n`) separated list of Artifact Registry locations to log\n      in to.\n    title: Artifact Registry locations\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: |-\n      Unique build URL of this build on Bitrise.io.\n\n      By default the step will use the Bitrise API.\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io.\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: |-\n      The build's API Token for the build on Bitrise.io\n\n      This will be used to communicate with the Bitrise API\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise build token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- GOOGLE_AUTH_TOKEN: null\n  opts:\n    summary: |-\n      The generated Google auth token.\n\n      This token can be used to authenticate with GCP services.\n    title: Google auth token\n- GOOGLE_APPLICATION_CREDENTIALS: null\n  opts:\n    summary: |-\n      The path to the service account key file.\n\n      This file is used by GCP SDKs and libraries to authenticate with GCP services.\n    title: Google credentials path\n"
  },
  {
    "path": "steps/authenticate-with-gcp/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/authenticate-with-github-oauth/0.9.0/step.yml",
    "content": "title: Authenticate with GitHub OAuth\nsummary: Adds your GitHub OAuth config to the .netrc file\ndescription: |-\n  Adds your GitHub OAuth config to the .netrc file.\n\n  If you already has a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth/issues\npublished_at: 2017-04-20T12:54:31.297075924+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth.git\n  commit: 954d2660a4c75a452a3b99e1f8a28b87893ac145\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-github-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: The username used for GitHub to login.\n    title: GitHub username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your GitHub Personal Access Token, follow the instructions below:\n      1) Login to yout GitHub account\n      2) In the upper-right corner of any page, click your profile photo, then click **Settings**.\n      3) In the left sidebar, click **Personal access tokens**.\n      4) Click **Generate new token**.\n      5) Give your token a descriptive name.\n      6) Select the scopes, or permissions, you'd like to grant this token.\n      7) Click Generate token.\n    is_required: true\n    title: Personal Access Token\n"
  },
  {
    "path": "steps/authenticate-with-github-oauth/0.9.1/step.yml",
    "content": "title: Authenticate with GitHub OAuth\nsummary: Adds your GitHub OAuth config to the .netrc file\ndescription: |-\n  Adds your GitHub OAuth config to the .netrc file.\n\n  If you already has a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth/issues\npublished_at: !!timestamp 2018-03-21T14:06:08.805031579+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth.git\n  commit: 3601e31f2f536f2d3b2c61f5e3f57f691f84645d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-github-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: The username used for GitHub to login.\n    title: GitHub username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your GitHub Personal Access Token, follow the instructions below:\n      1) Login to yout GitHub account\n      2) In the upper-right corner of any page, click your profile photo, then click **Settings**.\n      3) In the left sidebar, click **Personal access tokens**.\n      4) Click **Generate new token**.\n      5) Give your token a descriptive name.\n      6) Select the scopes, or permissions, you'd like to grant this token.\n      7) Click Generate token.\n    is_required: true\n    title: Personal Access Token\n"
  },
  {
    "path": "steps/authenticate-with-github-oauth/0.9.2/step.yml",
    "content": "title: Authenticate with GitHub OAuth\nsummary: This step adds your GitHub OAuth config to the .netrc file.\ndescription: |-\n  Adds your GitHub OAuth config to the .netrc file.\n\n  If you already have a .netrc file, the step will create a backup of the original, and appends the configs to the current one.\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth/issues\npublished_at: 2018-08-31T08:47:57.893584428Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth.git\n  commit: 5c3baff136d95c4017959255c1dd8c774841f3e7\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-github-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for GitHub to login.\n    title: GitHub username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your GitHub Personal Access Token, follow the instructions below:\n      1. Login to yout GitHub account.\n      2. In the upper-right corner of any page, click your profile photo, then click **Settings**.\n      3. In the left sidebar, click **Personal access tokens**.\n      4. Click **Generate new token**.\n      5. Give your token a descriptive name.\n      6. Select the scopes or permissions, you'd like to grant this token.\n      7. Click **Generate token**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token\n"
  },
  {
    "path": "steps/authenticate-with-github-oauth/0.9.3/step.yml",
    "content": "title: Authenticate with GitHub OAuth\nsummary: Adds your GitHub OAuth config to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth) writes GitHub OAuth configs to the `.netrc` file, so every single network call pointing to [github.com](https://github.com/) or [api.github.com](https://api.github.com/) hosts will be accessed with the given Personal Access Token and the GitHub username.\n  Please note that this Step must come before any other git Step in your Workflow, therefore, it can be, for example, the first Step in your Workflow.\n\n  ### Configuring the Step\n\n  1. Add your **GitHub username** in the respective input field.\n  2. Add your GitHub **Personal Access Token** in the respective input field.\n  To get your GitHub Personal Access Token, follow these steps:\n  1. Login to your GitHub account.\n  2. In the upper-right corner of any page, click your profile photo, then click **Settings**.\n  3. In the left sidebar, click **Personal access tokens**.\n  4. Click **Generate new token**.\n  5. Give your token a descriptive name.\n  6. Select the scopes, or permissions you’d like to grant this token with.\n  7. Click **Generate token**.\n\n  ### Useful links\n  - [Connecting your GitHub/GitLab/Bitbucket account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-account-bitrise/)\n\n  ### Related Steps\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth/issues\npublished_at: 2021-07-19T14:56:24.775170507Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth.git\n  commit: 525a1e8c52506289af02e80b37e13b020959b0fb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-github-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for GitHub to login.\n    title: GitHub username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your GitHub Personal Access Token, follow the instructions below:\n      1. Login to yout GitHub account.\n      2. In the upper-right corner of any page, click your profile photo, then click **Settings**.\n      3. In the left sidebar, click **Personal access tokens**.\n      4. Click **Generate new token**.\n      5. Give your token a descriptive name.\n      6. Select the scopes or permissions, you'd like to grant this token.\n      7. Click **Generate token**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token\n"
  },
  {
    "path": "steps/authenticate-with-github-oauth/0.9.4/step.yml",
    "content": "title: Authenticate with GitHub OAuth\nsummary: Adds your GitHub OAuth config to the `.netrc` file.\ndescription: |-\n  [This Step](https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth) writes GitHub OAuth configs to the `.netrc` file, so every single network call pointing to [github.com](https://github.com/) or [api.github.com](https://api.github.com/) hosts will be accessed with the given Personal Access Token and the GitHub username.\n  Please note that this Step must come before any other git Step in your Workflow, therefore, it can be, for example, the first Step in your Workflow.\n\n  ### Configuring the Step\n\n  1. Add your **GitHub username** in the respective input field.\n  2. Add your GitHub **Personal Access Token** in the respective input field.\n  To get your GitHub Personal Access Token, follow these steps:\n  1. Login to your GitHub account.\n  2. In the upper-right corner of any page, click your profile photo, then click **Settings**.\n  3. In the left sidebar, click **Personal access tokens**.\n  4. Click **Generate new token**.\n  5. Give your token a descriptive name.\n  6. Select the scopes, or permissions you’d like to grant this token with.\n  7. Click **Generate token**.\n\n  ### Useful links\n  - [Connecting your GitHub/GitLab/Bitbucket account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-account-bitrise/)\n\n  ### Related Steps\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\nwebsite: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsource_code_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth\nsupport_url: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth/issues\npublished_at: 2022-08-09T14:27:50.619871578Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-authenticate-with-github-oauth.git\n  commit: 90f4d5a8570602a53e5dfe4f3d4c7e4540c63cbb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-authenticate-with-github-oauth\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username used for GitHub to login.\n    title: GitHub username\n  username: null\n- access_token: null\n  opts:\n    description: |-\n      To get your GitHub Personal Access Token, follow the instructions below:\n      1. Login to yout GitHub account.\n      2. In the upper-right corner of any page, click your profile photo, then click **Settings**.\n      3. In the left sidebar, click **Personal access tokens**.\n      4. Click **Generate new token**.\n      5. Give your token a descriptive name.\n      6. Select the scopes or permissions, you'd like to grant this token.\n      7. Click **Generate token**.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token\n"
  },
  {
    "path": "steps/authenticate-with-github-oauth/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/autify-test-run/1.0.0/step.yml",
    "content": "title: Autify test run\nsummary: |\n  Run a test plan on Autify for Mobile.\ndescription: |\n  [Autify for Mobile](https://autify.com/mobile) is a test automation platform for your native app.\n  This step allows you to upload your app built in the previous steps to Autify and start a pre-recorded test plan against the build.\n\n  Optionally, this step can wait until the test plan finishes and fail if it doesn't pass.\n\n  Also, you can specify already uploaded build and just start a test plan against it.\n\n  If you want to upload your app to Autify, you need to build your app first by `Android Build`, `Xcode build for simulator`, etc.\n  and refer the target build path (*.apk or *.app) at `Build path to test` input.\nwebsite: https://github.com/autifyhq/bitrise-step-autify-test-run\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-test-run\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-test-run/issues\npublished_at: 2022-09-06T08:38:52.032898-07:00\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-test-run.git\n  commit: 81b2de30d3a68cbe5e7a39adf5e00af10fc014a4\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- access_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Personal Access Token of Autify for Mobile\n    title: Access token of Autify for Mobile\n- autify_test_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Autify for Mobile URL of your test plan. For example, `https://mobile-app.autify.com/projects/AAA/test_plans/BBB`\n    title: URL of a test plan\n- build_id: null\n  opts:\n    is_expand: true\n    summary: Autify for Mobile build ID you already uploaded before.\n    title: Build ID to test (Either \"Build ID to test\" or \"Build path to test\" is\n      required.)\n- build_path: null\n  opts:\n    is_expand: true\n    summary: |-\n      The file location of your build file i.e. /path/to/ios.app or /path/to/android.apk.\n      Typically, it's `$BITRISE_APP_DIR_PATH` for `Xcode build for simulator` step or `$BITRISE_APK_PATH` for `Android build` step.\n    title: Build path to test (Either \"Build ID to test\" or \"Build path to test\" is\n      required.)\n- opts:\n    title: Wait for the finish of test\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait: \"false\"\n- opts:\n    title: Timeout seconds while waiting the finish of test\n  timeout: 300\n- autify_path: autify\n  opts:\n    is_expand: true\n    title: A path to Autify CLI\noutputs:\n- AUTIFY_TEST_RESULT_URL: null\n  opts:\n    title: URL to see the test result at Autify for Mobile\n- AUTIFY_BUILD_ID: null\n  opts:\n    title: Used build id on Autify for Mobile\n- AUTIFY_TEST_RUN_EXIT_CODE: null\n  opts:\n    title: Exit code of the step\n"
  },
  {
    "path": "steps/autify-test-run/1.0.1/step.yml",
    "content": "title: Autify Test Run\nsummary: |\n  Run a test plan on Autify for Mobile.\ndescription: |\n  [Autify for Mobile](https://autify.com/mobile) is a test automation platform for your native app.\n  This step allows you to upload your app built in the previous steps to Autify and start a pre-recorded test plan against the build.\n\n  Optionally, this step can wait until the test plan finishes and fail if it doesn't pass.\n\n  Also, you can specify already uploaded build and just start a test plan against it.\n\n  If you want to upload your app to Autify, you need to build your app first by `Android Build`, `Xcode build for simulator`, etc.\n  and refer the target build path (*.apk or *.app) at `Build path to test` input.\nwebsite: https://github.com/autifyhq/bitrise-step-autify-test-run\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-test-run\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-test-run/issues\npublished_at: 2022-09-08T09:45:07.487401-07:00\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-test-run.git\n  commit: d6101b79f8410d6d055d98fc88e91afec0628cb5\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- access_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Personal Access Token of Autify for Mobile\n    title: Access token of Autify for Mobile\n- autify_test_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Autify for Mobile URL of your test plan. For example, `https://mobile-app.autify.com/projects/AAA/test_plans/BBB`\n    title: URL of a test plan\n- build_id: null\n  opts:\n    is_expand: true\n    summary: Autify for Mobile build ID you already uploaded before.\n    title: Build ID to test (Either \"Build ID to test\" or \"Build path to test\" is\n      required.)\n- build_path: null\n  opts:\n    is_expand: true\n    summary: |-\n      The file location of your build file i.e. /path/to/ios.app or /path/to/android.apk.\n      Typically, it's `$BITRISE_APP_DIR_PATH` for `Xcode build for simulator` step or `$BITRISE_APK_PATH` for `Android build` step.\n    title: Build path to test (Either \"Build ID to test\" or \"Build path to test\" is\n      required.)\n- opts:\n    title: Wait for the finish of test\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait: \"false\"\n- opts:\n    title: Timeout seconds while waiting the finish of test\n  timeout: 300\n- autify_path: autify\n  opts:\n    is_expand: true\n    title: A path to Autify CLI\noutputs:\n- AUTIFY_TEST_RESULT_URL: null\n  opts:\n    title: URL to see the test result at Autify for Mobile\n- AUTIFY_BUILD_ID: null\n  opts:\n    title: Used build id on Autify for Mobile\n- AUTIFY_TEST_RUN_EXIT_CODE: null\n  opts:\n    title: Exit code of the step\n"
  },
  {
    "path": "steps/autify-test-run/1.1.0/step.yml",
    "content": "title: Autify Test Run\nsummary: |\n  Run a test plan on Autify for Mobile.\ndescription: |\n  [Autify for Mobile](https://autify.com/mobile) is a test automation platform for your native app.\n  This step allows you to upload your app built in the previous steps to Autify and start a pre-recorded test plan against the build.\n\n  Optionally, this step can wait until the test plan finishes and fail if it doesn't pass.\n\n  Also, you can specify already uploaded build and just start a test plan against it.\n\n  If you want to upload your app to Autify, you need to build your app first by `Android Build`, `Xcode build for simulator`, etc.\n  and refer the target build path (*.apk or *.app) at `Build path to test` input.\nwebsite: https://github.com/autifyhq/bitrise-step-autify-test-run\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-test-run\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-test-run/issues\npublished_at: 2022-09-29T20:46:37.817606921Z\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-test-run.git\n  commit: 7b8b6ce6c5735748cc0df491c0e98d5a5da73c26\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- access_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Personal Access Token of Autify for Mobile\n    title: Access token of Autify for Mobile\n- autify_test_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Autify for Mobile URL of your test plan. For example, `https://mobile-app.autify.com/projects/AAA/test_plans/BBB`\n    title: URL of a test plan\n- build_id: null\n  opts:\n    is_expand: true\n    summary: Autify for Mobile build ID you already uploaded before.\n    title: Build ID to test (Either \"Build ID to test\" or \"Build path to test\" is\n      required.)\n- build_path: null\n  opts:\n    is_expand: true\n    summary: |-\n      The file location of your build file i.e. /path/to/ios.app or /path/to/android.apk.\n      Typically, it's `$BITRISE_APP_DIR_PATH` for `Xcode build for simulator` step or `$BITRISE_APK_PATH` for `Android build` step.\n    title: Build path to test (Either \"Build ID to test\" or \"Build path to test\" is\n      required.)\n- opts:\n    title: Wait for the finish of test\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait: \"false\"\n- opts:\n    title: Timeout seconds while waiting the finish of test\n  timeout: 300\n- autify_path: autify\n  opts:\n    is_expand: true\n    title: A path to Autify CLI\n- autify_cli_installer_url: https://autify-cli-assets.s3.amazonaws.com/autify-cli/channels/stable/install-cicd.bash\n  opts:\n    is_expand: true\n    title: Autify CLI installer URL\noutputs:\n- AUTIFY_TEST_RESULT_URL: null\n  opts:\n    title: URL to see the test result at Autify for Mobile\n- AUTIFY_BUILD_ID: null\n  opts:\n    title: Used build id on Autify for Mobile\n- AUTIFY_TEST_RUN_EXIT_CODE: null\n  opts:\n    title: Exit code of the step\n"
  },
  {
    "path": "steps/autify-test-run/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/autify-upload/0.0.1/step.yml",
    "content": "title: |\n  Autify Upload\nsummary: |\n  Uploads your build to Autify.\ndescription: |-\n  Uploads you build `.app` to [Autify](https://autify.com/mobile) using Autify's API. You can upload the iOS build with the Step.\n\n  This Step, however, does NOT generate your build: to create a `.app` file, you need the right step. For example, `Xcode build for simulator` Step or any other Step can generate a build. Add task URL\nwebsite: https://github.com/autifyhq/bitrise-step-autify-upload\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-upload\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-upload/issues\npublished_at: 2021-06-09T05:12:39.441439+09:00\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-upload.git\n  commit: 15809911647ee0fad8527ee92810755b76faec14\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_dir_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: |-\n      A `.app` path.\n\n      This path is generated in the previous step. For example:\n\n      - The `Xcode build for simulator` Step generate a app directory as `$BITRISE_APP_DIR_PATH`\n    is_required: true\n    summary: null\n    title: App directory path\n- opts:\n    description: |-\n      The Project ID can be found in the Auitify URL. For example:\n\n      - `autify.com/projects/<Project ID>`\n    is_required: true\n    summary: null\n    title: Autify project id\n  project_id: null\n- opts:\n    description: You can generate a Personal Access Token from Autify's Settings page.\n      Note that this value is associated with a specific user, as the name implies.\n    is_required: true\n    is_sensitive: true\n    summary: null\n    title: Autify Personal Access Token\n  upload_token: null\noutputs:\n- AUTIFY_UPLOAD_STEP_RESULT_JSON: null\n  opts:\n    description: This is the response to the API used to upload the build\n    summary: Response when uploading the build\n    title: Autify Upload Step Result JSON\n"
  },
  {
    "path": "steps/autify-upload/0.0.2/step.yml",
    "content": "title: |\n  Autify Upload\nsummary: |\n  Uploads your build to Autify.\ndescription: |-\n  Uploads you build `.app` to [Autify](https://autify.com/mobile) using [Autify's API](https://mobile-app.autify.com/api/docs/index.html). You can upload the iOS build with the Step.\n\n  This Step, however, does NOT generate your build: to create a `.app` file, you need the right step. For example, `Xcode build for simulator` Step or any other Step can generate a build\nwebsite: https://github.com/autifyhq/bitrise-step-autify-upload\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-upload\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-upload/issues\npublished_at: 2021-12-14T05:27:01.003204+09:00\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-upload.git\n  commit: 6ac944710c030a2a0ee09c92fc94310f9ce2a62e\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_dir_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: |-\n      A `.app` path.\n\n      This path is generated in the previous step. For example:\n\n      - The `Xcode build for simulator` Step generate a app directory as `$BITRISE_APP_DIR_PATH`\n    is_required: true\n    summary: null\n    title: App directory path\n- opts:\n    description: |-\n      The Project ID can be found in the Auitify URL. For example:\n\n      - `autify.com/projects/<Project ID>`\n    is_required: true\n    summary: null\n    title: Autify project id\n  project_id: null\n- opts:\n    description: You can generate a Personal Access Token from Autify's Settings page.\n      Note that this value is associated with a specific user, as the name implies.\n    is_required: true\n    is_sensitive: true\n    summary: null\n    title: Autify Personal Access Token\n  upload_token: null\noutputs:\n- AUTIFY_UPLOAD_STEP_RESULT_JSON: null\n  opts:\n    description: This is the response to the API used to upload the build\n    summary: Response when uploading the build\n    title: Autify Upload Step Result JSON\n"
  },
  {
    "path": "steps/autify-upload/0.0.3/step.yml",
    "content": "title: |\n  Autify Upload\nsummary: |\n  Uploads your build to Autify.\ndescription: |-\n  Uploads you build `.app` to [Autify](https://autify.com/mobile) using [Autify's API](https://mobile-app.autify.com/api/docs/index.html). You can upload the iOS build with the Step.\n\n  This Step, however, does NOT generate your build: to create a `.app` file, you need the right step. For example, `Xcode build for simulator` Step or any other Step can generate a build\nwebsite: https://github.com/autifyhq/bitrise-step-autify-upload\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-upload\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-upload/issues\npublished_at: 2022-08-10T09:28:51.758942+09:00\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-upload.git\n  commit: f5c883060a80a678520020d2f6797e8ec35010cc\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_dir_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: |-\n      A `.app` path.\n\n      This path is generated in the previous step. For example:\n\n      - The `Xcode build for simulator` Step generate a app directory as `$BITRISE_APP_DIR_PATH`\n    is_required: true\n    summary: null\n    title: App directory path\n- opts:\n    description: |-\n      The Project ID can be found in the Auitify URL. For example:\n\n      - `autify.com/projects/{Project ID}`\n    is_required: true\n    summary: null\n    title: Autify project id\n  project_id: null\n- opts:\n    description: You can generate a Personal Access Token from Autify's Settings page.\n      Note that this value is associated with a specific user, as the name implies.\n    is_required: true\n    is_sensitive: true\n    summary: null\n    title: Autify Personal Access Token\n  upload_token: null\noutputs:\n- AUTIFY_UPLOAD_STEP_RESULT_JSON: null\n  opts:\n    description: This is the response to the API used to upload the build\n    summary: Response when uploading the build\n    title: Autify Upload Step Result JSON\n"
  },
  {
    "path": "steps/autify-upload/1.0.0/step.yml",
    "content": "title: Autify Upload\nsummary: |\n  Upload a build file to Autify for Mobile.\ndescription: |\n  [Autify for Mobile](https://autify.com/mobile) is a test automation platform for your native app.\n  This step allows you to upload your app built in the previous steps to Autify.\n\n  You need to build your app first by `Android Build`, `Xcode build for simulator`, etc.\n  and refer the target build path (*.apk or *.app) at `Build path to test` input.\nwebsite: https://github.com/autifyhq/bitrise-step-autify-upload\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-upload\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-upload/issues\npublished_at: 2022-09-06T08:41:08.550307-07:00\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-upload.git\n  commit: ab3293c0f2575e19f731032ea191747a90f34a29\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- access_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Personal Access Token of Autify for Mobile\n    title: Access token of Autify for Mobile\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Your workspace ID of Autify for Mobile to upload the build\n    title: Workspace ID to upload\n  workspace_id: null\n- build_path: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |-\n      The file location of your build file i.e. /path/to/ios.app or /path/to/android.apk.\n      Typically, it's `$BITRISE_APP_DIR_PATH` for `Xcode build for simulator` step or `$BITRISE_APK_PATH` for `Android build` step.\n    title: Build path to upload\n- autify_path: autify\n  opts:\n    is_expand: true\n    title: A path to Autify CLI\noutputs:\n- AUTIFY_BUILD_ID: null\n  opts:\n    title: Uploaded build id on Autify for Mobile\n- AUTIFY_UPLOAD_EXIT_CODE: null\n  opts:\n    title: Exit code of the step\n"
  },
  {
    "path": "steps/autify-upload/1.1.0/step.yml",
    "content": "title: Autify Upload\nsummary: |\n  Upload a build file to Autify for Mobile.\ndescription: |\n  [Autify for Mobile](https://autify.com/mobile) is a test automation platform for your native app.\n  This step allows you to upload your app built in the previous steps to Autify.\n\n  You need to build your app first by `Android Build`, `Xcode build for simulator`, etc.\n  and refer the target build path (*.apk or *.app) at `Build path to test` input.\nwebsite: https://github.com/autifyhq/bitrise-step-autify-upload\nsource_code_url: https://github.com/autifyhq/bitrise-step-autify-upload\nsupport_url: https://github.com/autifyhq/bitrise-step-autify-upload/issues\npublished_at: 2022-09-29T20:47:23.028758865Z\nsource:\n  git: https://github.com/autifyhq/bitrise-step-autify-upload.git\n  commit: f209c48fd9db74c92439a06d47d122c715b82da3\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- access_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Personal Access Token of Autify for Mobile\n    title: Access token of Autify for Mobile\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Your workspace ID of Autify for Mobile to upload the build\n    title: Workspace ID to upload\n  workspace_id: null\n- build_path: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |-\n      The file location of your build file i.e. /path/to/ios.app or /path/to/android.apk.\n      Typically, it's `$BITRISE_APP_DIR_PATH` for `Xcode build for simulator` step or `$BITRISE_APK_PATH` for `Android build` step.\n    title: Build path to upload\n- autify_path: autify\n  opts:\n    is_expand: true\n    title: A path to Autify CLI\n- autify_cli_installer_url: https://autify-cli-assets.s3.amazonaws.com/autify-cli/channels/stable/install-cicd.bash\n  opts:\n    is_expand: true\n    title: Autify CLI installer URL\noutputs:\n- AUTIFY_BUILD_ID: null\n  opts:\n    title: Uploaded build id on Autify for Mobile\n- AUTIFY_UPLOAD_EXIT_CODE: null\n  opts:\n    title: Exit code of the step\n"
  },
  {
    "path": "steps/autify-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/avd-manager/0.9.1/step.yml",
    "content": "title: AVD Manager\nsummary: Create and run Android Virtual Device\ndescription: Create and run Android Virtual Device\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2017-12-01T15:45:31.799247621+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 2cb213006948bccae20100cb4e14e82c6965de7c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_expand: true\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n    value_options:\n    - tv_1080p\n    - tv_720p\n    - wear_round\n    - wear_round_chin_320_290\n    - wear_square\n    - Galaxy Nexus\n    - Nexus 10\n    - Nexus 4\n    - Nexus 5\n    - Nexus 5X\n    - Nexus 6\n    - Nexus 6P\n    - Nexus 7 2013\n    - Nexus 7\n    - Nexus 9\n    - Nexus One\n    - Nexus S\n    - pixel\n    - pixel_c\n    - pixel_xl\n    - 2.7in QVGA\n    - 2.7in QVGA slider\n    - 3.2in HVGA slider (ADP1)\n    - 3.2in QVGA (ADP2)\n    - 3.3in WQVGA\n    - 3.4in WQVGA\n    - 3.7 FWVGA slider\n    - 3.7in WVGA (Nexus One)\n    - 4in WVGA (Nexus S)\n    - 4.65in 720p (Galaxy Nexus)\n    - 4.7in WXGA\n    - 5.1in WVGA\n    - 5.4in FWVGA\n    - 7in WSVGA (Tablet)\n    - 10.1in WXGA (Tablet)\n  profile: Nexus 5X\n- opts:\n    description: The device will run with the specified version of android.\n    is_expand: true\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n  version: 26\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- opts:\n    category: Customize\n    description: If set to `true` then the step will print emulator logs\n    is_expand: true\n    is_required: true\n    summary: If set to `true` then the step will print emulator logs\n    title: Verbose Mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_mode: false\n- opts:\n    category: Customize\n    description: Set the device to the selected orientation.\n    is_expand: true\n    is_required: true\n    summary: Set the device to the selected orientation.\n    title: Orientation\n    value_options:\n    - portrait\n    - landscape\n  orientation: portrait\n- opts:\n    category: Customize\n    description: Set the device's display resolution. This field will override the\n      device profile's default resolution, if you need the device profile's default\n      resolution leave this field empty.\n    is_expand: true\n    is_required: false\n    summary: Set the device's display resolution. This field will override the device\n      profile's default resolution, if you need the device profile's default resolution\n      leave this field empty.\n    title: Resolution\n  resolution: 240x426\n- density: 120\n  opts:\n    category: Customize\n    description: Set the device's display density. This field will override the device\n      profile's default density, if you need the device profile's default density\n      leave this field empty.\n    is_expand: true\n    is_required: false\n    summary: Set the device's display density. This field will override the device\n      profile's default density, if you need the device profile's default density\n      leave this field empty.\n    title: Density\n- emulator_id: emulator\n  opts:\n    category: Customize\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_expand: true\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- custom_hw_config: |-\n    disk.dataPartition.size=1024M\n    hw.camera.back=emulated\n    hw.camera.front=emulated\n    hw.keyboard=yes\n    hw.gpu.enabled=true\n    hw.gpu.mode=swiftshader\n    hw.ramSize=1536\n    runtime.network.latency=none\n    runtime.network.speed=full\n    showDeviceFrame=no\n    skin.dynamic=yes\n    skin.path=_no_skin\n    skin.path.backup=_no_skin\n    vm.heapSize=384\n  opts:\n    category: Customize\n    description: |-\n      Will append, replace or remove your config entries to the default device hardware config.\n\n      Usage: one config per line in the format `key=value`\n\n      For example: `hw.gpu.enabled=false`\n\n      Append:\n\n      If the given `key` is not in the config already, it will be added.\n\n      Remove:\n\n      Set your key without value, for example: `key=`. It will be removed from the default device config.\n\n      Replace:\n\n      If the given `key` is already in the config, the `value` will be replaced.\n    is_expand: true\n    is_required: false\n    summary: |-\n      Will append, replace or remove your config entries to the default device hardware config.\n\n      Usage: one config per line in the format `key=value`\n\n      For example: `hw.gpu.enabled=false`\n\n      Append:\n\n      If the given `key` is not in the config already, it will be added.\n\n      Remove:\n\n      Set your key without value, for example: `key=`. It will be removed from the default device config.\n\n      Replace:\n\n      If the given `key` is already in the config, the `value` will be replaced.\n    title: Custom hardware config\n- opts:\n    category: Customize\n    description: Overwrite AVD images if already exists.\n    is_expand: true\n    is_required: true\n    summary: Overwrite AVD images if already exists.\n    title: Overwrite\n    value_options:\n    - \"true\"\n    - \"false\"\n  overwrite: true\n- custom_command_flags: -no-window -no-audio -debug-init\n  opts:\n    category: Customize\n    description: Flags used when running the command to start the emulator.\n    is_expand: true\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n- emulator_abi: x86\n  opts:\n    category: Customize\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: Emulator ABI\n    value_options:\n    - x86\n    - armeabi-v7a\n    - arm64-v8a\n    - x86_64\n    - mips\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/0.9.2/step.yml",
    "content": "title: AVD Manager\nsummary: Create and run Android Virtual Device\ndescription: Create and run Android Virtual Device\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2017-12-20T11:04:35.985026322+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: b7b59cee5cf3ffbf712d976ea2c2a783709919b0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_expand: true\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n    value_options:\n    - tv_1080p\n    - tv_720p\n    - wear_round\n    - wear_round_chin_320_290\n    - wear_square\n    - Galaxy Nexus\n    - Nexus 10\n    - Nexus 4\n    - Nexus 5\n    - Nexus 5X\n    - Nexus 6\n    - Nexus 6P\n    - Nexus 7 2013\n    - Nexus 7\n    - Nexus 9\n    - Nexus One\n    - Nexus S\n    - pixel\n    - pixel_c\n    - pixel_xl\n    - 2.7in QVGA\n    - 2.7in QVGA slider\n    - 3.2in HVGA slider (ADP1)\n    - 3.2in QVGA (ADP2)\n    - 3.3in WQVGA\n    - 3.4in WQVGA\n    - 3.7 FWVGA slider\n    - 3.7in WVGA (Nexus One)\n    - 4in WVGA (Nexus S)\n    - 4.65in 720p (Galaxy Nexus)\n    - 4.7in WXGA\n    - 5.1in WVGA\n    - 5.4in FWVGA\n    - 7in WSVGA (Tablet)\n    - 10.1in WXGA (Tablet)\n  profile: Nexus 5X\n- opts:\n    description: The device will run with the specified version of android.\n    is_expand: true\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n  version: 26\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- opts:\n    category: Customize\n    description: If set to `true` then the step will print emulator logs\n    is_expand: true\n    is_required: true\n    summary: If set to `true` then the step will print emulator logs\n    title: Verbose Mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_mode: false\n- opts:\n    category: Customize\n    description: Set the device to the selected orientation.\n    is_expand: true\n    is_required: true\n    summary: Set the device to the selected orientation.\n    title: Orientation\n    value_options:\n    - portrait\n    - landscape\n  orientation: portrait\n- opts:\n    category: Customize\n    description: Set the device's display resolution. This field will override the\n      device profile's default resolution, if you need the device profile's default\n      resolution leave this field empty.\n    is_expand: true\n    is_required: false\n    summary: Set the device's display resolution. This field will override the device\n      profile's default resolution, if you need the device profile's default resolution\n      leave this field empty.\n    title: Resolution\n  resolution: 240x426\n- density: 120\n  opts:\n    category: Customize\n    description: Set the device's display density. This field will override the device\n      profile's default density, if you need the device profile's default density\n      leave this field empty.\n    is_expand: true\n    is_required: false\n    summary: Set the device's display density. This field will override the device\n      profile's default density, if you need the device profile's default density\n      leave this field empty.\n    title: Density\n- emulator_id: emulator\n  opts:\n    category: Customize\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_expand: true\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- custom_hw_config: |-\n    disk.dataPartition.size=1024M\n    hw.camera.back=emulated\n    hw.camera.front=emulated\n    hw.keyboard=yes\n    hw.gpu.enabled=true\n    hw.gpu.mode=swiftshader\n    hw.ramSize=1536\n    runtime.network.latency=none\n    runtime.network.speed=full\n    showDeviceFrame=no\n    skin.dynamic=yes\n    skin.path=_no_skin\n    skin.path.backup=_no_skin\n    vm.heapSize=384\n  opts:\n    category: Customize\n    description: |-\n      Will append, replace or remove your config entries to the default device hardware config.\n\n      Usage: one config per line in the format `key=value`\n\n      For example: `hw.gpu.enabled=false`\n\n      Append:\n\n      If the given `key` is not in the config already, it will be added.\n\n      Remove:\n\n      Set your key without value, for example: `key=`. It will be removed from the default device config.\n\n      Replace:\n\n      If the given `key` is already in the config, the `value` will be replaced.\n    is_expand: true\n    is_required: false\n    summary: |-\n      Will append, replace or remove your config entries to the default device hardware config.\n\n      Usage: one config per line in the format `key=value`\n\n      For example: `hw.gpu.enabled=false`\n\n      Append:\n\n      If the given `key` is not in the config already, it will be added.\n\n      Remove:\n\n      Set your key without value, for example: `key=`. It will be removed from the default device config.\n\n      Replace:\n\n      If the given `key` is already in the config, the `value` will be replaced.\n    title: Custom hardware config\n- opts:\n    category: Customize\n    description: Overwrite AVD images if already exists.\n    is_expand: true\n    is_required: true\n    summary: Overwrite AVD images if already exists.\n    title: Overwrite\n    value_options:\n    - \"true\"\n    - \"false\"\n  overwrite: true\n- custom_command_flags: -no-window -no-audio -debug-init\n  opts:\n    category: Customize\n    description: Flags used when running the command to start the emulator.\n    is_expand: true\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n- emulator_abi: x86\n  opts:\n    category: Customize\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: Emulator ABI\n    value_options:\n    - x86\n    - armeabi-v7a\n    - arm64-v8a\n    - x86_64\n    - mips\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.0.0/step.yml",
    "content": "title: AVD Manager\nsummary: Create and run Android Virtual Device\ndescription: Create and run Android Virtual Device\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2019-11-29T09:10:47.909560831Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 9f3acec7876c827c22b1391e14e7d7fe0c0fe507\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.0.1/step.yml",
    "content": "title: AVD Manager\nsummary: Create and run Android Virtual Device\ndescription: Create and run Android Virtual Device\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2019-12-09T14:53:28.773467259Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 0d1ffeb956f3721fcd0671952a9774537b16a7b0\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.0.2/step.yml",
    "content": "title: AVD Manager\nsummary: Create an Android emulator with the AVD Manager Step.\ndescription: |-\n  Test your project in an Android emulator with the AVD Manager. Once some basic inputs are set, the Step checks the requirements, downloads and installs the packages before creating and starting the emulator.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2020-11-20T12:28:51.692898261Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: d46b9e1c64fb711400d0d4ac0414ea3df53ce46e\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.0.3/step.yml",
    "content": "title: AVD Manager\nsummary: Create an Android emulator with the AVD Manager Step.\ndescription: |-\n  Test your project in an Android emulator with the AVD Manager. Once some basic inputs are set, the Step checks the requirements, downloads and installs the packages before creating and starting the emulator.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2021-06-25T12:16:38.197258009Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: dd09e2ee12aba7274cb034bcc8cccba32c1b4131\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.0.4/step.yml",
    "content": "title: AVD Manager\nsummary: Create an Android emulator with the AVD Manager Step.\ndescription: |-\n  Test your project in an Android emulator with the AVD Manager. Once some basic inputs are set, the Step checks the requirements, downloads and installs the packages before creating and starting the emulator.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2021-10-04T13:01:00.710607342Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 2850730d7019c511e744ef4def536117dfcd1e36\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Set the device profile to create the new AVD. This profile contains\n      all the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    is_required: true\n    summary: Set the device profile to create the new AVD. This profile contains all\n      the parameters of the devices. To see the complete list of available profiles\n      please use the `avdmanager list device` command.\n    title: Device Profile\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.1.0/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2022-05-18T10:12:57.558272713Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 0dd41db07c364875216bcba56e9e229251c99046\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: This profile contains all the parameters of the devices. To see the\n      complete list of available profiles use the `avdmanager list device` command\n      locally and use the `id` value for this input.\n    is_required: true\n    summary: Set the device profile to create the new AVD.\n    title: Device Profile\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.1.1/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2022-07-07T08:37:01.320369676Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: e7f4b61ed2452023dc1a66cf94323d5f3b8199bb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.1.2/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** This Step is not yet supported on Apple Silicon (M1) machines. If you cannot find a solution to this error, try running this Workflow on an Intel-based machine type.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2022-07-18T14:21:27.935844946Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: f6ddcd9ce0aa9df0519df3e6899e31e9b57451dc\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: \"0\"\n  opts:\n    category: Debug\n    description: Select which channel to use with `sdkmanager` to fetch `emulator`\n      package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch `emulator` package.\n      Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.2.0/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** This Step is not yet supported on Apple Silicon (M1) machines. If you cannot find a solution to this error, try running this Workflow on an Intel-based machine type.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2022-09-01T10:20:51.688411844Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 4eb065786a6f6eef9462502426392c45445a71f1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: no update\n  opts:\n    category: Debug\n    description: |-\n      Select which channel to use with `sdkmanager` to fetch *emulator* package. Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n\n      - `no update`: The *emulator* preinstalled on the Stack will be used. *system-image* will be updated to the latest Stable version.\n\n      To update *emulator* and *system image* to the latest available in a given channel:\n      - `0`: Stable channel\n      - `1`: Beta channel\n      - `2`: Dev channel\n      - `3`: Canary channel\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch *emulator* package.\n      Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev),\n      and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - no update\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      In headless mode the emulator is not launched in the foreground.\n\n      If this input is set, the emulator will not be visible but tests (even the screenshots) will run just like if the emulator ran in the foreground.\n    is_required: true\n    summary: In headless mode the emulator is not launched in the foreground.\n    title: Run the emulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.2.1/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** This Step is not yet supported on Apple Silicon (M1) machines. If you cannot find a solution to this error, try running this Workflow on an Intel-based machine type.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://stacks.bitrise.io).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2023-09-18T13:22:47.529952991Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 2f405f12e5a07a7c34c97616cb4179bd822adb23\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified version of android.\n    is_required: true\n    summary: The device will run with the specified version of android.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Debug\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Debug\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 512M\n  opts:\n    category: Debug\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Debug\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_channel: no update\n  opts:\n    category: Debug\n    description: |-\n      Select which channel to use with `sdkmanager` to fetch *emulator* package. Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n\n      - `no update`: The *emulator* preinstalled on the Stack will be used. *system-image* will be updated to the latest Stable version.\n\n      To update *emulator* and *system image* to the latest available in a given channel:\n      - `0`: Stable channel\n      - `1`: Beta channel\n      - `2`: Dev channel\n      - `3`: Canary channel\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch *emulator* package.\n      Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev),\n      and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - no update\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      In headless mode the emulator is not launched in the foreground.\n\n      If this input is set, the emulator will not be visible but tests (even the screenshots) will run just like if the emulator ran in the foreground.\n    is_required: true\n    summary: In headless mode the emulator is not launched in the foreground.\n    title: Run the emulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/1.3.0/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** Android emulators can't run on Apple Silicon build machines. Until nested virtualization becomes supported, you should run emulator tests on Linux machines.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://stacks.bitrise.io).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2024-11-22T14:15:05.30224367Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 70b5f4f35674c8634a14c1f23fca0521ae4be124\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified system image version.\n    is_required: true\n    summary: The device will run with the specified system image version.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Advanced\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- emulator_id: emulator\n  opts:\n    category: Advanced\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 2048M\n  opts:\n    category: Advanced\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Advanced\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_build_number: preinstalled\n  opts:\n    category: Emulator\n    description: |-\n      Allows installing a specific emulator version at runtime. The default value (`preinstalled`) will use the emulator version preinstalled on the Stack, which is updated regularly to the latest stable version.\n\n      See available build numbers [here](https://developer.android.com/studio/emulator_archive) (you need the last segment of the download URL). Note: this input expects the **build number**, not the **version number**.\n\n      When this input set to a specific build number, the `emulator_channel` input should be set to `no update`.\n    title: Emulator build number\n- emulator_channel: no update\n  opts:\n    category: Emulator\n    description: |-\n      Select which channel to use with `sdkmanager` to fetch *emulator* package. Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n\n      - `no update`: The *emulator* preinstalled on the Stack will be used. *system-image* will be updated to the latest Stable version.\n\n      To update *emulator* and *system image* to the latest available in a given channel:\n      - `0`: Stable channel\n      - `1`: Beta channel\n      - `2`: Dev channel\n      - `3`: Canary channel\n\n      When this input set to a specific channel, the `emulator_build_number` input should be set to `preinstalled`.\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch *emulator* package.\n      Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev),\n      and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - no update\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\n- headless_mode: \"yes\"\n  opts:\n    category: Emulator\n    description: |-\n      In headless mode the emulator is not launched in the foreground.\n\n      If this input is set, the emulator will not be visible but tests (even the screenshots) will run just like if the emulator ran in the foreground.\n    is_required: true\n    summary: In headless mode the emulator is not launched in the foreground.\n    title: Run the emulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/2.0.0/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** Android emulators can't run on Apple Silicon build machines. Until nested virtualization becomes supported, you should run emulator tests on Linux machines.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://stacks.bitrise.io).\n\n  ### Troubleshooting\n  The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.\n  We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2024-11-29T12:28:52.138387147Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 22f530768a1e8afae85f7d03ebe949ed850d1abe\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified system image version.\n    is_required: true\n    summary: The device will run with the specified system image version.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Advanced\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- disable_animations: \"yes\"\n  opts:\n    category: Advanced\n    description: |-\n      Disable animations on the emulator in order to make tests faster and more stable.\n\n      Animations can be enabled/disabled from the test code too, so if your tests do need animations, set this step input to `no` and control the settings yourself.\n    is_required: true\n    summary: Disable animations on the emulator in order to make tests faster and\n      more stable.\n    title: Disable animations\n    value_options:\n    - \"yes\"\n    - \"no\"\n- emulator_id: emulator\n  opts:\n    category: Advanced\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 2048M\n  opts:\n    category: Advanced\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Advanced\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_build_number: preinstalled\n  opts:\n    category: Emulator\n    description: |-\n      Allows installing a specific emulator version at runtime. The default value (`preinstalled`) will use the emulator version preinstalled on the Stack, which is updated regularly to the latest stable version.\n\n      See available build numbers [here](https://developer.android.com/studio/emulator_archive). You need the last segment of the download URL, for example, build number `12658423` from `emulator-linux_x64-12658423.zip`. Note: this input expects the **build number**, not the **version number**.\n\n      When this input set to a specific build number, the `emulator_channel` input should be set to `no update`.\n    title: Emulator build number\n- emulator_channel: no update\n  opts:\n    category: Emulator\n    description: |-\n      Select which channel to use with `sdkmanager` to fetch *emulator* package. Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n\n      - `no update`: The *emulator* preinstalled on the Stack will be used. *system-image* will be updated to the latest Stable version.\n\n      To update *emulator* and *system image* to the latest available in a given channel:\n      - `0`: Stable channel\n      - `1`: Beta channel\n      - `2`: Dev channel\n      - `3`: Canary channel\n\n      When this input set to a specific channel, the `emulator_build_number` input should be set to `preinstalled`.\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch *emulator* package.\n      Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev),\n      and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - no update\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\n- headless_mode: \"yes\"\n  opts:\n    category: Emulator\n    description: |-\n      In headless mode the emulator is not launched in the foreground.\n\n      If this input is set, the emulator will not be visible but tests (even the screenshots) will run just like if the emulator ran in the foreground.\n    is_required: true\n    summary: In headless mode the emulator is not launched in the foreground.\n    title: Run the emulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/2.0.1/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** Android emulators can't run on Apple Silicon build machines. Until nested virtualization becomes supported, you should run emulator tests on Linux machines.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://stacks.bitrise.io).\n\n  By default, the Step waits for the emulator to boot up and disables system animations in order to make tests faster and more reliable. If you want to disable these, set the **Disable animations** input to `no`. In this case, make sure to add the [Wait for Android emulator Step](https://github.com/bitrise-steplib/steps-wait-for-android-emulator) to the right part of your workflow.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2025-01-23T15:36:57.655790823Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 9bc13d4d1fbb99751a8027855fd2aa6f9ce17d5c\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified system image version.\n    is_required: true\n    summary: The device will run with the specified system image version.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_playstore\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Advanced\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- disable_animations: \"yes\"\n  opts:\n    category: Advanced\n    description: |-\n      Disable animations on the emulator in order to make tests faster and more stable.\n\n      Note: when this input is `yes`, the step will pause and wait for the device to boot up.\n\n      Animations can be enabled/disabled from the test code too, so if your tests do need animations, set this step input to `no` and control the settings yourself.\n    is_required: true\n    summary: Disable animations on the emulator in order to make tests faster and\n      more stable.\n    title: Disable animations\n    value_options:\n    - \"yes\"\n    - \"no\"\n- emulator_id: emulator\n  opts:\n    category: Advanced\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 2048M\n  opts:\n    category: Advanced\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Advanced\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_build_number: preinstalled\n  opts:\n    category: Emulator\n    description: |-\n      Allows installing a specific emulator version at runtime. The default value (`preinstalled`) will use the emulator version preinstalled on the Stack, which is updated regularly to the latest stable version.\n\n      See available build numbers [here](https://developer.android.com/studio/emulator_archive). You need the last segment of the download URL, for example, build number `12658423` from `emulator-linux_x64-12658423.zip`. Note: this input expects the **build number**, not the **version number**.\n\n      When this input set to a specific build number, the `emulator_channel` input should be set to `no update`.\n    title: Emulator build number\n- emulator_channel: no update\n  opts:\n    category: Emulator\n    description: |-\n      Select which channel to use with `sdkmanager` to fetch *emulator* package. Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n\n      - `no update`: The *emulator* preinstalled on the Stack will be used. *system-image* will be updated to the latest Stable version.\n\n      To update *emulator* and *system image* to the latest available in a given channel:\n      - `0`: Stable channel\n      - `1`: Beta channel\n      - `2`: Dev channel\n      - `3`: Canary channel\n\n      When this input set to a specific channel, the `emulator_build_number` input should be set to `preinstalled`.\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch *emulator* package.\n      Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev),\n      and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - no update\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\n- headless_mode: \"yes\"\n  opts:\n    category: Emulator\n    description: |-\n      In headless mode the emulator is not launched in the foreground.\n\n      If this input is set, the emulator will not be visible but tests (even the screenshots) will run just like if the emulator ran in the foreground.\n    is_required: true\n    summary: In headless mode the emulator is not launched in the foreground.\n    title: Run the emulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/2.0.2/step.yml",
    "content": "title: AVD Manager\nsummary: Create and boot an Android emulator used for device testing\ndescription: |-\n  Run instrumented and UI tests on a virtual Android device. Once some basic inputs are set, the Step checks the requirements, downloads the selected system image before creating and starting the emulator.\n\n  **Warning:** Android emulators can't run on Apple Silicon build machines. Until nested virtualization becomes supported, you should run emulator tests on Linux machines.\n\n  ### Configuring the Step\n  1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.\n  2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command and use the `id` value for this input.\n  3. Set the **Android API Level**. The new virtual device will run with the specified Android version.\n  4. Select an **OS Tag** to have the required toolset on the new virtual device.\n\n  Some system images are pre-installed on the virtual machines. In this case the step won't have to spend time downloading the requested image. To check the list of pre-installed images for each stack, visit the [system reports](https://stacks.bitrise.io).\n\n  By default, the Step waits for the emulator to boot up and disables system animations in order to make tests faster and more reliable. If you want to disable these, set the **Disable animations** input to `no`. In this case, make sure to add the [Wait for Android emulator Step](https://github.com/bitrise-steplib/steps-wait-for-android-emulator) to the right part of your workflow.\n\n  ### Useful links\n  - [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)\n  - [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n\n  ### Related Steps\n  - [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)\n  - [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\nwebsite: https://github.com/bitrise-steplib/steps-avd-manager\nsource_code_url: https://github.com/bitrise-steplib/steps-avd-manager\nsupport_url: https://github.com/bitrise-steplib/steps-avd-manager/issues\npublished_at: 2025-08-13T09:49:35.673737614Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-avd-manager.git\n  commit: 30bae41ae6d430512e1b41d2a79c54362b96e8f2\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-avd-manager\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The profile contains parameters of the device, such as screen size and resolution.\n\n      To see the complete list of available profiles use the `avdmanager list device` command locally and use the `id` value for this input.\n    is_required: true\n    summary: Device profile to use when creating the virtual device.\n    title: Device Profile ID\n  profile: pixel\n- api_level: 26\n  opts:\n    description: The device will run with the specified system image version.\n    is_required: true\n    summary: The device will run with the specified system image version.\n    title: Android API Level\n- opts:\n    description: Select OS tag to have the required toolset on the device.\n    is_expand: true\n    is_required: true\n    summary: Select OS tag to have the required toolset on the device.\n    title: OS Tag\n    value_options:\n    - google_apis\n    - google_apis_ps16k\n    - google_apis_playstore\n    - google_apis_playstore_ps16k\n    - google_atd\n    - aosp_atd\n    - android-wear\n    - android-tv\n    - default\n  tag: google_apis\n- abi: x86\n  opts:\n    category: Advanced\n    description: Select which ABI to use running the emulator. Availability depends\n      on API level. Please use `sdkmanager --list` command to see the available ABIs.\n    is_expand: true\n    is_required: true\n    summary: Select which ABI to use running the emulator. Availability depends on\n      API level. Please use `sdkmanager --list` command to see the available ABIs.\n    title: ABI\n    value_options:\n    - x86\n    - x86_64\n    - armeabi-v7a\n    - arm64-v8a\n    - mips\n- disable_animations: \"yes\"\n  opts:\n    category: Advanced\n    description: |-\n      Disable animations on the emulator in order to make tests faster and more stable.\n\n      Note: when this input is `yes`, the step will pause and wait for the device to boot up.\n\n      Animations can be enabled/disabled from the test code too, so if your tests do need animations, set this step input to `no` and control the settings yourself.\n    is_required: true\n    summary: Disable animations on the emulator in order to make tests faster and\n      more stable.\n    title: Disable animations\n    value_options:\n    - \"yes\"\n    - \"no\"\n- emulator_id: emulator\n  opts:\n    category: Advanced\n    description: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    is_required: true\n    summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)\n    title: ID\n- create_command_flags: --sdcard 2048M\n  opts:\n    category: Advanced\n    description: Flags used when running the command to create the emulator.\n    is_required: false\n    summary: Flags used when running the command to create the emulator.\n    title: Create AVD command flags\n- opts:\n    category: Advanced\n    description: Flags used when running the command to start the emulator.\n    is_required: false\n    summary: Flags used when running the command to start the emulator.\n    title: Start AVD command flags\n  start_command_flags: -camera-back none -camera-front none\n- emulator_build_number: preinstalled\n  opts:\n    category: Emulator\n    description: |-\n      Allows installing a specific emulator version at runtime. The default value (`preinstalled`) will use the emulator version preinstalled on the Stack, which is updated regularly to the latest stable version.\n\n      See available build numbers [here](https://developer.android.com/studio/emulator_archive). You need the last segment of the download URL, for example, build number `12658423` from `emulator-linux_x64-12658423.zip`. Note: this input expects the **build number**, not the **version number**.\n\n      When this input set to a specific build number, the `emulator_channel` input should be set to `no update`.\n    title: Emulator build number\n- emulator_channel: no update\n  opts:\n    category: Emulator\n    description: |-\n      Select which channel to use with `sdkmanager` to fetch *emulator* package. Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).\n\n      - `no update`: The *emulator* preinstalled on the Stack will be used. *system-image* will be updated to the latest Stable version.\n\n      To update *emulator* and *system image* to the latest available in a given channel:\n      - `0`: Stable channel\n      - `1`: Beta channel\n      - `2`: Dev channel\n      - `3`: Canary channel\n\n      When this input set to a specific channel, the `emulator_build_number` input should be set to `preinstalled`.\n    is_expand: true\n    is_required: true\n    summary: Select which channel to use with `sdkmanager` to fetch *emulator* package.\n      Available options are no update, or channels 0 (Stable), 1 (Beta), 2 (Dev),\n      and 3 (Canary).\n    title: Emulator channel\n    value_options:\n    - no update\n    - \"0\"\n    - \"1\"\n    - \"2\"\n    - \"3\"\n- headless_mode: \"yes\"\n  opts:\n    category: Emulator\n    description: |-\n      In headless mode the emulator is not launched in the foreground.\n\n      If this input is set, the emulator will not be visible but tests (even the screenshots) will run just like if the emulator ran in the foreground.\n    is_required: true\n    summary: In headless mode the emulator is not launched in the foreground.\n    title: Run the emulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/avd-manager/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/aws-device-farm-file-deploy/0.0.1/step.yml",
    "content": "title: Amazon Device Farm File Deploy\nsummary: Amazon Device Farm File Deploy\ndescription: |-\n  Uploads file (i.e. test package, app data, etc.) to device farm\n\n  This Step requires an Amazon Device Farm registration. To register an account, [click here](https://aws.amazon.com/device-farm/)\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy/issues\npublished_at: 2016-09-21T15:09:57.928508568-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy.git\n  commit: 10505476e1a0dcf4ab004c71c147daba89e9fd9d\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\n- amazon\n- device-farm\ndeps:\n  brew:\n  - name: awscli\n  apt_get:\n  - name: awscli\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI 'devicefarm list-projects'\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: Path of file to upload. If this is a test package, aws-device-farm-runner\n      can be configured to use the latest package with this name.\n    is_required: true\n    summary: \"\"\n    title: Upload File Path\n  upload_file_path: \"\"\n- opts:\n    description: ex. APPIUM_PYTHON_TEST_PACKAGE. See http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Upload.html#devicefarm-Type-Upload-type\n    is_required: true\n    summary: \"\"\n    title: Upload Type\n  upload_type: \"\"\n- aws_region: \"\"\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/aws-device-farm-file-deploy/0.0.2/step.yml",
    "content": "title: Amazon Device Farm File Deploy\nsummary: Amazon Device Farm File Deploy\ndescription: |-\n  Uploads file (i.e. test package, app data, etc.) to device farm\n\n  This Step requires an Amazon Device Farm registration. To register an account, [click here](https://aws.amazon.com/device-farm/)\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy/issues\npublished_at: 2016-09-22T15:27:51.58994299-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy.git\n  commit: 9336ff44d80618c9362156773924cadc5694331a\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  apt_get:\n  - name: awscli\n    bin_name: aws\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI 'devicefarm list-projects'\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: Path of file to upload. If this is a test package, aws-device-farm-runner\n      can be configured to use the latest package with this name.\n    is_required: true\n    summary: \"\"\n    title: Upload File Path\n  upload_file_path: \"\"\n- opts:\n    description: ex. APPIUM_PYTHON_TEST_PACKAGE. See http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Upload.html#devicefarm-Type-Upload-type\n    is_required: true\n    summary: \"\"\n    title: Upload Type\n  upload_type: \"\"\n"
  },
  {
    "path": "steps/aws-device-farm-file-deploy/0.0.3/step.yml",
    "content": "title: Amazon Device Farm File Deploy\nsummary: Amazon Device Farm File Deploy\ndescription: |-\n  Uploads file (i.e. test package, app data, etc.) to device farm\n\n  This Step requires an Amazon Device Farm registration. To register an account, [click here](https://aws.amazon.com/device-farm/)\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy/issues\npublished_at: 2017-05-12T10:18:40.515728783-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy.git\n  commit: 1cbc7c6403295ccb3dd33df6c7ca51c89b8409cd\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  apt_get:\n  - name: awscli\n    bin_name: aws\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI 'devicefarm list-projects'\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: Path of file to upload. If this is a test package, aws-device-farm-runner\n      can be configured to use the latest package with this name.\n    is_required: true\n    summary: \"\"\n    title: Upload File Path\n  upload_file_path: \"\"\n- opts:\n    description: ex. APPIUM_PYTHON_TEST_PACKAGE. See http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Upload.html#devicefarm-Type-Upload-type\n    is_required: true\n    summary: \"\"\n    title: Upload Type\n  upload_type: \"\"\n"
  },
  {
    "path": "steps/aws-device-farm-file-deploy/0.0.4/step.yml",
    "content": "title: Amazon Device Farm File Deploy\nsummary: Amazon Device Farm File Deploy\ndescription: |-\n  Uploads file (i.e. test package, app data, etc.) to device farm. Intended to be used with the [aws-device-farm-runner](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner) step.\n  This step requires an Amazon Device Farm registration. [Please read the aws-device-farm-runner wiki for setup instructions](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/wiki).\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy/issues\npublished_at: 2017-06-21T10:06:03.777420191-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy.git\n  commit: ff1e2ce0484920b5afce94bfccf2cca66111dd55\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\n- deploy\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  apt_get:\n  - name: awscli\n    bin_name: aws\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: Access key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: Secret key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the [AWS CLI](https://aws.amazon.com/cli/)\n      `devicefarm list-projects` command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: Path of file to upload. If this is a test package, [aws-device-farm-runner](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner)\n      can be configured to use the latest package with this name.\n    is_required: true\n    summary: \"\"\n    title: Upload File Path\n  upload_file_path: \"\"\n- opts:\n    description: ex. `APPIUM_PYTHON_TEST_PACKAGE`. See [Upload.type documentation](http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Upload.html#devicefarm-Type-Upload-type).\n    is_required: true\n    summary: \"\"\n    title: Upload Type\n  upload_type: \"\"\noutputs:\n- BITRISE_DEVICEFARM_UPLOAD_ARN: null\n  opts:\n    description: ARN identifier of successfully uploaded file\n    title: Upload ARN\n"
  },
  {
    "path": "steps/aws-device-farm-file-deploy/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.2/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: |-\n  Deploys app to device farm and starts a test run with a preconfigured test package and device pool.\n\n  This Step requires an Amazon Device Farm registration. To register an account, [click here](https://aws.amazon.com/device-farm/)\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues\npublished_at: 2016-09-23T11:23:05.808962866-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git\n  commit: 6289c7b0cf2038cdc06d185d0c55eae926d70b51\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\n- amazon\n- device-farm\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  apt_get:\n  - name: awscli\n    bin_name: aws\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI 'devicefarm list-projects'\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: Filename of test package to run, the latest package with this name\n      will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: See http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI 'devicefarm\n      list-device-pools' command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      'devicefarm list-device-pools' command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.3/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: |-\n  Deploys app to device farm and starts a test run with a preconfigured test package and device pool.\n\n  This Step requires an Amazon Device Farm registration. To register an account, [click here](https://aws.amazon.com/device-farm/)\n\n  Use the [aws-device-farm-file-deploy](https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) step to upload your latest test package (and extra app data if required) before this step runs.\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues\npublished_at: 2016-12-09T15:06:14.344739677-08:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git\n  commit: 2cd694b2faf2f02eced82ccdbb8d8bc30dd23082\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\n- amazon\n- device-farm\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  apt_get:\n  - name: awscli\n    bin_name: aws\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI 'devicefarm list-projects'\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: |-\n      Filename of test package to run.\n      This should be a filename (not a path) that matches the name of the test bundle previously uploaded with the aws-device-farm-file-deploy step.\n      The most recently uploaded package with this name will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: See http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI 'devicefarm\n      list-device-pools' command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      'devicefarm list-device-pools' command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.4/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: |-\n  Deploys app to device farm and starts a test run with a preconfigured test package and device pool.\n\n  This Step requires an Amazon Device Farm registration. To register an account, [click here](https://aws.amazon.com/device-farm/)\n\n  Use the [aws-device-farm-file-deploy](https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) step to upload your latest test package (and extra app data if required) before this step runs.\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues\npublished_at: 2016-12-13T09:53:47.263729195-08:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git\n  commit: 21b689a8ca74dd0236c25a695a7a5cb124f12d79\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\n  apt_get:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI 'devicefarm list-projects'\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- opts:\n    description: |-\n      Filename of test package to run.\n      This should be a filename (not a path) that matches the name of the test bundle previously uploaded with the aws-device-farm-file-deploy step.\n      The most recently uploaded package with this name will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: See http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI 'devicefarm\n      list-device-pools' command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      'devicefarm list-device-pools' command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- opts:\n    description: |-\n      If set to true, the script waits for the test run to complete on\n      Devicefarm before returning success/failure. This will slow down your\n      Bitrise runs, however allows you to make decisions in subsequent steps\n      based on success/failure of the tests.\n    title: Whether or not to wait for the test results from Devicefarm\n  run_wait_for_results: \"true\"\n- opts:\n    description: |-\n      Depending on your tests, you may or may not wish to fail the step if\n      DeviceFarm returns a WARNED result. Only takes effect if\n      run_wait_for_results is also enabled.\n    title: Fail if the DeviceFarm results return result of WARNED\n  run_fail_on_warning: \"true\"\noutputs:\n- BITRISE_DEVICEFARM_RESULTS_RAW: null\n  opts:\n    description: This is the full results of the run in JSON from AWS Device Farm\n    title: The full output from the device farm run\n- BITRISE_DEVICEFARM_RESULTS_SUMMARY: null\n  opts:\n    description: A nice summary suitable for feeding into something like a slack message.\n    title: A human-readable summary of the results.\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.5/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: Deploys app to device farm and starts a test run. [Please see the wiki\n  for setup instructions](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/wiki).\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues\npublished_at: 2017-06-21T09:19:56.224790211-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git\n  commit: 8e6dc423971abd4f8784505e241f09d47e4830a4\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\n  apt_get:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: Access key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: Secret key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI `devicefarm list-projects`\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- billing_method: METERED\n  opts:\n    description: This step specifies the billing methodfor your test run. Use `METERED`\n      for free tier and pay-as-you-go billing, and `UNMETERED` to use [pre-paid device\n      slots](https://docs.aws.amazon.com/devicefarm/latest/developerguide/how-to-purchase-device-slots.html).\n    is_required: false\n    summary: \"\"\n    title: Billing Method\n    value_options:\n    - METERED\n    - UNMETERED\n- opts:\n    description: |-\n      Filename of test package to run.\n      This should be a filename (not a path) that matches the name of the test bundle previously uploaded with the [aws-device-farm-file-deploy](https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) step.\n      The most recently uploaded package with this name will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: '[See the Test.type documentation](http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type).'\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI `devicefarm\n      list-device-pools` command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      `devicefarm list-device-pools` command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- opts:\n    description: |-\n      If set to true, the script waits for the test run to complete on\n      Device farm before returning success/failure. This will slow down your\n      Bitrise runs, however allows you to make decisions in subsequent steps\n      based on success/failure of the tests.\n    title: Whether or not to wait for the test results from device farm\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_wait_for_results: \"true\"\n- opts:\n    description: |-\n      Depending on your tests, you may or may not wish to fail the step if\n      Device farm returns a WARNED result. Only takes effect if\n      `run_wait_for_results` is also enabled.\n    title: Fail if the device farm results return result of WARNED\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_fail_on_warning: \"true\"\noutputs:\n- BITRISE_DEVICEFARM_RESULTS_RAW: null\n  opts:\n    description: This is the full results of the run in JSON from AWS Device Farm\n    title: The full output from the device farm run\n- BITRISE_DEVICEFARM_RESULTS_SUMMARY: null\n  opts:\n    description: A nice summary suitable for feeding into something like a slack message.\n    title: A human-readable summary of the results.\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.6/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: Deploys app to device farm and starts a test run. [Please see the wiki\n  for setup instructions](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/wiki).\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues\npublished_at: 2017-08-02T14:53:42.980457224-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git\n  commit: 6c107aaf92cf0244d9b494fd678ed29425c4273a\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\n  apt_get:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: Access key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: Secret key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI `devicefarm list-projects`\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- billing_method: METERED\n  opts:\n    description: This step specifies the billing method for your test run. Use `METERED`\n      for free tier and pay-as-you-go billing, and `UNMETERED` to use [pre-paid device\n      slots](https://docs.aws.amazon.com/devicefarm/latest/developerguide/how-to-purchase-device-slots.html).\n    is_required: false\n    summary: \"\"\n    title: Billing Method\n    value_options:\n    - METERED\n    - UNMETERED\n- opts:\n    description: |-\n      Filename of test package to run.\n      This should be a filename (not a path) that matches the name of the test bundle previously uploaded with the [aws-device-farm-file-deploy](https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) step.\n      The most recently uploaded package with this name will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: '[See the Test.type documentation](http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type).'\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- filter: \"\"\n  opts:\n    description: This step adds the opportunity to filter your tests. For example\n      com.android.abc.test1. [See the ScheduleRunTest.filter documentation](https://docs.aws.amazon.com/devicefarm/latest/APIReference/API_ScheduleRunTest.html#devicefarm-Type-ScheduleRunTest-filter).\n    is_required: false\n    summary: \"\"\n    title: Test Filter\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI `devicefarm\n      list-device-pools` command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      `devicefarm list-device-pools` command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- opts:\n    description: |-\n      If set to true, the script waits for the test run to complete on\n      Device farm before returning success/failure. This will slow down your\n      Bitrise runs, however allows you to make decisions in subsequent steps\n      based on success/failure of the tests.\n    title: Whether or not to wait for the test results from device farm\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_wait_for_results: \"true\"\n- opts:\n    description: |-\n      Depending on your tests, you may or may not wish to fail the step if\n      Device farm returns a WARNED result. Only takes effect if\n      `run_wait_for_results` is also enabled.\n    title: Fail if the device farm results return result of WARNED\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_fail_on_warning: \"true\"\noutputs:\n- BITRISE_DEVICEFARM_RESULTS_RAW: null\n  opts:\n    description: This is the full results of the run in JSON from AWS Device Farm\n    title: The full output from the device farm run\n- BITRISE_DEVICEFARM_RESULTS_SUMMARY: null\n  opts:\n    description: A nice summary suitable for feeding into something like a slack message.\n    title: A human-readable summary of the results.\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.7/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: Deploys app to device farm and starts a test run. [Please see the wiki\n  for setup instructions](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/wiki).\nwebsite: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues\npublished_at: 2017-08-22T10:41:26.570632632-07:00\nsource:\n  git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git\n  commit: 161322fbcfbc33d0b01044fda0de1d6cceac6dfb\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\n  apt_get:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: $AWS_ACCESS_KEY\n  opts:\n    description: Access key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: Secret key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: $AWS_SECRET_KEY\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI `devicefarm list-projects`\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- billing_method: METERED\n  opts:\n    description: This step specifies the billing method for your test run. Use `METERED`\n      for free tier and pay-as-you-go billing, and `UNMETERED` to use [pre-paid device\n      slots](https://docs.aws.amazon.com/devicefarm/latest/developerguide/how-to-purchase-device-slots.html).\n    is_required: false\n    summary: \"\"\n    title: Billing Method\n    value_options:\n    - METERED\n    - UNMETERED\n- locale: en_US\n  opts:\n    description: The locale as ISO language and country code to be used by the test\n      devices\n    is_required: false\n    summary: \"\"\n    title: The locale for the devices to use\n    value_options:\n    - ar_IL\n    - bg_BG\n    - ca_ES\n    - zh_CN\n    - zh_TW\n    - hr_HR\n    - cs_CZ\n    - da_DK\n    - nl_BE\n    - nl_NL\n    - en_AU\n    - en_GB\n    - en_CA\n    - en_IE\n    - en_IN\n    - en_NZ\n    - en_US\n    - fi_FI\n    - fr_BE\n    - fr_CA\n    - fr_FR\n    - fr_CH\n    - de_AT\n    - de_DE\n    - de_LI\n    - de_CH\n    - el_GR\n    - he_IL\n    - hi_IN\n    - hu_HU\n    - id_ID\n    - it_IT\n    - it_CH\n    - ja_JP\n    - ko_KR\n    - lv_LV\n    - lt_LT\n    - nb_NO\n    - pl_PL\n    - ro_RO\n    - ru_RU\n    - sr_RS\n    - sk_SK\n    - sl_SI\n    - es_ES\n    - es_US\n    - sv_SE\n    - tl_PH\n    - th_TH\n    - tr_TR\n    - uk_UA\n    - vi_VN\n- opts:\n    description: |-\n      Filename of test package to run.\n      This should be a filename (not a path) that matches the name of the test bundle previously uploaded with the [aws-device-farm-file-deploy](https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) step.\n      The most recently uploaded package with this name will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: '[See the Test.type documentation](http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type).'\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- filter: \"\"\n  opts:\n    description: This step adds the opportunity to filter your tests. For example\n      com.android.abc.test1. [See the ScheduleRunTest.filter documentation](https://docs.aws.amazon.com/devicefarm/latest/APIReference/API_ScheduleRunTest.html#devicefarm-Type-ScheduleRunTest-filter).\n    is_required: false\n    summary: \"\"\n    title: Test Filter\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI `devicefarm\n      list-device-pools` command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      `devicefarm list-device-pools` command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: $AWS_REGION\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    summary: \"\"\n    title: AWS Region\n- opts:\n    description: |-\n      If set to true, the script waits for the test run to complete on\n      Device farm before returning success/failure. This will slow down your\n      Bitrise runs, however allows you to make decisions in subsequent steps\n      based on success/failure of the tests.\n    title: Whether or not to wait for the test results from device farm\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_wait_for_results: \"true\"\n- opts:\n    description: |-\n      Depending on your tests, you may or may not wish to fail the step if\n      Device farm returns a WARNED result. Only takes effect if\n      `run_wait_for_results` is also enabled.\n    title: Fail if the device farm results return result of WARNED\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_fail_on_warning: \"true\"\noutputs:\n- BITRISE_DEVICEFARM_RESULTS_RAW: null\n  opts:\n    description: This is the full results of the run in JSON from AWS Device Farm\n    title: The full output from the device farm run\n- BITRISE_DEVICEFARM_RESULTS_SUMMARY: null\n  opts:\n    description: A nice summary suitable for feeding into something like a slack message.\n    title: A human-readable summary of the results.\n"
  },
  {
    "path": "steps/aws-device-farm-runner/0.0.8/step.yml",
    "content": "title: Amazon Device Farm Runner\nsummary: Amazon Device Farm Runner\ndescription: Deploys app to device farm and starts a test run. [Please see the wiki\n  for setup instructions](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/wiki).\nwebsite: https://github.com/lautarochiarle/bitrise-aws-device-farm-runner\nsource_code_url: https://github.com/lautarochiarle/bitrise-aws-device-farm-runner\nsupport_url: https://github.com/lautarochiarle/bitrise-aws-device-farm-runner/issues\npublished_at: 2020-07-20T11:19:20.051479742-03:00\nsource:\n  git: https://github.com/lautarochiarle/bitrise-aws-device-farm-runner.git\n  commit: c76d89246c8d5f59d7f27e4567beed41137436c1\nhost_os_tags:\n- linux\n- osx-10.9\n- osx-10.10\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\n  apt_get:\n  - name: awscli\n    bin_name: aws\n  - name: jq\n    bin_name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_key_id: \"\"\n  opts:\n    description: Access key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Access Key\n- opts:\n    description: Secret key for your AWS/IAM user. Define this as a secret environment\n      variable in your workflow.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Secret Key\n  secret_access_key: \"\"\n- device_farm_project: \"\"\n  opts:\n    description: Project ARNs can be obtained using the AWS CLI `devicefarm list-projects`\n      command.\n    is_required: true\n    summary: \"\"\n    title: Device Farm Project ARN\n- billing_method: METERED\n  opts:\n    description: This step specifies the billing method for your test run. Use `METERED`\n      for free tier and pay-as-you-go billing, and `UNMETERED` to use [pre-paid device\n      slots](https://docs.aws.amazon.com/devicefarm/latest/developerguide/how-to-purchase-device-slots.html).\n    is_required: false\n    summary: \"\"\n    title: Billing Method\n    value_options:\n    - METERED\n    - UNMETERED\n- locale: en_US\n  opts:\n    description: The locale as ISO language and country code to be used by the test\n      devices\n    is_required: false\n    summary: \"\"\n    title: The locale for the devices to use\n    value_options:\n    - ar_IL\n    - bg_BG\n    - ca_ES\n    - zh_CN\n    - zh_TW\n    - hr_HR\n    - cs_CZ\n    - da_DK\n    - nl_BE\n    - nl_NL\n    - en_AU\n    - en_GB\n    - en_CA\n    - en_IE\n    - en_IN\n    - en_NZ\n    - en_US\n    - fi_FI\n    - fr_BE\n    - fr_CA\n    - fr_FR\n    - fr_CH\n    - de_AT\n    - de_DE\n    - de_LI\n    - de_CH\n    - el_GR\n    - he_IL\n    - hi_IN\n    - hu_HU\n    - id_ID\n    - it_IT\n    - it_CH\n    - ja_JP\n    - ko_KR\n    - lv_LV\n    - lt_LT\n    - nb_NO\n    - pl_PL\n    - ro_RO\n    - ru_RU\n    - sr_RS\n    - sk_SK\n    - sl_SI\n    - es_ES\n    - es_US\n    - sv_SE\n    - tl_PH\n    - th_TH\n    - tr_TR\n    - uk_UA\n    - vi_VN\n- opts:\n    description: |-\n      Filename of test package to run.\n      This should be a filename (not a path) that matches the name of the test bundle previously uploaded with the [aws-device-farm-file-deploy](https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) step.\n      The most recently uploaded package with this name will be used.\n    is_required: true\n    summary: \"\"\n    title: Test Package Filename\n  test_package_name: \"\"\n- opts:\n    description: '[See the Test.type documentation](http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type).'\n    is_required: true\n    summary: \"\"\n    title: Test Type\n  test_type: \"\"\n- filter: \"\"\n  opts:\n    description: This step adds the opportunity to filter your tests. For example\n      com.android.abc.test1. [See the ScheduleRunTest.filter documentation](https://docs.aws.amazon.com/devicefarm/latest/APIReference/API_ScheduleRunTest.html#devicefarm-Type-ScheduleRunTest-filter).\n    is_required: false\n    summary: \"\"\n    title: Test Filter\n- opts:\n    description: Environment ARNs can be obtained using the AWS CLI `devicefarm list-uploads`\n      command.\n    is_required: false\n    summary: \"\"\n    title: Device Farm Custom TestSpec ARN\n  test_spec: $TEST_SPEC\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - android\n    - ios+android\n  platform: ios+android\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Required for iOS runs.\n    title: IPA file path\n- ios_pool: \"\"\n  opts:\n    description: Required for iOS runs. ARNs can be obtained using the AWS CLI `devicefarm\n      list-device-pools` command.\n    title: Device Farm iOS Device Pool ARN\n- apk_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    description: Required for Android runs.\n    title: APK file path\n- android_pool: \"\"\n  opts:\n    description: Required for Android runs. ARNs can be obtained using the AWS CLI\n      `devicefarm list-device-pools` command.\n    title: Device Farm Android Device Pool ARN\n- opts:\n    description: |\n      If you want to specify a name, this prefix will be used\n      followed by platform and bitrise build number.\n    summary: \"\"\n    title: Run Name Prefix\n  run_name_prefix: \"\"\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: Build number\n    is_required: true\n    title: Build Number\n- aws_region: \"\"\n  opts:\n    description: |\n      If you want to specify a different AWS region. Leave\n      empty to use the default config/env setting.\n    is_sensitive: true\n    summary: \"\"\n    title: AWS Region\n- opts:\n    description: |-\n      If set to true, the script waits for the test run to complete on\n      Device farm before returning success/failure. This will slow down your\n      Bitrise runs, however allows you to make decisions in subsequent steps\n      based on success/failure of the tests.\n    title: Whether or not to wait for the test results from device farm\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_wait_for_results: \"true\"\n- opts:\n    description: |-\n      Depending on your tests, you may or may not wish to fail the step if\n      Device farm returns a WARNED result. Only takes effect if\n      `run_wait_for_results` is also enabled.\n    title: Fail if the device farm results return result of WARNED\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_fail_on_warning: \"true\"\noutputs:\n- BITRISE_DEVICEFARM_RESULTS_RAW: null\n  opts:\n    description: This is the full results of the run in JSON from AWS Device Farm\n    title: The full output from the device farm run\n- BITRISE_DEVICEFARM_RESULTS_SUMMARY: null\n  opts:\n    description: A nice summary suitable for feeding into something like a slack message.\n    title: A human-readable summary of the results.\n"
  },
  {
    "path": "steps/aws-device-farm-runner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/aws-s3-upload/0.0.1/step.yml",
    "content": "title: Amazon Web Services (AWS) S3 Upload\nsummary: The Step uploads a file to an Amazon S3 bucket.\ndescription: |-\n  The Step uploads a file to an Amazon S3 bucket.\n\n  It can handle both files and directories, uploading the contents to the specified S3 bucket with the desired access control settings.\n\n  Using the Authenticate with AWS Step beforehand is recommended to securely provide short lived AWS credentials.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-aws-s3-upload\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-aws-s3-upload\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-aws-s3-upload/issues\npublished_at: 2025-10-31T14:07:40.715424+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-aws-s3-upload.git\n  commit: 30bc2a24c71ddac5fb2ad427186efce3b0637511\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-aws-s3-upload\ninputs:\n- opts:\n    description: |-\n      Path to a file or folder to be uploaded.\n\n      You can use absolute or relative paths.\n    is_required: true\n    summary: Path to a file or folder to be uploaded.\n    title: Path\n  path: null\n- bucket_name: null\n  opts:\n    description: Name of the S3 bucket to upload the file to.\n    is_required: true\n    summary: Name of the S3 bucket to upload the file to.\n    title: Bucket Name\n- bucket_prefix: null\n  opts:\n    description: |-\n      Path in the S3 bucket where the file will be uploaded.\n\n      If not provided, the file will be uploaded to the root of the bucket with its original filename.\n    is_required: false\n    summary: Path in the S3 bucket where the file will be uploaded.\n    title: Bucket Prefix\n- acl_control: private\n  opts:\n    description: The access control level for the uploaded file.\n    is_required: true\n    summary: The access control level for the uploaded file.\n    title: Access Control\n    value_options:\n    - private\n    - public-read\n- opts:\n    description: The AWS region to use.\n    is_required: true\n    summary: The AWS region to use.\n    title: Region\n  region: us-east-1\n- access_key_id: $AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS Credentials\n    description: |-\n      The AWS Access Key ID.\n\n      You can provide it directly or use the Authenticate with AWS Step.\n    is_dont_change_value: true\n    is_required: true\n    summary: The AWS Access Key ID.\n    title: AWS Access Key ID\n- opts:\n    category: AWS Credentials\n    description: |-\n      The AWS Secret Access Key.\n\n      You can provide it directly or use the Authenticate with AWS Step.\n    is_dont_change_value: true\n    is_required: true\n    summary: The AWS Secret Access Key.\n    title: AWS Secret Access Key\n  secret_access_key: $AWS_SECRET_ACCESS_KEY\n- opts:\n    category: AWS Credentials\n    description: |-\n      The AWS Session Token.\n\n      You can provide it directly or use the Authenticate with AWS Step.\n    is_dont_change_value: true\n    is_required: false\n    summary: The AWS Session Token.\n    title: AWS Session Token\n  session_token: $AWS_SESSION_TOKEN\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/aws-s3-upload/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/aws-secrets-manager/0.0.1/step.yml",
    "content": "title: Fetch secrets\nsummary: Fetch secrets from AWS Secrets Manager\ndescription: |\n  The main intention of this custom step is to allow us to store sensitive data on AWS Secrets Manager, and fetching them on-demand during Bitrise workflow execution.\n\n  When a Bitrise workflow runs, this step fetches the secrets from AWS Secrets Manager, based on the list of secrets provided as input.\n\n  Each secret stored on AWS Secrets Manager is represented as a JSON object. For each secret that it fetches, it then retrieve the JSON object value from the secret's JSON object, using a specified JSON object key. The value is then stored in an environment variable, exported and propagated to be consumed in subsequent steps in the workflow.\nwebsite: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsource_code_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsupport_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager/issues\npublished_at: 2020-10-15T16:26:03.236312+08:00\nsource:\n  git: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager.git\n  commit: 59a6b3e2cd6e06cacca07c74c5be176428e50d3d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: moneylion.com/security/bitrise-step-aws-secrets-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aws_access_key_id: $AWS_ACCESS_KEY_ID\n  opts:\n    description: The access key ID for your AWS IAM user\n    is_required: true\n    is_sensitive: true\n    summary: AWS Access Key ID\n    title: AWS Access Key ID\n- aws_secret_access_key: $AWS_SECRET_ACCESS_KEY\n  opts:\n    description: The secret access key for your AWS IAM user\n    is_required: true\n    is_sensitive: true\n    summary: AWS Secret Access Key\n    title: AWS Secret Access Key\n- aws_default_region: $AWS_DEFAULT_REGION\n  opts:\n    description: The AWS region where the secrets are created\n    is_required: true\n    is_sensitive: true\n    summary: AWS region\n    title: AWS region\n- aws_role_arn: $AWS_ROLE_ARN\n  opts:\n    description: The ARN of AWS IAM role to assume. This role should have the necessary\n      permission to read secrets from AWS Secrets Manager.\n    is_required: true\n    is_sensitive: true\n    summary: ARN of AWS IAM role to assume\n    title: AWS Role ARN\n- opts:\n    description: |\n      The newline separated list of secrets to be fetched from AWS Secrets Manager.\n\n      Each secret itself consists of three components:\n\n        - The ARN of the secret. This can be either full ARN, or partial ARN, which contains only the name of the secret, without the six random character suffix.\n\n        - The secret's JSON object key. The JSON object key for identifying the value that we want to retrieve in the secret's JSON object.\n\n        - The environment variable to store the value in. The environment variable where the JSON object value, identified by the JSON object key, is stored in.\n    is_required: true\n    summary: |\n      Newline separated list of secret. Each secret is delimited with hash symbol, consisting of the secret ARN, the secret's JSON object key, and the environment variable in which to store the corresponding JSON object value in.\n\n      Example: `arn:aws:secretsmanager:us-east-1:123456789012:secret:db-credential#username#USERNAME`.\n    title: Secret list\n  secret_list: null\n"
  },
  {
    "path": "steps/aws-secrets-manager/0.0.2/step.yml",
    "content": "title: Fetch secrets\nsummary: Fetch secrets from AWS Secrets Manager\ndescription: |\n  The main intention of this custom step is to allow us to store sensitive data on AWS Secrets Manager, and fetching them on-demand during Bitrise workflow execution.\n\n  When a Bitrise workflow runs, this step fetches the secrets from AWS Secrets Manager, based on the list of secrets provided as input.\n\n  Each secret stored on AWS Secrets Manager is represented as a JSON object. For each secret that it fetches, it then retrieve the JSON object value from the secret's JSON object, using a specified JSON object key. The value is then stored in an environment variable, exported and propagated to be consumed in subsequent steps in the workflow.\nwebsite: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsource_code_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsupport_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager/issues\npublished_at: 2020-11-13T14:50:21.621537+08:00\nsource:\n  git: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager.git\n  commit: 58b123623a351dcbe1621af4784d096caf3f58b9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: moneylion.com/security/bitrise-step-aws-secrets-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aws_access_key_id: $AWS_ACCESS_KEY_ID\n  opts:\n    description: The access key ID for your AWS IAM user\n    is_required: true\n    is_sensitive: true\n    summary: AWS Access Key ID\n    title: AWS Access Key ID\n- aws_secret_access_key: $AWS_SECRET_ACCESS_KEY\n  opts:\n    description: The secret access key for your AWS IAM user\n    is_required: true\n    is_sensitive: true\n    summary: AWS Secret Access Key\n    title: AWS Secret Access Key\n- aws_default_region: $AWS_DEFAULT_REGION\n  opts:\n    description: The AWS region where the secrets are created\n    is_required: true\n    is_sensitive: true\n    summary: AWS region\n    title: AWS region\n- aws_role_arn: $AWS_ROLE_ARN\n  opts:\n    description: The ARN of AWS IAM role to assume. This role should have the necessary\n      permission to read secrets from AWS Secrets Manager.\n    is_required: true\n    is_sensitive: true\n    summary: ARN of AWS IAM role to assume\n    title: AWS Role ARN\n- opts:\n    description: |\n      The newline separated list of secrets to be fetched from AWS Secrets Manager.\n\n      Each secret itself consists of three components:\n\n        - The ARN of the secret. This can be either full ARN, or partial ARN, which contains only the name of the secret, without the six random character suffix.\n\n        - The secret's JSON object key. The JSON object key for identifying the value that we want to retrieve in the secret's JSON object.\n\n        - The environment variable to store the value in. The environment variable where the JSON object value, identified by the JSON object key, is stored in.\n    is_required: true\n    summary: |\n      Newline separated list of secret. Each secret is delimited with hash symbol, consisting of the secret ARN, the secret's JSON object key, and the environment variable in which to store the corresponding JSON object value in.\n\n      Example: `arn:aws:secretsmanager:us-east-1:123456789012:secret:db-credential#username#USERNAME`.\n    title: Secret list\n  secret_list: null\n"
  },
  {
    "path": "steps/aws-secrets-manager/1.0.0/step.yml",
    "content": "title: Fetch secrets from AWS Secrets Manager\nsummary: Fetch secrets from AWS Secrets Manager\ndescription: |\n  The main intention of this Step is to allow storage of sensitive data on AWS Secrets Manager, and fetching them on-demand during Bitrise workflow execution.\n\n  When a workflow runs, the Step fetches a list of specified secrets from AWS Secrets Manager.\n\n  The fetched secrets are then propagated into subsequent steps in the workflow.\n\n  The Step uses AWS SDK for Go v2 with the default config loader. This means for authenticating with AWS, you may:\n\n    - Use static AWS credentials via environment variable, e.g. `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.\n    - Use shared configuration files, e.g. `AWS_PROFILE`.\n\n  Checkout the main repository README for more usage guide.\nwebsite: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsource_code_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsupport_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager/issues\npublished_at: 2021-07-21T21:06:31.545432+08:00\nsource:\n  git: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager.git\n  commit: 18db9fda4e3bbeb88b47e75f4bb4cde7ca0ba1eb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: moneylion.com/security/bitrise-step-aws-secrets-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aws_access_key_id: \"\"\n  opts:\n    description: The AWS Access Key ID. If you are supplying this input, ensure the\n      variable is named exactly `AWS_ACCESS_KEY_ID`.\n    is_sensitive: true\n    summary: AWS access key ID\n    title: AWS access key ID\n- aws_secret_access_key: \"\"\n  opts:\n    description: The AWS secret access key. If you are supplying this input, ensure\n      the variable is named exactly `AWS_SECRET_ACCESS_KEY`.\n    is_sensitive: true\n    summary: AWS secret access key\n    title: AWS secret access key\n- aws_region: \"\"\n  opts:\n    description: The AWS region to operate in. If you are supplying this input, ensure\n      the variable is named exactly `AWS_DEFAULT_REGION` or `AWS_REGION`.\n    summary: AWS region\n    title: AWS region\n- aws_iam_role_arn: \"\"\n  opts:\n    description: The ARN of AWS IAM role to assume. This role should have the necessary\n      permission to read secrets from AWS Secrets Manager.\n    summary: The ARN of AWS IAM role to assume.\n    title: AWS IAM role ARN\n- opts:\n    description: |\n      A newline separated list of secrets to fetch from AWS Secrets Manager.\n\n      Each line is in the form of:\n\n      ```\n      <Secret ARN> # <JSON object key> # <Environment variable>\n      ```\n\n      For example, given the secret with an ARN `arn:aws:secret-1`, and a secret value:\n\n      ```\n      {\n        \"username\": \"admin\",\n        \"password\": \"str0ngpassword\"\n      }\n      ```\n\n      Specifying this line in the secret list:\n\n      ```\n      arn:aws:secret-1 # username # USERNAME\n      ```\n\n      Fetches the secret, retrieves the JSON value under the key `username`, and store that value in the `USERNAME` environment variable. `$USERNAME` will now contain the value `admin`.\n    is_required: true\n    summary: A list of secrets to fetch.\n    title: Secret list\n  secret_list: null\n"
  },
  {
    "path": "steps/aws-secrets-manager/2.0.0/step.yml",
    "content": "title: Fetch secrets from AWS Secrets Manager\nsummary: Fetch secrets from AWS Secrets Manager\ndescription: |\n  This Step fetches secrets on-demand from AWS Secrets Manager, during Bitrise workflow execution.\n\n  The fetched secrets are then propagated into subsequent steps in the workflow.\n\n  Include this Step in your workflow, for example:\n\n  ```yaml\n  workflows:\n    foo:\n      steps:\n      - aws-secrets-manager@x.x.x:\n          inputs:\n          - aws_access_key_id: $AWS_ACCESS_KEY_ID\n          - aws_secret_access_key: $AWS_SECRET_ACCESS_KEY\n          - aws_default_region: a-region-1\n          - secret_list: |\n              arn:aws:secret-1 # username # USERNAME\n              arn:aws:secret-2 # password # PASSWORD\n      - script@1:\n          inputs:\n          - content: |\n              #!/bin/bash\n              #\n              # Access your secrets via $USERNAME and $PASSWORD\n  ```\n\n  Checkout the main repository README for more usage guide.\nwebsite: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsource_code_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsupport_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager/issues\npublished_at: 2021-07-25T05:57:58.17624+08:00\nsource:\n  git: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager.git\n  commit: 72b0bb599fa60abad1e423f92c6f4a969771106d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: moneylion.com/security/bitrise-step-aws-secrets-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aws_access_key_id: \"\"\n  opts:\n    description: AWS access key ID.\n    is_sensitive: true\n    summary: AWS access key ID.\n    title: AWS access key ID\n- aws_secret_access_key: \"\"\n  opts:\n    description: AWS secret access key.\n    is_sensitive: true\n    summary: AWS secret access key.\n    title: AWS secret access key\n- aws_default_region: \"\"\n  opts:\n    description: AWS region to operate in.\n    summary: AWS region to operate in.\n    title: AWS region\n- aws_profile: \"\"\n  opts:\n    description: An AWS named profile in shared configuration file.\n    summary: An AWS named profile in shared configuration file.\n    title: AWS named profile\n- aws_iam_role_arn: \"\"\n  opts:\n    description: The ARN of AWS IAM role to assume.\n    summary: The ARN of AWS IAM role to assume.\n    title: AWS IAM role ARN\n- opts:\n    description: |\n      A newline separated list of secrets to fetch from AWS Secrets Manager.\n\n      Each line is in the form of:\n\n      ```\n      <Secret ARN> # <JSON object key> # <Environment variable>\n      ```\n\n      For example, given the secret with an ARN `arn:aws:secret-1`, and a secret value:\n\n      ```\n      {\n        \"username\": \"admin\",\n        \"password\": \"str0ngpassword\"\n      }\n      ```\n\n      Specifying this line in the secret list:\n\n      ```\n      arn:aws:secret-1 # username # USERNAME\n      ```\n\n      Fetches the secret, retrieves the JSON value under the key `username`, and store that value in the `USERNAME` environment variable. `$USERNAME` will now contain the value `admin`.\n    is_required: true\n    summary: A list of secrets to fetch.\n    title: Secret list\n  secret_list: null\n"
  },
  {
    "path": "steps/aws-secrets-manager/2.1.0/step.yml",
    "content": "title: Fetch secrets from AWS Secrets Manager\nsummary: Fetch secrets from AWS Secrets Manager\ndescription: |\n  This Step fetches secrets on-demand from AWS Secrets Manager, during Bitrise workflow execution.\n\n  The fetched secrets are then propagated into subsequent steps in the workflow.\n\n  Include this Step in your workflow, for example:\n\n  ```yaml\n  workflows:\n    foo:\n      steps:\n      - aws-secrets-manager@x.x.x:\n          inputs:\n          - aws_access_key_id: $AWS_ACCESS_KEY_ID\n          - aws_secret_access_key: $AWS_SECRET_ACCESS_KEY\n          - aws_default_region: a-region-1\n          - secret_list: |\n              arn:aws:secret-1 # username # USERNAME\n              arn:aws:secret-2 # password # PASSWORD\n      - script@1:\n          inputs:\n          - content: |\n              #!/bin/bash\n              #\n              # Access your secrets via $USERNAME and $PASSWORD\n  ```\n\n  Checkout the main repository README for more usage guide.\nwebsite: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsource_code_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsupport_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager/issues\npublished_at: 2022-03-01T22:24:56.567286+08:00\nsource:\n  git: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager.git\n  commit: ca54ddf8f393d583dc302c25569073f6c08bd343\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: moneylion.com/security/bitrise-step-aws-secrets-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aws_access_key_id: \"\"\n  opts:\n    description: AWS access key ID.\n    is_sensitive: true\n    summary: AWS access key ID.\n    title: AWS access key ID\n- aws_secret_access_key: \"\"\n  opts:\n    description: AWS secret access key.\n    is_sensitive: true\n    summary: AWS secret access key.\n    title: AWS secret access key\n- aws_default_region: \"\"\n  opts:\n    description: AWS region to operate in.\n    summary: AWS region to operate in.\n    title: AWS region\n- aws_profile: \"\"\n  opts:\n    description: An AWS named profile in shared configuration file.\n    summary: An AWS named profile in shared configuration file.\n    title: AWS named profile\n- aws_iam_role_arn: \"\"\n  opts:\n    description: The ARN of AWS IAM role to assume.\n    summary: The ARN of AWS IAM role to assume.\n    title: AWS IAM role ARN\n- opts:\n    description: |\n      A newline separated list of secrets to fetch from AWS Secrets Manager.\n\n      Each line is in the form of:\n\n      ```\n      <Secret ARN> # <JSON object key> # <Environment variable>\n      ```\n\n      For example, given the secret with an ARN `arn:aws:secret-1`, and a secret value:\n\n      ```\n      {\n        \"username\": \"admin\",\n        \"password\": \"str0ngpassword\"\n      }\n      ```\n\n      Specifying this line in the secret list:\n\n      ```\n      arn:aws:secret-1 # username # USERNAME\n      ```\n\n      Fetches the secret, retrieves the JSON value under the key `username`, and store that value in the `USERNAME` environment variable. `$USERNAME` will now contain the value `admin`.\n    is_required: true\n    summary: A list of secrets to fetch.\n    title: Secret list\n  secret_list: null\n"
  },
  {
    "path": "steps/aws-secrets-manager/2.2.0/step.yml",
    "content": "title: Fetch secrets from AWS Secrets Manager\nsummary: Fetch secrets from AWS Secrets Manager\ndescription: |\n  This Step fetches secrets on-demand from AWS Secrets Manager, during Bitrise workflow execution.\n\n  The fetched secrets are then propagated into subsequent steps in the workflow.\n\n  This step can detect if it should parse the SecretString as JSON or as regular text. No extra configuration required.\n\n  Include this Step in your workflow, for example:\n\n  ```yaml\n  workflows:\n    foo:\n      steps:\n      - aws-secrets-manager@x.x.x:\n          inputs:\n          - aws_access_key_id: $AWS_ACCESS_KEY_ID\n          - aws_secret_access_key: $AWS_SECRET_ACCESS_KEY\n          - aws_default_region: a-region-1\n          - secret_list: |\n              arn:aws:secret-1 # username # USERNAME\n              arn:aws:secret-2 # password # PASSWORD\n      - script@1:\n          inputs:\n          - content: |\n              #!/bin/bash\n              #\n              # Access your secrets via $USERNAME and $PASSWORD\n  ```\n\n  Checkout the main repository README for more usage guide.\nwebsite: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsource_code_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager\nsupport_url: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager/issues\npublished_at: 2023-02-08T13:18:09.982416+08:00\nsource:\n  git: https://github.com/MoneyLion/bitrise-step-aws-secrets-manager.git\n  commit: 1ddeccc3207abc94a39603f96b3a9d432ba952b4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: moneylion.com/security/bitrise-step-aws-secrets-manager\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aws_access_key_id: \"\"\n  opts:\n    description: AWS access key ID.\n    is_sensitive: true\n    summary: AWS access key ID.\n    title: AWS access key ID\n- aws_secret_access_key: \"\"\n  opts:\n    description: AWS secret access key.\n    is_sensitive: true\n    summary: AWS secret access key.\n    title: AWS secret access key\n- aws_default_region: \"\"\n  opts:\n    description: AWS region to operate in.\n    summary: AWS region to operate in.\n    title: AWS region\n- aws_profile: \"\"\n  opts:\n    description: An AWS named profile in shared configuration file.\n    summary: An AWS named profile in shared configuration file.\n    title: AWS named profile\n- aws_iam_role_arn: \"\"\n  opts:\n    description: The ARN of AWS IAM role to assume.\n    summary: The ARN of AWS IAM role to assume.\n    title: AWS IAM role ARN\n- opts:\n    description: |\n      A newline separated list of secrets to fetch from AWS Secrets Manager.\n\n      Each line is in the form of:\n\n      ```\n      <Secret ARN> # <JSON object key> # <Environment variable>\n      ```\n\n      For example, given the secret with an ARN `arn:aws:secret-1`, and a secret value:\n\n      ```\n      {\n        \"username\": \"admin\",\n        \"password\": \"str0ngpassword\"\n      }\n      ```\n\n      Specifying this line in the secret list:\n\n      ```\n      arn:aws:secret-1 # username # USERNAME\n      ```\n\n      Fetches the secret, retrieves the JSON value under the key `username`, and store that value in the `USERNAME` environment variable. `$USERNAME` will now contain the value `admin`.\n    is_required: true\n    summary: A list of secrets to fetch.\n    title: Secret list\n  secret_list: null\n"
  },
  {
    "path": "steps/aws-secrets-manager/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/azure-devops-status/1.0.0/step.yml",
    "content": "title: Azure DevOps status\nsummary: |\n  Update commit status for Azure DevOps repositories\ndescription: |\n  Update commit status for Azure DevOps repositories.\n  This step always runs, no matter if build succeeded or failed.\nwebsite: https://github.com/mediusoft/bitrise-step-azure-devops-status\nsource_code_url: https://github.com/mediusoft/bitrise-step-azure-devops-status\nsupport_url: https://github.com/mediusoft/bitrise-step-azure-devops-status/issues\npublished_at: 2020-03-15T20:28:19.936735+02:00\nsource:\n  git: https://github.com/mediusoft/bitrise-step-azure-devops-status.git\n  commit: 3c853bceaf36f19e011b1517e67349d320d313cf\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: not (enveq \"BITRISE_GIT_COMMIT\" \"\")\ninputs:\n- devops_user: $AZURE_DEVOPS_USER\n  opts:\n    description: |\n      Azure DevOps user name.\n      Can also be taken from env var `AZURE_DEVOPS_USER`.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Azure DevOps user name\n- devops_pat: $AZURE_DEVOPS_PAT\n  opts:\n    description: |\n      Azure DevOps Personal Access Token.\n      Can also be taken from env var `AZURE_DEVOPS_PAT`.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Azure DevOps Personal Access Token\n- devops_organization: $AZURE_DEVOPS_ORGANIZATION\n  opts:\n    description: |\n      Azure DevOps organization.\n      Can also be taken from env var `AZURE_DEVOPS_ORGANIZATION`.\n    is_expand: true\n    is_required: true\n    title: Azure DevOps organization\n- devops_project: $AZURE_DEVOPS_PROJECT\n  opts:\n    description: |\n      Azure DevOps project.\n      Can also be taken from env var `AZURE_DEVOPS_PROJECT`.\n    is_expand: true\n    is_required: true\n    title: Azure DevOps project\n- devops_repository_id: $AZURE_DEVOPS_REPOSITORY_ID\n  opts:\n    description: |\n      Azure DevOps repository ID.\n      Can also be taken from env var `AZURE_DEVOPS_REPOSITORY_ID`.\n    is_expand: true\n    is_required: true\n    title: Azure DevOps repository ID\n- devops_commit_state: auto\n  opts:\n    description: |\n      Status to set on commit.\n\n      Possible values are `auto`, `error`, `failed`, `notApplicable`, `notSet`, `pending`, `succeeded`.\n      If set to `auto` then step will automatically set 'succeeded' or 'failed' based on build status.\n    is_expand: true\n    is_required: true\n    title: Commit status\n    value_options:\n    - auto\n    - pending\n    - succeeded\n    - failed\n    - error\n    - notSet\n    - notApplicable\n- devops_description: \"\"\n  opts:\n    description: \"Status description. \\nTypically describes current state of the status.\\n\"\n    is_expand: true\n    is_required: false\n    title: Commit status description\n- devops_target_url: $BITRISE_BUILD_URL\n  opts:\n    description: |\n      URL with status details.\n    is_expand: true\n    is_required: true\n    title: Target URL\n- devops_context_name: build/$BITRISE_APP_TITLE\n  opts:\n    description: \"Name identifier of the status. \\nCannot be empty.\\n\"\n    is_expand: true\n    is_required: true\n    title: Name identifier\n- devops_context_genre: continuous-integration\n  opts:\n    description: \"Genre of the status. \\nTypically name of the service/tool generating\n      the status, can be empty.\\n\"\n    is_expand: true\n    is_required: false\n    title: Status genre\n"
  },
  {
    "path": "steps/azure-devops-status/1.0.1/step.yml",
    "content": "title: Azure DevOps status\nsummary: |\n  Update commit status for Azure DevOps repositories\ndescription: |\n  Update commit status for Azure DevOps repositories.\n  This step always runs, no matter if build succeeded or failed.\nwebsite: https://github.com/mediusoft/bitrise-step-azure-devops-status\nsource_code_url: https://github.com/mediusoft/bitrise-step-azure-devops-status\nsupport_url: https://github.com/mediusoft/bitrise-step-azure-devops-status/issues\npublished_at: 2020-03-17T00:04:11.37749+02:00\nsource:\n  git: https://github.com/mediusoft/bitrise-step-azure-devops-status.git\n  commit: 1c28119b926f95b405ddad80b258ce9e414d44bf\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: not (enveq \"BITRISE_GIT_COMMIT\" \"\")\ninputs:\n- devops_user: $AZURE_DEVOPS_USER\n  opts:\n    description: |\n      Azure DevOps user name.\n\n      Can also be taken from secret `AZURE_DEVOPS_USER`. Cannot be empty.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Azure DevOps user name\n- devops_pat: $AZURE_DEVOPS_PAT\n  opts:\n    description: |\n      Azure DevOps Personal Access Token.\n\n      Can also be taken from secret `AZURE_DEVOPS_PAT`. Cannot be empty.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Azure DevOps Personal Access Token\n- devops_organization: $AZURE_DEVOPS_ORGANIZATION\n  opts:\n    description: |\n      Azure DevOps organization.\n\n      Can also be taken from env var `AZURE_DEVOPS_ORGANIZATION`. Cannot be empty.\n    is_expand: true\n    is_required: true\n    title: Azure DevOps organization\n- devops_project: $AZURE_DEVOPS_PROJECT\n  opts:\n    description: |\n      Azure DevOps project.\n\n      Can also be taken from env var `AZURE_DEVOPS_PROJECT`. Cannot be empty.\n    is_expand: true\n    is_required: true\n    title: Azure DevOps project\n- devops_repository_id: $AZURE_DEVOPS_REPOSITORY_ID\n  opts:\n    description: |\n      Azure DevOps repository ID.\n\n      Can also be taken from env var `AZURE_DEVOPS_REPOSITORY_ID`. Cannot be empty.\n    is_expand: true\n    is_required: true\n    title: Azure DevOps repository ID\n- devops_commit_state: auto\n  opts:\n    description: |\n      Status to set on commit.\n\n      Possible values are `auto`, `error`, `failed`, `notApplicable`, `notSet`, `pending`, `succeeded`.\n      If set to `auto` then step will automatically set `succeeded` or `failed` based on build status.\n    is_expand: true\n    is_required: true\n    title: Commit status\n    value_options:\n    - auto\n    - pending\n    - succeeded\n    - failed\n    - error\n    - notSet\n    - notApplicable\n- devops_description: \"\"\n  opts:\n    description: \"Status description.\\n\\nTypically describes current state of the\n      status. \\nIf no value provided, then will be set to `$BITRISE_APP_TITLE build\n      #$BITRISE_BUILD_NUMBER $state`.\\n\"\n    is_expand: true\n    is_required: false\n    title: Commit status description\n- devops_target_url: $BITRISE_BUILD_URL\n  opts:\n    description: |\n      URL with status details.\n\n      This URL will be opened when status description is clicked from Azure DevOps. Cannot be empty\n    is_expand: true\n    is_required: true\n    title: Target URL\n- devops_context_name: build/$BITRISE_APP_TITLE\n  opts:\n    description: |\n      Name identifier of the status.\n\n      Typically name of the build pipeline/configuration. Cannot be empty.\n    is_expand: true\n    is_required: true\n    title: Name identifier\n- devops_context_genre: continuous-integration\n  opts:\n    description: |\n      Genre of the status.\n\n      Typically name of the service/tool generating the status. Can be empty.\n    is_expand: true\n    is_required: false\n    title: Status genre\n"
  },
  {
    "path": "steps/azure-devops-status/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/badgetizr/3.0.3/step.yml",
    "content": "source:\n  git: https://github.com/aiKrice/homebrew-badgetizr.git\n  commit: 18db6c368edc4f16628a12ad43602ceac6603727\n\ntitle: Badgetizr\nsummary: Automatically add custom badges to pull/merge requests - boost productivity and streamline code reviews\ndescription: |\n  Badgetizr automatically adds customizable badges to your GitHub and GitLab pull/merge requests to boost team productivity.\n\n  Features:\n  - Track ticket references automatically from PR titles\n  - Identify work-in-progress pull requests clearly\n  - Monitor CI/CD status without clicking through pipelines\n  - Visualize completion status of checklists and tasks\n  - Highlight target branches for better merge awareness\n\n  This step works on both macOS and Linux stacks by cloning the repository and running the badgetizr script.\nmaintainer: community\nwebsite: https://github.com/aiKrice/homebrew-badgetizr\nsource_code_url: https://github.com/aiKrice/homebrew-badgetizr\nsupport_url: https://github.com/aiKrice/homebrew-badgetizr/issues\npublished_at: 2025-12-17T00:00:00Z\n\ntype_tags:\n  - notification\n\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\n\ntoolkit:\n  bash:\n    entry_file: step.sh\n\ndeps:\n  brew:\n    - name: gh\n    - name: glab\n  apt_get:\n    - name: wget\n\ninputs:\n  - pr_id: \"$BITRISE_PULL_REQUEST\"\n    opts:\n        title: \"Pull/Merge Request ID\"\n        summary: \"The ID of the pull request or merge request\"\n        description: |\n          The ID number of the pull/merge request where badges will be added.\n\n          For GitHub: Use `$BITRISE_PULL_REQUEST` or `$PR_NUMBER`\n          For GitLab: Use `$BITRISE_PULL_REQUEST` or your custom variable\n        is_required: true\n\n  - configuration: \".badgetizr.yml\"\n    opts:\n      title: \"Configuration file path\"\n      summary: \"Path to the badgetizr configuration file\"\n      description: |\n        Path to the YAML configuration file that defines which badges to display.\n        Default: `.badgetizr.yml`\n      is_required: true\n\n  - pr_destination_branch:\n    opts:\n        title: \"PR destination branch\"\n        summary: \"Target branch for the pull/merge request\"\n        description: |\n          The branch that the PR/MR is targeting. Required when branch badge is enabled.\n\n          For GitHub: Use `$BITRISEIO_GIT_BRANCH_DEST`\n          For GitLab: Use your target branch variable\n        is_required: false\n\n  - pr_build_number:\n    opts:\n        title: \"Build number\"\n        summary: \"Current build number\"\n        description: |\n          The build number to display in the CI badge. Use `$BITRISE_BUILD_NUMBER`.\n          Required when CI badge is enabled without ci_status.\n        is_required: false\n\n  - pr_build_url:\n    opts:\n        title: \"Build URL\"\n        summary: \"URL to the current build\"\n        description: |\n          The URL to the build page. Use `$BITRISE_BUILD_URL`.\n          Required when CI badge is enabled.\n        is_required: false\n\n  - ci_status:\n    opts:\n        title: \"CI Status\"\n        summary: \"Current CI/CD pipeline status\"\n        description: |\n          Controls the CI badge color and behavior.\n\n          **Modes:**\n          - **automatic** (recommended for final status): Auto-detect from Bitrise environment\n            - Uses $BITRISE_BUILD_STATUS and $BITRISE_PIPELINE_BUILD_STATUS\n            - Returns \"passed\" (green) or \"failed\" (red) at build end\n\n            **⚠️ IMPORTANT - Timing:**\n            - MUST be used as the FINAL step in your workflow\n            - Place AFTER all build, test, and deploy steps complete\n            - Only then will $BITRISE_BUILD_STATUS reflect the true final status\n\n            **Example workflow:**\n            ```yaml\n            workflows:\n              primary:\n                steps:\n                  - git-clone: {}\n                  - script: { title: \"Build\" }\n                  - script: { title: \"Test\" }\n                  - script: { title: \"Deploy\" }\n                  - badgetizr: { ci_status: \"automatic\" }  # ← Final step\n            ```\n\n          - **Manual status** (for intermediate steps or custom control):\n            - started = yellow (use for running/in-progress builds at workflow START)\n            - passed = green\n            - warning = orange\n            - failed = red\n\n            **Use cases:**\n            - Show \"started\" at beginning of workflow\n            - Update to \"passed\"/\"failed\" at specific checkpoints\n            - Custom statuses for complex multi-stage pipelines\n\n          - **Empty**: Build number mode - static badge with build number (requires --pr-build-number)\n\n        is_required: false\n        value_options:\n          - \"automatic\"\n          - \"started\"\n          - \"passed\"\n          - \"warning\"\n          - \"failed\"\n\n  - ci_text:\n    opts:\n        title: \"CI Badge Text\"\n        summary: \"Custom text for the CI badge\"\n        description: |\n          Custom text to display in the CI badge.\n          If not provided, defaults to the status or build number.\n        is_required: false\n\n  - provider: \"github\"\n    opts:\n      title: \"Provider\"\n      summary: \"Force specific provider (github or gitlab)\"\n      description: |\n        Force a specific provider. If not set, auto-detection will be used.\n        Valid values: github, gitlab\n      is_required: false\n      value_options:\n        - \"github\"\n        - \"gitlab\"\n\n  - github_token:\n    opts:\n        title: \"GitHub Token\"\n        summary: \"GitHub authentication token\"\n        description: |\n          GitHub personal access token or `$GITHUB_TOKEN` for authentication.\n          Required when using GitHub provider.\n        is_required: false\n        is_sensitive: true\n        is_expand: true\n\n  - gitlab_token:\n    opts:\n        title: \"GitLab Token\"\n        summary: \"GitLab authentication token\"\n        description: |\n          GitLab personal access token for authentication.\n          Required when using GitLab provider.\n        is_required: false\n        is_sensitive: true\n        is_expand: true\n\n  - gitlab_host:\n    opts:\n        title: \"GitLab Host\"\n        summary: \"GitLab instance hostname\"\n        description: |\n          GitLab instance hostname (e.g., gitlab.example.com).\n          Only needed for self-managed GitLab instances. Defaults to gitlab.com.\n        is_required: false\n"
  },
  {
    "path": "steps/badgetizr/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/beat-android-code-stats/0.0.2/step.yml",
    "content": "title: Android code stats\nsummary: |\n  Generates some Android project stats\ndescription: |\n  Generates some variables for Android project stats\nwebsite: https://github.com/luismunyoz/bitrise-step-beat-android-code-stats\nsource_code_url: https://github.com/luismunyoz/bitrise-step-beat-android-code-stats\nsupport_url: https://github.com/luismunyoz/bitrise-step-beat-android-code-stats/issues\npublished_at: 2021-02-15T09:32:24.642047+01:00\nsource:\n  git: https://github.com/luismunyoz/bitrise-step-beat-android-code-stats.git\n  commit: 66b93dc2032902bdf3babf70d0c8ca9e29f90602\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: cloc\n  apt_get:\n  - name: cloc\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: The root directory of your Android project. For example, where your\n      root build gradle file exist (also gradlew, settings.gradle, and so on)\n    is_required: true\n    summary: The root directory of your Android project.\n    title: Project Location\n  project_location: $BITRISE_PROJECT_PATH\noutputs:\n- KOTLIN_LINES_CODE: null\n  opts:\n    summary: Lines of code written in Kotlin\n    title: Kotlin lines of code\n- JAVA_LINES_CODE: null\n  opts:\n    summary: Lines of code written in Java\n    title: Java lines of code\n- XML_LINES_CODE: null\n  opts:\n    summary: Lines of code written in XML\n    title: XML lines of code\n- KOTLIN_PERCENTAGE_CODE: null\n  opts:\n    summary: Percentage of the code written in Kotlin\n    title: Kotlin percentage of code\n- JAVA_PERCENTAGE_CODE: null\n  opts:\n    summary: Percentage of the code written in Java\n    title: Java percentage of code\n- DOCUMENTATION_FILES: null\n  opts:\n    summary: Number of documentation files in the project\n    title: Documentation files\n- UNIT_TESTS_COUNT: null\n  opts:\n    summary: Number of unit tests in the project\n    title: Unit tests\n- UI_TESTS_COUNT: null\n  opts:\n    summary: Number of UI tests in the project\n    title: UI tests\n- MVP_PRESENTERS_COUNT: null\n  opts:\n    summary: Number of MVP Presenters in the project\n    title: MVP Presenters\n- VIEWMODEL_COUNT: null\n  opts:\n    summary: Number of ViewModels in the project\n    title: ViewModels\n"
  },
  {
    "path": "steps/beat-android-code-stats/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/0.0.10/step.yml",
    "content": "title: Bitbucket server post build status\nsummary: |\n  Post build status to bitbucket server\ndescription: |\n  Post build status to bitbucket server\nwebsite: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsource_code_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsupport_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/issues\npublished_at: 2020-04-16T14:38:44.138332+02:00\nsource:\n  git: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git\n  commit: e9c2699942f07972e16bc4c2ed6e24ad74849b2b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- domain: null\n  opts:\n    description: Full domain name without protocol eg 'my-domain.com'\n    is_required: true\n    summary: Full domain name without protocol eg 'my-domain.com'\n    title: Bitbucket Server domain name\n- opts:\n    description: The username used to make REST calls to bitbucket server\n    is_required: true\n    summary: The username used to make REST calls to bitbucket server\n    title: Bitbucket Server username\n  username: null\n- opts:\n    description: The password for the bitbucket server username\n    is_required: true\n    is_sensitive: true\n    summary: The password for the bitbucket server username\n    title: Bitbucket Server password\n  password: null\n- opts:\n    description: |-\n      If not set to `AUTO`, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of `AUTO`, `INPROGRESS`, `SUCCESSFUL`, or `FAILED`.\n\n      If you don't set this option, or select `AUTO`, the step will send `SUCCESSFUL` status if the current build status is `SUCCESSFUL`\n      (no step failed previously) and `FAILED` status if the build previously failed.\n\n      Use this to report `INPROGRESS` for builds that are just started.\n    summary: Override bitrise build status\n    title: Set Specific Status\n    value_options:\n    - AUTO\n    - INPROGRESS\n    - SUCCESSFUL\n    - FAILED\n  preset_status: AUTO\n- git_clone_commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    is_required: true\n    title: Git commit hash\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise app title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build number\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build url\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise triggered workflow id\n  triggered_workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/0.0.11/step.yml",
    "content": "title: Bitbucket server post build status\nsummary: |\n  Post build status to bitbucket server\ndescription: |\n  Post build status to bitbucket server\nwebsite: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsource_code_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsupport_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/issues\npublished_at: 2020-04-23T19:48:26.712315+02:00\nsource:\n  git: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git\n  commit: 8be387006477f130bc0e54c9cf1f95beb24bf542\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- domain: null\n  opts:\n    description: Full domain name without protocol eg 'my-domain.com'\n    is_required: true\n    summary: Full domain name without protocol eg 'my-domain.com'\n    title: Bitbucket Server domain name\n- opts:\n    description: The username used to make REST calls to bitbucket server\n    is_required: true\n    summary: The username used to make REST calls to bitbucket server\n    title: Bitbucket Server username\n  username: null\n- opts:\n    description: The password for the bitbucket server username\n    is_required: true\n    is_sensitive: true\n    summary: The password for the bitbucket server username\n    title: Bitbucket Server password\n  password: null\n- opts:\n    description: |-\n      If not set to `AUTO`, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of `AUTO`, `INPROGRESS`, `SUCCESSFUL`, or `FAILED`.\n\n      If you don't set this option, or select `AUTO`, the step will send `SUCCESSFUL` status if the current build status is `SUCCESSFUL`\n      (no step failed previously) and `FAILED` status if the build previously failed.\n\n      Use this to report `INPROGRESS` for builds that are just started.\n    summary: Override bitrise build status\n    title: Set Specific Status\n    value_options:\n    - AUTO\n    - INPROGRESS\n    - SUCCESSFUL\n    - FAILED\n  preset_status: AUTO\n- git_clone_commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    is_required: true\n    title: Git commit hash\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise app title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build number\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build url\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise triggered workflow id\n  triggered_workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/0.0.12/step.yml",
    "content": "title: Bitbucket server post build status\nsummary: |\n  Post build status to bitbucket server\ndescription: |\n  Post build status to bitbucket server\nwebsite: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsource_code_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsupport_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/issues\npublished_at: 2021-11-12T17:41:22.424761+01:00\nsource:\n  git: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git\n  commit: 1d7dd9fc055a80b976d89fdab9943b2c293d7387\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- domain: null\n  opts:\n    description: Full domain name without protocol eg 'my-domain.com'\n    is_required: true\n    summary: Full domain name without protocol eg 'my-domain.com'\n    title: Bitbucket Server domain name\n- opts:\n    description: The username used to make REST calls to bitbucket server\n    is_required: true\n    summary: The username used to make REST calls to bitbucket server\n    title: Bitbucket Server username\n  username: null\n- opts:\n    description: The password for the bitbucket server username\n    is_required: true\n    is_sensitive: true\n    summary: The password for the bitbucket server username\n    title: Bitbucket Server password\n  password: null\n- opts:\n    description: |-\n      If not set to `AUTO`, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of `AUTO`, `INPROGRESS`, `SUCCESSFUL`, or `FAILED`.\n\n      If you don't set this option, or select `AUTO`, the step will send `SUCCESSFUL` status if the current build status is `SUCCESSFUL`\n      (no step failed previously) and `FAILED` status if the build previously failed.\n\n      Use this to report `INPROGRESS` for builds that are just started.\n    summary: Override bitrise build status\n    title: Set Specific Status\n    value_options:\n    - AUTO\n    - INPROGRESS\n    - SUCCESSFUL\n    - FAILED\n  preset_status: AUTO\n- git_clone_commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    is_required: true\n    title: Git commit hash\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise app title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build number\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build url\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise triggered workflow id\n  triggered_workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/0.0.13/step.yml",
    "content": "title: Bitbucket server post build status\nsummary: |\n  Post build status to bitbucket server\ndescription: |\n  Post build status to bitbucket server\nwebsite: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsource_code_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsupport_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/issues\npublished_at: 2022-06-14T09:58:53.464212+02:00\nsource:\n  git: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git\n  commit: 08702dc3d799b8671b47078e328cb21518a8de4a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- domain: null\n  opts:\n    description: Full domain name without protocol eg 'my-domain.com'\n    is_required: true\n    summary: Full domain name without protocol eg 'my-domain.com'\n    title: Bitbucket Server domain name\n- opts:\n    description: The username used to make REST calls to bitbucket server\n    is_required: true\n    summary: The username used to make REST calls to bitbucket server\n    title: Bitbucket Server username\n  username: null\n- opts:\n    description: The password for the bitbucket server username\n    is_required: true\n    is_sensitive: true\n    summary: The password for the bitbucket server username\n    title: Bitbucket Server password\n  password: null\n- opts:\n    description: |-\n      If not set to `AUTO`, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of `AUTO`, `INPROGRESS`, `SUCCESSFUL`, or `FAILED`.\n\n      If you don't set this option, or select `AUTO`, the step will send `SUCCESSFUL` status if the current build status is `SUCCESSFUL`\n      (no step failed previously) and `FAILED` status if the build previously failed.\n\n      Use this to report `INPROGRESS` for builds that are just started.\n    summary: Override bitrise build status\n    title: Set Specific Status\n    value_options:\n    - AUTO\n    - INPROGRESS\n    - SUCCESSFUL\n    - FAILED\n  preset_status: AUTO\n- git_clone_commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    is_required: true\n    title: Git commit hash\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise app title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build number\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build url\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise triggered workflow id\n  triggered_workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/0.0.8/step.yml",
    "content": "title: Bitbucket server post build status\nsummary: |\n  Post build status to bitbucket server\ndescription: |\n  Post build status to bitbucket server\nwebsite: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsource_code_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsupport_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/issues\npublished_at: 2020-01-14T22:21:58.87928+01:00\nsource:\n  git: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git\n  commit: 09749b47e4aa02c41e36069be447370497253799\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- domain: null\n  opts:\n    description: Full domain name without protocol eg 'my-domain.com'\n    is_required: true\n    summary: Full domain name without protocol eg 'my-domain.com'\n    title: Bitbucket Server domain name\n- opts:\n    description: The username used to make REST calls to bitbucket server\n    is_required: true\n    summary: The username used to make REST calls to bitbucket server\n    title: Bitbucket Server username\n  username: null\n- opts:\n    description: The password for the bitbucket server username\n    is_required: true\n    is_sensitive: true\n    summary: The password for the bitbucket server username\n    title: Bitbucket Server password\n  password: null\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of `AUTO`, `INPROGRESS`, `SUCCESSFUL`, or `FAILED`.\n\n      If you don't set this option, or select `AUTO`, the step will send `SUCCESSFUL` status if the current build status is `SUCCESSFUL`\n      (no step failed previously) and `FAILED` status if the build previously failed.\n\n      Use this to report `INPROGRESS` for builds that are just started.\n    summary: Override bitrise build status\n    title: Set Specific Status\n    value_options:\n    - AUTO\n    - INPROGRESS\n    - SUCCESSFUL\n    - FAILED\n  preset_status: AUTO\n- git_clone_commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    is_required: true\n    title: Git commit hash\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise app title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build number\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build url\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise triggered workflow id\n  triggered_workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/0.0.9/step.yml",
    "content": "title: Bitbucket server post build status\nsummary: |\n  Post build status to bitbucket server\ndescription: |\n  Post build status to bitbucket server\nwebsite: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsource_code_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status\nsupport_url: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/issues\npublished_at: 2020-01-21T16:06:15.174176+01:00\nsource:\n  git: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git\n  commit: 5697327a4f8f8c975982659ee34fd06595fd79b2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- domain: null\n  opts:\n    description: Full domain name without protocol eg 'my-domain.com'\n    is_required: true\n    summary: Full domain name without protocol eg 'my-domain.com'\n    title: Bitbucket Server domain name\n- opts:\n    description: The username used to make REST calls to bitbucket server\n    is_required: true\n    summary: The username used to make REST calls to bitbucket server\n    title: Bitbucket Server username\n  username: null\n- opts:\n    description: The password for the bitbucket server username\n    is_required: true\n    is_sensitive: true\n    summary: The password for the bitbucket server username\n    title: Bitbucket Server password\n  password: null\n- opts:\n    description: |-\n      If not set to `AUTO`, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of `AUTO`, `INPROGRESS`, `SUCCESSFUL`, or `FAILED`.\n\n      If you don't set this option, or select `AUTO`, the step will send `SUCCESSFUL` status if the current build status is `SUCCESSFUL`\n      (no step failed previously) and `FAILED` status if the build previously failed.\n\n      Use this to report `INPROGRESS` for builds that are just started.\n    summary: Override bitrise build status\n    title: Set Specific Status\n    value_options:\n    - AUTO\n    - INPROGRESS\n    - SUCCESSFUL\n    - FAILED\n  preset_status: AUTO\n- git_clone_commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git commit hash\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise app title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build number\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise build url\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Bitrise triggered workflow id\n  triggered_workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n"
  },
  {
    "path": "steps/bitbucket-server-post-build-status/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitbucket-snippet-runner/0.1.0/step.yml",
    "content": "title: Bitbucket Snippet Runner\nsummary: \"Found a great Bitbucket Snippet that you'd like to use during your workflow?\n  \\ \\nJust add the raw URL, Bitrise will download it and run it as a bash script!\\n\"\ndescription: \"Downloads the content of the input url and runs it as a bash script.\n  \\ \\nFor example you can provide a Bitbucket Snippet url.\\n\"\nwebsite: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsource_code_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsupport_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner/issues\npublished_at: 2017-09-01T14:52:03.922219085+01:00\nsource:\n  git: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner.git\n  commit: 7ff971e9c97760d99340d839b6aafe55632cb1c7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The snippet to run can be private or public, hosted on cloud or server based Bitbucket accounts\n    is_expand: true\n    is_required: true\n    summary: |\n      The Bitbucket url of the snippet to run\n\n      https://bitbucket.org/snippets/<username|team>/<encoded_id>\n\n      Example: https://bitbucket.org/snippets/waracle/xLMA9q\n    title: Snippet URL\n    value_options: []\n  script_url: null\n- opts:\n    is_required: false\n    summary: The Bitbucket username to access the snippet with.\n    title: Username\n  username: $BITBUCKET_USERNAME\n- opts:\n    is_required: false\n    summary: The password (or *app* password if 2FA is enabled) for the user to authenticate\n      against.\n    title: Password\n  password: $BITBUCKET_PASSWORD\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bitbucket-snippet-runner/1.0.0/step.yml",
    "content": "title: Bitbucket Snippet Runner\nsummary: \"Found a great Bitbucket Snippet that you'd like to use during your workflow?\n  \\ \\nJust add the raw URL, Bitrise will download it and run it as a bash script!\\n\"\ndescription: \"Downloads the content of the input url and runs it as a bash script.\n  \\ \\nFor example you can provide a Bitbucket Snippet url.\\n\"\nwebsite: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsource_code_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsupport_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner/issues\npublished_at: 2017-09-19T16:09:14.899480353+01:00\nsource:\n  git: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner.git\n  commit: f724a9eea9ea72cdb312ec94a49f6e5a982326ac\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The snippet to run can be private or public, hosted on cloud or server based Bitbucket accounts\n    is_expand: true\n    is_required: true\n    summary: |\n      The Bitbucket url of the snippet to run\n\n      https://bitbucket.org/snippets/<username|team>/<encoded_id>\n\n      Example: https://bitbucket.org/snippets/waracle/xLMA9q\n    title: Snippet URL\n    value_options: []\n  script_url: null\n- opts:\n    is_required: false\n    summary: The Bitbucket username to access the snippet with.\n    title: Username\n  username: $BITBUCKET_USERNAME\n- opts:\n    is_required: false\n    summary: The password (or *app* password if 2FA is enabled) for the user to authenticate\n      against.\n    title: Password\n  password: $BITBUCKET_PASSWORD\n- opts:\n    category: Config\n    description: \"This directory will be set as the current working\\ndirectory for\n      the script.\\nAny relative path in the Script (content) will be\\nrelative to\n      this directory.   \\n\"\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bitbucket-snippet-runner/1.1.0/step.yml",
    "content": "title: Bitbucket Snippet Runner\nsummary: \"Found a great Bitbucket Snippet that you'd like to use during your workflow?\n  \\ \\nJust add the raw URL, Bitrise will download it and run it as a bash script!\\n\"\ndescription: \"Downloads the content of the input url and runs it as a bash script.\n  \\ \\nFor example you can provide a Bitbucket Snippet url.\\n\"\nwebsite: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsource_code_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsupport_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner/issues\npublished_at: 2017-09-22T11:26:38.593604819+01:00\nsource:\n  git: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner.git\n  commit: 8a58ce63f187ea75ca71691a8e75c13ddf0100d3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    category: Config\n    description: |\n      The snippet to run can be private or public, hosted on cloud or server based Bitbucket accounts\n    is_expand: true\n    is_required: true\n    summary: |\n      The Bitbucket url of the snippet to run\n\n      https://bitbucket.org/snippets/<username|team>/<encoded_id>\n\n      Example: https://bitbucket.org/snippets/waracle/xLMA9q\n    title: Snippet URL\n    value_options: []\n  script_url: null\n- opts:\n    category: Config\n    is_required: false\n    summary: The Bitbucket username to access the snippet with.\n    title: Username\n  username: $BITBUCKET_USERNAME\n- opts:\n    category: Config\n    is_required: false\n    summary: The password (or *app* password if 2FA is enabled) for the user to authenticate\n      against.\n    title: Password\n  password: $BITBUCKET_PASSWORD\n- opts:\n    category: Config\n    description: \"This directory will be set as the current working\\ndirectory for\n      the script.\\nAny relative path in the Script (content) will be\\nrelative to\n      this directory. \\n\"\n    is_required: false\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Allows passing of arguments to be passed\n      into the downloaded script\n    is_required: false\n    title: Script Arguments\n  script_args: null\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bitbucket-snippet-runner/1.1.1/step.yml",
    "content": "title: Bitbucket Snippet Runner\nsummary: \"Found a great Bitbucket Snippet that you'd like to use during your workflow?\n  \\ \\nJust add the raw URL, Bitrise will download it and run it as a bash script!\\n\"\ndescription: \"Downloads the content of the input url and runs it as a bash script.\n  \\ \\nFor example you can provide a Bitbucket Snippet url.\\n\"\nwebsite: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsource_code_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsupport_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner/issues\npublished_at: 2018-01-26T14:07:48.711174Z\nsource:\n  git: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner.git\n  commit: ddeebb540610bbfb0e3c8f55a781102eb2194145\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    category: Config\n    description: |\n      The snippet to run can be private or public, hosted on cloud or server based Bitbucket accounts\n    is_expand: true\n    is_required: true\n    summary: |\n      The Bitbucket url of the snippet to run\n\n      https://bitbucket.org/snippets/<username|team>/<encoded_id>\n\n      Example: https://bitbucket.org/snippets/waracle/xLMA9q\n    title: Snippet URL\n    value_options: []\n  script_url: null\n- opts:\n    category: Config\n    is_required: false\n    summary: The Bitbucket username to access the snippet with.\n    title: Username\n  username: $BITBUCKET_USERNAME\n- opts:\n    category: Config\n    is_required: false\n    summary: The password (or *app* password if 2FA is enabled) for the user to authenticate\n      against.\n    title: Password\n  password: $BITBUCKET_PASSWORD\n- opts:\n    category: Config\n    description: \"This directory will be set as the current working\\ndirectory for\n      the script.\\nAny relative path in the Script (content) will be\\nrelative to\n      this directory. \\n\"\n    is_required: false\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Allows passing of arguments to be passed\n      into the downloaded script\n    is_required: false\n    title: Script Arguments\n  script_args: null\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bitbucket-snippet-runner/1.2.0/step.yml",
    "content": "title: Bitbucket Snippet Runner\nsummary: \"Found a great Bitbucket Snippet that you'd like to use during your workflow?\n  \\ \\nJust add the raw URL, Bitrise will download it and run it as a bash script!\\n\"\ndescription: \"Downloads the content of the input url and runs it as a bash script.\n  \\ \\nFor example you can provide a Bitbucket Snippet url.\\n\"\nwebsite: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsource_code_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner\nsupport_url: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner/issues\npublished_at: 2018-02-26T16:04:46.489891Z\nsource:\n  git: https://github.com/waracle/bitrise-step-bitbucket-snippet-runner.git\n  commit: e8dedef3bbf75247a9f69c4fe6526003ebc671c2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    category: Config\n    description: |\n      The snippet to run can be private or public, hosted on cloud or server based Bitbucket accounts\n    is_expand: true\n    is_required: true\n    summary: |\n      The Bitbucket url of the snippet to run\n\n      https://bitbucket.org/snippets/<username|team>/<encoded_id>\n\n      Example: https://bitbucket.org/snippets/waracle/xLMA9q\n    title: Snippet URL\n    value_options: []\n  script_url: null\n- opts:\n    category: Config\n    is_required: false\n    summary: The Bitbucket username to access the snippet with.\n    title: Username\n  username: $BITBUCKET_USERNAME\n- opts:\n    category: Config\n    is_required: false\n    summary: The password (or *app* password if 2FA is enabled) for the user to authenticate\n      against.\n    title: Password\n  password: $BITBUCKET_PASSWORD\n- opts:\n    category: Config\n    description: \"This directory will be set as the current working\\ndirectory for\n      the script.\\nAny relative path in the Script (content) will be\\nrelative to\n      this directory. \\n\"\n    is_required: false\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Allows passing of arguments to be passed\n      into the downloaded script\n    is_required: false\n    title: Script Arguments\n  script_args: null\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bitbucket-snippet-runner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-aws-device-farm-runner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-run/0.9.0/step.yml",
    "content": "title: Bitrise Run\nsummary: Runs a specified workflow from the given bitrise.yml\ndescription: Runs a specified workflow from the given bitrise.yml\nwebsite: https://github.com/bitrise-steplib/step-bitrise-run\nsource_code_url: https://github.com/bitrise-steplib/step-bitrise-run\nsupport_url: https://github.com/bitrise-steplib/step-bitrise-run/issues\npublished_at: 2017-10-11T12:12:42.175939663+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-bitrise-run.git\n  commit: b7c9611bbaf953498cc49714bcca51cd6f6d7073\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: ID (name) of the Bitrise workflow to run\n    is_expand: true\n    is_required: true\n    summary: ID (name) of the Bitrise workflow to run\n    title: Workflow ID\n  workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n- bitrise_config_path: ./bitrise.yml\n  opts:\n    description: The Bitrise configuration (bitrise.yml) file path\n    is_expand: true\n    is_required: true\n    summary: The Bitrise configuration (bitrise.yml) file path\n    title: bitrise.yml path\n"
  },
  {
    "path": "steps/bitrise-run/0.9.1/step.yml",
    "content": "title: Bitrise Run\nsummary: Runs a specified workflow from the given bitrise.yml\ndescription: Runs a specified workflow from the given bitrise.yml\nwebsite: https://github.com/bitrise-steplib/steps-bitrise-run\nsource_code_url: https://github.com/bitrise-steplib/steps-bitrise-run\nsupport_url: https://github.com/bitrise-steplib/steps-bitrise-run/issues\npublished_at: 2018-02-07T13:08:39.32139366+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-bitrise-run.git\n  commit: 03ff77b448d7482f8c201853ee1256fb38f6647a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: ID (name) of the Bitrise workflow to run\n    is_expand: true\n    is_required: true\n    summary: ID (name) of the Bitrise workflow to run\n    title: Workflow ID\n  workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n- bitrise_config_path: ./bitrise.yml\n  opts:\n    description: The Bitrise configuration (bitrise.yml) file path\n    is_expand: true\n    is_required: true\n    summary: The Bitrise configuration (bitrise.yml) file path\n    title: bitrise.yml path\n"
  },
  {
    "path": "steps/bitrise-run/0.9.2/step.yml",
    "content": "title: Bitrise Run\nsummary: Runs a specified Workflow from the `bitrise.yml` file.\ndescription: |-\n  This Step runs a specified Workflow from the targeted `bitrise.yml` file.\n\n  ### Configuring the Step\n\n  1. Set the **Workflow ID** input. It uses the `$BITRISE_TRIGGERED_WORKFLOW_ID` Environment Variable (Env Var) by default. This Env Var is automatically set to the Workflow that triggered the build.\n  2. Set the **bitrise.yml path**. It's populated with `./bitrise.yml` path by default.\n\n  ### Troubleshooting\n  Please make sure that you select an existing Workflow ID.\n  Please make sure that you set a correct and existing `bitrise.yml` file path.\n\n  ### Related Steps\n  - [Bitrise Start Build](https://www.bitrise.io/integrations/steps/build-router-start)\n  - [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-wait)\nwebsite: https://github.com/bitrise-steplib/steps-bitrise-run\nsource_code_url: https://github.com/bitrise-steplib/steps-bitrise-run\nsupport_url: https://github.com/bitrise-steplib/steps-bitrise-run/issues\npublished_at: 2021-10-18T11:29:28.044384891Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-bitrise-run.git\n  commit: 11504e76c3af7f0677e0ad1fa42ed8df0e013eeb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      ID (name) of the workflow to run.\n\n      It must exist in the bitrise.yml file.\n    is_expand: true\n    is_required: true\n    summary: ID (name) of the workflow to run.\n    title: Workflow ID\n  workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n- bitrise_config_path: ./bitrise.yml\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The Bitrise configuration (bitrise.yml) file path.\n    title: bitrise.yml path\n"
  },
  {
    "path": "steps/bitrise-run/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/bitrise-snyk-scan/0.1.0/step.yml",
    "content": "title: Bitrise Snyk scan\nsummary: |\n  This is a step to run snyk SAST and dependencies scanning for mobile apps\ndescription: |\n  This is a step to run snyk SAST and dependencies scanning for mobile apps\nwebsite: https://github.com/Zegocover/bitrise-snyk-scan\nsource_code_url: https://github.com/Zegocover/bitrise-snyk-scan\nsupport_url: https://github.com/Zegocover/bitrise-snyk-scan/issues\npublished_at: 2022-11-15T12:27:15.382324Z\nsource:\n  git: https://github.com/Zegocover/bitrise-snyk-scan.git\n  commit: de3b281aea40136b79b0b04260d4d5b0f66ca8b3\ntype_tags:\n- test\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: false\n    is_required: true\n    title: Project's OS\n    value_options:\n    - \"ios\"\n    - \"android\"\n  os_list: ios\n- opts:\n    is_expand: false\n    is_required: true\n    summary: Severity threshold (cannot be set to critical - not supported by 'snyk\n      code'\n    title: Severity threshold\n    value_options:\n    - \"low\"\n    - \"medium\"\n    - \"high\"\n  severity_threshold: low\n- opts:\n    is_expand: false\n    is_required: true\n    summary: Organisation name used to configure snyk organisation setting\n    title: Organisation name\n  org_name: null\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Snyk authentication token\n  snyk_auth_token: $SNYK_AUTH_TOKEN\n- js_scan: false\n  opts:\n    is_expand: false\n    is_required: false\n    title: Project is using javascript\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/bitrise-snyk-scan/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-appdome-build-2secure-ios/1.0.2/step.yml",
    "content": "title: Appdome-Build-2Secure step for iOS\nsummary: |\n  Builds an iOS mobile app using Appdome's platform\ndescription: |\n  Integration that allows activating security and app protection features, bulding and signing mobile apps using Appdome's API. For detailes see: https://www.appdome.com/how-to/appsec-release-orchestration/mobile-appsec-cicd/use-appdome-build-2secure-step-for-bitrise\nwebsite: https://github.com/Appdome/bitrise_build-2secure-ios\nsource_code_url: https://github.com/Appdome/bitrise_build-2secure-ios\nsupport_url: https://github.com/Appdome/bitrise_build-2secure-ios/issues\npublished_at: 2023-04-23T10:59:00.488173+03:00\nsource:\n  git: https://github.com/Appdome/bitrise-step-appdome-build-2secure-ios.git\n  commit: 8c31b1530cc5ee7c7bfe5e6e50918a1bd38d4a61\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- app_location: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    summary: URL to app file\n    title: App file URL\n- fusion_set_id: null\n  opts:\n    is_required: true\n    title: Fusion set ID\n- opts:\n    is_required: false\n    title: Team ID\n  team_id: null\n- opts:\n    description: App signing method\n    is_required: true\n    title: Signing Method\n    value_options:\n    - On-Appdome\n    - Private-Signing\n    - Auto-Dev-Signing\n  sign_method: On-Appdome\n- entitlements: null\n  opts:\n    description: iOS Entitlement EnvVar/s (separated by space)\n    is_required: true\n    title: iOS Entitlement EnvVar/s\n"
  },
  {
    "path": "steps/bitrise-step-appdome-build-2secure-ios/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2023-06-11\"\ndeprecate_notes: |\n  This step is deprecated as it was replaced by appdome-build-2secure-ios, and it is no longer maintained.\n"
  },
  {
    "path": "steps/bitrise-step-appledoc/1.0.2/step.yml",
    "content": "title: Appledoc\nsummary: This step allows the creation of apple docs\ndescription: This step allows the creation of apple docs HTML files from a template,\n  and code comments.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-appledoc\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-appledoc\npublished_at: 2019-08-22T16:13:29.664503+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-appledoc.git\n  commit: abbf9fd315669905a205afc70d8f7fc67651f278\nhost_os_tags:\n- osx-10.14\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- utility\ndeps: {}\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Documentation will be generated for the source files found at this\n      location.\n    is_expand: true\n    is_required: true\n    summary: The path to the directory containing the source files to process.\n    title: Source files\n    value_options: []\n  source_path: \"\"\n- appledoc_conf: config.plist\n  opts:\n    description: This file contains all the necessary configuration to run appledoc.\n    is_expand: true\n    is_required: true\n    summary: The configuration file of appledoc.\n    title: Appledoc configuration plist\n    value_options: []\n- opts:\n    description: The readme will be included as the landing page of the docs.\n    is_expand: true\n    is_required: true\n    summary: The path to a README.md to include in the docs.\n    title: Readme path\n    value_options: []\n  readme_path: \"\"\n- opts:\n    description: This archive contains the generated appledocs.\n    is_expand: true\n    is_required: true\n    summary: The filepath of the final zip archive.\n    title: Output file\n    value_options: []\n  output_file: docs.zip\n"
  },
  {
    "path": "steps/bitrise-step-appledoc/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-eschecker/0.0.1/step.yml",
    "content": "title: esChecker, by eShard\nsummary: |\n  Run Mobile Application Security Testing using esChecker\ndescription: |\n  Run esChecker analyses on new application builds directly from Bitrise.\nwebsite: https://github.com/eshard/bitrise-step-eschecker\nsource_code_url: https://github.com/eshard/bitrise-step-eschecker\nsupport_url: https://github.com/eshard/bitrise-step-eschecker/issues\npublished_at: 2022-12-07T17:37:01.44587+01:00\nsource:\n  git: https://github.com/eshard/bitrise-step-eschecker.git\n  commit: cfa105125ac67168579a86f39b013e1bd195110b\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- opts:\n    description: |\n      Path to the binary file to be tested\n    is_required: true\n    summary: The app file you want to test.\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- eschecker_token: null\n  opts:\n    description: |\n      esChecker token generated from esChecker UI.\n    is_required: true\n    is_sensitive: true\n    summary: Your esChecker API token, get it from https://eschecker.eshard.com/rest-api\n    title: esChecker API token\n- eschecker_app_id: null\n  opts:\n    description: |\n      Application ID in esChecker\n    is_required: true\n    summary: Unique ID of your application in esChecker, get it from the `App Information`\n      tab of the app\n    title: Application ID\n- eschecker_campaign_id: null\n  opts:\n    description: |\n      Campaign ID in esChecker\n    is_required: true\n    summary: Unique ID of the campaign you can to run in esChecker\n    title: Campaign ID\noutputs:\n- eschecker_pdf_report: null\n  opts:\n    description: |\n      PDF export of the esChecker report.\n    summary: Contains all relevant information oo an esChecker Campaign.\n    title: esChecker report PDF\n"
  },
  {
    "path": "steps/bitrise-step-eschecker/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-export-universal-apk/0.1.1/step.yml",
    "content": "title: Export Universal APK\nsummary: |\n  Exports a universal APK from an Android App Bundle.\ndescription: |\n  This Step generates a universal APK from an Android App Bundle, and exports it to the `$BITRISE_APK_PATH` Environment Variable so that the next Step or [Ship add-on](https://devcenter.bitrise.io/deploy/ship/) can pick it up. The Step also signs the generated APK with the keystore file you uploaded to the [Code Signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/) tab or, if there was no keystore available, it signs the APK with a debug keystore file.\n\n  ### Configuring the Step\n  1. Insert the Step after a build Step in your Workflow.\n  2. The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step.\n  3. The **Keystore URL** is automatically filled out based on the uploaded keystore file on the **Code Signing** tab.\n  4. If the keystore file is uploaded to the **Code Signing** tab, the **Keystore alias**, **Keystore password**, and **Private key password** inputs are automatically populated.\n  5. The latest Bundletool version is set in the respective input. If, for any reason, you wish to use an older version, you can add it here, but make sure you use the [correct version](https://github.com/google/bundletool/releases).\n\n  ### Troubleshooting\n  This Step works with Bundletool's latest version which is automatically set in the respective Step input. If you wish to switch to an older version, you have to add it manually. Make sure you add the [correct version](https://github.com/google/bundletool/releases), otherwise the Step will fail.\n\n  ### Useful links\n  - [Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n  - [Deploying and Android app](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk/issues\npublished_at: 2020-07-29T12:34:47.2133096Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk.git\n  commit: a582681d23d651a5947f0c150c802872b289ad58\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-export-universal-apk\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |\n      The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step\n    is_expand: true\n    is_required: true\n    summary: Android App Bundle file (`.aab`) path\n    title: Android App Bundle path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: The keystore file's URL which is generated when you upload the file to\n      the Code Signing tab.\n    title: Keystore URL\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: The password you added to the keystore.\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: Identifier name you added to the keystore.\n    title: Keystore alias\n- opts:\n    description: null\n    is_sensitive: true\n    summary: Password you added to the private key.\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- bundletool_version: 1.0.0\n  opts:\n    description: If you wish to set a specific version, add it here based on [Bundletool's\n      official release](https://github.com/google/bundletool/releases) page.\n    is_expand: true\n    summary: You can override this Bundletool version if you need a specific one.\n    title: Bundletool version\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: \"\"\n    summary: The APK is exported to this output Environment Variable and can be picked\n      up by the next Step or Ship.\n    title: The exported APK's path\n"
  },
  {
    "path": "steps/bitrise-step-export-universal-apk/0.1.2/step.yml",
    "content": "title: Export Universal APK\nsummary: |\n  Exports a universal APK from an Android App Bundle.\ndescription: |\n  This Step generates a universal APK from an Android App Bundle, and exports it to the `$BITRISE_APK_PATH` Environment Variable so that the next Step or [Ship add-on](https://devcenter.bitrise.io/deploy/ship/) can pick it up. The Step also signs the generated APK with the keystore file you uploaded to the [Code Signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/) tab or, if there was no keystore available, it signs the APK with a debug keystore file.\n\n  ### Configuring the Step\n  1. Insert the Step after a build Step in your Workflow.\n  2. The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step.\n  3. The **Keystore URL** is automatically filled out based on the uploaded keystore file on the **Code Signing** tab.\n  4. If the keystore file is uploaded to the **Code Signing** tab, the **Keystore alias**, **Keystore password**, and **Private key password** inputs are automatically populated.\n  5. The latest Bundletool version is set in the respective input. If, for any reason, you wish to use an older version, you can add it here, but make sure you use the [correct version](https://github.com/google/bundletool/releases).\n\n  ### Troubleshooting\n  This Step works with Bundletool's latest version which is automatically set in the respective Step input. If you wish to switch to an older version, you have to add it manually. Make sure you add the [correct version](https://github.com/google/bundletool/releases), otherwise the Step will fail.\n\n  ### Useful links\n  - [Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n  - [Deploying and Android app](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk/issues\npublished_at: 2021-10-05T07:38:36.616905339Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk.git\n  commit: 51999c4a8dba345a80f4847cd2e7438d3cc07906\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-export-universal-apk\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |\n      The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step\n    is_expand: true\n    is_required: true\n    summary: Android App Bundle file (`.aab`) path\n    title: Android App Bundle path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: The keystore file's URL which is generated when you upload the file to\n      the Code Signing tab.\n    title: Keystore URL\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: The password you added to the keystore.\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: Identifier name you added to the keystore.\n    title: Keystore alias\n- opts:\n    description: null\n    is_sensitive: true\n    summary: Password you added to the private key.\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- bundletool_version: 1.8.1\n  opts:\n    description: If you wish to set a specific version, add it here based on [Bundletool's\n      official release](https://github.com/google/bundletool/releases) page.\n    is_expand: true\n    summary: You can override this Bundletool version if you need a specific one.\n    title: Bundletool version\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: \"\"\n    summary: The APK is exported to this output Environment Variable and can be picked\n      up by the next Step or Ship.\n    title: The exported APK's path\n"
  },
  {
    "path": "steps/bitrise-step-export-universal-apk/0.1.3/step.yml",
    "content": "title: Export Universal APK\nsummary: |\n  Exports a universal APK from an Android App Bundle.\ndescription: |\n  This Step generates a universal APK from an Android App Bundle, and exports it to the `$BITRISE_APK_PATH` Environment Variable so that the next Step or [Ship add-on](https://devcenter.bitrise.io/deploy/ship/) can pick it up. The Step also signs the generated APK with the keystore file you uploaded to the [Code Signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/) tab or, if there was no keystore available, it signs the APK with a debug keystore file.\n\n  ### Configuring the Step\n  1. Insert the Step after a build Step in your Workflow.\n  2. The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step.\n  3. The **Keystore URL** is automatically filled out based on the uploaded keystore file on the **Code Signing** tab.\n  4. If the keystore file is uploaded to the **Code Signing** tab, the **Keystore alias**, **Keystore password**, and **Private key password** inputs are automatically populated.\n  5. The latest Bundletool version is set in the respective input. If, for any reason, you wish to use an older version, you can add it here, but make sure you use the [correct version](https://github.com/google/bundletool/releases).\n\n  ### Troubleshooting\n  This Step works with Bundletool's latest version which is automatically set in the respective Step input. If you wish to switch to an older version, you have to add it manually. Make sure you add the [correct version](https://github.com/google/bundletool/releases), otherwise the Step will fail.\n\n  ### Useful links\n  - [Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n  - [Deploying and Android app](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk/issues\npublished_at: 2023-08-28T09:42:39.845366736Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk.git\n  commit: 5455537f21c4acd90ee60628f89156211aecea3a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-export-universal-apk\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |\n      The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step\n    is_expand: true\n    is_required: true\n    summary: Android App Bundle file (`.aab`) path\n    title: Android App Bundle path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: The keystore file's URL which is generated when you upload the file to\n      the Code Signing tab.\n    title: Keystore URL\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: The password you added to the keystore.\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: Identifier name you added to the keystore.\n    title: Keystore alias\n- opts:\n    description: null\n    is_sensitive: true\n    summary: Password you added to the private key.\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- bundletool_version: 1.8.1\n  opts:\n    description: If you wish to set a specific version, add it here based on [Bundletool's\n      official release](https://github.com/google/bundletool/releases) page.\n    is_expand: true\n    summary: You can override this Bundletool version if you need a specific one.\n    title: Bundletool version\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: \"\"\n    summary: The APK is exported to this output Environment Variable and can be picked\n      up by the next Step or Ship.\n    title: The exported APK's path\n"
  },
  {
    "path": "steps/bitrise-step-export-universal-apk/0.1.4/step.yml",
    "content": "title: Export Universal APK\nsummary: |\n  Exports a universal APK from an Android App Bundle.\ndescription: |\n  This Step generates a universal APK from an Android App Bundle, and exports it to the `$BITRISE_APK_PATH` Environment Variable so that the next Step or [Ship add-on](https://devcenter.bitrise.io/deploy/ship/) can pick it up. The Step also signs the generated APK with the keystore file you uploaded to the [Code Signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/) tab or, if there was no keystore available, it signs the APK with a debug keystore file.\n\n  ### Configuring the Step\n  1. Insert the Step after a build Step in your Workflow.\n  2. The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step.\n  3. The **Keystore URL** is automatically filled out based on the uploaded keystore file on the **Code Signing** tab.\n  4. If the keystore file is uploaded to the **Code Signing** tab, the **Keystore alias**, **Keystore password**, and **Private key password** inputs are automatically populated.\n  5. The latest Bundletool version is set in the respective input. If, for any reason, you wish to use an older version, you can add it here, but make sure you use the [correct version](https://github.com/google/bundletool/releases).\n\n  ### Troubleshooting\n  This Step works with Bundletool's latest version which is automatically set in the respective Step input. If you wish to switch to an older version, you have to add it manually. Make sure you add the [correct version](https://github.com/google/bundletool/releases), otherwise the Step will fail.\n\n  ### Useful links\n  - [Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-index/)\n  - [Deploying and Android app](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk/issues\npublished_at: 2025-11-14T13:13:39.701980048Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-export-universal-apk.git\n  commit: 17ff53debcf18029defefe113008c904d3551281\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-export-universal-apk\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: The **Android App Bundle path** input field is automatically filled\n      out by the output of the previous build Step\n    is_expand: true\n    is_required: true\n    summary: Android App Bundle file (`.aab`) path\n    title: Android App Bundle path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: The keystore file's URL which is generated when you upload the file to\n      the Code Signing tab.\n    title: Keystore URL\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: The password you added to the keystore.\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Identifier name you added to the keystore.\n    title: Keystore alias\n- opts:\n    is_sensitive: true\n    summary: Password you added to the private key.\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- bundletool_version: 1.8.1\n  opts:\n    description: If you wish to set a specific version, add it here based on [Bundletool's\n      official release](https://github.com/google/bundletool/releases) page.\n    is_expand: true\n    summary: You can override this Bundletool version if you need a specific one.\n    title: Bundletool version\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    summary: The APK is exported to this output Environment Variable and can be picked\n      up by the next Step or Ship.\n    title: The exported APK's path\n"
  },
  {
    "path": "steps/bitrise-step-export-universal-apk/step-info.yml",
    "content": "maintainer: bitrise"
  },
  {
    "path": "steps/bitrise-step-icon-overlay/1.0.1/step.yml",
    "content": "title: Icon overlay\nsummary: This step allow to print any text on top of the app's icon in order to distinguish\n  different builds\ndescription: \"\"\nwebsite: https://github.com/FutureWorkshops/bitrise-step-icon-overlay\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-icon-overlay\npublished_at: 2019-08-22T17:10:52.188049+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-icon-overlay.git\n  commit: eafd98b021fe857821bcd4294972df686ed9353c\nhost_os_tags:\n- osx-10.14\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: imagemagick\n  apt_get:\n  - name: imagemagick\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- iconsbundle_name: AppIcon.appiconset\n  opts:\n    description: The name of the appiconset file including the extension '.appiconset'\n    is_expand: true\n    is_required: true\n    summary: The name of the appiconset file inside the xcasset.\n    title: Icon bundle name\n- opts:\n    description: Folder where the project and the asset files are stored in the repository.\n    is_expand: true\n    is_required: true\n    summary: Folder where the project and the asset files are stored in the repository.\n    title: Project Location\n  project_location: .\n- opts:\n    description: The first six characters of this text will be displayed at the bottom\n      on top of the app's icon image\n    is_expand: true\n    is_required: true\n    summary: The text to print over the app icon (6 characters maximum).\n    title: Overlay text\n  overlay_text: $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/bitrise-step-icon-overlay/2.0.0/step.yml",
    "content": "title: Icon overlay\nsummary: This step allow to print any text on top of the app's icon in order to distinguish\n  different builds\ndescription: \"\"\nwebsite: https://github.com/OhMyApp/bitrise-step-icon-overlay\nsource_code_url: https://github.com/OhMyApp/bitrise-step-icon-overlay\nsupport_url: https://github.com/OhMyApp/bitrise-step-icon-overlay/issues\npublished_at: 2026-04-12T16:07:47.648173+02:00\nsource:\n  git: https://github.com/OhMyApp/bitrise-step-icon-overlay.git\n  commit: 024993fe55cf9b6ade979f821a47ff551a7d8ba2\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: imagemagick\n  apt_get:\n  - name: imagemagick\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- iconsbundle_name: AppIcon.appiconset\n  opts:\n    description: The name of the appiconset file including the extension '.appiconset'\n    is_expand: true\n    is_required: true\n    summary: The name of the appiconset file inside the xcasset.\n    title: Icon bundle name\n- opts:\n    description: Folder where the project and the asset files are stored in the repository.\n    is_expand: true\n    is_required: true\n    summary: Folder where the project and the asset files are stored in the repository.\n    title: Project Location\n  project_location: .\n- opts:\n    description: The first six characters of this text will be displayed at the bottom\n      on top of the app's icon image\n    is_expand: true\n    is_required: true\n    summary: The text to print over the app icon (6 characters maximum).\n    title: Overlay text\n  overlay_text: $BITRISE_GIT_COMMIT\n- font: /System/Library/Fonts/Supplemental/Arial.ttf\n  opts:\n    description: Arial by default.\n    is_expand: true\n    is_required: false\n    summary: The font used for the text.\n    title: Font\n"
  },
  {
    "path": "steps/bitrise-step-icon-overlay/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-ionic-build/0.0.1/step.yml",
    "content": "title: Ionic Build\nsummary: |\n  The Step runs ionic build with the arguments you provide.\ndescription: |\n  The Step runs ionic build with the arguments you provide.\nwebsite: https://github.com/non-binary/bitrise-step-ionic-build\nsource_code_url: https://github.com/non-binary/bitrise-step-ionic-build\nsupport_url: https://github.com/non-binary/bitrise-step-ionic-build/issues\npublished_at: 2020-06-05T18:31:09.731777-04:00\nsource:\n  git: https://github.com/non-binary/bitrise-step-ionic-build.git\n  commit: 8621bfc85a5419c3169cc2c29b6baad8731a06c5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Set to yes if you want `--prod` to be used.\n    is_expand: true\n    is_required: true\n    summary: To use the production configuration.\n    title: Production Configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n  production_mode: \"no\"\n- options: \"\"\n  opts:\n    description: |\n      You can pass additional options to this command to customize your build (just the flag).\n      Flags that are available can be found here: https://ionicframework.com/docs/cli/commands/build#advanced-options.\n    is_expand: true\n    is_required: false\n    summary: To optionally use advanced options flags.\n    title: Options\n"
  },
  {
    "path": "steps/bitrise-step-ionic-build/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-multikey-restore-cache/0.1.0/step.yml",
    "content": "title: Multikey Restore Cache\nsummary: Restores build cache using a cache keys. This Step needs to be used in combination\n  with **Multikey Save Cache** or **Save Cache**.\ndescription: |\n  Restores items from the cache based on a list of keys.\n\n  The format of the keys input is the following:\n  ```\n  KEY1 || KEY1_ALTERNATIVE1 || KEY1_ALTERNATIVE2\n  KEY2\n  KEY3 || KEY3_ALTERNATIVE1\n  ```\n  The number of keys and paths for each are limited to a number of 10. Commas (`,`) and equal signs (`=`) are not allowed in keys. See templates that can be used in the keys below.\n\n  Example (somewhat artificial):\n  ```\n  multikey_0 || multikey_0_fallback\n  multikey_1\n  multikey_2 || multikey_2_fallback\n  ```\n\n  This Step needs to be used in combination with **Multikey Save Cache** or **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Multikey Restore Cache** step downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional alternative keys by appending them with `||` in the same line as the key. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      multikey_0 || multikey_0_fallback\n      multikey\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2025-08-05T14:48:22.923282+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache.git\n  commit: 246caa5e66015b3d5dbc08dd224bc290c2cbb0d8\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- keys: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/bitrise-step-multikey-restore-cache/0.1.1/step.yml",
    "content": "title: Multikey Restore Cache\nsummary: Restores build cache using a cache keys. This Step needs to be used in combination\n  with **Multikey Save Cache** or **Save Cache**.\ndescription: |\n  Restores items from the cache based on a list of keys.\n\n  The format of the keys input is the following:\n  ```\n  KEY1 || KEY1_ALTERNATIVE1 || KEY1_ALTERNATIVE2\n  KEY2\n  KEY3 || KEY3_ALTERNATIVE1\n  ```\n  The number of keys and paths for each are limited to a number of 10. Commas (`,`) and equal signs (`=`) are not allowed in keys. See templates that can be used in the keys below.\n\n  Example (somewhat artificial):\n  ```\n  multikey_0 || multikey_0_fallback\n  multikey_1\n  multikey_2 || multikey_2_fallback\n  ```\n\n  This Step needs to be used in combination with **Multikey Save Cache** or **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Multikey Restore Cache** step downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional alternative keys by appending them with `||` in the same line as the key. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      multikey_0 || multikey_0_fallback\n      multikey\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache/issues\npublished_at: 2025-09-30T11:20:43.600861847Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache.git\n  commit: a6a94e060c006222ab1f9899f0112ce0eb340a14\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-multikey-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- keys: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/bitrise-step-multikey-restore-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/bitrise-step-multikey-save-cache/0.1.0/step.yml",
    "content": "title: Multikey Save Cache\nsummary: Saves items to the cache based on key-value pairs. This Step needs to be\n  used in combination with **Multikey Restore Cache** or **Restore Cache**.\ndescription: |\n  Saves items to the cache based on an input in the form of:\n  ```\n  OPTIONAL_UNIQUNESS_PREFIX KEY1 = PATH1, PATH2, ...\n  OPTIONAL_UNIQUNESS_PREFIX KEY2 = PATH3, ...\n  ```\n  where `OPTIONAL_UNIQUNESS_PREFIX` is `[u]` and means that the key in the given line is unique (see **Restore Cache**).\n  The number of keys and paths for each are limited to a number of 10. The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) and equal signs (`=`) are not allowed in keys neither in paths.\n  See templates that can be used in the keys below. The path list is a list of files and folders to include in the cache, separated by a comma (`,`). Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n\n  Example (somewhat artificial):\n  ```\n  [u] multikey_0 = e2e/tmp/multikey_0.txt\n  [u] multikey_1 = e2e/tmp/multikey_1_0.txt, e2e/tmp/multikey_1_1.txt\n  [u]multikey_2=e2e/tmp/multikey_2_0.txt,e2e/tmp/multikey_2_1.txt\n  multikey_3 = e2e/tmp/multikey_3.txt\n  multikey_4 = e2e/tmp/multikey_4_0.txt, e2e/tmp/multikey_4_1.txt\n  multikey_5=e2e/tmp/multikey_5_0.txt,e2e/tmp/multikey_5_1.txt\n  ```\n\n  This Step needs to be used in combination with **Multikey Restore Cache** or **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Multikey save cache** and **Multikey restore cache** steps  use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Multikey restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the [**Multikey restore cache** step](https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache/) for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Multikey Restore Cache](https://github.com/bitrise-steplib/bitrise-step-multikey-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-multikey-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-multikey-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-multikey-save-cache/issues\npublished_at: 2025-07-29T15:15:28.858711+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-multikey-save-cache.git\n  commit: bd30e324ae227fb5d4b6321e1de397a2dc9f52ad\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-multikey-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_path_pairs: null\n  opts:\n    description: |-\n      A mapping used to define the cache keys and the paths to include in the cache archive. The format is:\n      ```\n      OPTIONAL_UNIQUNESS_PREFIX KEY1 = PATH1, PATH2, ...\n      OPTIONAL_UNIQUNESS_PREFIX KEY2 = PATH3, ...\n      ```\n      where `OPTIONAL_UNIQUNESS_PREFIX` is `[u]` and means that the key in the given line is unique (see **Restore Cache**). The number of keys and paths for each are limited to a number of 10\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) and equal signs (`=`) are not allowed in keys neither in paths.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n    is_required: true\n    summary: A key -> path list mapping. This can contain template elements.\n    title: Cache key -> path list pairs\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- custom_tar_args: null\n  opts:\n    description: |-\n      Additional arguments to pass to the tar command when creating the cache archive.\n\n      The arguments are passed directly to the `tar` command. Use this input to customize the behavior of the tar command when creating the cache archive\n      (these are appended to the default arguments used by the step).\n\n      Example: `--format posix`\n    is_required: false\n    summary: Additional arguments to pass to the tar command when creating the cache\n      archive.\n    title: Custom tar arguments\n"
  },
  {
    "path": "steps/bitrise-step-multikey-save-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/bitrise-step-nowsecure-auto-analysis/0.1.1/step.yml",
    "content": "title: NowSecure Auto Analysis\nsummary: |\n  Performs security analysis using NowSecure Auto (https://lab.nowsecure.com/).\ndescription: |\n  Performs security analysis using NowSecure Auto (https://lab.nowsecure.com/).\nwebsite: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis\nsource_code_url: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis\nsupport_url: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis/issues\npublished_at: 2020-01-21T09:47:07.099682099-06:00\nsource:\n  git: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis.git\n  commit: 77680c2a364c9b0a253570cadbaf7c65922ce08c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- nowsecure_api_token: null\n  opts:\n    description: |\n      NowSecure token generated from NowSecure Auto console\n    is_required: true\n    is_sensitive: true\n    summary: Your NowSecure Auto API token\n    title: NowSecure Auto API token\n- nowsecure_group_id: null\n  opts:\n    description: |\n      NowSecure Group ID which is required only if your NowSecure token has access to multiple groups\n    is_required: false\n    is_sensitive: true\n    summary: Your NowSecure Auto group ID for this app\n    title: NowSecure Auto group ID\n"
  },
  {
    "path": "steps/bitrise-step-nowsecure-auto-analysis/0.1.3/step.yml",
    "content": "title: NowSecure Auto Analysis\nsummary: |\n  Performs security analysis using NowSecure Auto (https://lab.nowsecure.com/).\ndescription: |\n  Performs security analysis using NowSecure Auto (https://lab.nowsecure.com/).\nwebsite: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis\nsource_code_url: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis\nsupport_url: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis/issues\npublished_at: 2020-12-03T20:35:10.759739869-06:00\nsource:\n  git: https://github.com/sp3nx0r/bitrise-step-nowsecure-auto-analysis.git\n  commit: 9e97312648f29ed8da11596128c233a54c246229\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- nowsecure_api_token: null\n  opts:\n    description: |\n      NowSecure token generated from NowSecure Auto console\n    is_required: true\n    is_sensitive: true\n    summary: Your NowSecure Auto API token\n    title: NowSecure Auto API token\n- nowsecure_group_id: null\n  opts:\n    description: |\n      NowSecure Group ID which is required only if your NowSecure token has access to multiple groups\n    is_required: false\n    is_sensitive: true\n    summary: Your NowSecure Auto group ID for this app\n    title: NowSecure Auto group ID\n"
  },
  {
    "path": "steps/bitrise-step-nowsecure-auto-analysis/0.1.4/step.yml",
    "content": "title: NowSecure Platform Analysis\nsummary: |\n  Performs security analysis using NowSecure Platform (https://lab.nowsecure.com/).\ndescription: |\n  Performs security analysis using NowSecure Platform (https://lab.nowsecure.com/).\nwebsite: https://github.com/nowsecure/bitrise-step-nowsecure-auto-analysis\nsource_code_url: https://github.com/nowsecure/bitrise-step-nowsecure-auto-analysis\nsupport_url: https://support.nowsecure.com\npublished_at: 2022-01-27T12:40:41.910877-08:00\nsource:\n  git: https://github.com/nowsecure/bitrise-step-nowsecure-auto-analysis.git\n  commit: 57cf75ad057d67ffb039c29be7840b50dc6e2f53\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- nowsecure_api_token: null\n  opts:\n    description: |\n      NowSecure token generated from NowSecure Platform console\n    is_required: true\n    is_sensitive: true\n    summary: Your NowSecure Platform API token\n    title: NowSecure Platform API token\n- nowsecure_group_id: null\n  opts:\n    description: |\n      NowSecure Group ID which is required only if your NowSecure token has access to multiple groups\n    is_required: false\n    is_sensitive: true\n    summary: Your NowSecure Platform group ID for this app\n    title: NowSecure Platform group ID\n"
  },
  {
    "path": "steps/bitrise-step-nowsecure-auto-analysis/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/bitrise-step-qyrus-mobility-test-runner-android/0.0.1/step.yml",
    "content": "title: Qyrus Mobile Runner Android\nsummary: Upload apk and ipa to Qyrus platform, triggers the tests.\ndescription: |\n  This step uploads the apk or ipa to Qyrus test platform, runs the test on real devices.\nwebsite: https://github.com/qyrusai/bitrise-step-qyrus-mobility-test-runner-android\nsource_code_url: https://github.com/qyrusai/bitrise-step-qyrus-mobility-test-runner-android\nsupport_url: https://github.com/qyrusai/bitrise-step-qyrus-mobility-test-runner-android/issues\npublished_at: 2021-11-22T15:42:32.198078+05:30\nsource:\n  git: https://github.com/QyrusAI/bitrise-step-qyrus-mobility-test-runner-android.git\n  commit: 722203873bdb01644bf4cf00a82169659dfdb741\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: nodejs\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- gateway_url: null\n  opts:\n    description: |\n      Enter the url of the gateway which is provided by Qyrus else\n      contact support@qyrus.com\n    is_required: true\n    summary: Qyrus provided gateway url\n    title: Gateway URL\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- opts:\n    description: |\n      The username used to run devops tasks on Qyrus.\n    is_required: true\n    summary: Your Qyrus devops username\n    title: Qyrus Username\n  qyrus_username: null\n- opts:\n    description: |\n      The password used to run devops tasks on Qyrus.\n    is_required: true\n    is_sensitive: true\n    summary: Your Qyrus devops password\n    title: Qyrus Password\n  qyrus_password: null\n- opts:\n    description: |\n      Team name you can find by logging into Qyrus app. Copy the team name and paste it.\n    is_required: true\n    summary: Enter the team name\n    title: Qyrus Team Name\n  qyrus_team_name: null\n- opts:\n    description: |\n      Project name you can find by logging into Qyrus app. Copy the team name and paste it.\n    is_required: true\n    summary: Enter the project name\n    title: Qyrus Project Name\n  qyrus_project_name: null\n- opts:\n    description: |\n      Suite name you can find by logging into Qyrus app. Copy the team name and paste it.\n    is_required: true\n    summary: Enter the project name\n    title: Qyrus Suite Name\n  qyrus_suite_name: null\n- app_activity: null\n  opts:\n    description: |\n      Enter android app activity which will be in the form of com.example.splash_screen\n    is_required: true\n    summary: Enter your android app activity\n    title: App Activity\n- device_pool_name: null\n  opts:\n    description: |\n      Specify your device pool name which you created on Qyrus,\n      a device pool will have list of devices added and a test\n      run will happen on a device from the pool.\n    is_required: true\n    summary: Enter device pool name created on Qyrus\n    title: Device pool name\n- enable_debug: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If you just want to run tests without upload app\n      change the option to no.\n    is_required: true\n    title: Upload app\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_app: \"no\"\noutputs:\n- QYRUS_TEST_REPORT_URL: null\n  opts:\n    description: |\n      The output of test is the report URL which can be used\n      to download and analyse the test steps\n    summary: Its the report download URL\n    title: Qyrus report download url\n"
  },
  {
    "path": "steps/bitrise-step-qyrus-mobility-test-runner-android/0.0.2/step.yml",
    "content": "title: Qyrus App Automate\nsummary: Upload an app to Qyrus and run tests.\ndescription: \"This step uploads a provided app apk/ipa to Qyrus. It then will execute\n  the tests for the provided apks/ipas in Qyrus. \\nQyrus is a end to end testing platform\n  designed to test Web, Mobile and APIs for all digital enterprises. With its codeless\n  approach to testing Web, Mobile & APIs, Qyrus is the fastest way to start the journey\n  of automated testing for your enterprise.\\n\"\nwebsite: https://github.com/qyrusai/bitrise-step-qyrus-mobility-test-runner-android\nsource_code_url: https://github.com/qyrusai/bitrise-step-qyrus-mobility-test-runner-android\nsupport_url: https://github.com/qyrusai/bitrise-step-qyrus-mobility-test-runner-android/issues\npublished_at: 2021-11-24T01:57:41.720214+05:30\nsource:\n  git: https://github.com/QyrusAI/bitrise-step-qyrus-mobility-test-runner-android.git\n  commit: 4280247b93d0c985f095143d3a84bd882e44d463\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: nodejs\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- enable_debug: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If you just want to run tests without upload app\n      change the option to no.\n    is_required: true\n    title: Upload app\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_app: \"no\"\n- gateway_url: null\n  opts:\n    description: |\n      Enter the url of the gateway which is provided by Qyrus else\n      contact support@qyrus.com\n    is_required: true\n    summary: Qyrus provided gateway url\n    title: Gateway URL\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to Qyrus, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- opts:\n    description: |\n      The username used to run devops tasks on Qyrus.\n    is_required: true\n    summary: Your Qyrus devops username\n    title: Qyrus Username\n  qyrus_username: null\n- opts:\n    description: |\n      The password used to run devops tasks on Qyrus.\n    is_required: true\n    is_sensitive: true\n    summary: Your Qyrus devops password\n    title: Qyrus Password\n  qyrus_password: null\n- opts:\n    description: |\n      Team name you can find by logging into Qyrus app. Copy the team name and paste it.\n    is_required: true\n    summary: Enter the team name\n    title: Qyrus Team Name\n  qyrus_team_name: null\n- opts:\n    description: |\n      Project name you can find by logging into Qyrus app. Copy the team name and paste it.\n    is_required: true\n    summary: Enter the project name\n    title: Qyrus Project Name\n  qyrus_project_name: null\n- opts:\n    description: |\n      Suite name you can find by logging into Qyrus app. Copy the team name and paste it.\n    is_required: true\n    summary: Enter the project name\n    title: Qyrus Suite Name\n  qyrus_suite_name: null\n- app_activity: null\n  opts:\n    description: |\n      Enter android app activity which will be in the form of com.example.splash_screen\n    is_required: false\n    summary: Enter your android app activity\n    title: App Activity\n- bundle_id: null\n  opts:\n    description: |\n      Enter iOS app bundleId which will be in the form of com.example.splash_screen\n    is_required: false\n    summary: Enter your iOS app bundle id\n    title: Bundle Id\n- device_pool_name: null\n  opts:\n    description: |\n      Specify your device pool name which you created on Qyrus,\n      a device pool will have list of devices added and a test\n      run will happen on a device from the pool.\n    is_required: true\n    summary: Enter device pool name created on Qyrus\n    title: device_pool_name\noutputs:\n- QYRUS_TEST_REPORT_URL: null\n  opts:\n    description: |\n      The output of test is the report URL which can be used\n      to download and analyse the test steps\n    summary: Its the report download URL\n    title: Qyrus report download url\n"
  },
  {
    "path": "steps/bitrise-step-qyrus-mobility-test-runner-android/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-stamp-appicon-with-version-number/1.0.0/step.yml",
    "content": "title: Stamp AppIcon with version number\nsummary: |\n  This script will use ImageMagick to stamp the version number to all icons.\ndescription: |\n  Stamps version \"version(build number)\" to the bottom of the icon.\nwebsite: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\nsource_code_url: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\nsupport_url: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number/issues\npublished_at: !!timestamp 2018-04-04T16:50:55.395108202+03:00\nsource:\n  git: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number.git\n  commit: 5c7c44df263ab5201f14dfcb7be2eeb95417bce0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\ndeps:\n  brew:\n  - name: imagemagick\n  apt_get:\n  - name: imagemagick\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: \"true\"\ninputs:\n- opts:\n    description: |\n      Relative path to icons for example `Project/General.xcassets/AppIcon.appiconset`\n    is_expand: true\n    is_required: true\n    summary: Relative path to icons\n    title: Path to icons of the project\n    value_options: []\n  stamp_path_to_icons: null\n- opts:\n    description: |\n      Version number or string for example 0.1 or Dev\n    is_expand: true\n    is_required: true\n    summary: Version number or string\n    title: Version number or string\n    value_options: []\n  stamp_version: null\n- opts:\n    description: |\n      Build number to stamp on the icon. Defaults to BITRISE_BUILD_NUMBER\n    is_expand: true\n    is_required: true\n    summary: Build number to stamp on the icon\n    title: Build number to stamp on the icon\n    value_options: []\n  stamp_build_number: $BITRISE_BUILD_NUMBER\n"
  },
  {
    "path": "steps/bitrise-step-stamp-appicon-with-version-number/1.2.0/step.yml",
    "content": "title: Stamp AppIcon with version number\nsummary: |\n  This step will use ImageMagick to stamp the version number to all icons.\ndescription: |\n  Stamps version \"version(build number)\" to the bottom of the icon.\nwebsite: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\nsource_code_url: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\nsupport_url: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number/issues\npublished_at: 2020-03-25T08:34:01.972373+02:00\nsource:\n  git: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number.git\n  commit: 3fd47f61abba83b6f7500958dfe4cd0e8569ec8b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\ndeps:\n  brew:\n  - name: imagemagick\n  - name: ghostscript\n  apt_get:\n  - name: imagemagick\n  - name: ghostscript\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"true\"\ninputs:\n- opts:\n    description: |\n      Relative path to icons for example `Project/General.xcassets/AppIcon.appiconset`\n    is_expand: true\n    is_required: true\n    summary: Relative path to icons\n    title: Path to icons of the project\n    value_options: []\n  stamp_path_to_icons: null\n- opts:\n    description: |\n      Version number or string for example 0.1 or Dev\n    is_expand: true\n    is_required: true\n    summary: Version number or string\n    title: Version number or string\n    value_options: []\n  stamp_version: null\n- opts:\n    description: |\n      Build number to stamp on the icon. Defaults to `BITRISE_BUILD_NUMBER`\n    is_expand: true\n    is_required: true\n    summary: Build number to stamp on the icon\n    title: Build number to stamp on the icon\n    value_options: []\n  stamp_build_number: $BITRISE_BUILD_NUMBER\n- foreground_color: white\n  opts:\n    description: |\n      Foreground color (text color) of the stamp. Defaults to \"white\"\n    is_expand: true\n    is_required: true\n    summary: Foreground color of the stamp\n    title: Foreground color of the stamp\n    value_options: []\n- background_color: '#0008'\n  opts:\n    description: |\n      Background color of the stamp. Defaults to translucent black\n    is_expand: true\n    is_required: true\n    summary: Background color of the stamp\n    title: Background color of the stamp\n    value_options: []\n"
  },
  {
    "path": "steps/bitrise-step-stamp-appicon-with-version-number/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-version-pre-release-info/1.0.3/step.yml",
    "content": "title: Version pre-release info\nsummary: Generate version containing pre-release information (`v1.0.0-alpha.1`, `2.4.1.beta+2`,\n  `v2.0-rc.3`) based on git tags.\ndescription: |-\n  This step extends version provided as a parameter (`Version number`) with a pre-release identifier (`Pre-release identifier`, e.g. `alpha`, `beta`, `rc`)\n  and a pre-release number. The pre-release number is automatically incremented based on the existing git tags.\n  If there are no tags for the provided version, pre-release number is set to the initial value (`Pre-release initial value`).\n  Pre-release information is exported to the following environment variables:\n  - **APP_PRE_RELEASE_INFO** (e.g. `rc.3`)\n  - **APP_VERSION_WITH_PRE_RELEASE_INFO** (e.g. `v2.0-rc.3`)\n\n  You can use these environment variables in next steps (e.g. when creating a git tag).\nwebsite: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsource_code_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsupport_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info/issues\npublished_at: 2018-11-29T19:23:57.27884901+01:00\nsource:\n  git: https://github.com/pmkowal/bitrise-step-version-pre-release-info.git\n  commit: d8a701c649719538ba3249e58a5339325d556dda\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\n- utility\n- build\ndeps:\n  brew:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      e.g.: `1.0.0`\n    is_required: true\n    title: Version number\n  version_number: $XPI_VERSION\n- opts:\n    description: |\n      e.g.: `alpha`, `beta`, `rc`\n    is_required: true\n    title: Pre-release identifier\n  pre_release_identifier: beta\n- opts:\n    description: |\n      If there are no tags, pre-release number is set to this value\n    is_required: true\n    title: Pre-release initial value\n  pre_release_initial_value: 1\n- opts:\n    description: |\n      e.g. [v]2.0-rc.3\n    is_required: false\n    title: Version prefix\n  version_prefix: v\n- opts:\n    description: |\n      e.g. 2.0[-]rc.3\n    is_required: false\n    title: Pre-release identifier prefix\n  pre_release_identifier_prefix: '-'\n- opts:\n    description: |\n      e.g. 2.0-rc[.]3\n    is_required: false\n    title: Pre-release number prefix\n  pre_release_number_prefix: .\noutputs:\n- APP_VERSION_PRE_RELEASE_INFO: null\n  opts:\n    title: Pre-release info (e.g. `rc.3`)\n- APP_VERSION_WITH_PRE_RELEASE_INFO: null\n  opts:\n    title: Version number containing pre-release info (e.g. `v2.0-rc.3`)\n"
  },
  {
    "path": "steps/bitrise-step-version-pre-release-info/1.1.0/step.yml",
    "content": "title: Version pre-release info\nsummary: Generate version containing pre-release information (`v1.0.0-alpha.1`, `2.4.1.249-beta+2`,\n  `v2.0-rc.3`) based on git tags.\ndescription: |-\n  This step extends version and build number provided as parameters (`Version number`, `Build number`) with a pre-release identifier (`Pre-release identifier`, e.g. `alpha`, `beta`, `rc`)\n  and a pre-release number. The build number is optional and it's not incremented. The pre-release number is automatically incremented based on the existing git tags.\n  If there are no tags for the provided version, pre-release number is set to the initial value (`Pre-release initial value`).\n  Pre-release information is exported to the following environment variables:\n  - **APP_PRE_RELEASE_INFO** (e.g. `rc.3`)\n  - **APP_VERSION_WITH_PRE_RELEASE_INFO** (e.g. `v2.0-rc.3`)\n\n  You can use these environment variables in next steps (e.g. when creating a git tag).\nwebsite: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsource_code_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsupport_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info/issues\npublished_at: 2019-07-04T22:43:13.648325605+02:00\nsource:\n  git: https://github.com/pmkowal/bitrise-step-version-pre-release-info.git\n  commit: 527f277b60600054075de63ae598996c7c2ae317\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\n- utility\n- build\ndeps:\n  brew:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      e.g.: `1.0.0`\n    is_required: true\n    title: Version number\n  version_number: $XPI_VERSION\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      e.g.: `463`\n    is_required: false\n    title: Build number\n- opts:\n    description: |\n      e.g.: `alpha`, `beta`, `rc`\n    is_required: true\n    title: Pre-release identifier\n  pre_release_identifier: beta\n- opts:\n    description: |\n      If there are no tags, pre-release number is set to this value\n    is_required: true\n    title: Pre-release initial value\n  pre_release_initial_value: 1\n- opts:\n    description: |\n      e.g. [v]2.0-rc.3\n    is_required: false\n    title: Version prefix\n  version_prefix: v\n- build_prefix: .\n  opts:\n    description: |\n      e.g.: `2.0[.]463-rc.3`\n    is_required: true\n    title: Build prefix\n- opts:\n    description: |\n      e.g. 2.0[-]rc.3\n    is_required: false\n    title: Pre-release identifier prefix\n  pre_release_identifier_prefix: '-'\n- opts:\n    description: |\n      e.g. 2.0-rc[.]3\n    is_required: false\n    title: Pre-release number prefix\n  pre_release_number_prefix: .\noutputs:\n- APP_VERSION_PRE_RELEASE_INFO: null\n  opts:\n    title: Pre-release info (e.g. `rc.3`)\n- APP_VERSION_WITH_PRE_RELEASE_INFO: null\n  opts:\n    title: Version number containing pre-release info (e.g. `v2.0-rc.3`)\n"
  },
  {
    "path": "steps/bitrise-step-version-pre-release-info/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-step-xctest-cobertura-xml/1.0.0/step.yml",
    "content": "title: Convert XCTest result to Cobertura XML\nsummary: |\n  Converts XCTest results to cobertura compatible xml\ndescription: |\n  Converts test results from XCTest step to Cobertura formatted xml to be uploaded to Coveralls or Sonarqube\nwebsite: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nsource_code_url: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nsupport_url: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml/issues\npublished_at: 2020-01-13T09:46:15.420146+02:00\nsource:\n  git: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml.git\n  commit: c7a5ab2fb18259aebcf86ff5c8f8ac288a4a0dbe\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to XCTest result bundle, usually located in  `..../DerivedData/<Project dir>/Logs/Test`\n      Bitrise Xcode test step provides this in variable `$BITRISE_XCRESULT_PATH`\n    is_expand: true\n    is_required: true\n    summary: Path to XCTest result bundle\n    title: Path to XCTest result bundle\n    value_options: []\n  path_to_xcresult: $BITRISE_XCRESULT_PATH\n- opts:\n    description: |\n      Directory where to put the resulting `coverage.json` and `cobertura.xml`\n      Default is `$BITRISE_DEPLOY_DIR`\n    is_expand: true\n    is_required: true\n    summary: Directory where to put the resulting cobertura.xml\n    title: Directory where to put the resulting cobertura.xml\n    value_options: []\n  xml_output_dir: $BITRISE_DEPLOY_DIR\noutputs:\n- COVERAGE_XML_TEST_RESULT_PATH: null\n  opts:\n    description: |\n      Path to the resulting `cobertura.xml`\n    summary: Path to the resulting `cobertura.xml`\n    title: Path to the resulting cobertura.xml\n- COVERAGE_JSON_TEST_RESULT_PATH: null\n  opts:\n    description: Path to the resulting `coverage.json`\n    summary: Path to the resulting `coverage.json`\n    title: Path to the resulting coverage.json\n"
  },
  {
    "path": "steps/bitrise-step-xctest-cobertura-xml/1.1.0/step.yml",
    "content": "title: Convert XCTest result to Cobertura XML\nsummary: |\n  Converts XCTest results to cobertura compatible xml\ndescription: |\n  Converts test results from XCTest step to Cobertura formatted xml to be uploaded to Coveralls or Sonarqube\nwebsite: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nsource_code_url: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nsupport_url: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml/issues\npublished_at: 2020-03-27T11:15:58.609528+02:00\nsource:\n  git: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml.git\n  commit: e1d25a018c6bf6106e68895cd8841ba6d0de19cf\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to XCTest result bundle, usually located in  `..../DerivedData/<Project dir>/Logs/Test`\n      Bitrise Xcode test step provides this in variable `$BITRISE_XCRESULT_PATH`\n    is_expand: true\n    is_required: true\n    summary: Path to XCTest result bundle\n    title: Path to XCTest result bundle\n    value_options: []\n  path_to_xcresult: $BITRISE_XCRESULT_PATH\n- opts:\n    description: |\n      Directory where to put the resulting `coverage.json` and `cobertura.xml`\n      Default is `$BITRISE_DEPLOY_DIR`\n    is_expand: true\n    is_required: true\n    summary: Directory where to put the resulting cobertura.xml\n    title: Directory where to put the resulting cobertura.xml\n    value_options: []\n  xml_output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    description: |\n      Directory where the source files that used by xcode to create the test \"Path to the resulting coverage.json\"\n      This directory is referenced by the <sources> item of cobertura xml.\n      Default is `$BITRISE_SOURCE_DIR`\n    is_expand: true\n    is_required: true\n    summary: Directory where the source files are located.\n    title: Directory where the source files are located.\n    value_options: []\n  path_to_source_dir: $BITRISE_SOURCE_DIR\noutputs:\n- COVERAGE_XML_TEST_RESULT_PATH: null\n  opts:\n    description: |\n      Path to the resulting `cobertura.xml`\n    summary: Path to the resulting `cobertura.xml`\n    title: Path to the resulting cobertura.xml\n- COVERAGE_JSON_TEST_RESULT_PATH: null\n  opts:\n    description: Path to the resulting `coverage.json`\n    summary: Path to the resulting `coverage.json`\n    title: Path to the resulting coverage.json\n"
  },
  {
    "path": "steps/bitrise-step-xctest-cobertura-xml/1.2.0/step.yml",
    "content": "title: Convert XCTest result to Cobertura XML\nsummary: |\n  Converts XCTest results to cobertura compatible xml\ndescription: |\n  Converts test results from XCTest step to Cobertura formatted xml to be uploaded to Coveralls or Sonarqube\nwebsite: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nsource_code_url: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nsupport_url: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml/issues\npublished_at: 2020-05-18T11:45:52.567908+03:00\nsource:\n  git: https://github.com/ollitapa/bitrise-step-xctest-cobertura-xml.git\n  commit: e9d93fba557f15023d7077f10e438148a47dbc8e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/ollitapa/bitrise-step-xctest-cobertura-xml\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to XCTest result bundle, usually located in  `..../DerivedData/<Project dir>/Logs/Test`\n      Bitrise Xcode test step provides this in variable `$BITRISE_XCRESULT_PATH`\n    is_expand: true\n    is_required: true\n    summary: Path to XCTest result bundle\n    title: Path to XCTest result bundle\n    value_options: []\n  path_to_xcresult: $BITRISE_XCRESULT_PATH\n- opts:\n    description: |\n      Directory where to put the resulting `coverage.json` and `cobertura.xml`\n      Default is `$BITRISE_DEPLOY_DIR`\n    is_expand: true\n    is_required: true\n    summary: Directory where to put the resulting cobertura.xml\n    title: Directory where to put the resulting cobertura.xml\n    value_options: []\n  xml_output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    description: |\n      Directory where the source files that used by xcode to create the test \"Path to the resulting coverage.json\"\n      This directory is referenced by the <sources> item of cobertura xml.\n      Default is `$BITRISE_SOURCE_DIR`\n    is_expand: true\n    is_required: true\n    summary: Directory where the source files are located.\n    title: Directory where the source files are located.\n    value_options: []\n  path_to_source_dir: $BITRISE_SOURCE_DIR\noutputs:\n- COVERAGE_XML_TEST_RESULT_PATH: null\n  opts:\n    description: |\n      Path to the resulting `cobertura.xml`\n    summary: Path to the resulting `cobertura.xml`\n    title: Path to the resulting cobertura.xml\n- COVERAGE_JSON_TEST_RESULT_PATH: null\n  opts:\n    description: Path to the resulting `coverage.json`\n    summary: Path to the resulting `coverage.json`\n    title: Path to the resulting coverage.json\n"
  },
  {
    "path": "steps/bitrise-step-xctest-cobertura-xml/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bitrise-to-appscan/0.2.4/step.yml",
    "content": "title: AppScan Security Analysis\nsummary: Performs security analysis using the IBM AppScan Cloud.\ndescription: |\n  Performs security analysis using the IBM AppScan Cloud.\nwebsite: https://github.com/ipiranga-atq/bitrise_appscan_step\nsource_code_url: https://github.com/ipiranga-atq/bitrise_appscan_step\nsupport_url: https://github.com/ipiranga-atq/bitrise_appscan_step/issues\npublished_at: 2018-09-28T15:14:10.722212144-03:00\nsource:\n  git: https://github.com/ipiranga-atq/bitrise_appscan_step.git\n  commit: b1623ebc6a5858092ce936919b6a074c45fd0146\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/ipiranga-atq/bitrise_appscan_step\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: \"\"\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      Recommended is *$BITRISE_APK_PATH* or *$BITRISE_IPA_PATH*.\n    is_expand: true\n    is_required: true\n    title: Path to the applications IPA/PATH.\n- app_name: null\n  opts:\n    description: |\n      (If no application is found with the given name, the step will fail)\n    is_expand: true\n    is_required: true\n    title: Application's Name on AppScan\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Username for AppScan\n  user_name: null\n- opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Password for AppScan\n  user_password: null\n- app_user: null\n  opts:\n    description: |\n      Username to log in the application\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Application's Username\n- app_password: null\n  opts:\n    description: |\n      Password to log in the application\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Application's Password\n- opts:\n    description: |\n      The Presence Id to access the private network of the application.\n    is_expand: true\n    is_required: false\n    title: Presence Id\n  presence_id: null\n"
  },
  {
    "path": "steps/bitrise-to-appscan/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bluepill-build-test-for-ios/0.2.6/step.yml",
    "content": "title: Bluepill Build/Test for iOS\nsummary: Build and run parallel UI/Unit tests for iOS using LinkedIn's bluepill testing\n  tool\ndescription: Run tests in parallel by using multiple simulators. Generate a JUnit\n  report after each test run.\nwebsite: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsource_code_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsupport_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios/issues\npublished_at: 2019-07-11T11:50:55.339419+08:00\nsource:\n  git: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios.git\n  commit: 38f3436a2845cc8081c38a0df9c83e807d332299\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- bluepill_version: bluepill_4_1_1__xcode_10_2\n  opts:\n    is_required: true\n    summary: Which version of Bluepill to install/run?\n    title: Bluepill Version\n    value_options:\n    - bluepill_4_1_1__xcode_10_2\n    - bluepill_3_1_1__xcode_10_1\n    - bluepill_3_1_0__xcode_10_0\n    - bluepill_2_4_0__xcode_9_4\n    - bluepill_2_3_1__xcode_9_3\n    - bluepill_2_2_0__xcode_9_2\n    - bluepill_2_1_0__xcode_9_1\n    - bluepill_2_0_2__xcode_9_0\n    - bluepill_1_1_2__xcode_8_3\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Target name in bundle (e.g. 'MyApp')\n    title: Target Name\n  target_name: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode scheme (e.g. 'MyApp')\n    title: Scheme\n  scheme: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode workspace file (e.g. MyApp.xcworkspace)\n    title: Workspace File\n  workspace: \"\"\n- device_type: iPhone 6\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Device to build/run (e.g. 'iPhone 6', 'iPad Pro (12.9-inch)')\n    title: Device Type\n- ios_version: \"12.2\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Version to build/run simulators (e.g. '11.0', '12.2')\n    title: iOS Version\n- derived_data_path: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Derived data directory (e.g. 'build')\n    title: Derived Data Path\n- bluepill_output_dir: bluepill-output\n  opts:\n    is_expand: true\n    is_required: true\n    summary: 'Directory to place all the bluepill logs/results files. Individual test\n      reports will sit inside this directory, named like: \"iPhone SE - 12.2 - TIMESTAMP\"'\n    title: Bluepill Logs Path\n- num_simulators: 4\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of iOS simulators to run in parallel.\n    title: Num. Simulators (-n)\n- failure_tolerance: 0\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of times to retry on test failures.\n    title: Failure Tolerance (-f)\n- opts:\n    is_required: true\n    summary: When Failure Tolerance is above zero, only retry tests that failed.\n    title: Only Retry Failed Tests? (-F)\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_only_failed_tests: \"false\"\n- additional_bluepill_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: See https://github.com/linkedin/bluepill for a full list of supported\n      argumentss.\n    title: Additional Bluepill Arguments\n- fail_build_if_coverage_fails: \"false\"\n  opts:\n    summary: Fail the build if Bluepill fails to gather valid coverage data (e.g.\n      `${bluepill_output_dir}/${target_name}.app.coverage.txt`)\n    title: Fail Build on Invalid Coverage Data\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Environment variable to capture test results as a human-readable string.\n      This will also produce a Markdown-formatted copy with the `_MARKDOWN` suffix.\n      e.g. (`MY_RESULT` and `MY_RESULT_MARKDOWN`)\n    title: Test Results Output Environment Variable\n  test_result_env_var: TEST_RESULTS\n"
  },
  {
    "path": "steps/bluepill-build-test-for-ios/0.2.7/step.yml",
    "content": "title: Bluepill Build/Test for iOS\nsummary: Build and run parallel UI/Unit tests for iOS using LinkedIn's bluepill testing\n  tool\ndescription: Run tests in parallel by using multiple simulators. Generate a JUnit\n  report after each test run.\nwebsite: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsource_code_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsupport_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios/issues\npublished_at: 2019-07-18T11:43:18.16339+08:00\nsource:\n  git: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios.git\n  commit: 4e55fe66aa418ebcb5cf7fad1cc0ac267f9c71a7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- bluepill_version: bluepill_4_1_1__xcode_10_2\n  opts:\n    is_required: true\n    summary: Which version of Bluepill to install/run?\n    title: Bluepill Version\n    value_options:\n    - bluepill_4_1_1__xcode_10_2\n    - bluepill_3_1_1__xcode_10_1\n    - bluepill_3_1_0__xcode_10_0\n    - bluepill_2_4_0__xcode_9_4\n    - bluepill_2_3_1__xcode_9_3\n    - bluepill_2_2_0__xcode_9_2\n    - bluepill_2_1_0__xcode_9_1\n    - bluepill_2_0_2__xcode_9_0\n    - bluepill_1_1_2__xcode_8_3\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Target name in bundle (e.g. 'MyApp')\n    title: Target Name\n  target_name: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode scheme (e.g. 'MyApp')\n    title: Scheme\n  scheme: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode workspace file (e.g. MyApp.xcworkspace)\n    title: Workspace File\n  workspace: \"\"\n- device_type: iPhone 6\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Device to build/run (e.g. 'iPhone 6', 'iPad Pro (12.9-inch)')\n    title: Device Type\n- ios_version: \"12.2\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Version to build/run simulators (e.g. '11.0', '12.2')\n    title: iOS Version\n- derived_data_path: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Derived data directory (e.g. 'build')\n    title: Derived Data Path\n- generate_coverage: \"true\"\n  opts:\n    is_required: true\n    summary: Generate code coverage for the build.\n    title: Generate Coverage\n    value_options:\n    - \"true\"\n    - \"false\"\n- bluepill_output_dir: bluepill-output\n  opts:\n    is_expand: true\n    is_required: true\n    summary: 'Directory to place all the bluepill logs/results files. Individual test\n      reports will sit inside this directory, named like: \"iPhone SE - 12.2 - TIMESTAMP\"'\n    title: Bluepill Logs Path\n- num_simulators: 4\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of iOS simulators to run in parallel.\n    title: Num. Simulators (-n)\n- failure_tolerance: 0\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of times to retry on test failures.\n    title: Failure Tolerance (-f)\n- opts:\n    is_required: true\n    summary: When Failure Tolerance is above zero, only retry tests that failed.\n    title: Only Retry Failed Tests? (-F)\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_only_failed_tests: \"false\"\n- additional_xcodebuild_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Additional arguments to send to `xcodebuild`\n    title: Additional Xcodebuild Arguments\n- additional_bluepill_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: See https://github.com/linkedin/bluepill for a full list of supported\n      argumentss.\n    title: Additional Bluepill Arguments\n- fail_build_if_coverage_fails: \"false\"\n  opts:\n    summary: Fail the build if Bluepill fails to gather valid coverage data (e.g.\n      `${bluepill_output_dir}/${target_name}.app.coverage.txt`)\n    title: Fail Build on Invalid Coverage Data\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Environment variable to capture test results as a human-readable string.\n      This will also produce a Markdown-formatted copy with the `_MARKDOWN` suffix.\n      e.g. (`MY_RESULT` and `MY_RESULT_MARKDOWN`)\n    title: Test Results Output Environment Variable\n  test_result_env_var: TEST_RESULTS\n"
  },
  {
    "path": "steps/bluepill-build-test-for-ios/0.3.0/step.yml",
    "content": "title: Bluepill Build/Test for iOS\nsummary: Build and run parallel UI/Unit tests for iOS using LinkedIn's bluepill testing\n  tool\ndescription: Run tests in parallel by using multiple simulators. Generate a JUnit\n  report after each test run.\nwebsite: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsource_code_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsupport_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios/issues\npublished_at: 2019-10-28T13:55:28.84506+08:00\nsource:\n  git: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios.git\n  commit: 321f91524eb35fa0da986f0d938a383a26830db7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- bluepill_version: bluepill_5_0_0__xcode_11_0\n  opts:\n    is_required: true\n    summary: Which version of Bluepill to install/run?\n    title: Bluepill Version\n    value_options:\n    - bluepill_5_0_0__xcode_11_0\n    - bluepill_4_1_1__xcode_10_2\n    - bluepill_3_1_1__xcode_10_1\n    - bluepill_3_1_0__xcode_10_0\n    - bluepill_2_4_0__xcode_9_4\n    - bluepill_2_3_1__xcode_9_3\n    - bluepill_2_2_0__xcode_9_2\n    - bluepill_2_1_0__xcode_9_1\n    - bluepill_2_0_2__xcode_9_0\n    - bluepill_1_1_2__xcode_8_3\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Target name in bundle (e.g. 'MyApp')\n    title: Target Name\n  target_name: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode scheme (e.g. 'MyApp')\n    title: Scheme\n  scheme: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode workspace file (e.g. MyApp.xcworkspace)\n    title: Workspace File\n  workspace: \"\"\n- device_type: iPhone 6\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Device to build/run (e.g. 'iPhone 6', 'iPad Pro (12.9-inch)')\n    title: Device Type\n- ios_version: \"13.0\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Version to build/run simulators (e.g. '12.2', '13.0')\n    title: iOS Version\n- derived_data_path: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Derived data directory (e.g. 'build')\n    title: Derived Data Path\n- generate_coverage: \"true\"\n  opts:\n    is_required: true\n    summary: Generate code coverage for the build.\n    title: Generate Coverage\n    value_options:\n    - \"true\"\n    - \"false\"\n- bluepill_output_dir: bluepill-output\n  opts:\n    is_expand: true\n    is_required: true\n    summary: 'Directory to place all the bluepill logs/results files. Individual test\n      reports will sit inside this directory, named like: \"iPhone SE - 12.2 - TIMESTAMP\"'\n    title: Bluepill Logs Path\n- num_simulators: 4\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of iOS simulators to run in parallel.\n    title: Num. Simulators (-n)\n- failure_tolerance: 0\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of times to retry on test failures.\n    title: Failure Tolerance (-f)\n- opts:\n    is_required: true\n    summary: When Failure Tolerance is above zero, only retry tests that failed.\n    title: Only Retry Failed Tests? (-F)\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_only_failed_tests: \"false\"\n- additional_xcodebuild_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Additional arguments to send to `xcodebuild`\n    title: Additional Xcodebuild Arguments\n- additional_bluepill_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: See https://github.com/linkedin/bluepill for a full list of supported\n      argumentss.\n    title: Additional Bluepill Arguments\n- fail_build_if_coverage_fails: \"false\"\n  opts:\n    summary: Fail the build if Bluepill fails to gather valid coverage data (e.g.\n      `${bluepill_output_dir}/${target_name}.app.coverage.txt`)\n    title: Fail Build on Invalid Coverage Data\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Environment variable to capture test results as a human-readable string.\n      This will also produce a Markdown-formatted copy with the `_MARKDOWN` suffix.\n      e.g. (`MY_RESULT` and `MY_RESULT_MARKDOWN`)\n    title: Test Results Output Environment Variable\n  test_result_env_var: TEST_RESULTS\n"
  },
  {
    "path": "steps/bluepill-build-test-for-ios/0.4.0/step.yml",
    "content": "title: Bluepill Build/Test for iOS\nsummary: Build and run parallel UI/Unit tests for iOS using LinkedIn's bluepill testing\n  tool\ndescription: Run tests in parallel by using multiple simulators. Generate a JUnit\n  report after each test run.\nwebsite: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsource_code_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios\nsupport_url: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios/issues\npublished_at: 2019-12-11T11:05:26.727538+08:00\nsource:\n  git: https://github.com/HealthEngineAU/bitrise-step-bluepill-build-test-for-ios.git\n  commit: 51a77e3847a29a0d5ea21903ae7d5c99d20c708c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- bluepill_version: bluepill_5_1_1__xcode_11_2\n  opts:\n    is_required: true\n    summary: Which version of Bluepill to install/run?\n    title: Bluepill Version\n    value_options:\n    - bluepill_5_1_1__xcode_11_2\n    - bluepill_5_0_0__xcode_11_0\n    - bluepill_4_1_1__xcode_10_2\n    - bluepill_3_1_1__xcode_10_1\n    - bluepill_3_1_0__xcode_10_0\n    - bluepill_2_4_0__xcode_9_4\n    - bluepill_2_3_1__xcode_9_3\n    - bluepill_2_2_0__xcode_9_2\n    - bluepill_2_1_0__xcode_9_1\n    - bluepill_2_0_2__xcode_9_0\n    - bluepill_1_1_2__xcode_8_3\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Target name in bundle (e.g. 'MyApp')\n    title: Target Name\n  target_name: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode scheme (e.g. 'MyApp')\n    title: Scheme\n  scheme: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Xcode workspace file (e.g. MyApp.xcworkspace)\n    title: Workspace File\n  workspace: \"\"\n- device_type: iPhone 11\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Device to build/run (e.g. 'iPhone 11', 'iPad Pro (12.9-inch) (3rd\n      generation)')\n    title: Device Type\n- ios_version: \"13.2\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: iOS Version to build/run simulators (e.g. '12.4', '13.2')\n    title: iOS Version\n- derived_data_path: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Derived data directory (e.g. 'build')\n    title: Derived Data Path\n- generate_coverage: \"true\"\n  opts:\n    is_required: true\n    summary: Generate code coverage for the build.\n    title: Generate Coverage\n    value_options:\n    - \"true\"\n    - \"false\"\n- bluepill_output_dir: bluepill-output\n  opts:\n    is_expand: true\n    is_required: true\n    summary: 'Directory to place all the bluepill logs/results files. Individual test\n      reports will sit inside this directory, named like: \"iPhone SE - 12.2 - TIMESTAMP\"'\n    title: Bluepill Logs Path\n- num_simulators: 4\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of iOS simulators to run in parallel.\n    title: Num. Simulators (-n)\n- failure_tolerance: 0\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Number of times to retry on test failures.\n    title: Failure Tolerance (-f)\n- opts:\n    is_required: true\n    summary: When Failure Tolerance is above zero, only retry tests that failed.\n    title: Only Retry Failed Tests? (-F)\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_only_failed_tests: \"false\"\n- additional_xcodebuild_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Additional arguments to send to `xcodebuild`\n    title: Additional Xcodebuild Arguments\n- additional_bluepill_args: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: See https://github.com/linkedin/bluepill for a full list of supported\n      argumentss.\n    title: Additional Bluepill Arguments\n- fail_build_if_coverage_fails: \"false\"\n  opts:\n    summary: Fail the build if Bluepill fails to gather valid coverage data (e.g.\n      `${bluepill_output_dir}/${target_name}.app.coverage.txt`)\n    title: Fail Build on Invalid Coverage Data\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Environment variable to capture test results as a human-readable string.\n      This will also produce a Markdown-formatted copy with the `_MARKDOWN` suffix.\n      e.g. (`MY_RESULT` and `MY_RESULT_MARKDOWN`)\n    title: Test Results Output Environment Variable\n  test_result_env_var: TEST_RESULTS\n"
  },
  {
    "path": "steps/bluepill-build-test-for-ios/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bower/0.1.2/step.yml",
    "content": "title: Run bower command\nsummary: Runs `bower` with the given command and args.\ndescription: Runs `bower` with the given command and args.\nwebsite: https://github.com/nhammond101/steps-bower\nsource_code_url: https://github.com/nhammond101/steps-bower\nsupport_url: https://github.com/nhammond101/steps-bower/issues\npublished_at: 2016-11-23T12:58:05.247749879Z\nsource:\n  git: https://github.com/nhammond101/steps-bower.git\n  commit: b3cdda75d4541afacc08826a328c285d5e7225f1\ntype_tags:\n- bower\ndeps:\n  brew:\n  - name: npm\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: Specify the command to run with `bower`. For example `install`, or\n      `test`.\n    title: The `bower` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `bower` command. You can specify multiple arguments, separated\n      by a space character. For example `-dd -ll`\n    title: Arguments for running `bower` commands\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bower/0.1.3/step.yml",
    "content": "title: Run bower command\nsummary: Runs `bower` with the given command and args.\ndescription: Runs `bower` with the given command and args.\nwebsite: https://github.com/nhammond101/steps-bower\nsource_code_url: https://github.com/nhammond101/steps-bower\nsupport_url: https://github.com/nhammond101/steps-bower/issues\npublished_at: 2016-12-02T10:46:39.400538674Z\nsource:\n  git: https://github.com/nhammond101/steps-bower.git\n  commit: f01eca0dffbc693d959bb6758cfb07c72de72077\nproject_type_tags:\n- web\ntype_tags:\n- installer\ndeps:\n  brew:\n  - name: npm\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: Specify the command to run with `bower`. For example `install`, or\n      `test`.\n    title: The `bower` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `bower` command. You can specify multiple arguments, separated\n      by a space character Nb. --allow-root is appended automatically. For example `--save`\n    title: Arguments for running `bower` commands\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/bower/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/brew-install/0.10.0/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade formula with brew\ndescription: Install or upgrade formula with brew\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2019-09-04T14:05:28.633248533Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: f852abd2db2d170f23829787ec472e397f90662f\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    description: Name of the formula to install/upgrade\n    is_expand: true\n    is_required: true\n    summary: Name of the formula to install/upgrade\n    title: Name of the formula to install/upgrade\n  packages: null\n- options: null\n  opts:\n    description: |\n      Flags to pass to the bew install/reinstall command.\n\n      `brew install/reinstall [options] [packages]`\n    is_expand: true\n    summary: Options for Brew install/upgrade\n    title: Options for Brew install/upgrade\n- opts:\n    description: |\n      If set the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n\n      Otherwise the step calls `brew install [options] [packages]`\n    is_expand: true\n    summary: Upgrade formula if previously installed\n    title: Upgrade formula if previously installed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- cache_enabled: \"no\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of ~/Library/Caches/Homebrew directory should be cached.\n      `true`: Mark brew installers to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.10.2/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade formula with brew\ndescription: Install or upgrade formula with brew\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2019-10-03T11:22:45.452593286Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: f307d278e39a32b2301b6a4fcb03b977c1561d63\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: true\n    summary: Name of the formula to install/reinstall.\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n\n      Otherwise the step calls `brew install [options] [packages]`.\n    is_required: true\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.11.0/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade formula with brew\ndescription: Install or upgrade formula with brew\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2020-09-23T14:21:39.060674976Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: fa006cfaa3102ff923083b6f90a08ef278be94cb\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: true\n    summary: Name of the formula to install/reinstall.\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n\n      Otherwise the step calls `brew install [options] [packages]`.\n    is_required: true\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.11.1/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: \"\\nInstall or upgrade dependencies using Homebrew, a package manager\n  for MacOS. \\n\\n### Configuring the Step \\n\\nHomebrew defines the available packages\n  as formulae. Our Step needs the name of the Homebrew formulae you want to use. \\n\\n1.\n  In the **Formula name** input, put the name of the formula you want to download.\n  \\n1. In the **Upgrade formula?** input, set the default behavior for previously\n  installed packages. If the input is set to `yes`, the Step will call `brew reinstall`\n  to upgrade them to the latest version.\\n1. In the **Brew install/reinstall options**\n  input, you can set additional flags for the `brew install` or `brew reinstall` commands.\n  \\n   For the possible options, see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\\n\n  \\  \\n### Useful links\\n\\n- [Homebrew documentation](https://docs.brew.sh/Manpage)\\n-\n  [Caching Homebrew installers](https://devcenter.bitrise.io/builds/caching/caching-homebrew-installers/)\\n\\n###\n  Related Steps \\n\\n- [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n-\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2020-11-19T16:47:56.779628511Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: 84e475ef1abc35842dab480c223e6310fe5442af\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: true\n    summary: Name of the formula to install/reinstall.\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    is_required: true\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.12.0/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: \"\\nInstall or upgrade dependencies using Homebrew, a package manager\n  for MacOS. \\n\\n### Configuring the Step \\n\\nHomebrew defines the available packages\n  as formulae. Our Step needs the name of the Homebrew formulae you want to use. \\n\\n1.\n  In the **Formula name** input, put the name of the formula you want to download.\n  \\n1. In the **Upgrade formula?** input, set the default behavior for previously\n  installed packages. If the input is set to `yes`, the Step will call `brew reinstall`\n  to upgrade them to the latest version.\\n1. In the **Brew install/reinstall options**\n  input, you can set additional flags for the `brew install` or `brew reinstall` commands.\n  \\n   For the possible options, see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\\n\n  \\  \\n### Useful links\\n\\n- [Homebrew documentation](https://docs.brew.sh/Manpage)\\n-\n  [Caching Homebrew installers](https://devcenter.bitrise.io/builds/caching/caching-homebrew-installers/)\\n\\n###\n  Related Steps \\n\\n- [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n-\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2021-10-07T11:24:00.840784548Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: 9ae4dc4bad6d53b113bdd550aff60192e57c3bef\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: false\n    summary: Name of the formula to install/reinstall. Must be specified when `use_brewfile`\n      is not `yes`\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    is_required: true\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.12.1/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: \"\\nInstall or upgrade dependencies using Homebrew, a package manager\n  for MacOS. \\n\\n### Configuring the Step \\n\\nHomebrew defines the available packages\n  as formulae. Our Step needs the name of the Homebrew formulae you want to use, either\n  specified as a step input, or from a Brewfile in the project's source.\\n\\nTo specify\n  formulae in the step configuration\\n\\n1. In the **Formula name** input, put the\n  name of the formula you want to download. \\n1. In the **Upgrade formula?** input,\n  set the default behavior for previously installed packages. If the input is set\n  to `yes`, the Step will call `brew reinstall` to upgrade them to the latest version.\\n1.\n  In the **Brew install/reinstall options** input, you can set additional flags for\n  the `brew install` or `brew reinstall` commands. \\n   For the possible options,\n  see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\\n\\nAlternatively\n  you can install formulae using a Brewfile\\n\\n1. Add a `Brewfile` to the root of\n  the project's source. For the format of the Brewfile, see the [Homebrew Bundle documentation](https://github.com/Homebrew/homebrew-bundle#usage)\\n1.\n  Set the **Use a Brewfile to install packages?** input to \\\"yes\\\". \\n1. (optional)\n  Set the **Path to the Brewfile** input if it is not in the root of the project's\n  source\\n\\n### Useful links\\n\\n- [Homebrew documentation](https://docs.brew.sh/Manpage)\\n-\n  [Caching Homebrew installers](https://devcenter.bitrise.io/builds/caching/caching-homebrew-installers/)\\n\\n###\n  Related Steps \\n\\n- [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n-\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2021-10-08T13:11:40.022856808Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: 0b454ca6435917dfe967d75d0ea19ae23c1210f9\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: false\n    summary: Name of the formula to install/reinstall. Must be specified when `use_brewfile`\n      is not `yes`\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`. Path must end with `Brewfile`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.12.2/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: \"\\nInstall or upgrade dependencies using Homebrew, a package manager\n  for MacOS. \\n\\n### Configuring the Step \\n\\nHomebrew defines the available packages\n  as formulae. Our Step needs the name of the Homebrew formulae you want to use, either\n  specified as a step input, or from a Brewfile in the project's source.\\n\\nTo specify\n  formulae in the step configuration\\n\\n1. In the **Formula name** input, put the\n  name of the formula you want to download. \\n1. In the **Upgrade formula?** input,\n  set the default behavior for previously installed packages. If the input is set\n  to `yes`, the Step will call `brew reinstall` to upgrade them to the latest version.\\n1.\n  In the **Brew install/reinstall options** input, you can set additional flags for\n  the `brew install` or `brew reinstall` commands. \\n   For the possible options,\n  see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\\n\\nAlternatively\n  you can install formulae using a Brewfile\\n\\n1. Add a `Brewfile` to the root of\n  the project's source. For the format of the Brewfile, see the [Homebrew Bundle documentation](https://github.com/Homebrew/homebrew-bundle#usage)\\n1.\n  Set the **Use a Brewfile to install packages?** input to \\\"yes\\\". \\n1. (optional)\n  Set the **Path to the Brewfile** input if it is not in the root of the project's\n  source\\n\\n### Useful links\\n\\n- [Homebrew documentation](https://docs.brew.sh/Manpage)\\n-\n  [Caching Homebrew installers](https://devcenter.bitrise.io/builds/caching/caching-homebrew-installers/)\\n\\n###\n  Related Steps \\n\\n- [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n-\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2023-05-18T12:01:25.919537441Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: 19807654133026007b9ff208d06d6c3b66efde1a\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: false\n    summary: Name of the formula to install/reinstall. Must be specified when `use_brewfile`\n      is not `yes`\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`. Path must end with `Brewfile`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.12.3/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: \"\\nInstall or upgrade dependencies using Homebrew, a package manager\n  for MacOS. \\n\\n### Configuring the Step \\n\\nHomebrew defines the available packages\n  as formulae. Our Step needs the name of the Homebrew formulae you want to use, either\n  specified as a step input, or from a Brewfile in the project's source.\\n\\nTo specify\n  formulae in the step configuration\\n\\n1. In the **Formula name** input, put the\n  name of the formula you want to download. \\n1. In the **Upgrade formula?** input,\n  set the default behavior for previously installed packages. If the input is set\n  to `yes`, the Step will call `brew reinstall` to upgrade them to the latest version.\\n1.\n  In the **Brew install/reinstall options** input, you can set additional flags for\n  the `brew install` or `brew reinstall` commands. \\n   For the possible options,\n  see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\\n\\nAlternatively\n  you can install formulae using a Brewfile\\n\\n1. Add a `Brewfile` to the root of\n  the project's source. For the format of the Brewfile, see the [Homebrew Bundle documentation](https://github.com/Homebrew/homebrew-bundle#usage)\\n1.\n  Set the **Use a Brewfile to install packages?** input to \\\"yes\\\". \\n1. (optional)\n  Set the **Path to the Brewfile** input if it is not in the root of the project's\n  source\\n\\n### Useful links\\n\\n- [Homebrew documentation](https://docs.brew.sh/Manpage)\\n-\n  [Caching Homebrew installers](https://devcenter.bitrise.io/builds/caching/caching-homebrew-installers/)\\n\\n###\n  Related Steps \\n\\n- [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n-\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2023-06-23T12:10:42.618033739Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: fab2305911fba702b13984571b3f256ecb73245b\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    is_required: false\n    summary: Name of the formula to install/reinstall. Must be specified when `use_brewfile`\n      is not `yes`\n    title: Formula name\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`. Path must end with `Brewfile`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.12.4/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: |-\n  Install or upgrade dependencies using Homebrew, a package manager for MacOS.\n\n  ### Configuring the Step\n\n  Homebrew defines the available packages as formulae. Our Step needs the name of the Homebrew formulae you want to use, either specified as a step input, or from a Brewfile in the project's source.\n\n  To specify formulae in the step configuration\n\n  1. In the **Formula name** input, put the name of the formula you want to download.\n  1. In the **Upgrade formula?** input, set the default behavior for previously installed packages. If the input is set to `yes`, the Step will call `brew reinstall` to upgrade them to the latest version.\n  1. In the **Brew install/reinstall options** input, you can set additional flags for the `brew install` or `brew reinstall` commands.\n\n  For the possible options, see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\n\n  Alternatively you can install formulae using a Brewfile\n\n  1. Add a `Brewfile` to the root of the project's source. For the format of the Brewfile, see the [Homebrew Bundle documentation](https://github.com/Homebrew/homebrew-bundle#usage)\n  1. Set the **Use a Brewfile to install packages?** input to \"yes\".\n  1. (optional) Set the **Path to the Brewfile** input if it is not in the root of the project's source\n\n  ### Useful links\n\n  - [Homebrew documentation](https://docs.brew.sh/Manpage)\n  - [Caching Homebrew installers](https://devcenter.bitrise.io/builds/caching/caching-homebrew-installers/)\n\n  ### Related Steps\n\n  - [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2024-04-25T13:10:22.067116681Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: f03437263660f7e9ec6fe626cdc6e4519e2eebe3\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    description: |-\n      Name of the formulas to install. Multiple formulas can be specified by separating them with a space, e.g. `git-lfs sqlite pipx`\n\n      This input must be specified when `use_brewfile` is `no`\n    is_required: false\n    title: Formulas to install\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`. Path must end with `Brewfile`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- cache_enabled: \"no\"\n  opts:\n    description: |\n      If set to `\"yes\"` the contents of `~/Library/Caches/Homebrew` directory will be cached.\n    is_required: true\n    summary: Should the step collect files to be cached?\n    title: Enable cache?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/0.9.0/step.yml",
    "content": "title: Brew install\nsummary: |\n  Install or upgrade formula with brew\ndescription: |\n  Install or upgrade formula with brew\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2017-10-27T17:22:48.641520695+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: 2f3c953e7178a92e3d05ed67d91a01c181f0675a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Name of the formula to install/upgrade\n    is_expand: true\n    is_required: true\n    summary: Name of the formula to install/upgrade\n    title: Name of the formula to install/upgrade\n    value_options: []\n  packages: null\n- options: null\n  opts:\n    description: |\n      Flags to pass to the bew install/reinstall command.\n\n      `brew install/reinstall [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Options for Brew install/upgrade\n    title: Options for Brew install/upgrade\n    value_options: []\n- opts:\n    description: |\n      If set the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n\n      Otherwise the step calls `brew install [options] [packages]`\n    is_expand: true\n    is_required: false\n    summary: Upgrade formula if previously installed\n    title: Upgrade formula if previously installed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n"
  },
  {
    "path": "steps/brew-install/1.0.0/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: |-\n  Install or upgrade dependencies using Homebrew, a package manager for MacOS.\n\n  ### Configuring the Step\n\n  Homebrew defines the available packages as formulae. Our Step needs the name of the Homebrew formulae you want to use, either specified as a step input, or from a Brewfile in the project's source.\n\n  To specify formulae in the step configuration\n\n  1. In the **Formula name** input, put the name of the formula you want to download.\n  1. In the **Upgrade formula?** input, set the default behavior for previously installed packages. If the input is set to `yes`, the Step will call `brew reinstall` to upgrade them to the latest version.\n  1. In the **Brew install/reinstall options** input, you can set additional flags for the `brew install` or `brew reinstall` commands.\n\n  For the possible options, see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\n\n  Alternatively you can install formulae using a Brewfile\n\n  1. Add a `Brewfile` to the root of the project's source. For the format of the Brewfile, see the [Homebrew Bundle documentation](https://github.com/Homebrew/homebrew-bundle#usage)\n  1. Set the **Use a Brewfile to install packages?** input to \"yes\".\n  1. (optional) Set the **Path to the Brewfile** input if it is not in the root of the project's source\n\n  ### Useful links\n\n  - [Homebrew documentation](https://docs.brew.sh/Manpage)\n\n  ### Related Steps\n\n  - [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2024-04-30T12:38:50.831106751Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: 46c19dbb3454a99bd8988f321bc76cb6e2472f54\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    description: |-\n      Name of the formulas to install. Multiple formulas can be specified by separating them with a space, e.g. `git-lfs sqlite pipx`\n\n      This input must be specified when `use_brewfile` is `no`\n    is_required: false\n    title: Formulas to install\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `no`, the step won't upgrade other **installed packages** that depend on the package to be installed.\n\n      This helps predictability and install times, but sometimes could cause problems with existing installed packages if they are not compatible with the newly installed package (Homebrew is an evergreen package manager by design). More information is available [here](https://docs.brew.sh/FAQ#why-does-brew-upgrade-formula-or-brew-install-formula-also-upgrade-a-bunch-of-other-stuff) and [here](https://docs.brew.sh/Manpage#install-options-formulacask-).\n\n      If you experience a broken package, set this input to `yes`.\n\n      This input controls the `HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` env var.\n    title: Upgrade dependent packages\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade_dependents: \"no\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`. Path must end with `Brewfile`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/1.0.1/step.yml",
    "content": "title: Brew install\nsummary: Install or upgrade dependencies with Homebrew.\ndescription: |-\n  Install or upgrade dependencies using Homebrew, a package manager for MacOS.\n\n  ### Configuring the Step\n\n  Homebrew defines the available packages as formulae. Our Step needs the name of the Homebrew formulae you want to use, either specified as a step input, or from a Brewfile in the project's source.\n\n  To specify formulae in the step configuration\n\n  1. In the **Formula name** input, put the name of the formula you want to download.\n  1. In the **Upgrade formula?** input, set the default behavior for previously installed packages. If the input is set to `yes`, the Step will call `brew reinstall` to upgrade them to the latest version.\n  1. In the **Brew install/reinstall options** input, you can set additional flags for the `brew install` or `brew reinstall` commands.\n\n  For the possible options, see [Homebrew's documentation](https://docs.brew.sh/Manpage#install-options-formulacask).\n\n  Alternatively you can install formulae using a Brewfile\n\n  1. Add a `Brewfile` to the root of the project's source. For the format of the Brewfile, see the [Homebrew Bundle documentation](https://github.com/Homebrew/homebrew-bundle#usage)\n  1. Set the **Use a Brewfile to install packages?** input to \"yes\".\n  1. (optional) Set the **Path to the Brewfile** input if it is not in the root of the project's source\n\n  ### Useful links\n\n  - [Homebrew documentation](https://docs.brew.sh/Manpage)\n\n  ### Related Steps\n\n  - [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-steplib/steps-brew-install\nsource_code_url: https://github.com/bitrise-steplib/steps-brew-install\nsupport_url: https://github.com/bitrise-steplib/steps-brew-install/issues\npublished_at: 2025-11-14T13:11:05.534535404Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-brew-install.git\n  commit: d95cf3095856c807d3f6bb58ce7ff79bb9dd1236\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-brew-install\ninputs:\n- opts:\n    description: |-\n      Name of the formulas to install. Multiple formulas can be specified by separating them with a space, e.g. `git-lfs sqlite pipx`\n\n      This input must be specified when `use_brewfile` is `no`\n    is_required: false\n    title: Formulas to install\n  packages: null\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will upgrade the defined packages by calling `brew reinstall [options] [packages]` command.\n      Otherwise the step calls `brew install [options] [packages]`.\n    summary: Upgrade formula if previously installed?\n    title: Upgrade formula?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade: \"yes\"\n- opts:\n    description: |\n      If set to `no`, the step won't upgrade other **installed packages** that depend on the package to be installed.\n\n      This helps predictability and install times, but sometimes could cause problems with existing installed packages if they are not compatible with the newly installed package (Homebrew is an evergreen package manager by design). More information is available [here](https://docs.brew.sh/FAQ#why-does-brew-upgrade-formula-or-brew-install-formula-also-upgrade-a-bunch-of-other-stuff) and [here](https://docs.brew.sh/Manpage#install-options-formulacask-).\n\n      If you experience a broken package, set this input to `yes`.\n\n      This input controls the `HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` env var.\n    title: Upgrade dependent packages\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upgrade_dependents: \"no\"\n- opts:\n    description: |\n      If set to `\"yes\"`, the step will install packages in the Brewfile by running `brew bundle`. If no Brewfile path is set, it assumes a Brewfile exists in the current directory.\n    is_required: false\n    summary: Installs packages using a Brewfile\n    title: Use a Brewfile to install packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_brewfile: \"no\"\n- brewfile_path: null\n  opts:\n    description: |\n      If set, `use_brewfile` must be set to `yes`. Path must end with `Brewfile`\n    is_required: false\n    summary: Installs packages from a Brewfile at the specified path\n    title: Path to the Brewfile\n- options: null\n  opts:\n    description: |\n      Flags to pass to the brew install/reinstall command.\n      `brew install/reinstall [options] [packages]`\n    summary: Flags to pass to the brew install/reinstall command.\n    title: Brew install/reinstall options\n- opts:\n    is_required: true\n    summary: Should the step print more detailed log?\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/brew-install/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/browserstack-app-live-upload/1.0.0/step.yml",
    "content": "title: Browserstack App Live Upload\nsummary: |\n  Uploads your APK or IPA to Browserstack for interactive app testing.\ndescription: |\n  Uploads your APK or IPA to Browserstack for interactive app testing. You can find your username and access key at https://www.browserstack.com/accounts/settings\nwebsite: https://github.com/andrewmarmion/bitrise-step-browserstack-app-live-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-browserstack-app-live-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-browserstack-app-live-upload/issues\npublished_at: 2019-10-10T16:51:25.06298+01:00\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-browserstack-app-live-upload.git\n  commit: d7100a123466d55bae8f93d536bdd3c7be8a4dca\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_ipa_filepath: null\n  opts:\n    description: |\n      The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH or $BITRISE\\_IPA\\_PATH.\n    is_expand: true\n    is_required: true\n    summary: Location of the IPA or APK that you want to upload.\n    title: Location of the IPA or APK\n- browserstack_username: null\n  opts:\n    description: |\n      The username you use to log into Browserstack.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The username you use to log into Browserstack.\n    title: Browserstack Username\n- browserstack_access_key: null\n  opts:\n    description: |\n      The access key for your Browserstack account.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The access key for your Browserstack account.\n    title: Browserstack Access Key\n"
  },
  {
    "path": "steps/browserstack-app-live-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/browserstack-bitrise-espresso-step/1.0.0/step.yml",
    "content": "title: BrowserStack App Automate - Espresso\nsummary: |\n  Run your Espresso tests on BrowserStack App Automate\ndescription: |\n  Run your Espresso tests on BrowserStack App Automate. This step collects the built APK from $BITRISE_APK_PATH  and test apk from `$BITRISE_TEST_APK_PATH` Environment Variables\nwebsite: https://www.browserstack.com/app-automate\nsource_code_url: https://github.com/browserstack/browserstack-bitrise-espresso-step\nsupport_url: https://github.com/browserstack/browserstack-bitrise-espresso-step/issues\npublished_at: 2022-08-16T20:35:40.110892+05:30\nsource:\n  git: https://github.com/browserstack/browserstack-bitrise-espresso-step.git\n  commit: 180c566836b44627cf5bbb28e4e9acb771877b2e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/browserstack/browserstack-bitrise-espresso-step\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_username: null\n  opts:\n    category: Authentication\n    description: Username of the BrowserStack account\n    is_required: true\n    is_sensitive: true\n    summary: Username for the BrowserStack account\n    title: BrowserStack username\n- browserstack_accesskey: null\n  opts:\n    category: Authentication\n    description: Access Key of the BrowserStack account\n    is_required: true\n    is_sensitive: true\n    summary: Accesskey for the BrowserStack account\n    title: BrowserStack accesskey\n- android_app_under_test: $BITRISE_APK_PATH\n  opts:\n    category: App & Test Suite\n    description: Path of the app (.apk) file\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: Android app under test\n- espresso_test_suite: $BITRISE_TEST_APK_PATH\n  opts:\n    category: App & Test Suite\n    description: Path of the test suite (.apk) file\n    is_expand: true\n    is_required: true\n    summary: Path to the testsuite .apk file\n    title: Espresso test suite\n- devices_list: null\n  opts:\n    category: Devices\n    description: \"Name of one or more device-OS combination in new line \\nFor example:\\n\\n`Samsung\n      Galaxy S9 Plus-9.0`\\n\\n`Google Pixel 3a-9.0`\\n\"\n    is_expand: true\n    is_required: true\n    summary: Name of one or more device-OS combination in new line from the [device list](https://www.browserstack.com/list-of-browsers-and-platforms/app_automate). \n    title: Devices\n- instrumentation_logs: \"true\"\n  opts:\n    category: Debug logs\n    description: Instrumentation logs are a comprehensive record of your Espresso\n      test executions that helps you identify all the steps executed in the test.\n    summary: Enable Instrumentation Logs generated by AndroidJunitRunner\n    title: Instrumentation logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- network_logs: \"false\"\n  opts:\n    category: Debug logs\n    description: 'Network logs captures the network traffic, latency, HTTP requests\n      and responses in the HAR (HTTP Archive) format. '\n    summary: Enable network traffic, latency, HTTP requests and responses in the HAR\n      (HTTP Archive) format\n    title: Network Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- device_logs: \"false\"\n  opts:\n    category: Debug logs\n    description: Device logs are system logs specific to your application generated\n      by Android logcat that help you debug any test crashes.\n    summary: Enable logs generated by Android logcat\n    title: Android logcat logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- debug_screenshots: \"false\"\n  opts:\n    category: Debug logs\n    description: Screenshots makes it easier to identify the exact step in your test\n      where the failure occurred, especially any layout or design-related issues.\n    summary: Capture the screenshots in your tests\n    title: Capture Screenshots\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Debug logs\n    description: Video recording helps you view the entire test execution and helps\n      debug any failed test.\n    summary: Enable the video of the test run\n    title: Video recording\n    value_options:\n    - \"true\"\n    - \"false\"\n  video_recording: \"true\"\n- opts:\n    category: Test Configuration\n    description: A project name helps you group multiple Espresso test executions\n      under a single project.\n    summary: Project name of the tests.\n    title: Project name\n  project: null\n- filter_test: null\n  opts:\n    category: Test Configuration\n    description: |\n      Provide key-value pairs of filters to run tests: class, package, annotation, size\n\n      For example: class com.foo.AddToCartClass,class com.foo.CheckoutClass\n\n      package com.foo\n\n      Learn more.(https://www.browserstack.com/docs/app-automate/espresso/select-test-cases)\n    summary: Provide a comma-separated list of class or test names followed by supported\n      filtering strategies.\n    title: Filter tests\n- opts:\n    category: Test Configuration\n    description: Test sharding splits and run test cases into different group called\n      shards. This behaviour is helpful when your test-suite has a large number of\n      test cases. [Learn more.](https://www.browserstack.com/docs/app-automate/espresso/test-sharding)\n    summary: 'Enable test sharding to split tests cases into different groups instead\n      of running them sequentially. '\n    title: Test sharding\n  use_test_sharding: null\n- clear_app_data: \"false\"\n  opts:\n    category: Test Configuration\n    description: An app might need clean state of the app storage to run every test\n      case. Use this feature  to clear app data after every test run. [Learn more.](https://www.browserstack.com/docs/app-automate/espresso/clear-app-data)\n    summary: Enable to clear app data after every test run\n    title: Clear app data\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Test Configuration\n    description: The single runner invocation feature runs each test case in a single\n      process that reduces the overall build time. [Learn more.](https://www.browserstack.com/docs/app-automate/espresso/single-runner-invocation)\n    summary: Enable to run each test case in a single process to reduce overall build\n      time.\n    title: Single runner invocation\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_single_runner_invocation: \"false\"\n- opts:\n    category: Test Configuration\n    description: A callback URL helps you enable BrowserStack notify you upon the\n      completion of all builds under a given project. You will receive a callback\n      if no new builds triggered for 5 minutes and all existing builds have completed\n      their execution.This parameter requires that the Project name parameter also\n      be set.\n    summary: 'A callback URL to enable BrowserStack notify about completion of build\n      under a given project. '\n    title: Notify project status\n  project_notify_url: null\n- opts:\n    category: Test Configuration\n    description: Enable local testing to retrieve app data hosted on local/private\n      servers\n    summary: Enable local testing to retrieve app data hosted on local/private servers\n    title: Local testing\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_local: \"false\"\n- opts:\n    category: Test Configuration\n    description: A mock web server mocks the behavior of an actual remote server.\n      This makes it easy to test different scenarios without depending on your remote\n      server and without having to make changes to your remote server. Local Testing,\n      Network logs, and IP geolocation will not work if you are using a mock server.\n      [Learn more.](https://www.browserstack.com/docs/app-automate/espresso/use-mock-server)\n    summary: Enable to mock a web server in your espresso tests to mock your API responses.\n      Learn more.\n    title: Mock server\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_mock_server: \"false\"\n- api_params: null\n  opts:\n    category: Test Configuration\n    description: |\n      New line key-value pairs of capabilities provided by BrowserStack.\n\n      For example:\n      coverage=true\n\n      geoLocation=CN\n\n      [Learn about more capabilities.](https://www.browserstack.com/docs/app-automate/api-reference/espresso/builds#execute-a-build)\n    summary: New line key-value pairs of capabilities provided by BrowserStack.\n    title: Test capabilities\n- check_build_status: \"true\"\n  opts:\n    category: Test Configuration\n    description: Wait for build results\n    summary: Wait for BrowserStack to complete the execution and get the test results\n    title: Build Status\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BROWSERSTACK_BUILD_URL: null\n  opts:\n    description: BrowserStack Dashboard url for the executed build\n    summary: BrowserStack Dashboard url for the executed build\n    title: BrowserStack Dashboard url\n- BROWSERSTACK_BUILD_STATUS: null\n  opts:\n    description: |\n      Status of the executed build. Check values [here:] (https://www.browserstack.com/docs/app-automate/espresso/view-test-results)\n    summary: BrowserStack build status\n    title: BrowserStack Build Status\n"
  },
  {
    "path": "steps/browserstack-bitrise-espresso-step/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/browserstack-bitrise-xcui-step/1.0.0/step.yml",
    "content": "title: BrowserStack App Automate - XCUITest\nsummary: |\n  Run your XCUITest tests on BrowserStack App Automate\ndescription: |\n  Run your XCUITest tests on BrowserStack App Automate. This step collects the built IPA from `$BITRISE_IPA_PATH`  and test suite from `$BITRISE_BUNDLE_PATH` Environment Variables\nwebsite: https://github.com/browserstack/browserstack-bitrise-xcui-step\nsource_code_url: https://github.com/browserstack/browserstack-bitrise-xcui-step\nsupport_url: https://github.com/browserstack/browserstack-bitrise-xcui-step/issues\npublished_at: 2022-08-16T20:11:30.271023+05:30\nsource:\n  git: https://github.com/browserstack/browserstack-bitrise-xcui-step.git\n  commit: cd90e8eafe9e9130ea792e98b76b9e79eedde467\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/browserstack/browserstack-bitrise-xcui-step\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_username: null\n  opts:\n    description: Username of the BrowserStack account\n    is_required: true\n    is_sensitive: true\n    summary: Username for the BrowserStack account\n    title: BrowserStack username\n- browserstack_accesskey: null\n  opts:\n    description: Access Key of the BrowserStack account\n    is_required: true\n    is_sensitive: true\n    summary: Accesskey for the BrowserStack account\n    title: BrowserStack accesskey\n- app_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the app (.ipa) file\n    is_expand: true\n    is_required: true\n    summary: Path to the app (.ipa) file\n    title: iOS app under test\n- opts:\n    description: Path of the output bundle (.app) file. Add either the `$BITRISE_TEST_BUNDLE_PATH`\n      (generated from the \"Xcode Build for testing for iOS\" step) or the absolute\n      path of the output bundle file\n    is_expand: true\n    is_required: true\n    summary: Path of the output bundle file\n    title: XCUI test suite\n  xcui_test_suite: $BITRISE_TEST_BUNDLE_PATH\n- devices_list: null\n  opts:\n    description: \"Name of one or more device-OS combination in new line \\n For example:\\n\n      \\n `iPhone 11-13`\\n \\n `iPhone XS-15`\\n \\n [View supported device-OS combinations](https://www.browserstack.com/list-of-browsers-and-platforms/app_automate)\\n\"\n    is_expand: true\n    is_required: true\n    summary: Name of one or more device-OS combination in new line from the [device\n      list](https://www.browserstack.com/list-of-browsers-and-platforms/app_automate).\n    title: Devices\n- instrumentation_logs: \"true\"\n  opts:\n    category: Debug logs\n    description: Instrumentation logs are a comprehensive record of your XCUITest\n      test executions that helps you identify all the steps executed in the test.\n    summary: Generate instrumentation logs of the test session\n    title: Instrumentation logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- network_logs: \"false\"\n  opts:\n    category: Debug logs\n    description: 'Network logs captures the network traffic, latency, HTTP requests\n      and responses in the HAR (HTTP Archive) format. '\n    summary: Generate network logs of your XCUI test sessions to capture network traffic,\n      latency, etc.\n    title: Network Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- device_logs: \"false\"\n  opts:\n    category: Debug logs\n    description: Device logs are system logs specific to your application generated\n      by iOS device\n    summary: Generate device logs\n    title: Device Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- debug_screenshots: \"false\"\n  opts:\n    category: Debug logs\n    description: Screenshots makes it easier to identify the exact step in your test\n      where the failure occurred, especially any layout or design-related issues.\n    summary: Capture the screenshots of the test execution\n    title: Capture Screenshots\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Debug logs\n    description: Video recording helps you view the entire test execution and helps\n      debug any failed test.\n    summary: Record video of the test execution\n    title: Video recording\n    value_options:\n    - \"true\"\n    - \"false\"\n  video_recording: \"true\"\n- opts:\n    category: Test Configuration\n    description: A project name helps you group multiple XCUITest test executions\n      under a single project.\n    summary: Project name of the tests.\n    title: Project name\n  project: null\n- opts:\n    category: Test Configuration\n    description: |\n      A callback URL helps you enable BrowserStack notify you upon the completion of all builds under a given project. You will receive a callback if no new builds triggered for 5 minutes and all existing builds have completed their execution.\n\n      This parameter requires that the **Project name** parameter also be set.\n    summary: A callback URL to enable BrowserStack notify about completion of build\n      under a given project.\n    title: Notify project status\n  project_notify_url: null\n- opts:\n    category: Test Configuration\n    description: Enable local testing to retrieve app data hosted on local/private\n      servers\n    summary: Enable local testing to retrieve app data hosted on local/private servers\n    title: Local testing\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_local: \"false\"\n- opts:\n    category: Test Configuration\n    description: |\n      Enable test sharding to split tests cases into different groups instead of running them sequentially.\n      Add the sharding value json here. Examples:\n      Input for only-testing strategy:\n      `{\"numberOfShards\": 2, \"mapping\": [{\"name\": \"Shard 1\", \"strategy\": \"only-testing\", \"values\": [\"SampleXCUITestsClass/testAlert\", \"SampleXCUITestsClass/testText\"]}, {\"name\": \"Shard 2\", \"strategy\": \"only-testing\", \"values\": [\"SampleXCUITestsClass/testLogin\"]}]}`\n\n      Input for skip-testing strategy:\n      `{\"numberOfShards\": 2, \"mapping\": [{\"name\": \"Shard 1\", \"strategy\": \"skip-testing\", \"values\": [\"SampleXCUITestsClass/testAlert\"]}, {\"name\": \"Shard 2\", \"strategy\": \"skip-testing\", \"values\": [\"SampleXCUITestsClass/testText\"]}]}`\n    summary: Test sharding splits and run test cases into different group called shards.\n      This behaviour is helpful when your test-suite has a large number of test cases.\n      [Learn more.](https://www.browserstack.com/docs/app-automate/xcuitest/test-sharding)\n    title: Test sharding\n  use_test_sharding: null\n- filter_test: null\n  opts:\n    category: Test Configuration\n    description: |\n      Provide a comma-separated list of class or test names followed by supported filters: \"only-testing\" and \"skip-testing\".\n\n      For example: `only-testing SampleXCUITestsClass/testAlertTest`\n\n      [Learn more](https://www.browserstack.com/docs/app-automate/xcuitest/select-test-cases)\n    summary: Provide a comma-separated list of class or test names followed by supported\n      filtering strategies.\n    title: Filter test cases\n- opts:\n    category: Test Configuration\n    description: Enable to run runtime discoverable tests or dynamic tests. [Learn\n      more](https://www.browserstack.com/docs/app-automate/xcuitest/dynamic-tests)\n    summary: Enable to run runtime discoverable tests or dynamic tests. [Learn more](https://www.browserstack.com/docs/app-automate/xcuitest/dynamic-tests)\n    title: Run dynamic tests\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_dynamic_tests: \"false\"\n- check_build_status: \"true\"\n  opts:\n    category: Test Configuration\n    description: 'Enable to let the pipeline wait for build results '\n    summary: 'Enable to let the pipeline wait for build results '\n    title: Build Status\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_params: null\n  opts:\n    category: Test Configuration\n    description: |\n      New line key-value pairs of capabilities provided by BrowserStack.\n\n      For example:\n      coverage=true\n\n      geoLocation=CN\n\n      [Learn about more capabilities.](https://www.browserstack.com/docs/app-automate/api-reference/xcuitest/builds#execute-a-build)\n    summary: New line key-value pairs of capabilities provided by BrowserStack.\n    title: Test capabilities\noutputs:\n- BROWSERSTACK_BUILD_URL: null\n  opts:\n    description: BrowserStack Dashboard url for the executed build\n    summary: BrowserStack Dashboard url for the executed build\n    title: BrowserStack Dashboard url\n- BROWSERSTACK_BUILD_STATUS: null\n  opts:\n    description: Status of the executed build. Check values [here:] (https://www.browserstack.com/docs/app-automate/xcui/view-test-results)\n    summary: BrowserStack build status\n    title: BrowserStack Build Status\n"
  },
  {
    "path": "steps/browserstack-bitrise-xcui-step/1.0.1/step.yml",
    "content": "title: BrowserStack App Automate - XCUITest\nsummary: |\n  Run your XCUITest tests on BrowserStack App Automate\ndescription: |\n  Run your XCUITest tests on BrowserStack App Automate. This step collects the built IPA from `$BITRISE_IPA_PATH`  and test suite from `$BITRISE_BUNDLE_PATH` Environment Variables\nwebsite: https://github.com/browserstack/browserstack-bitrise-xcui-step\nsource_code_url: https://github.com/browserstack/browserstack-bitrise-xcui-step\nsupport_url: https://github.com/browserstack/browserstack-bitrise-xcui-step/issues\npublished_at: 2022-09-22T20:38:19.560375+05:30\nsource:\n  git: https://github.com/browserstack/browserstack-bitrise-xcui-step.git\n  commit: 480c4bbdb8eb57b7eb5a995228d9b76d646ad0c2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/browserstack/browserstack-bitrise-xcui-step\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_username: null\n  opts:\n    description: Username of the BrowserStack account\n    is_required: true\n    is_sensitive: true\n    summary: Username for the BrowserStack account\n    title: BrowserStack username\n- browserstack_accesskey: null\n  opts:\n    description: Access Key of the BrowserStack account\n    is_required: true\n    is_sensitive: true\n    summary: Accesskey for the BrowserStack account\n    title: BrowserStack accesskey\n- app_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the app (.ipa) file\n    is_expand: true\n    is_required: true\n    summary: Path to the app (.ipa) file\n    title: iOS app under test\n- opts:\n    description: Path of the output bundle (.app) file. Add either the $BITRISE_TEST_BUNDLE_PATH\n      (generated from the \"Xcode Build for testing for iOS\" step) or the absolute\n      path of the output bundle file\n    is_expand: true\n    is_required: true\n    summary: Path of the output bundle file\n    title: XCUI test suite\n  xcui_test_suite: $BITRISE_TEST_BUNDLE_PATH\n- devices_list: null\n  opts:\n    description: \"Name of one or more device-OS combination in new line \\n For example:\\n\n      \\n `iPhone 11-13`\\n \\n `iPhone XS-15`\\n \\n [View supported device-OS combinations](https://www.browserstack.com/list-of-browsers-and-platforms/app_automate)\\n\"\n    is_expand: true\n    is_required: true\n    summary: Name of one or more device-OS combination in new line from the [device\n      list](https://www.browserstack.com/list-of-browsers-and-platforms/app_automate).\n    title: Devices\n- instrumentation_logs: \"true\"\n  opts:\n    category: Debug logs\n    description: Instrumentation logs are a comprehensive record of your XCUITest\n      test executions that helps you identify all the steps executed in the test.\n    summary: Generate instrumentation logs of the test session\n    title: Instrumentation logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- network_logs: \"false\"\n  opts:\n    category: Debug logs\n    description: 'Network logs captures the network traffic, latency, HTTP requests\n      and responses in the HAR (HTTP Archive) format. '\n    summary: Generate network logs of your XCUI test sessions to capture network traffic,\n      latency, etc.\n    title: Network Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- device_logs: \"false\"\n  opts:\n    category: Debug logs\n    description: Device logs are system logs specific to your application generated\n      by iOS device\n    summary: Generate device logs\n    title: Device Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- debug_screenshots: \"false\"\n  opts:\n    category: Debug logs\n    description: Screenshots makes it easier to identify the exact step in your test\n      where the failure occurred, especially any layout or design-related issues.\n    summary: Capture the screenshots of the test execution\n    title: Capture Screenshots\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Debug logs\n    description: Video recording helps you view the entire test execution and helps\n      debug any failed test.\n    summary: Record video of the test execution\n    title: Video recording\n    value_options:\n    - \"true\"\n    - \"false\"\n  video_recording: \"true\"\n- opts:\n    category: Test Configuration\n    description: A project name helps you group multiple XCUITest test executions\n      under a single project.\n    summary: Project name of the tests.\n    title: Project name\n  project: null\n- opts:\n    category: Test Configuration\n    description: |\n      A callback URL helps you enable BrowserStack notify you upon the completion of all builds under a given project. You will receive a callback if no new builds triggered for 5 minutes and all existing builds have completed their execution.\n\n      This parameter requires that the **Project name** parameter also be set.\n    summary: A callback URL to enable BrowserStack notify about completion of build\n      under a given project.\n    title: Notify project status\n  project_notify_url: null\n- opts:\n    category: Test Configuration\n    description: Enable local testing to retrieve app data hosted on local/private\n      servers\n    summary: Enable local testing to retrieve app data hosted on local/private servers\n    title: Local testing\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_local: \"false\"\n- opts:\n    category: Test Configuration\n    description: |\n      Enable test sharding to split tests cases into different groups instead of running them sequentially.\n      Add the sharding value json here. Examples:\n      Input for only-testing strategy:\n      `{\"numberOfShards\": 2, \"mapping\": [{\"name\": \"Shard 1\", \"strategy\": \"only-testing\", \"values\": [\"SampleXCUITestsClass/testAlert\", \"SampleXCUITestsClass/testText\"]}, {\"name\": \"Shard 2\", \"strategy\": \"only-testing\", \"values\": [\"SampleXCUITestsClass/testLogin\"]}]}`\n\n      Input for skip-testing strategy:\n      `{\"numberOfShards\": 2, \"mapping\": [{\"name\": \"Shard 1\", \"strategy\": \"skip-testing\", \"values\": [\"SampleXCUITestsClass/testAlert\"]}, {\"name\": \"Shard 2\", \"strategy\": \"skip-testing\", \"values\": [\"SampleXCUITestsClass/testText\"]}]}`\n    summary: Test sharding splits and run test cases into different group called shards.\n      This behaviour is helpful when your test-suite has a large number of test cases.\n      [Learn more.](https://www.browserstack.com/docs/app-automate/xcuitest/test-sharding)\n    title: Test sharding\n  use_test_sharding: null\n- filter_test: null\n  opts:\n    category: Test Configuration\n    description: |\n      Provide a comma-separated list of class or test names followed by supported filters: \"only-testing\" and \"skip-testing\".\n\n      For example: `only-testing SampleXCUITestsClass/testAlertTest`\n\n      [Learn more](https://www.browserstack.com/docs/app-automate/xcuitest/select-test-cases)\n    summary: Provide a comma-separated list of class or test names followed by supported\n      filtering strategies.\n    title: Filter test cases\n- opts:\n    category: Test Configuration\n    description: Enable to run runtime discoverable tests or dynamic tests. [Learn\n      more](https://www.browserstack.com/docs/app-automate/xcuitest/dynamic-tests)\n    summary: Enable to run runtime discoverable tests or dynamic tests. [Learn more](https://www.browserstack.com/docs/app-automate/xcuitest/dynamic-tests)\n    title: Run dynamic tests\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_dynamic_tests: \"false\"\n- check_build_status: \"true\"\n  opts:\n    category: Test Configuration\n    description: 'Enable to let the pipeline wait for build results '\n    summary: 'Enable to let the pipeline wait for build results '\n    title: Build Status\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_params: null\n  opts:\n    category: Test Configuration\n    description: |\n      New line key-value pairs of capabilities provided by BrowserStack.\n\n      For example:\n      coverage=true\n\n      geoLocation=CN\n\n      [Learn about more capabilities.](https://www.browserstack.com/docs/app-automate/api-reference/xcuitest/builds#execute-a-build)\n    summary: New line key-value pairs of capabilities provided by BrowserStack.\n    title: Test capabilities\noutputs:\n- BROWSERSTACK_BUILD_URL: null\n  opts:\n    description: BrowserStack Dashboard url for the executed build\n    summary: BrowserStack Dashboard url for the executed build\n    title: BrowserStack Dashboard url\n- BROWSERSTACK_BUILD_STATUS: null\n  opts:\n    description: |\n      Status of the executed build. Check values [here:] (https://www.browserstack.com/docs/app-automate/xcui/view-test-results)\n    summary: BrowserStack build status\n    title: BrowserStack Build Status\n"
  },
  {
    "path": "steps/browserstack-bitrise-xcui-step/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/browserstack-espresso-app-automate/0.3.0/step.yml",
    "content": "title: BrowserStack App Automate\nsummary: |\n  Upload an app apk and an Espresso test apk to BrowserStack and run tests with App Automate.\ndescription: |\n  This step uploads a provided app apk and  test apk to browserstack.  It then will execute the Espresso Tests for the provided apks in BrowserStacks app automate.\nwebsite: https://github.com/fernanthonies/bitrise-step-browserstack-espresso-app-automate\nsource_code_url: https://github.com/fernanthonies/bitrise-step-browserstack-espresso-app-automate\nsupport_url: https://github.com/fernanthonies/bitrise-step-browserstack-espresso-app-automate/issues\npublished_at: 2019-01-30T11:33:43.007202-06:00\nsource:\n  git: https://github.com/fernanthonies/bitrise-step-browserstack-espresso-app-automate.git\n  commit: 9bd67786b66b7c0618379fd53926d20a66ad7a8a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The .apk file for your app\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app, likely generated by the Android Build for UI Testing step\n    is_expand: true\n    is_required: true\n    summary: Path to the espresso test .apk file\n    title: Test suite apk path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- browserstack_username: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for browserstack\n    title: BrowserStack username\n- browserstack_access_key: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for browserstack\n    title: BrowserStack access key\n- browserstack_device_list: '\"Google Pixel-8.0\", \"Google Pixel-7.1\"'\n  opts:\n    category: Automated Test Options\n    description: |\n      Provide a comma separated list of Device and OS version you want to run your tests on, with quotes. Acceptable format example: \"Google Pixel-8.0\", \"Google Pixel-7.1\"\n      A list of available device and OS combinations can be found [here](https://www.browserstack.com/list-of-browsers-and-platforms/app_automate)\n    is_expand: true\n    is_required: true\n    summary: A comma separated list of desired test devices\n    title: Device list\n- browserstack_package: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter to test only some selected packages. Acceptable format is: \"com.browserstack\", \"com.browserstack1\"\n    is_required: false\n    summary: Set this parameter to test only some selected packages.\n    title: Package\n- browserstack_class: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter to test only some selected classes. Acceptable format is: \"com.browserstack.class1\", \"com.browserstack.class2\"\n    is_required: false\n    summary: |\n      Set this parameter to test only some selected classes.\n    title: Class\n- browserstack_annotation: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter if you want to run tests only for particular annotations.  Acceptable format is: \"P1\", \"P2\"\n    is_required: false\n    summary: |\n      Set this parameter if you want to run tests only for particular annotations.\n    title: Annotation\n- browserstack_size: null\n  opts:\n    category: Automated Test Options\n    description: Set this parameter if you want to run tests that have @SmallTest,\n      @MediumTest and @LargeTest annotations.\n    is_required: false\n    summary: |\n      Set this parameter if you want to run tests that have @SmallTest, @MediumTest and @LargeTest annotations.\n    title: Size\n- browserstack_device_logs: \"true\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter if you want to enable the device logs\n    is_required: false\n    summary: Set this parameter if you want to enable the device logs\n    title: Device Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_video: \"true\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter if you want to enable the video of the test run.\n      By default it's set to true.\n    is_required: false\n    summary: Set this parameter if you want to enable the video of the test run.\n    title: Video\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter if you want to enable local testing. By default\n      its set to false\n    is_required: false\n    summary: Set this parameter if you want to enable local testing.\n    title: Local\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_identifier: null\n  opts:\n    category: Automated Test Options\n    description: If you are using same account to test multiple applications, you\n      can setup named connection using the localIdentifier option.\n    is_required: false\n    summary: If you are using same account to test multiple applications, you can\n      setup named connection using the localIdentifier option.\n    title: Local Identifier\n- browserstack_gps_location: 40.730610,-73.935242\n  opts:\n    category: Automated Test Options\n    description: |\n      Required if you want to simulate the location of the device to a particular GPS location. Acceptable range for latitude is -90 to +90 and for longitude is -180 to +180. Example: \"40.730610,-73.935242\"\n    is_required: false\n    summary: Required if you want to simulate the location of the device to a particular\n      GPS location.\n    title: GPS Location\n- browserstack_language: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter if you want to change the language to test localization of your App. Example: \"fr\"\n    is_required: false\n    summary: |\n      Set this parameter if you want to change the language to test localization of your App.\n    title: Language\n- browserstack_locale: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter if you want to change the locale to test localization of your App. Example: \"fr\"\n    is_required: false\n    summary: |\n      Set this parameter if you want to change the locale to test localization of your App.\n    title: Locale\n- callback_url: null\n  opts:\n    category: Automated Test Options\n    is_expand: false\n    is_required: false\n    summary: Set the callback url where we can send a confirmation once your test\n      execution is completed\n    title: Callback Url\noutputs:\n- BUILD_ID: null\n  opts:\n    summary: The Build ID for this test run in BrowserStack\n    title: Build ID\n"
  },
  {
    "path": "steps/browserstack-espresso-app-automate/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/browserstack-upload/0.1.3/step.yml",
    "content": "title: browserstack-upload\nsummary: |\n  Upload APK/IPA files to BrowserStack's App Automate\ndescription: |\n  Upload your build files to Browserstack for remote device testing. Upload your IPA/APK file to BrowserStack App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/marcelkalveram/bitrise-step-browserstack-upload\nsource_code_url: https://github.com/marcelkalveram/bitrise-step-browserstack-upload\nsupport_url: https://github.com/marcelkalveram/bitrise-step-browserstack-upload/issues\npublished_at: 2018-10-15T23:42:44.579154284+02:00\nsource:\n  git: https://github.com/marcelkalveram/bitrise-step-browserstack-upload.git\n  commit: cbc5f80199abad4bc78289eb42d8a815b2f57f4a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- browserstack_username: $BROWSERSTACK_USERNAME\n  opts:\n    description: |\n      The username you use to log into your Browserstack account\n    is_required: true\n    is_sensitive: true\n    summary: Your Browserstack username\n    title: Browserstack username\n- browserstack_access_key: $BROWSERSTACK_ACCESS_KEY\n  opts:\n    description: |\n      The access key you use to log into your Browserstack account\n    is_required: true\n    is_sensitive: true\n    summary: Your Browserstack access key\n    title: Browserstack access key\noutputs:\n- BROWSERSTACK_APP_URL: null\n  opts:\n    description: \"The app url returned by Browserstack App Automate with the following\n      format \\\"bs://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: Browserstack App Automate App URL\n"
  },
  {
    "path": "steps/browserstack-upload/0.1.4/step.yml",
    "content": "title: browserstack-upload\nsummary: |\n  Upload APK/IPA files to BrowserStack's App Automate\ndescription: |\n  Upload your build files to Browserstack for remote device testing. Upload your IPA/APK file to BrowserStack App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/marcelkalveram/bitrise-step-browserstack-upload\nsource_code_url: https://github.com/marcelkalveram/bitrise-step-browserstack-upload\nsupport_url: https://github.com/marcelkalveram/bitrise-step-browserstack-upload/issues\npublished_at: 2019-10-25T11:17:57.226211+02:00\nsource:\n  git: https://github.com/marcelkalveram/bitrise-step-browserstack-upload.git\n  commit: 3a619edc2f2f8faf3d83e3739bd33ff41a3bb647\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to BrowserStack, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- browserstack_username: $BROWSERSTACK_USERNAME\n  opts:\n    description: |\n      The username you use to log into your Browserstack account\n    is_required: true\n    is_sensitive: true\n    summary: Your Browserstack username\n    title: Browserstack username\n- browserstack_access_key: $BROWSERSTACK_ACCESS_KEY\n  opts:\n    description: |\n      The access key you use to log into your Browserstack account\n    is_required: true\n    is_sensitive: true\n    summary: Your Browserstack access key\n    title: Browserstack access key\n- custom_id: null\n  opts:\n    summary: Custom id to distinguish uploads in case there are multiple apps\n    title: Custom Id\noutputs:\n- BROWSERSTACK_APP_URL: null\n  opts:\n    description: \"The app url returned by Browserstack App Automate with the following\n      format \\\"bs://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: Browserstack App Automate App URL\n"
  },
  {
    "path": "steps/browserstack-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/build-number-adjust/1.0.0/step.yml",
    "content": "title: Adjust BuildNumber\nsummary: Adjust the $BITRISE_BUILD_NUMBER\ndescription: |-\n  In some cases you want to use the $BITRISE_BUILD_NUMBER for setting version info, but for some reason\n  you want to add, substract or just change the variable (for example when migrating from another build system\n  and you already have a certain build number to start with)\nwebsite: https://github.com/stefandevo/bitrise-buildnumberadjust-step\nsource_code_url: https://github.com/stefandevo/bitrise-buildnumberadjust-step\nsupport_url: https://github.com/stefandevo/bitrise-buildnumberadjust-step/issues\npublished_at: 2017-05-02T18:37:35.12670068+02:00\nsource:\n  git: https://github.com/stefandevo/bitrise-buildnumberadjust-step.git\n  commit: 93b784999facfcea50c464aada4dde0e3905eeb1\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- change: null\n  opts:\n    description: |\n      Just change the $BITRISE_BUILD_NUMBER value\n    is_expand: true\n    is_required: false\n    title: Change Build Number\n- increase: null\n  opts:\n    description: |\n      Add a certain number to the current $BITRISE_BUILD_NUMBER value\n    is_expand: true\n    is_required: false\n    title: Increase Value\n- decrease: null\n  opts:\n    description: |\n      Substract a certain number of to the current $BITRISE_BUILD_NUMBER value\n    is_expand: true\n    is_required: false\n    title: Decrease Value\noutputs:\n- BITRISE_BUILD_NUMBER: null\n  opts:\n    description: \"\"\n    title: Adjusted BITRISE_BUILD_NUMBER value\n"
  },
  {
    "path": "steps/build-number-adjust/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2024-06-20\"\ndeprecate_notes: \"This community step is no longer available as a GitHub repo.\"\n"
  },
  {
    "path": "steps/build-router-start/0.10.0/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2018-08-31T08:04:26.041242318Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 55c041556b225b93a798e70edef26445d01ee2e9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.11.1/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2018-09-12T15:03:57.427775503Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: dfa563784e24268a58c4b7d8776d834ca48e928f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.11.2/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2019-02-01T15:16:43.274008692Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 864b685e012a125341898f3875e7594e16cf8d4c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.11.3/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2019-07-16T06:28:31.292700808Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 9a51d1a3693bf151a051708038b97ab0750b3574\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.12.0/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2020-05-13T09:30:37.006516905Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 8c34093730ac44ce30902d8865e99492ae1df41d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.12.1/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2020-05-19T11:57:56.901341958Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: ce48df3e40459dc74439a42f0ff4b8d06003cd65\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.13.0/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2020-07-20T18:30:56.144691991Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 7b09287ecbe125d0e309de222e2317a8d762a3f0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      This is where the artifacts will be saved to so you can access them in the workflow\n    is_required: false\n    is_sensitive: false\n    summary: This is where the artifacts will be saved to if wait_for_builds == true\n    title: Path to save the Artifacts in (leave empty to not save artifacts)\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.0/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2020-08-05T16:47:54.606978353Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 63a29bf46ca6346a88030bd5208163e241cff8f8\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      This is where the artifacts will be saved to so you can access them in the workflow\n    is_required: false\n    is_sensitive: false\n    summary: This is where the artifacts will be saved to if wait_for_builds == true\n    title: Path to save the Artifacts in (leave empty to not save artifacts)\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all if any fail\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.1/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2021-07-01T21:37:18.587148995Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 91166a6c3f4c7d1bdbfc8ebd1178eb879a7a3b9e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered workflows.\n    title: Environments to share\n- opts:\n    description: Should the step wait for the builds to be finished?\n    is_required: false\n    summary: Should the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      This is where the artifacts will be saved to so you can access them in the workflow\n    is_required: false\n    is_sensitive: false\n    summary: This is where the artifacts will be saved to if wait_for_builds == true\n    title: Path to save the Artifacts in (leave empty to not save artifacts)\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all if any fail\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.2/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts a new build with the specified Workflow(s).\ndescription: \"The Step starts a new build of the same app. In combination with the\n  **Bitrise Wait for Build** Step you can use this Step to start multiple builds that\n  run in parallel at the same time. You can put this Step in a Workflow that is triggered\n  by a code push or pull request and use this Step to trigger multiple other builds\n  at the same time. \\n\\nTo do that, you need multiple concurrencies - at least two!\n  You also need a Personal Access Token to use the Step: [check out our guide](https://devcenter.bitrise.io/getting-started/account-security/#generating-personal-access-tokens-manually)\n  on how to generate the token.\\n\\n### Configuring the Step \\n\\nBefore you run a build\n  with this Step, make sure you have your Personal Access Token stored in a [Secret\n  Environment Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nNote\n  that all builds you trigger using this Step will have the same build number! \\n\\n\n  \\  1. Set up at least two Workflows in the Workflow Editor: one will contain the\n  Step, the other will be triggered by the Step. \\n     You can set up as many Workflows\n  as you wish: your number of concurrencies limit the number of Workflows you can\n  run simultaneously.\\n  2. Add the **Bitrise Start Build** Step to the part of the\n  Workflow where you want to trigger another build. \\n  3. Add the Secret Env Var\n  storing your Personal Access Token to the **Bitrise Access Token** input of the\n  **Bitrise Start Build** Step: click the **Select secret variable** button, and choose\n  the key you created.\\n  4. Find the **Workflows** input of the **Bitrise Start Build**\n  Step, and add the Workflow(s) you want to run. \\n  5. In the **Environments to share**\n  input, add Environment Variables (Env Vars) that you want to share between the builds\n  triggered by the Step. \\n  6. Add the **Bitrise Wait for Build** Step to the end\n  of Workflow that contains the **Bitrise Start Build** Step. \\n  7. Add the Secret\n  Env Var storing your Personal Access Token to the **Bitrise Access Token** input\n  of the **Bitrise Wait for Build** Step: click the **Select secret variable** button,\n  and choose the key you created.\\n  8. In the **Build slugs** input, define the builds\n  for the Step. \\n     The build slugs you need are stored by the **Bitrise Start\n  Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the builds\n  defined by the slugs are running, the Step will hold the build it is running in.\n  The build will fail if any of the builds included in the Step fail.\\n  9. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n     - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n       The value of the input\n  must be an actual, existing path, ending with `/`. The `BITRISE_DEPLOY_DIR` Environment\n  Variable is NOT a valid value.\\n     - Set the **Abort all builds if one fails**\n  input to either `yes` or `no`. \\n     Please note that the build artifacts of child\n  Workflows - Workflows triggered by this Step - will be only available if the child\n  Workflow contains a **Deploy to Bitrise.io** Step.\\n\\n### Troubleshooting \\n\\n-\n  Make sure you have both the **Bitrise Start Build** and the **Bitrise Wait for Build**\n  Steps in the right place in your initial Workflow. \\n- Always check all your builds:\n  if your concurrencies are taken up by other builds, this Step cannot start new ones.\n  \\n- Your Personal Access Token can expire! Make sure it's still valid - without\n  it, you can't start new builds with this Step.  \\n\\n### Useful links \\n\\n- [Starting\n  parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-Workflows/)\\n\\n###\n  Related Steps \\n\\n- [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-start)\\n-\n  [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n- [Build Status\n  Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2021-09-13T11:58:51.344829553Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 0e94e7718f8cf0d5c457591c6f64dee70f591049\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The Workflow(s) to start. One Workflow per line.\n    is_required: true\n    summary: The Workflow(s) to start. One Workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered Workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered Workflows.\n    title: Environments to share\n- opts:\n    description: Should the Step wait for the builds to be finished?\n    is_required: false\n    summary: Should the Step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: \"The path where build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`. \\n\\nPlease note that the path must be an actual,\n      existing path, ending with `/`. The `BITRISE_DEPLOY_DIR` Environment Variable\n      is NOT a valid value. \\n\\nNote that when this Step triggers a Workflow, the\n      artifacts of the triggered Workflow are only available to the Workflow that\n      contains this Step, and not other Workflows. \\nThe triggered Workflow MUST have\n      a **Deploy to Bitrise.io** Step to deploy build artifacts!\\n\"\n    is_required: false\n    is_sensitive: false\n    summary: The path that the build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if any of them\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.3/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts a new build with the specified Workflow(s).\ndescription: \"The Step starts a new build of the same app. In combination with the\n  **Bitrise Wait for Build** Step you can use this Step to start multiple builds that\n  run in parallel at the same time. You can put this Step in a Workflow that is triggered\n  by a code push or pull request and use this Step to trigger multiple other builds\n  at the same time. \\n\\nTo do that, you need multiple concurrencies - at least two!\n  You also need a Personal Access Token to use the Step: [check out our guide](https://devcenter.bitrise.io/getting-started/account-security/#generating-personal-access-tokens-manually)\n  on how to generate the token.\\n\\nIf manual build approval is enabled for the project,\n  this step won't be able to start new builds automatically.\\n\\n### Configuring the\n  Step \\n\\nBefore you run a build with this Step, make sure you have your Personal\n  Access Token stored in a [Secret Environment Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nNote\n  that all builds you trigger using this Step will have the same build number! \\n\\n\n  \\  1. Set up at least two Workflows in the Workflow Editor: one will contain the\n  Step, the other will be triggered by the Step. \\n     You can set up as many Workflows\n  as you wish: your number of concurrencies limit the number of Workflows you can\n  run simultaneously.\\n  2. Add the **Bitrise Start Build** Step to the part of the\n  Workflow where you want to trigger another build. \\n  3. Add the Secret Env Var\n  storing your Personal Access Token to the **Bitrise Access Token** input of the\n  **Bitrise Start Build** Step: click the **Select secret variable** button, and choose\n  the key you created.\\n  4. Find the **Workflows** input of the **Bitrise Start Build**\n  Step, and add the Workflow(s) you want to run. \\n  5. In the **Environments to share**\n  input, add Environment Variables (Env Vars) that you want to share between the builds\n  triggered by the Step. \\n  6. Add the **Bitrise Wait for Build** Step to the end\n  of Workflow that contains the **Bitrise Start Build** Step. \\n  7. Add the Secret\n  Env Var storing your Personal Access Token to the **Bitrise Access Token** input\n  of the **Bitrise Wait for Build** Step: click the **Select secret variable** button,\n  and choose the key you created.\\n  8. In the **Build slugs** input, define the builds\n  for the Step. \\n     The build slugs you need are stored by the **Bitrise Start\n  Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the builds\n  defined by the slugs are running, the Step will hold the build it is running in.\n  The build will fail if any of the builds included in the Step fail.\\n  9. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n     - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n       The value of the input\n  must be an actual, existing path, ending with `/`. The `BITRISE_DEPLOY_DIR` Environment\n  Variable is NOT a valid value.\\n     - Set the **Abort all builds if one fails**\n  input to either `yes` or `no`. \\n     Please note that the build artifacts of child\n  Workflows - Workflows triggered by this Step - will be only available if the child\n  Workflow contains a **Deploy to Bitrise.io** Step.\\n\\n### Troubleshooting \\n\\n-\n  Make sure you have both the **Bitrise Start Build** and the **Bitrise Wait for Build**\n  Steps in the right place in your initial Workflow. \\n- Always check all your builds:\n  if your concurrencies are taken up by other builds, this Step cannot start new ones.\n  \\n- Your Personal Access Token can expire! Make sure it's still valid - without\n  it, you can't start new builds with this Step.  \\n\\n### Useful links \\n\\n- [Starting\n  parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\n  \\n\\n\\n### Related Steps \\n\\n- [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-start)\\n-\n  [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n- [Build Status\n  Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2021-09-27T14:10:57.908078119Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 65b6db13972d0b8e491565455b334df766348e9d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The Workflow(s) to start. One Workflow per line.\n    is_required: true\n    summary: The Workflow(s) to start. One Workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered Workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered Workflows.\n    title: Environments to share\n- opts:\n    description: Should the Step wait for the builds to be finished?\n    is_required: false\n    summary: Should the Step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: \"The path where build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`. \\n\\nPlease note that the path must be an actual,\n      existing path, ending with `/`. The `BITRISE_DEPLOY_DIR` Environment Variable\n      is NOT a valid value. \\n\\nNote that when this Step triggers a Workflow, the\n      artifacts of the triggered Workflow are only available to the Workflow that\n      contains this Step, and not other Workflows. \\nThe triggered Workflow MUST have\n      a **Deploy to Bitrise.io** Step to deploy build artifacts!\\n\"\n    is_required: false\n    is_sensitive: false\n    summary: The path that the build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if any of them\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.4/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts a new build with the specified Workflow(s).\ndescription: \"The Step starts a new build of the same app. In combination with the\n  **Bitrise Wait for Build** Step you can use this Step to start multiple builds that\n  run in parallel at the same time. You can put this Step in a Workflow that is triggered\n  by a code push or pull request and use this Step to trigger multiple other builds\n  at the same time. \\n\\nTo do that, you need multiple concurrencies - at least two!\n  You also need a Personal Access Token to use the Step: [check out our guide](https://devcenter.bitrise.io/getting-started/account-security/#generating-personal-access-tokens-manually)\n  on how to generate the token.\\n\\nIf manual build approval is enabled for the project,\n  this step won't be able to start new builds automatically.\\n\\n### Configuring the\n  Step \\n\\nBefore you run a build with this Step, make sure you have your Personal\n  Access Token stored in a [Secret Environment Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nNote\n  that all builds you trigger using this Step will have the same build number! \\n\\n\n  \\  1. Set up at least two Workflows in the Workflow Editor: one will contain the\n  Step, the other will be triggered by the Step. \\n     You can set up as many Workflows\n  as you wish: your number of concurrencies limit the number of Workflows you can\n  run simultaneously.\\n  2. Add the **Bitrise Start Build** Step to the part of the\n  Workflow where you want to trigger another build. \\n  3. Add the Secret Env Var\n  storing your Personal Access Token to the **Bitrise Access Token** input of the\n  **Bitrise Start Build** Step: click the **Select secret variable** button, and choose\n  the key you created.\\n  4. Find the **Workflows** input of the **Bitrise Start Build**\n  Step, and add the Workflow(s) you want to run. \\n  5. In the **Environments to share**\n  input, add Environment Variables (Env Vars) that you want to share between the builds\n  triggered by the Step. \\n  6. Add the **Bitrise Wait for Build** Step to the end\n  of Workflow that contains the **Bitrise Start Build** Step. \\n  7. Add the Secret\n  Env Var storing your Personal Access Token to the **Bitrise Access Token** input\n  of the **Bitrise Wait for Build** Step: click the **Select secret variable** button,\n  and choose the key you created.\\n  8. In the **Build slugs** input, define the builds\n  for the Step. \\n     The build slugs you need are stored by the **Bitrise Start\n  Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the builds\n  defined by the slugs are running, the Step will hold the build it is running in.\n  The build will fail if any of the builds included in the Step fail.\\n  9. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n     - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n       The value of the input\n  must be an actual, existing path, ending with `/`.\\n     - Set the **Abort all builds\n  if one fails** input to either `yes` or `no`. \\n     Please note that the build\n  artifacts of child Workflows - Workflows triggered by this Step - will be only available\n  if the child Workflow contains a **Deploy to Bitrise.io** Step.\\n\\n### Troubleshooting\n  \\n\\n- Make sure you have both the **Bitrise Start Build** and the **Bitrise Wait\n  for Build** Steps in the right place in your initial Workflow. \\n- Always check\n  all your builds: if your concurrencies are taken up by other builds, this Step cannot\n  start new ones. \\n- Your Personal Access Token can expire! Make sure it's still\n  valid - without it, you can't start new builds with this Step.  \\n\\n### Useful links\n  \\n\\n- [Starting parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\n  \\n\\n\\n### Related Steps \\n\\n- [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-start)\\n-\n  [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n- [Build Status\n  Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2022-03-01T10:38:55.83004121Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 18c3e2b28690a1eb958b5968adc89a4affe51d7e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The Workflow(s) to start. One Workflow per line.\n    is_required: true\n    summary: The Workflow(s) to start. One Workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered Workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered Workflows.\n    title: Environments to share\n- opts:\n    description: Should the Step wait for the builds to be finished?\n    is_required: false\n    summary: Should the Step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: \"The path where build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`. \\n\\nNote that when this Step triggers a Workflow,\n      the artifacts of the triggered Workflow are only available to the Workflow that\n      contains this Step, and not other Workflows. \\nThe triggered Workflow MUST have\n      a **Deploy to Bitrise.io** Step to deploy build artifacts!\\n\"\n    is_required: false\n    is_sensitive: false\n    summary: The path that the build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if any of them\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.5/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts a new build with the specified Workflow(s).\ndescription: \"The Step starts a new build of the same app with specified Workflow(s).\n  On its own, the Step can be used to start multiple builds that run in parallel.\n  In combination with the **Bitrise Wait for Build** Step, you can also add additional\n  Steps to run in parallel while the triggered builds are running. For an example,\n  check out our [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html##)\n  Workflow Recipe. \\nYou can put this Step in a Workflow that is triggered by a code\n  push or pull request and use this Step to trigger multiple other builds at the same\n  time. \\n\\nTo do that, you need multiple concurrencies - at least two! You also need\n  a Personal Access Token to use the Step: [check out our guide](https://devcenter.bitrise.io/getting-started/account-security/#generating-personal-access-tokens-manually)\n  on how to generate the token.\\n\\nIf manual build approval is enabled for the project,\n  this step won't be able to start new builds automatically.\\n\\n### Configuring the\n  Step \\n\\nBefore you run a build with this Step, make sure you have your Personal\n  Access Token stored in a [Secret Environment Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nNote\n  that all builds you trigger using this Step will have the same build number! \\n\\n\n  \\  1. Set up at least two Workflows in the Workflow Editor: one will contain the\n  Step, the other will be triggered by the Step. \\n     You can set up as many Workflows\n  as you wish: your number of concurrencies limit the number of Workflows you can\n  run simultaneously.\\n  2. Add the **Bitrise Start Build** Step to the part of the\n  Workflow where you want to trigger another build. \\n  3. Add the Secret Env Var\n  storing your Personal Access Token to the **Bitrise Access Token** input of the\n  **Bitrise Start Build** Step: click the **Select secret variable** button, and choose\n  the key you created.\\n  4. Find the **Workflows** input of the **Bitrise Start Build**\n  Step, and add the Workflow(s) you want to run. \\n  5. In the **Environments to share**\n  input, add Environment Variables (Env Vars) that you want to share between the builds\n  triggered by the Step.\\n  6. (Optional) You can set the **Wait for builds** input\n  to `true` if you would like to pause the current build until the triggered build(s)\n  are finished. \\n  7. (Optional) You can add any Step you would like to run in parallel\n  while the triggered Workflow(s) are running in the parent Workflow.\\n     Make sure\n  to add the **Bitrise Wait for Build** Step to the end of Workflow.\\n  8. Add the\n  Secret Env Var storing your Personal Access Token to the **Bitrise Access Token**\n  input of the **Bitrise Wait for Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n  9. In the **Build slugs** input, define\n  the builds for the Step. \\n     The build slugs you need are stored by the **Bitrise\n  Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the\n  builds defined by the slugs are running, the Step will hold the build it is running\n  in. The build will fail if any of the builds included in the Step fail.\\n  10. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n     - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n       The value of the input\n  must be an actual, existing path, ending with `/`.\\n     - Set the **Abort all builds\n  if one fails** input to either `yes` or `no`. \\n     Please note that the build\n  artifacts of child Workflows - Workflows triggered by this Step - will be only available\n  if the child Workflow contains a **Deploy to Bitrise.io** Step.\\n\\n### Troubleshooting\n  \\n\\n- Make sure you have both the **Bitrise Start Build** and the **Bitrise Wait\n  for Build** Steps in the right place in your initial Workflow. \\n- Always check\n  all your builds: if your concurrencies are taken up by other builds, this Step cannot\n  start new ones. \\n- Your Personal Access Token can expire! Make sure it's still\n  valid - without it, you can't start new builds with this Step.  \\n\\n### Useful links\n  \\n\\n- [Starting parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\\n-\n  [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html##)\n  \\ \\n\\n\\n### Related Steps \\n\\n- [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-wait)\\n-\n  [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n- [Build Status\n  Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2022-08-01T15:43:30.713049078Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 931fe89f1d06a049e1c996b119c84f5dc3f9ba58\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The Workflow(s) to start. One Workflow per line.\n    is_required: true\n    summary: The Workflow(s) to start. One Workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: \"The keys of the envs which will be shared with the triggered Workflows\\n\\n\\n**FORMAT**\n      Seperate the keys with new line. E.g: \\n`ENV_1\\nENV_2\\nENV_3`\"\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered Workflows.\n    title: Environments to share\n- opts:\n    description: Should the Step wait for the builds to be finished?\n    is_required: false\n    summary: Should the Step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: \"The path where build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`. \\n\\nNote that when this Step triggers a Workflow,\n      the artifacts of the triggered Workflow are only available to the Workflow that\n      contains this Step, and not other Workflows. \\nThe triggered Workflow MUST have\n      a **Deploy to Bitrise.io** Step to deploy build artifacts!\\n\"\n    is_required: false\n    is_sensitive: false\n    summary: The path that the build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if any of them\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.6/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts a new build with the specified Workflow(s).\ndescription: \"The Step starts a new build of the same app with specified Workflow(s).\n  On its own, the Step can be used to start multiple builds that run in parallel.\n  In combination with the **Bitrise Wait for Build** Step, you can also add additional\n  Steps to run in parallel while the triggered builds are running. For an example,\n  check out our [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html##)\n  Workflow Recipe. \\nYou can put this Step in a Workflow that is triggered by a code\n  push or pull request and use this Step to trigger multiple other builds at the same\n  time. \\n\\nTo do that, you need multiple concurrencies - at least two! You also need\n  a Personal Access Token to use the Step: [check out our guide](https://devcenter.bitrise.io/getting-started/account-security/#generating-personal-access-tokens-manually)\n  on how to generate the token.\\n\\nIf manual build approval is enabled for the project,\n  this step won't be able to start new builds automatically.\\n\\n### Configuring the\n  Step \\n\\nBefore you run a build with this Step, make sure you have your Personal\n  Access Token stored in a [Secret Environment Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nNote\n  that all builds you trigger using this Step will have the same build number! \\n\\n\n  \\  1. Set up at least two Workflows in the Workflow Editor: one will contain the\n  Step, the other will be triggered by the Step. \\n     You can set up as many Workflows\n  as you wish: your number of concurrencies limit the number of Workflows you can\n  run simultaneously.\\n  2. Add the **Bitrise Start Build** Step to the part of the\n  Workflow where you want to trigger another build. \\n  3. Add the Secret Env Var\n  storing your Personal Access Token to the **Bitrise Access Token** input of the\n  **Bitrise Start Build** Step: click the **Select secret variable** button, and choose\n  the key you created.\\n  4. Find the **Workflows** input of the **Bitrise Start Build**\n  Step, and add the Workflow(s) you want to run. \\n  5. In the **Environments to share**\n  input, add Environment Variables (Env Vars) that you want to share between the builds\n  triggered by the Step.\\n  6. (Optional) You can set the **Wait for builds** input\n  to `true` if you would like to pause the current build until the triggered build(s)\n  are finished. \\n  7. (Optional) You can add any Step you would like to run in parallel\n  while the triggered Workflow(s) are running in the parent Workflow.\\n     Make sure\n  to add the **Bitrise Wait for Build** Step to the end of Workflow.\\n  8. Add the\n  Secret Env Var storing your Personal Access Token to the **Bitrise Access Token**\n  input of the **Bitrise Wait for Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n  9. In the **Build slugs** input, define\n  the builds for the Step. \\n     The build slugs you need are stored by the **Bitrise\n  Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the\n  builds defined by the slugs are running, the Step will hold the build it is running\n  in. The build will fail if any of the builds included in the Step fail.\\n  10. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n     - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n       The value of the input\n  must be an actual, existing path, ending with `/`.\\n     - Set the **Abort all builds\n  if one fails** input to either `yes` or `no`. \\n     Please note that the build\n  artifacts of child Workflows - Workflows triggered by this Step - will be only available\n  if the child Workflow contains a **Deploy to Bitrise.io** Step.\\n\\n### Troubleshooting\n  \\n\\n- Make sure you have both the **Bitrise Start Build** and the **Bitrise Wait\n  for Build** Steps in the right place in your initial Workflow. \\n- Always check\n  all your builds: if your concurrencies are taken up by other builds, this Step cannot\n  start new ones. \\n- Your Personal Access Token can expire! Make sure it's still\n  valid - without it, you can't start new builds with this Step.  \\n\\n### Useful links\n  \\n\\n- [Starting parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\\n-\n  [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html##)\n  \\ \\n\\n\\n### Related Steps \\n\\n- [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-wait)\\n-\n  [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n- [Build Status\n  Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2022-08-09T10:07:04.465910714Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: b134fc58b80f0761ee6c4e324f91b5540152a12b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The Workflow(s) to start. One Workflow per line.\n    is_required: true\n    summary: The Workflow(s) to start. One Workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: |-\n      The keys of the envs which will be shared with the triggered Workflows.\n\n\n      **FORMAT** Seperate the keys with new line. E.g:\n\n      `ENV_1`\n\n      `ENV_2`\n\n      `ENV_3`\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered Workflows.\n    title: Environments to share\n- opts:\n    description: Should the Step wait for the builds to be finished?\n    is_required: false\n    summary: Should the Step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: \"The path where build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`. \\n\\nNote that when this Step triggers a Workflow,\n      the artifacts of the triggered Workflow are only available to the Workflow that\n      contains this Step, and not other Workflows. \\nThe triggered Workflow MUST have\n      a **Deploy to Bitrise.io** Step to deploy build artifacts!\\n\"\n    is_required: false\n    is_sensitive: false\n    summary: The path that the build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if any of them\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.14.7/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts a new build with the specified Workflow(s).\ndescription: |-\n  The Step starts a new build of the same app with specified Workflow(s). On its own, the Step can be used to start multiple builds that run in parallel. In combination with the **Bitrise Wait for Build** Step, you can also add additional Steps to run in parallel while the triggered builds are running. For an example, check out our [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html##) Workflow Recipe.\n  You can put this Step in a Workflow that is triggered by a code push or pull request and use this Step to trigger multiple other builds at the same time.\n\n  To do that, you need multiple concurrencies - at least two! You also need a Personal Access Token to use the Step: [check out our guide](https://devcenter.bitrise.io/getting-started/account-security/#generating-personal-access-tokens-manually) on how to generate the token.\n\n  If manual build approval is enabled for the project, this step won't be able to start new builds automatically.\n\n  ### Configuring the Step\n\n  Before you run a build with this Step, make sure you have your Personal Access Token stored in a [Secret Environment Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\n\n  Note that all builds you trigger using this Step will have the same build number!\n\n     1. Set up at least two Workflows in the Workflow Editor: one will contain the Step, the other will be triggered by the Step.\n       You can set up as many Workflows as you wish: your number of concurrencies limit the number of Workflows you can run simultaneously.\n    2. Add the **Bitrise Start Build** Step to the part of the Workflow where you want to trigger another build.\n    3. Add the Secret Env Var storing your Personal Access Token to the **Bitrise Access Token** input of the **Bitrise Start Build** Step: click the **Select secret variable** button, and choose the key you created.\n    4. Find the **Workflows** input of the **Bitrise Start Build** Step, and add the Workflow(s) you want to run.\n    5. In the **Environments to share** input, add Environment Variables (Env Vars) that you want to share between the builds triggered by the Step.\n    6. (Optional) You can set the **Wait for builds** input to `true` if you would like to pause the current build until the triggered build(s) are finished.\n    7. (Optional) You can add any Step you would like to run in parallel while the triggered Workflow(s) are running in the parent Workflow.\n       Make sure to add the **Bitrise Wait for Build** Step to the end of Workflow.\n    8. Add the Secret Env Var storing your Personal Access Token to the **Bitrise Access Token** input of the **Bitrise Wait for Build** Step: click the **Select secret variable** button, and choose the key you created.\n    9. In the **Build slugs** input, define the builds for the Step.\n       The build slugs you need are stored by the **Bitrise Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the builds defined by the slugs are running, the Step will hold the build it is running in. The build will fail if any of the builds included in the Step fail.\n    10. Optionally, you can save the build artifacts from the builds and configure the Step to abort all builds if any of the builds fail:\n       - In **The path of the build artifacts** input, set where you'd like to save the artifacts.\n         The value of the input must be an actual, existing path, ending with `/`.\n       - Set the **Abort all builds if one fails** input to either `yes` or `no`.\n       Please note that the build artifacts of child Workflows - Workflows triggered by this Step - will be only available if the child Workflow contains a **Deploy to Bitrise.io** Step.\n\n  ### Troubleshooting\n\n  - Make sure you have both the **Bitrise Start Build** and the **Bitrise Wait for Build** Steps in the right place in your initial Workflow.\n  - Always check all your builds: if your concurrencies are taken up by other builds, this Step cannot start new ones.\n  - Your Personal Access Token can expire! Make sure it's still valid - without it, you can't start new builds with this Step.\n\n  ### Useful links\n\n  - [Starting parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\n  - [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html##)\n\n  ### Related Steps\n\n  - [Bitrise Wait for Build](https://www.bitrise.io/integrations/steps/build-router-wait)\n  - [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\n  - [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2024-11-15T10:06:10.256582766Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 47e940d4e0867b61e93459b3d2b8caabc33ae4ec\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: |\n      Your access token\n\n      To acquire a `Personal Access Token` for your user, sign in with that user on [bitrise.io](https://bitrise.io),\n      go to your `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security) on the left side.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- opts:\n    description: The Workflow(s) to start. One Workflow per line.\n    is_required: true\n    summary: The Workflow(s) to start. One Workflow per line.\n    title: Workflows\n  workflows: null\n- environment_key_list: null\n  opts:\n    description: |-\n      The keys of the envs which will be shared with the triggered Workflows.\n\n      **FORMAT** Seperate the keys with new line. E.g:\n\n      `ENV_1`\n\n      `ENV_2`\n\n      `ENV_3`\n    is_expand: false\n    is_required: false\n    summary: The keys of the envs which will be shared with the triggered Workflows.\n    title: Environments to share\n- opts:\n    description: Should the Step wait for the builds to be finished?\n    is_required: false\n    summary: Should the Step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      The path where build artifacts will be saved to if the **Wait for builds** input is set to `true`.\n\n      Note that when this Step triggers a Workflow, the artifacts of the triggered Workflow are only available to the Workflow that contains this Step, and not other Workflows.\n      The triggered Workflow MUST have a **Deploy to Bitrise.io** Step to deploy build artifacts!\n    is_required: false\n    is_sensitive: false\n    summary: The path that the build artifacts will be saved to if the **Wait for\n      builds** input is set to `true`.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if any of them\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/0.9.0/step.yml",
    "content": "title: Bitrise Start Build\nsummary: Starts the given workflows in the same app\ndescription: Starts the given workflows in the same app\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-start/issues\npublished_at: 2018-04-19T16:17:00.302411204+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-start.git\n  commit: 52e6fb7e14e7a9e9c327f0e627dc3a34c5ed7cc0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-start\nis_always_run: false\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token that has access to the app in you want to run\n      workflows.\\n\\nTo acquire a Personal Access Token for your user, sign in with\n      that user on [bitrise.io](https://bitrise.io),  \\ngo to your Account Settings\n      page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    summary: Your access token that has access to the app in you want to run workflows.\n    title: Bitrise Access Token\n- opts:\n    description: The workflow(s) to start. One workflow per line.\n    is_required: true\n    summary: The workflow(s) to start. One workflow per line.\n    title: Workflows\n  workflows: null\n- opts:\n    description: Shall the step wait for the builds to be finished?\n    is_required: false\n    summary: Shall the step wait for the builds to be finished?\n    title: Wait for builds\n    value_options:\n    - \"false\"\n    - \"true\"\n  wait_for_builds: \"false\"\noutputs:\n- ROUTER_STARTED_BUILD_SLUGS: null\n  opts:\n    description: Newline separated list of started build slugs.\n    summary: Newline separated list of started build slugs.\n    title: Started Build Slugs\n"
  },
  {
    "path": "steps/build-router-start/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/build-router-wait/0.10.0/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2020-05-13T09:47:52.501673394Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 228e3592e85beaf6e7bacb8f564bd2651ae2193f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.10.1/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2020-05-19T13:37:04.878962882Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 97ec5358a6295397b74f617895fd70057093bbb3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.11.0/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2020-07-20T18:29:50.046353452Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 44aeeefb8aec15f878ae38d20045202cd8a3309d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      This is where the artifacts will be saved to so you can access them in the workflow\n    is_required: false\n    is_sensitive: false\n    summary: This is where the artifacts will be saved to\n    title: Path to save the Artifacts in (leave empty to not save artifacts)\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.12.0/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2020-08-05T16:50:40.533100729Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: b79b54d67c22cd0b6d9c5701a2acc74698d249b5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      This is where the artifacts will be saved to so you can access them in the workflow\n    is_required: false\n    is_sensitive: false\n    summary: This is where the artifacts will be saved to\n    title: Path to save the Artifacts in (leave empty to not save artifacts)\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any build fails\n    is_required: true\n    is_sensitive: false\n    title: Abort all if any fail\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.12.1/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: The Step pauses the current build until another running build is finished.\ndescription: \"\\\"The Step pauses the current build until another running build or builds\n  are finished. The Step checks statuses of the builds defined in the Step. The builds\n  are defined in the **Build slugs** input: you can add these slugs manually but the\n  typical use case is to use the Environment Variable exported by the **Bitrise Start\n  Build** Step. \\n\\n As long as the builds defined by the slugs are running, the Step\n  will hold the build it is running in. The build will fail if any of the builds included\n  in the Step fail.\\n \\n ### Configuring the Step \\n \\n Before you run a build with\n  this Step, make sure you have your Personal Access Token stored in a [Secret Environment\n  Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\n  \\n This Step is generally used in combination with the **Bitrise Start Build** Step\n  which starts other builds in parallel with the current one. The build that triggered\n  the parallel builds needs to wait for those builds to finish in order to report\n  a successful or a failed build: this Step ensures the build is on hold until the\n  other builds are finished.\\n \\n  1. Set up at least two Workflows in the Workflow\n  Editor: one will contain the Step, the other will be triggered by the Step. \\n     You\n  can set up as many Workflows as you wish: your number of concurrencies limit the\n  number of Workflows you can run simultaneously.\\n  2. Add the **Bitrise Start Build**\n  Step to the part of the Workflow where you want to trigger another build. \\n  3.\n  Add the Secret Env Var storing your Personal Access Token to the **Bitrise Access\n  Token** input of the **Bitrise Start Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n  4. Find the **Workflows** input of the\n  **Bitrise Start Build** Step, and add the Workflow(s) you want to run. \\n  5. In\n  the **Environments to share** input, add Environment Variables (Env Vars) that you\n  want to share between the builds triggered by the Step. \\n  6. Add the **Bitrise\n  Wait for Build** Step to the end of Workflow that contains the **Bitrise Start Build**\n  Step. \\n  7. Add the Secret Env Var storing your Personal Access Token to the **Bitrise\n  Access Token** input of the **Bitrise Wait for Build** Step: click the **Select\n  secret variable** button, and choose the key you created.\\n  8. In the **Build slugs**\n  input, define the builds for the Step. \\n     The build slugs you need are stored\n  by the **Bitrise Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var.\n  As long as the builds defined by the slugs are running, the Step will hold the build\n  it is running in. The build will fail if any of the builds included in the Step\n  fail.\\n  9. Optionally, you can save the build artifacts from the builds and configure\n  the Step to abort all builds if any of the builds fail:\\n     - In **The path of\n  the build artifacts** input, set where you'd like to save the artifacts. \\n     -\n  Set the **Abort all builds if one fails** input to either `yes` or `no`.\\n  \\n  ###\n  Troubleshooting \\n\\n  - Make sure you have both the **Bitrise Start Build** and\n  the **Bitrise Wait for Build** Steps in the right place in your initial Workflow.\n  \\n  - Your Personal Access Token can expire! Make sure it's still valid - without\n  it, you can't start new builds with this Step. \\n\\n  ### Useful links \\n\\n  - [Starting\n  parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\\n\\n\n  \\ ### Related Steps \\n\\n  - [Bitrise Start Build](https://www.bitrise.io/integrations/steps/build-router-wait)\\n\n  \\ - [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n  - [Build\n  Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2020-11-19T16:52:36.027727324Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 97214bff857c3d8d4665a47905ae5ae1c54b2916\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your Personal Access Token\\n\\nTo acquire a Personal Access Token\n      for your user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo\n      to your **Account settings** page, and select the [**Security** tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your Personal Access Token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line. We recommend\n      using the $ROUTER_STARTED_BUILD_SLUGS Env Var exported by the **Bitrise Start\n      Build** Step.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build slugs\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      The provided path is where Bitrise will save your build artifacts so you can access them in the Workflow. Leave it empty if you don't want to save artifacts.\n    is_required: false\n    is_sensitive: false\n    summary: The provided path is where Bitrise will save your build artifacts.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any of the builds fails.\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if one fails\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.12.2/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: The Step pauses the current build until another running build is finished.\ndescription: \"\\\"The Step pauses the current build until another running build or builds\n  are finished. The Step checks statuses of the builds defined in the Step. The builds\n  are defined in the **Build slugs** input: you can add these slugs manually but the\n  typical use case is to use the Environment Variable exported by the **Bitrise Start\n  Build** Step. \\n\\n As long as the builds defined by the slugs are running, the Step\n  will hold the build it is running in. The build will fail if any of the builds included\n  in the Step fail.\\n \\n ### Configuring the Step \\n \\n Before you run a build with\n  this Step, make sure you have your Personal Access Token stored in a [Secret Environment\n  Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\n  \\n This Step is generally used in combination with the **Bitrise Start Build** Step\n  which starts other builds in parallel with the current one. The build that triggered\n  the parallel builds needs to wait for those builds to finish in order to report\n  a successful or a failed build: this Step ensures the build is on hold until the\n  other builds are finished.\\n \\n  1. Set up at least two Workflows in the Workflow\n  Editor: one will contain the Step, the other will be triggered by the Step. \\n     You\n  can set up as many Workflows as you wish: your number of concurrencies limit the\n  number of Workflows you can run simultaneously.\\n  2. Add the **Bitrise Start Build**\n  Step to the part of the Workflow where you want to trigger another build. \\n  3.\n  Add the Secret Env Var storing your Personal Access Token to the **Bitrise Access\n  Token** input of the **Bitrise Start Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n  4. Find the **Workflows** input of the\n  **Bitrise Start Build** Step, and add the Workflow(s) you want to run. \\n  5. In\n  the **Environments to share** input, add Environment Variables (Env Vars) that you\n  want to share between the builds triggered by the Step. \\n  6. Add the **Bitrise\n  Wait for Build** Step to the end of Workflow that contains the **Bitrise Start Build**\n  Step. \\n  7. Add the Secret Env Var storing your Personal Access Token to the **Bitrise\n  Access Token** input of the **Bitrise Wait for Build** Step: click the **Select\n  secret variable** button, and choose the key you created.\\n  8. In the **Build slugs**\n  input, define the builds for the Step. \\n     The build slugs you need are stored\n  by the **Bitrise Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var.\n  As long as the builds defined by the slugs are running, the Step will hold the build\n  it is running in. The build will fail if any of the builds included in the Step\n  fail.\\n  9. Optionally, you can save the build artifacts from the builds and configure\n  the Step to abort all builds if any of the builds fail:\\n     - In **The path of\n  the build artifacts** input, set where you'd like to save the artifacts. \\n     -\n  Set the **Abort all builds if one fails** input to either `yes` or `no`.\\n  \\n  ###\n  Troubleshooting \\n\\n  - Make sure you have both the **Bitrise Start Build** and\n  the **Bitrise Wait for Build** Steps in the right place in your initial Workflow.\n  \\n  - Your Personal Access Token can expire! Make sure it's still valid - without\n  it, you can't start new builds with this Step. \\n\\n  ### Useful links \\n\\n  - [Starting\n  parallel builds with a single Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\\n\\n\n  \\ ### Related Steps \\n\\n  - [Bitrise Start Build](https://www.bitrise.io/integrations/steps/build-router-wait)\\n\n  \\ - [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n  - [Build\n  Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2021-07-01T21:41:37.250796883Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 01e869a1a5950cb19aba8d6932768b4d98c35c57\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your Personal Access Token\\n\\nTo acquire a Personal Access Token\n      for your user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo\n      to your **Account settings** page, and select the [**Security** tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your Personal Access Token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line. We recommend\n      using the $ROUTER_STARTED_BUILD_SLUGS Env Var exported by the **Bitrise Start\n      Build** Step.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build slugs\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      The provided path is where Bitrise will save your build artifacts so you can access them in the Workflow. Leave it empty if you don't want to save artifacts.\n    is_required: false\n    is_sensitive: false\n    summary: The provided path is where Bitrise will save your build artifacts.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any of the builds fails.\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if one fails\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.12.3/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: The Step pauses the current build until another running build is finished.\ndescription: \"The Step pauses the current build until another running build or builds\n  are finished. The Step checks statuses of the builds defined in the Step. The builds\n  are defined in the **Build slugs** input: you can add these slugs manually but the\n  typical use case is to use the Environment Variable exported by the **Bitrise Start\n  Build** Step. \\n\\nAs long as the builds defined by the slugs are running, the Step\n  will hold the build it is running in. The build will fail if any of the builds included\n  in the Step fail.\\n\\n### Configuring the Step \\n\\nBefore you run a build with this\n  Step, make sure you have your Personal Access Token stored in a [Secret Environment\n  Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nThis\n  Step is generally used in combination with the **Bitrise Start Build** Step which\n  starts other builds in parallel with the current one. The build that triggered the\n  parallel builds needs to wait for those builds to finish in order to report a successful\n  or a failed build: this Step ensures the build is on hold until the other builds\n  are finished.\\n\\n 1. Set up at least two Workflows in the Workflow Editor: one will\n  contain the Step, the other will be triggered by the Step. \\n    You can set up\n  as many Workflows as you wish: your number of concurrencies limit the number of\n  Workflows you can run simultaneously.\\n 2. Add the **Bitrise Start Build** Step\n  to the part of the Workflow where you want to trigger another build. \\n 3. Add the\n  Secret Env Var storing your Personal Access Token to the **Bitrise Access Token**\n  input of the **Bitrise Start Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n 4. Find the **Workflows** input of the\n  **Bitrise Start Build** Step, and add the Workflow(s) you want to run. \\n 5. In\n  the **Environments to share** input, add Environment Variables (Env Vars) that you\n  want to share between the builds triggered by the Step.\\n 6. Optionally, you can\n  add any Step you would like to run in parallel while the triggered Workflow(s) are\n  running in the parent Workflow.\\n 7. Add the **Bitrise Wait for Build** Step to\n  the end of Workflow that contains the **Bitrise Start Build** Step. \\n 8. Add the\n  Secret Env Var storing your Personal Access Token to the **Bitrise Access Token**\n  input of the **Bitrise Wait for Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n 9. In the **Build slugs** input, define\n  the builds for the Step. \\n    The build slugs you need are stored by the **Bitrise\n  Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the\n  builds defined by the slugs are running, the Step will hold the build it is running\n  in. The build will fail if any of the builds included in the Step fail.\\n 10. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n    - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n    - Set the **Abort all builds\n  if one fails** input to either `yes` or `no`.\\n \\n ### Troubleshooting \\n\\n - Make\n  sure you have both the **Bitrise Start Build** and the **Bitrise Wait for Build**\n  Steps in the right place in your initial Workflow. \\n - Your Personal Access Token\n  can expire! Make sure it's still valid - without it, you can't start new builds\n  with this Step. \\n\\n ### Useful links \\n\\n - [Starting parallel builds with a single\n  Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\\n\n  - [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html)\\n\\n\n  ### Related Steps \\n\\n - [Bitrise Start Build](https://www.bitrise.io/integrations/steps/build-router-start)\\n\n  - [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n - [Build\n  Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2022-06-29T12:52:41.290660346Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 3fb7b33276a215d31f892979ec231a161fd1cead\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your Personal Access Token\\n\\nTo acquire a Personal Access Token\n      for your user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo\n      to your **Account settings** page, and select the [**Security** tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your Personal Access Token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line. We recommend\n      using the $ROUTER_STARTED_BUILD_SLUGS Env Var exported by the **Bitrise Start\n      Build** Step.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build slugs\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      The provided path is where Bitrise will save your build artifacts so you can access them in the Workflow. Leave it empty if you don't want to save artifacts.\n    is_required: false\n    is_sensitive: false\n    summary: The provided path is where Bitrise will save your build artifacts.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any of the builds fails.\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if one fails\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.12.4/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: The Step pauses the current build until another running build is finished.\ndescription: \"The Step pauses the current build until another running build or builds\n  are finished. The Step checks statuses of the builds defined in the Step. The builds\n  are defined in the **Build slugs** input: you can add these slugs manually but the\n  typical use case is to use the Environment Variable exported by the **Bitrise Start\n  Build** Step. \\n\\nAs long as the builds defined by the slugs are running, the Step\n  will hold the build it is running in. The build will fail if any of the builds included\n  in the Step fail.\\n\\n### Configuring the Step \\n\\nBefore you run a build with this\n  Step, make sure you have your Personal Access Token stored in a [Secret Environment\n  Variable](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/#adding-a-secret-env-var).\\n\\nThis\n  Step is generally used in combination with the **Bitrise Start Build** Step which\n  starts other builds in parallel with the current one. The build that triggered the\n  parallel builds needs to wait for those builds to finish in order to report a successful\n  or a failed build: this Step ensures the build is on hold until the other builds\n  are finished.\\n\\n 1. Set up at least two Workflows in the Workflow Editor: one will\n  contain the Step, the other will be triggered by the Step. \\n    You can set up\n  as many Workflows as you wish: your number of concurrencies limit the number of\n  Workflows you can run simultaneously.\\n 2. Add the **Bitrise Start Build** Step\n  to the part of the Workflow where you want to trigger another build. \\n 3. Add the\n  Secret Env Var storing your Personal Access Token to the **Bitrise Access Token**\n  input of the **Bitrise Start Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n 4. Find the **Workflows** input of the\n  **Bitrise Start Build** Step, and add the Workflow(s) you want to run. \\n 5. In\n  the **Environments to share** input, add Environment Variables (Env Vars) that you\n  want to share between the builds triggered by the Step.\\n 6. Optionally, you can\n  add any Step you would like to run in parallel while the triggered Workflow(s) are\n  running in the parent Workflow.\\n 7. Add the **Bitrise Wait for Build** Step to\n  the end of Workflow that contains the **Bitrise Start Build** Step. \\n 8. Add the\n  Secret Env Var storing your Personal Access Token to the **Bitrise Access Token**\n  input of the **Bitrise Wait for Build** Step: click the **Select secret variable**\n  button, and choose the key you created.\\n 9. In the **Build slugs** input, define\n  the builds for the Step. \\n    The build slugs you need are stored by the **Bitrise\n  Start Build** Step in the `$ROUTER_STARTED_BUILD_SLUGS` Env Var. As long as the\n  builds defined by the slugs are running, the Step will hold the build it is running\n  in. The build will fail if any of the builds included in the Step fail.\\n 10. Optionally,\n  you can save the build artifacts from the builds and configure the Step to abort\n  all builds if any of the builds fail:\\n    - In **The path of the build artifacts**\n  input, set where you'd like to save the artifacts. \\n    - Set the **Abort all builds\n  if one fails** input to either `yes` or `no`.\\n \\n ### Troubleshooting \\n\\n - Make\n  sure you have both the **Bitrise Start Build** and the **Bitrise Wait for Build**\n  Steps in the right place in your initial Workflow. \\n - Your Personal Access Token\n  can expire! Make sure it's still valid - without it, you can't start new builds\n  with this Step. \\n\\n ### Useful links \\n\\n - [Starting parallel builds with a single\n  Workflow](https://devcenter.bitrise.io/builds/triggering-builds/trigger-multiple-workflows/)\\n\n  - [Start builds from a parent Workflow](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/start--parallel--builds-from-the-workflow.html)\\n\\n\n  ### Related Steps \\n\\n - [Bitrise Start Build](https://www.bitrise.io/integrations/steps/build-router-start)\\n\n  - [Bitrise Run](https://www.bitrise.io/integrations/steps/bitrise-run)\\n - [Build\n  Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2022-08-01T17:23:46.121677247Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 7c158823042454c60dd0bb3e5360d4d72c82ef5e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your Personal Access Token\\n\\nTo acquire a Personal Access Token\n      for your user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo\n      to your **Account settings** page, and select the [**Security** tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your Personal Access Token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line. We recommend\n      using the $ROUTER_STARTED_BUILD_SLUGS Env Var exported by the **Bitrise Start\n      Build** Step.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build slugs\n- build_artifacts_save_path: null\n  opts:\n    description: |\n      The provided path is where Bitrise will save your build artifacts so you can access them in the Workflow. Leave it empty if you don't want to save artifacts.\n    is_required: false\n    is_sensitive: false\n    summary: The provided path is where Bitrise will save your build artifacts.\n    title: The path of the build artifacts\n- abort_on_fail: \"no\"\n  opts:\n    description: Abort all started builds if any of the builds fails.\n    is_required: true\n    is_sensitive: false\n    title: Abort all builds if one fails\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: You can enable the verbose log for easier debugging.\n    is_required: true\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/build-router-wait/0.9.0/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2018-04-20T12:34:24.60152076+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: c595844e99d819af24eadec34a4c24cecad804aa\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token that has access to the app in you want to run\n      workflows.\\n\\nTo acquire a Personal Access Token for your user, sign in with\n      that user on [bitrise.io](https://bitrise.io),  \\ngo to your Account Settings\n      page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    summary: Your access token that has access to the app in you want to run workflows.\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n"
  },
  {
    "path": "steps/build-router-wait/0.9.1/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2018-08-31T12:30:11.080236326Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 4ca295ac2f35b74ef1b71d143d26c41a0fcde059\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n"
  },
  {
    "path": "steps/build-router-wait/0.9.2/step.yml",
    "content": "title: Bitrise Wait for Build\nsummary: Waiting for the given builds to be finished\ndescription: Waiting for the given builds to be finished\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-router-wait/issues\npublished_at: 2019-11-08T09:51:52.525417026Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-router-wait.git\n  commit: 9c76b93ba043c0fe99386645820a36eaae9ef21c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-router-wait\nis_always_run: true\nis_skippable: false\ninputs:\n- access_token: null\n  opts:\n    description: \"Your access token\\n\\nTo acquire a `Personal Access Token` for your\n      user, sign in with that user on [bitrise.io](https://bitrise.io),  \\ngo to your\n      `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security)\n      on the left side.\\n\"\n    is_required: true\n    is_sensitive: true\n    summary: Your access token\n    title: Bitrise Access Token\n- buildslugs: $ROUTER_STARTED_BUILD_SLUGS\n  opts:\n    description: The build slug(s) to check. One build slug per line.\n    is_required: true\n    summary: The build slug(s) to check. One build slug per line.\n    title: Build Slugs\n"
  },
  {
    "path": "steps/build-router-wait/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/build-status-change/0.1.1/step.yml",
    "content": "title: Build Status Change\nsummary: Exports environment variables to be able to detect if the currently running\n  build's status has changed to a previous one.\ndescription: Exports environment variables to be able to detect if the currently running\n  build's status has changed to a previous one.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-status-change\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-status-change\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-status-change/issues\npublished_at: 2019-05-03T14:07:35.9285827Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-status-change.git\n  commit: f29dfc0d45da286cf6d37776fab197476bc21cef\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-status-change\nis_always_run: true\nis_skippable: true\ninputs:\n- access_token: null\n  opts:\n    description: Your access token for the account that has access to the Bitrise\n      app.\n    is_required: true\n    is_sensitive: true\n    summary: Your access token for the account that has access to the Bitrise app.\n    title: Bitrise Access Token\noutputs:\n- BUILD_STATUS_CHANGED: null\n  opts:\n    description: True if the actual build status is different from the previous one.\n    summary: True if the actual build status is different from the previous one.\n    title: Build Status Changed\n- PREVIOUS_BUILD_STATUS: null\n  opts:\n    description: Status text of the previous build.\n    summary: Status text of the previous build.\n    title: Previous Build Status\n"
  },
  {
    "path": "steps/build-status-change/0.1.2/step.yml",
    "content": "title: Build Status Change\nsummary: Exports environment variables to be able to detect if the currently running\n  build's status has changed to a previous one.\ndescription: Exports environment variables to be able to detect if the currently running\n  build's status has changed to a previous one.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-build-status-change\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-build-status-change\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-build-status-change/issues\npublished_at: 2019-12-17T09:44:38.58146885Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-build-status-change.git\n  commit: bb65d7e73d2bc668f8712dd7f47e4a1df3ea5237\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-build-status-change\nis_always_run: true\nis_skippable: true\ninputs:\n- access_token: null\n  opts:\n    description: Your access token for the account that has access to the Bitrise\n      app.\n    is_required: true\n    is_sensitive: true\n    summary: Your access token for the account that has access to the Bitrise app.\n    title: Bitrise Access Token\n- opts:\n    description: Enable debug logging, if set to \"yes\".\n    is_required: true\n    summary: Enable debug level logging, if set to \"yes\".\n    title: Enable verbose logging?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  verbose: \"no\"\noutputs:\n- BUILD_STATUS_CHANGED: null\n  opts:\n    description: True if the actual build status is different from the previous one.\n    summary: True if the actual build status is different from the previous one.\n    title: Build Status Changed\n- PREVIOUS_BUILD_STATUS: null\n  opts:\n    description: Status text of the previous build.\n    summary: Status text of the previous build.\n    title: Previous Build Status\n"
  },
  {
    "path": "steps/build-status-change/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/bundle-universal-apk/0.0.2/step.yml",
    "content": "title: Bundle Universal Apk\nsummary: |\n  Generates an universal apk from an app bundle\ndescription: |\n  Runs a bundletool that gets an app bundle path and generates an universal apk that it can be upload to alternative app stores or test platforms.\nwebsite: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsource_code_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsupport_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk/issues\npublished_at: 2019-01-24T15:12:40.106954+01:00\nsource:\n  git: https://github.com/ch4vi/bitrise-step-bundle-universal-apk.git\n  commit: 9d6aa9a9987b71eb2f160af8db92839488e04321\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file `.aab`. You can build the bundle running `:bundleRelease` gradle task\n      Format examples:\n      - `/path/to/my/app.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)`'\n    title: Build artifact path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- keystore_alias_password: $BITRISEIO_ANDROID_KEYSTORE_ALIAS_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias password\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |\n      You can upload this apk to alternative app stores or your test platform\n    summary: This is the path to the universal apk signed with the passed keystore\n    title: Path to the universal apk\n"
  },
  {
    "path": "steps/bundle-universal-apk/0.0.3/step.yml",
    "content": "title: Bundle Universal Apk\nsummary: |\n  Generates an universal apk from an app bundle\ndescription: |\n  Runs a bundletool that gets an app bundle path and generates an universal apk that it can be upload to alternative app stores or test platforms.\nwebsite: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsource_code_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsupport_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk/issues\npublished_at: 2019-02-04T12:02:54.817601+01:00\nsource:\n  git: https://github.com/ch4vi/bitrise-step-bundle-universal-apk.git\n  commit: 7c7e986769f360b13524f036bc13fae0790a8dce\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file `.aab`. You can build the bundle running `:bundleRelease` gradle task\n      Format examples:\n      - `/path/to/my/app.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)`'\n    title: Build artifact path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- keystore_alias_password: $BITRISEIO_ANDROID_KEYSTORE_ALIAS_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias password\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |\n      You can upload this apk to alternative app stores or your test platform\n    summary: This is the path to the universal apk signed with the passed keystore\n    title: Path to the universal apk\n"
  },
  {
    "path": "steps/bundle-universal-apk/0.0.4/step.yml",
    "content": "title: Bundle Universal Apk\nsummary: |\n  Generates an universal apk from an app bundle\ndescription: |\n  Runs a bundletool that gets an app bundle path and generates an universal apk that it can be upload to alternative app stores or test platforms.\nwebsite: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsource_code_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsupport_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk/issues\npublished_at: 2019-03-05T16:07:44.355859+01:00\nsource:\n  git: https://github.com/ch4vi/bitrise-step-bundle-universal-apk.git\n  commit: 780f9c2305fefcf3d62fe5e231152da2f6fa0367\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file `.aab`. You can build the bundle running `:bundleRelease` gradle task\n      Format examples:\n      - `/path/to/my/app.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)`'\n    title: Build artifact path.\n- apk_name: $BITRISE_APK_RESULT_NAME\n  opts:\n    description: |-\n      The name must end with .apk\n      Format examples:\n      - `apk_name.apk` or `apk_name`\n    is_required: false\n    summary: '`Name of the resulting apk`'\n    title: Universal apk name\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- keystore_alias_password: $BITRISEIO_ANDROID_KEYSTORE_ALIAS_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias password\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |\n      You can upload this apk to alternative app stores or your test platform\n    summary: This is the path to the universal apk signed with the passed keystore\n    title: Path to the universal apk\n"
  },
  {
    "path": "steps/bundle-universal-apk/0.0.5/step.yml",
    "content": "title: Bundle Universal Apk\nsummary: |\n  Generates an universal apk from an app bundle\ndescription: |\n  Runs a bundletool that gets an app bundle path and generates an universal apk that it can be upload to alternative app stores or test platforms.\nwebsite: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsource_code_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsupport_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk/issues\npublished_at: 2019-03-12T09:27:31.634368+01:00\nsource:\n  git: https://github.com/ch4vi/bitrise-step-bundle-universal-apk.git\n  commit: a4f7dc0bc35274c28ea6c872b30c4dac576226f7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file `.aab`. You can build the bundle running `:bundleRelease` gradle task\n      Format examples:\n      - `/path/to/my/app.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)`'\n    title: Build artifact path.\n- apk_name: $BITRISE_APK_RESULT_NAME\n  opts:\n    description: |-\n      The name must end with .apk\n      Format examples:\n      - `apk_name.apk` or `apk_name`\n    is_required: false\n    summary: '`Name of the resulting apk`'\n    title: Universal apk name\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- keystore_alias_password: $BITRISEIO_ANDROID_KEYSTORE_ALIAS_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias password\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |\n      You can upload this apk to an alternative app stores or your test platform\n    summary: Path to the universal apk signed with the given keystore\n    title: Universal apk path\n- BITRISE_APK_DIR: null\n  opts:\n    description: |\n      You can upload this directory to an alternative app stores or your test platform\n    summary: Path to directory where all the apk's are stored after the step.\n    title: Apk direcotry\n"
  },
  {
    "path": "steps/bundle-universal-apk/0.0.6/step.yml",
    "content": "title: Bundle Universal Apk\nsummary: |\n  Generates an universal apk from an app bundle\ndescription: |\n  Runs a bundletool that gets an app bundle path and generates an universal apk that it can be upload to alternative app stores or test platforms.\nwebsite: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsource_code_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk\nsupport_url: https://github.com/ch4vi/bitrise-step-bundle-universal-apk/issues\npublished_at: 2019-10-25T13:42:24.097604+02:00\nsource:\n  git: https://github.com/ch4vi/bitrise-step-bundle-universal-apk.git\n  commit: b3be8f910c7a76aa722e59700957cf9a058535fb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file `.aab`. You can build the bundle running `:bundleRelease` gradle task\n      Format examples:\n      - `/path/to/my/app.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)`'\n    title: Build artifact path.\n- apk_name: $BITRISE_APK_OUTPUT_NAME\n  opts:\n    description: |-\n      The name must end with .apk\n      Format examples:\n      - `apk_name.apk` or `apk_name`\n    is_required: false\n    summary: '`Name of the resulting apk`'\n    title: Universal apk name\n- apk_output_dir: $BITRISE_APK_OUTPUT_DIR\n  opts:\n    description: |-\n      If no Apk otuput dir is provided, the apk's will be at $BITRISE_APK_DIR\n      Format examples:\n      - `$BITRISE_DEPLOY_DIR`\n    is_required: false\n    summary: '`Path where the apk''s will be moved after`'\n    title: APK's output directory\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- keystore_alias_password: $BITRISEIO_ANDROID_KEYSTORE_ALIAS_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias password\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |\n      You can upload this apk to an alternative app stores or your test platform\n    summary: Path to the universal apk signed with the given keystore\n    title: Universal apk path\n- BITRISE_APK_DIR: null\n  opts:\n    description: |\n      You can upload this directory to an alternative app stores or your test platform\n    summary: Path to directory where all the apk's are stored after the step.\n    title: Apk direcotry\n"
  },
  {
    "path": "steps/bundle-universal-apk/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/bundler/0.0.1/step.yml",
    "content": "title: Bundler\nsummary: Bundler\ndescription: Bundler\nwebsite: https://github.com/chrisfuller/bitrise-step-bundler\nsource_code_url: https://github.com/chrisfuller/bitrise-step-bundler\nsupport_url: https://github.com/chrisfuller/bitrise-step-bundler/issues\npublished_at: 2019-08-25T17:06:28.030329-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-bundler.git\n  commit: 149ca2687cbe8080812daea6d7a408a4e5e7517e\nhost_os_tags:\n- osx\ntype_tags:\n- utility\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- bundle_install_jobs: \"4\"\n  opts:\n    description: |\n      The maximum number of parallel download and install jobs.\n    is_expand: true\n    is_required: true\n    title: --jobs\n- bundle_install_retry: \"1\"\n  opts:\n    description: |\n      The number of times to retry failed network or git requests.\n    is_expand: true\n    is_required: true\n    title: --retry\n"
  },
  {
    "path": "steps/bundler/0.0.2/step.yml",
    "content": "title: Bundler\nsummary: Install Ruby Dependencies with Bundler\ndescription: Install Ruby Dependencies with Bundler\nwebsite: https://github.com/chrisfuller/bitrise-step-bundler\nsource_code_url: https://github.com/chrisfuller/bitrise-step-bundler\nsupport_url: https://github.com/chrisfuller/bitrise-step-bundler/issues\npublished_at: 2019-09-03T02:30:23.222685-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-bundler.git\n  commit: c8bc9835332d7d618f02ff4897ebfe017713ef15\nhost_os_tags:\n- osx\ntype_tags:\n- utility\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- bundle_install_jobs: \"4\"\n  opts:\n    description: |\n      The maximum number of parallel download and install jobs.\n    is_expand: true\n    is_required: true\n    title: --jobs\n- bundle_install_retry: \"1\"\n  opts:\n    description: |\n      The number of times to retry failed network or git requests.\n    is_expand: true\n    is_required: true\n    title: --retry\n"
  },
  {
    "path": "steps/bundler/0.0.3/step.yml",
    "content": "title: Bundler\nsummary: Install Ruby Dependencies with Bundler\ndescription: Install Ruby Dependencies with Bundler\nwebsite: https://github.com/chrisfuller/bitrise-step-bundler\nsource_code_url: https://github.com/chrisfuller/bitrise-step-bundler\nsupport_url: https://github.com/chrisfuller/bitrise-step-bundler/issues\npublished_at: 2019-09-08T16:41:15.363368-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-bundler.git\n  commit: 5941e841a021216b90c13e32f1b38bfdc7ac6691\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- bundle_install_jobs: \"4\"\n  opts:\n    description: |\n      The maximum number of parallel download and install jobs.\n    is_expand: true\n    is_required: true\n    title: --jobs\n- bundle_install_retry: \"1\"\n  opts:\n    description: |\n      The number of times to retry failed network or git requests.\n    is_expand: true\n    is_required: true\n    title: --retry\n"
  },
  {
    "path": "steps/bundler/0.0.4/step.yml",
    "content": "title: Bundler\nsummary: Install Ruby Dependencies with Bundler\ndescription: Install Ruby Dependencies with Bundler\nwebsite: https://github.com/chrisfuller/bitrise-step-bundler\nsource_code_url: https://github.com/chrisfuller/bitrise-step-bundler\nsupport_url: https://github.com/chrisfuller/bitrise-step-bundler/issues\npublished_at: 2019-09-11T08:58:52.875111-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-bundler.git\n  commit: 0e27995bfe32237fe7b61fa64445cc6885dae03e\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- bundle_install_jobs: \"4\"\n  opts:\n    description: |\n      The value of the `--jobs` Bundler option.\n    is_expand: true\n    is_required: true\n    title: The maximum number of parallel download and install jobs.\n- bundle_install_retry: \"1\"\n  opts:\n    description: |\n      The value of the `--retry` Bundler option.\n    is_expand: true\n    is_required: true\n    title: The number of times to retry failed network or git requests.\n"
  },
  {
    "path": "steps/bundler/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cache-pull/0.9.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull [BETA]\nsummary: WIP\ndescription: WIP\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2016-04-13T16:18:48.559722571+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: a888a463aa719766ad011d084c445b79c2a77c85\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- bitrise.io\n- cache\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/0.9.1/step.yml",
    "content": "title: Bitrise.io Cache:Pull [BETA]\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/docs/using-the-build-cache](http://devcenter.bitrise.io/docs/using-the-build-cache).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2016-04-20T11:35:10.976596542+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 60ed678708702719d6331f0abc7312b02af003fb\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- bitrise.io\n- cache\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/0.9.2/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2017-01-24T21:38:29.244611111+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 582f304450221e1771c3ccff2c1377abb000cd64\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/0.9.4/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2017-05-25T15:24:47.69329435+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 5d5eaaf418fcb0c6ddc287cb1a672f5d6f3852db\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/1.0.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2017-05-26T16:08:45.88575208+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: b74a8e2e0825a588081c7a10a189da5a0e1257ed\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/2.0.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2017-09-26T16:19:36.336485711+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: be822420a0144c34ed1d5a3e093fd534260b67c8\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/2.0.1/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2017-12-04T13:14:46.805494797+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 4c2ed8c1fbe1b9a28beaa5c89439f8a9be775793\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache API URL\n    title: Cache API URL\noutputs:\n- BITRISE_CACHE_INFO_PATH: null\n  opts:\n    description: Path to the uncompressed cache-info.json\n    title: Bitrise Cache-Info (JSON) file path\n"
  },
  {
    "path": "steps/cache-pull/2.1.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  For more information on setting it up and for tips & tricks, head over to our Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2019-07-31T07:46:16.391239715Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: e597469c16788103b08f3abc9583235a6002189e\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.1.1/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  For more information on setting it up and for tips & tricks, head over to our Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2019-09-16T14:49:21.515743981Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: d584736cc2785a6bdbd6cce9b70573297f7729be\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.1.2/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download Build Cache from Bitrise.io\ndescription: |-\n  Downloads the Build Cache from Bitrise.io, and moves the files back to\n  their original place.\n\n  For more information on setting it up and for tips & tricks, head over to our Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2019-11-26T16:03:38.823187845Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 3117c54a706e0081471f7dcd7b407aeff51da1be\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.1.3/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2019-12-10T12:58:41.252120819Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 0517fc3cae2bfcb1ab42db2139321d3853a2660e\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.1.4/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2020-02-13T14:51:45.811395168Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 5c3ffa53c8c94729f6e08d97b0fe9a5c260b2cec\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.1.5/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2020-08-28T08:45:10.833575393Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 374582060769cdd26c8208dcb29e8a17a17f681a\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.1.6/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2020-09-03T10:57:29.501693496Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 1eefc5a4e54aab40d8241d9e48b80965de87084c\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n"
  },
  {
    "path": "steps/cache-pull/2.3.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2020-10-30T08:08:36.974821487Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 98851de3dee34acec45b501bb72000d0de4c0406\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.4.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2020-12-02T14:16:32.83367111Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 110adc795816f919359ccc3a19da3926ec9fe416\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.5.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2021-02-05T13:55:45.706010167Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: f0d513ac1880cc3480eea547b47bdd07813b8b18\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.6.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2022-05-25T14:02:03.47052731Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 27d2d450a2fa7c6ace5ee461e952021f1cabe439\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.6.1/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2022-06-28T06:52:39.57447806Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: a6b4345d40b7eefad09e4ce14caeed04886ac3f8\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.7.0/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2022-07-14T12:18:58.05073766Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 43c8047f9bd3b471cd5ea8ecb49827fc5444cb41\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n- ignore_stack_difference: \"false\"\n  opts:\n    is_required: false\n    summary: Allow to use the same cache across different Bitrise stacks. Use at your\n      own risk, it might cause build problems.\n    title: Ignore stack difference\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.7.1/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2022-08-08T13:24:21.583156972Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: 02d25fa07cc1755b043298faffa6dda49d16811c\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n- ignore_stack_difference: \"false\"\n  opts:\n    is_required: false\n    summary: Allow to use the same cache across different Bitrise stacks. Use at your\n      own risk, it might cause build problems.\n    title: Ignore stack difference\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/2.7.2/step.yml",
    "content": "title: Bitrise.io Cache:Pull\nsummary: Download the build cache from bitrise.io.\ndescription: |-\n  Downloads the build cache from bitrise.io, and moves the files back to\n  their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.\n\n  ### Configuring the Step\n\n  To be able to pull from a previous build's cache, you need two things.\n\n  1. The **Cache:Push** Step at the end of your Workflow.\n  2. At least one successful build on the same branch in the last seven days.\n\n  If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.\n\n  ### Troubleshooting\n\n  If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the **Cache:Push** Step.\n\n  If the **Cache:Push** Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.\n\n  ### Useful links\n\n  - [Caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\n\n  ### Related Steps\n\n  - [Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [yarn](https://www.bitrise.io/integrations/steps/yarn)\nwebsite: https://github.com/bitrise-steplib/steps-cache-pull\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-pull.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-pull/issues\npublished_at: 2022-09-07T13:31:05.076017764Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-pull.git\n  commit: d22f399218153c59b8cb520eb4a8473b7c824d9f\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-pull\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache API URL\n    is_dont_change_value: true\n    summary: Cache API URL\n    title: Cache API URL\n- is_debug_mode: \"false\"\n  opts:\n    is_required: true\n    summary: If enabled, the step will print verbose logs.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n- extract_to_relative_path: \"false\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    summary: Should we extract the archive content under current working directory?\n    title: Extract to relative path?\n    value_options:\n    - \"true\"\n    - \"false\"\n- allow_fallback: \"true\"\n  opts:\n    category: Debug\n    is_dont_change_value: true\n    is_required: true\n    title: Allow fallback cache extraction?\n    value_options:\n    - \"true\"\n    - \"false\"\n- ignore_stack_difference: \"false\"\n  opts:\n    is_required: false\n    summary: Allow to use the same cache across different Bitrise stacks. Use at your\n      own risk, it might cause build problems.\n    title: Ignore stack difference\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cache-pull/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2025-04-11\"\ndeprecate_notes: |\n  The branch-based caching steps are deprecated and being replaced by key-based caching.\n\n  Check out our migration guide: [Migrating from branch-based caching to key-based caching](https://devcenter.bitrise.io/en/dependencies-and-caching/branch-based-caching/migrating-from-branch-based-caching-to-key-based-caching.html).\n"
  },
  {
    "path": "steps/cache-push/0.9.0/step.yml",
    "content": "title: Bitrise.io Cache:Push [BETA]\nsummary: WIP\ndescription: |-\n  WIP\n\n  It won't upload if the Cache did not change, nor in case of PullRequest build.\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2016-04-13T16:20:27.064787455+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: d92ce9091bc52951d5a193bd70c3e16d28564a09\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- bitrise.io\n- cache\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n    ./Pods -> ./Podfile.lock\n    $HOME/.gradle/wrapper\n    ./.gradle\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n    is_required: true\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: \"\"\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/0.9.1/step.yml",
    "content": "title: Bitrise.io Cache:Push [BETA]\nsummary: WIP\ndescription: It won't upload if the Cache did not change, nor in case of PullRequest\n  build.\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2016-04-15T18:17:04.700062962+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: b984a1c7db4579c5ff87bfe2bce3aee34eb92b78\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- bitrise.io\n- cache\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n\n    ./Pods -> ./Podfile.lock\n\n    $HOME/.gradle\n    ./.gradle\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    is_required: true\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: |-\n    $HOME/.gradle/caches/*.lock\n    ./.gradle/*.lock\n    ./.gradle/*.bin\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      The path can also include the `*` wildcard character, which will\n      do a **string** based compare (e.g. `a/*/b` will match `a/1/2/3/b` too,\n      not just `a/x/b`).\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/0.9.2/step.yml",
    "content": "title: Bitrise.io Cache:Push [BETA]\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/docs/using-the-build-cache](http://devcenter.bitrise.io/docs/using-the-build-cache).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2016-04-20T11:37:56.014160296+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: f11171e91e836020f7b6ded6d0345d0ac42d52d4\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- bitrise.io\n- cache\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n\n    ./Pods -> ./Podfile.lock\n\n    $HOME/.gradle\n    ./.gradle\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    is_required: true\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: |-\n    $HOME/.gradle/caches/*.lock\n    ./.gradle/*.lock\n    ./.gradle/*.bin\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      The path can also include the `*` wildcard character, which will\n      do a **string** based compare (e.g. `a/*/b` will match `a/1/2/3/b` too,\n      not just `a/x/b`).\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/0.9.3/step.yml",
    "content": "title: Bitrise.io Cache:Push [BETA]\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/docs/using-the-build-cache](http://devcenter.bitrise.io/docs/using-the-build-cache).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2016-04-25T21:10:32.062430991+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: ac9b7e9f4f7ba827a5f5c47449223bf043a2d24a\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- bitrise.io\n- cache\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n\n    ./Pods -> ./Podfile.lock\n\n    $HOME/.gradle\n    ./.gradle\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    is_required: true\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: |-\n    $HOME/.gradle/caches/*.lock\n    $HOME/.gradle/caches/*.bin\n    ./.gradle/*.lock\n    ./.gradle/*.bin\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      The path can also include the `*` wildcard character, which will\n      do a **string** based compare (e.g. `a/*/b` will match `a/1/2/3/b` too,\n      not just `a/x/b`).\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/0.9.4/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-01-24T21:43:03.078107607+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 2da1564f54bb15f5c9b75419c6a7840efe81e481\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n\n    ./Pods -> ./Podfile.lock\n\n    $HOME/.gradle\n    ./.gradle\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    is_required: true\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: |-\n    $HOME/.gradle/caches/*.lock\n    $HOME/.gradle/caches/*.bin\n    ./.gradle/*.lock\n    ./.gradle/*.bin\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      The path can also include the `*` wildcard character, which will\n      do a **string** based compare (e.g. `a/*/b` will match `a/1/2/3/b` too,\n      not just `a/x/b`).\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/0.9.6/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-05-25T15:28:41.595572648+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: ced70be20dc008861f1de95da7a50240cbdbf5f5\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n\n    ./Pods -> ./Podfile.lock\n\n    $HOME/.gradle\n    ./.gradle\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    is_required: true\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: |-\n    $HOME/.gradle/caches/*.lock\n    $HOME/.gradle/caches/*.bin\n    ./.gradle/*.lock\n    ./.gradle/*.bin\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      The path can also include the `*` wildcard character, which will\n      do a **string** based compare (e.g. `a/*/b` will match `a/1/2/3/b` too,\n      not just `a/x/b`).\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/1.0.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-05-26T16:12:48.706808259+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 0b614664850d56082802a65b1cc9f17076f8faea\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: |-\n      These paths will be ignored from change checking.\n      If something changed under the specified path(s) and nothing else changed\n      then the cache won't be updated.\n\n      **These paths are NOT ignored from the cache**, if a path is located\n      inside a specified Cache Path item it'll be included in the cache,\n      just won't be checked for changes.\n\n      The path can also include the `*` wildcard character, which will\n      do a **string** based compare (e.g. `a/*/b` will match `a/1/2/3/b` too,\n      not just `a/x/b`).\n\n      Important: you can't ignore a path which results in an invalid cache item.\n      For example, if you specify the path `a/path/to/cache` to be cached, you\n      can't ignore `a/path/to`, as that would ignore every file from checking\n      for a change - no fingerprint could be generated for `a/path/to/cache`.\n      You're free to ignore paths inside a Cache Path however, e.g.\n      if path is `a/path/to/cache` you're free to ignore `a/path/to/cache/.ignore-me`,\n      unless that's the only file inside `a/path/to/cache`.\n\n      The point is: you should not specify an ignore rule which would completely\n      ignore a specified Cache Path item, as that would result in a path which\n      can't be checked for updates/changes/fingerprints.\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/1.1.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-05-31T16:50:17.972459775+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 5f422d43576266395935224fe73e2a062e3b7da6\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/1.1.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-06-26T16:52:45.450269192+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 815d3b4d8e4a20b9a27217b497a57f5cccb35898\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/1.1.3/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-07-04T15:44:00.951870409+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 689c1dbb4d1844f22ba7b73a74af89be81b7af78\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/1.1.4/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-08-04T15:06:51.622133832+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: bc384c8ef395cf38eadb1e4318622b1665efdb4b\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: rsync\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.0.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-09-26T16:22:31.428258216+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 1bd0a0b4dd038143b9e18643c9f82ff9e3f79b44\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.0.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-09-27T14:33:31.271479016+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 6659a2345f185a64e1b5fa6f2bff09b831c1cd16\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.0.2/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-10-10T15:49:08.530462222+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 4ba1ed81ef5c28dcb3220df3fdd72aebd588d682\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.0.3/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2017-11-23T16:24:39.837780321+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 7f267e29be97268b08cd558a7c155c403c9eb30a\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.0.4/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2018-01-26T13:32:07.329829902+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 1e4186d1f85def111294ecf6a04619e93b81a1a1\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.0.5/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This Step checks whether the Cache have to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs),\n  and if it have to be it will create a new cache archive and upload it.\n\n  It won't update/upload the Cache if the Cache did not change,\n  nor in case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  You can find a setup and tips & tricks guide on the Bitrise DevCenter\n  at [http://devcenter.bitrise.io/caching/about-caching/](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2018-01-31T15:55:43.791898978+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 1625d22863a08160560b988078d19af6f6d0d47e\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this Step to fail. It'll be logged but the Step will try to gather\n      as many specified & valid paths as it can, and just print warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      changed under the specified path(s) and nothing else changed\\nthen the cache\n      won't be updated.\\n\\n**Paths are not prefixed with `!` will NOT ignored from\n      the cache archive**,\\nif a path is located inside a specified Cache Path item\n      and not prefixed with `!`,\\nit'll be included in the cache archive, just won't\n      be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*` will\n      do path element replace (e.g. `a/*/b` will match `a/x/b`).\\n`**` will do path\n      part replace (e.g. `a/**/b` will match `a/x/y/z/b`).\\nTo exclude full directory\n      like: `/my/full/path`, just simply put a `/` behind of it,\\nso it will be `/my/full/path/`.\\n\\nImportant:\n      you can't ignore a path which results in an invalid cache item.\\nFor example,\n      if you specify the path `a/path/to/cache` to be cached, you\\ncan't ignore `a/path/to`,\n      as that would ignore every file from checking\\nfor a change - no fingerprint\n      could be generated for `a/path/to/cache`.\\nYou're free to ignore paths inside\n      a Cache Path however, e.g.\\nif path is `a/path/to/cache` you're free to ignore\n      `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside `a/path/to/cache`.\\n\\nThe\n      point is: you should not specify an ignore rule which would completely\\nignore\n      a specified Cache Path item, as that would result in a path which\\ncan't be\n      checked for updates/changes/fingerprints.\"\n    summary: Ignore these Paths when checking for cache changes\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed a new cache will be generated,\n      if the fingerprint matches the previous cache version's fingerprint then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file don't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\" the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If compress cache set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If compress cache set to `true`, then it will upload a compressed archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected runtime\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected regularly changing files or extensions by steps from the build\n    title: Ignore paths collected runtime\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n- compare_cache_info_path: $BITRISE_CACHE_INFO_PATH\n  opts:\n    description: |-\n      Compare the fingerprints against this Cache Info, to see if cache\n      update/upload is required or not.\n    is_dont_change_value: true\n    is_required: true\n    summary: Compare the fingerprints against this Cache Info\n    title: Cache Info file path, for compare\n"
  },
  {
    "path": "steps/cache-push/2.1.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This step checks whether the cache has to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs).\n  If it has to be updated, the step will create a new cache archive and upload it.\n\n  It won't update/upload the cache if the cache did not change,\n  nor in the case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  For more information on setup and tips & tricks, check out our [Bitrise DevCenter guide](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2019-03-20T10:07:32.946564502Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 7f7710fed5ab024de45c7511e217f5feb42ba03a\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n"
  },
  {
    "path": "steps/cache-push/2.1.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This step checks whether the cache has to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs).\n  If it has to be updated, the step will create a new cache archive and upload it.\n\n  It won't update/upload the cache if the cache did not change,\n  nor in the case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  For more information on setup and tips & tricks, check out our [Bitrise DevCenter guide](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2019-03-26T09:15:44.786419483Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 271dc5b19e3b1d639e210094066c7141c904599f\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n"
  },
  {
    "path": "steps/cache-push/2.2.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This step checks whether the cache has to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs).\n  If it has to be updated, the step will create a new cache archive and upload it.\n\n  It won't update/upload the cache if the cache did not change,\n  nor in the case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  For more information on setup and tips & tricks, check out our [Bitrise DevCenter guide](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2019-05-16T13:57:04.391320918Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 43d9deb931bf7155941fa7f3b21d494df852753d\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: 'TMP: Cache Upload URL'\n"
  },
  {
    "path": "steps/cache-push/2.2.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This step checks whether the cache has to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs).\n  If it has to be updated, the step will create a new cache archive and upload it.\n\n  It won't update/upload the cache if the cache did not change,\n  nor in the case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  For more information on setup and tips & tricks, check out our [Bitrise DevCenter guide](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2019-10-10T13:23:07.49798563Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: b966f9de2aa606f7199ff87f4570744d253c3e64\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.2.2/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This step checks whether the cache has to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs).\n  If it has to be updated, the step will create a new cache archive and upload it.\n\n  It won't update/upload the cache if the cache did not change,\n  nor in the case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  For more information on setup and tips & tricks, check out our [Bitrise DevCenter guide](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2019-11-15T18:00:26.719481848Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: f935d7cfd70525b7a0ff29295cccd59a4dff6ee8\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.2.3/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: |-\n  This step checks whether the cache has to be updated (based on the\n  `Cache Paths` and `Ignore Paths from change check` inputs).\n  If it has to be updated, the step will create a new cache archive and upload it.\n\n  It won't update/upload the cache if the cache did not change,\n  nor in the case of Pull Request builds (unless you change the `run_if` property of the Step).\n\n  For more information on setup and tips & tricks, check out our [Bitrise DevCenter guide](http://devcenter.bitrise.io/caching/about-caching/).\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2019-11-26T14:41:46.52280457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: febc82b3cff84ff5dca6a85f4f6f6e019ae6f5bb\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.2.4/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2020-05-28T06:55:31.002559337Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 51479b03f622c3510b182423d5a6a45d7df4f465\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.3.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2020-06-09T14:24:29.932785882Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: af27a1087f5b6ba234986ea4011b665efacbb8a6\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.3.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2020-08-28T08:44:03.702168935Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: a5e43ae6ac5e0478feae7dea2b688bf317097f3b\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.3.2/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2020-09-03T10:58:27.297006438Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 4311cd87125b74e84670ef98eeb197cfc3b83865\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.4.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2020-12-02T14:26:20.636411742Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: acb955b85681f5d4c280b07be8b9de9a1d09cd0d\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.4.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2020-12-11T20:36:10.744228152Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 83c9a81f8229609f2586d9f2012d722fafa773a9\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: |\n    $BITRISE_CACHE_DIR\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.5.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2021-02-03T16:33:17.508965069Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: ddeb86dc5c0a193da443c41f28d55edf866953e0\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.5.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2021-06-01T08:59:26.487159511Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 42ba67bb29267bf65b8955d0d0e1739f1c218fff\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.6.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2021-09-03T12:01:58.337196091Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: dbada48e00031538650408b0dab0ca302df61a42\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.7.0/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2022-05-17T12:23:39.60033785Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: 4d9f583bb3ab1fc00715475200bda20a0ade524b\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/2.7.1/step.yml",
    "content": "title: Bitrise.io Cache:Push\nsummary: Updates the Cache, if required\ndescription: \"Checks whether cache has to be updated based on the **Cache Paths**\n  and **Ignore Paths** inputs.\\nIf it does, the Step creates a new cache archive and\n  uploads it. \\nIt won't update/upload the cache if the cache hasn't changed nor in\n  the case of a pull request unless you change the Step's `run_if` property. \\nFor\n  caching, you will need the **Bitrise.io Cache:Pull** Step at the beginning of your\n  Workflow (after the **Git Clone Repository** Step but before a dependency installer\n  Step) to download the previous cache, if any. \\nThe **Bitrise.io Cache:Push** Step\n  should be the very last Step in your Workflow.\\n\\n### Configuring the Step\\n\\n1.\n  Cache any directory or file by adding it in the **Cache paths** field.\\nFor most\n  cases, caching will automatically work based on your native build and testing Steps\n  as these automatically configure cache paths in your cache Steps.\\nIf adding multiple\n  paths, separate them with a newline.\\nIf you have a path in the list which does\n  not exist, it will not cause the Step to fail. \\nYou can also specify an update\n  indicator file with the `->` syntax, for example, `update/this -> if/this/file/is/updated.`\n  \\nPlease note the indicator points to a file and not to a folder.\\n2. In the **Ignore\n  Paths from change check** field, you can set any path which you don't want to do\n  change analysis for.\\n- Paths prefixed with an `!` will get ignored from the cache\n  archive.\\n- The path can also include `*`, `**`, `/`. \\nThe `*` will replace a path\n  element, the `**` will replace part of a path. \\nTo exclude a full directory, simply\n  put a `/` behind the directory.\\nNote that you can't ignore a path which results\n  in an invalid cache item.\\n3. Modify **Working directory** if you wish to set relative\n  cache paths and reference them from a working directory other than `$BITRISE_SOURCE_DIR`.\\n4.\n  Select a **Fingerprint Method** option (`file-content-hash` or `file-mod-time`)\n  to detect changes in a directory, file, or in an update indicator file. \\nIf changes\n  are detected, new cache gets generated.\\n5. If you set **Debug mode?** input to\n  `true`, the Step will print out more detailed logs.\\n6. With **Compress cache?**\n  input set to `true`, you can compress the cache archive for faster uploads and downloads,\n  especially useful for node-modules and other huge dependency folders.\\n7. In `Ignore\n  paths collected by steps` you can set which files or extensions should be ignored\n  by the Step during the build.\\n8. `Cache Upload URL` shows the URL where the cache\n  gets uploaded.\\n\\n### Troubleshooting\\nWe recommend you do not cache any dependency\n  manager lock file (for example, `package.lock`, `gemfile.lock`, `podfile.lock`)\n  as it would override the lock file in your repository.\\n\\n### Useful links\\n- [About\n  caching](https://devcenter.bitrise.io/builds/caching/about-caching-index/)\\n- [Caching\n  Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n- [Caching\n  Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n\\n### Related\n  Steps\\n- [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Git Clone Repository](https://www.bitrise.io/integrations/steps/git-clone)\"\nwebsite: https://github.com/bitrise-steplib/steps-cache-push\nsource_code_url: https://github.com/bitrise-steplib/steps-cache-push.git\nsupport_url: https://github.com/bitrise-steplib/steps-cache-push/issues\npublished_at: 2022-05-20T15:04:58.949481039Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cache-push.git\n  commit: f1aa51a651f8b4076f61a1f099ee0cc954711634\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cache-push\ndeps:\n  apt_get:\n  - name: tar\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- cache_paths: null\n  opts:\n    description: |-\n      Cache these paths. Separate paths with a newline.\n\n      A path item can be either a file or a directory.\n\n      You can also specify an \"update indicator file\" with the `->`\n      syntax: `update/this -> if/this/file/is/updated`.\n      *The indicator can only be a file!*\n\n      If you have a path in the list which doesn't exist that will not cause\n      this step to fail. It'll be logged but the step will try to gather\n      as many specified & valid paths as it can, and just print a warning\n      about the invalid items.\n    summary: Cache these paths. Separate paths with a newline.\n    title: Cache paths\n- ignore_check_on_paths: null\n  opts:\n    description: \"These paths will be ignored from change checking.\\nIf something\n      has changed under the specified path(s) and nothing else has changed,\\nthen\n      the cache won't be updated.\\n\\n**Paths prefixed with an `!` will get ignored\n      from the cache archive**.\\nIf a path is located inside a specified Cache Path\n      item and not prefixed with an `!`,\\nit'll be included in the cache archive,\n      but won't be checked for changes. \\n\\nThe path can also include `*`, `**`, `/`.\\n`*`\n      will replace a path element (for example, `a/*/b` will match `a/x/b`).\\n`**`\n      will replace part of a path (for example, `a/**/b` will match `a/x/y/z/b`).\\nTo\n      exclude a full directory like `/my/full/path`, simply put a `/` behind `/my/full/path`,\\nso\n      it will be `/my/full/path/`.\\n\\nImportant: you can't ignore a path which results\n      in an invalid cache item.\\nFor example, if you specify the path `a/path/to/cache`\n      to be cached, you\\ncan't ignore `a/path/to`, as that would ignore every file\n      from checking\\nfor a change and no fingerprint could be generated for `a/path/to/cache`.\\nYou\n      can ignore paths inside a Cache Path, however, if, for example, a path is `a/path/to/cache`,\n      you can ignore `a/path/to/cache/.ignore-me`,\\nunless that's the only file inside\n      `a/path/to/cache`.\\n\\nThe point is: you should not specify an ignore rule which\n      would completely\\nignore a specified Cache Path item, as that would result in\n      a path which\\ncan't be checked for updates,changes or fingerprints.\"\n    summary: Define the paths which have to be ignored when checking for cache changes.\n    title: Ignore Paths from change check\n- opts:\n    description: Working directory path - should be an absolute path.\n    summary: Working directory path\n    title: Working directory path\n  workdir: $BITRISE_SOURCE_DIR\n- fingerprint_method: file-content-hash\n  opts:\n    description: |-\n      The specified Fingerprint Method will be used to calculate\n      fingerprints for the cached files.\n\n      The (file) fingerprint is used to check whether\n      the cached files did change - if it changed, a new cache will be generated.\n      If the fingerprint matches the previous cache version's fingerprint, then\n      no new cache will be generated.\n\n      **Regardless of which method you choose** the following file attributes will\n      be used to create the fingerprint **in addition** to the method you choose:\n\n      * File path\n      * File size\n      * File permission bits\n\n      Information about the options:\n\n      * `file-content-hash` : create a file content checksum hash for every file in the cache,\n        and use that as the fingerprint source of the file. This means that **the full file content will be loaded** in\n        order to create the checksum hash!\n      * `file-mod-time` : use the file's \"modified at\" time information. For larger files this method\n        can be significantly faster, as the file doesn't have to be loaded to calculate this information!\n\n      **Note**: in case of \"update indicator files\", the fingerprint method will always be `file-content-hash`,\n      regardless of which option you select here.\n    summary: Fingerprint method, used for checking file changes.\n    title: Fingerprint Method\n    value_options:\n    - file-content-hash\n    - file-mod-time\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled the step will print verbose logs.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs.\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- compress_archive: \"false\"\n  opts:\n    description: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    is_required: true\n    summary: If Compress cache is set to `true`, then it will upload a compressed\n      archive.\n    title: Compress cache?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bitrise_cache_include_paths: $BITRISE_CACHE_INCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Collected dependencies by steps from the build\n    title: Cache paths collected by steps\n- bitrise_cache_exclude_paths: $BITRISE_CACHE_EXCLUDE_PATHS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: Changing files or extensions are collected regularly by steps from the\n      build.\n    title: Ignore paths collected by steps\n- cache_api_url: $BITRISE_CACHE_API_URL\n  opts:\n    description: Cache Upload URL\n    is_dont_change_value: true\n    is_required: true\n    summary: Cache Upload URL\n    title: Cache Upload URL\n"
  },
  {
    "path": "steps/cache-push/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2025-04-11\"\ndeprecate_notes: |\n  The branch-based caching steps are deprecated and being replaced by key-based caching.\n\n  Check out our migration guide: [Migrating from branch-based caching to key-based caching](https://devcenter.bitrise.io/en/dependencies-and-caching/branch-based-caching/migrating-from-branch-based-caching-to-key-based-caching.html).\n"
  },
  {
    "path": "steps/cakebuild/1.0.0/step.yml",
    "content": "title: Execute Cake C# Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/stefandevo/bitrise-cake-step\nsource_code_url: https://github.com/stefandevo/bitrise-cake-step\nsupport_url: https://github.com/stefandevo/bitrise-cake-step/issues\npublished_at: 2017-04-25T12:54:20.55383053+02:00\nsource:\n  git: https://github.com/stefandevo/bitrise-cake-step.git\n  commit: 6cd05453ce279b129513e426351e2edb00663baa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- dotnetcore: \"no\"\n  opts:\n    description: |\n      Is the project a .NET Core project? Default is no.\n    is_expand: true\n    is_required: true\n    title: .NET Core Needed?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n"
  },
  {
    "path": "steps/cakebuild/1.0.1/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/stefandevo/bitrise-cake-step\nsource_code_url: https://github.com/stefandevo/bitrise-cake-step\nsupport_url: https://github.com/stefandevo/bitrise-cake-step/issues\npublished_at: 2017-04-27T22:54:16.974189021+02:00\nsource:\n  git: https://github.com/stefandevo/bitrise-cake-step.git\n  commit: ec50ab6d13f13369f052d7aff03d125fb38021a6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- dotnetcore: \"no\"\n  opts:\n    description: |\n      Is the project a .NET Core project? Default is no.\n    is_expand: true\n    is_required: true\n    title: .NET Core Needed?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n"
  },
  {
    "path": "steps/cakebuild/1.0.2/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: http://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2017-04-28T13:30:51.935075275+02:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 9f83c661ae9fadb56bd3a58ad7e24cdc48873dea\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- dotnetcore: \"no\"\n  opts:\n    description: |\n      Is the project a .NET Core project? Default is no.\n    is_expand: true\n    is_required: true\n    title: .NET Core Needed?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n"
  },
  {
    "path": "steps/cakebuild/1.0.3/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: http://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2017-04-30T17:05:10.352420098+02:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: cc49ae420e67319814560f11688c39cae59f580a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- dotnetcore: \"no\"\n  opts:\n    description: |\n      Is the project a .NET Core project? Default is no.\n    is_expand: true\n    is_required: true\n    title: .NET Core Needed?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n"
  },
  {
    "path": "steps/cakebuild/1.0.4/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2018-03-07T10:52:32.572679+01:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 5eaa3dc63c8ddcad9b0ff8ae58c6fe0e7af4b21f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n"
  },
  {
    "path": "steps/cakebuild/1.0.5/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2018-03-08T20:41:33.325992+01:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 29425670048f3e15c7a7de001ab6cd8926f16602\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n- nuget_source_name: null\n  opts:\n    description: |\n      Name to use for specified NuGet private source in the NuGet source list.\n    summary: \"\"\n    title: NuGet private source name\n- nuget_source_path_or_url: null\n  opts:\n    description: |\n      Path or URL of the NuGet private package(s) source.\n    summary: \"\"\n    title: NuGet private source path / url\n- nuget_source_username: null\n  opts:\n    description: |\n      UserName to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source username\n- nuget_source_password: null\n  opts:\n    description: Password to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source password\n"
  },
  {
    "path": "steps/cakebuild/1.0.6/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2018-03-08T23:14:54.207488+01:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 3f1104b84e8faabbe55c1b63abc42fd898036a62\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n- nuget_source_name: null\n  opts:\n    description: |\n      Name to use for specified NuGet private source in the NuGet source list.\n    summary: \"\"\n    title: NuGet private source name\n- nuget_source_path_or_url: null\n  opts:\n    description: |\n      Path or URL of the NuGet private package(s) source.\n    summary: \"\"\n    title: NuGet private source path / url\n- nuget_source_username: null\n  opts:\n    description: |\n      UserName to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source username\n- nuget_source_password: null\n  opts:\n    description: Password to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source password\n"
  },
  {
    "path": "steps/cakebuild/1.0.7/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2018-03-09T11:21:52.664581+01:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 8913a0b3a4acc0cdc8d82bd825351af285221fbb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n- nuget_source_name: null\n  opts:\n    description: |\n      Name to use for specified NuGet private source in the NuGet source list.\n    summary: \"\"\n    title: NuGet private source name\n- nuget_source_path_or_url: null\n  opts:\n    description: |\n      Path or URL of the NuGet private package(s) source.\n    summary: \"\"\n    title: NuGet private source path / url\n- nuget_source_username: null\n  opts:\n    description: |\n      UserName to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source username\n- nuget_source_password: null\n  opts:\n    description: Password to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source password\n"
  },
  {
    "path": "steps/cakebuild/1.0.8/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2018-04-19T00:17:15.686104+02:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 5d490cf665426ac770f37e4a6695f80942466d30\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n- custom_args: null\n  opts:\n    description: |\n      Custom arguments to add to the build script\n    is_expand: true\n    is_required: false\n    title: Custom arguments\n- nuget_source_name: null\n  opts:\n    description: |\n      Name to use for specified NuGet private source in the NuGet source list.\n    summary: \"\"\n    title: NuGet private source name\n- nuget_source_path_or_url: null\n  opts:\n    description: |\n      Path or URL of the NuGet private package(s) source.\n    summary: \"\"\n    title: NuGet private source path / url\n- nuget_source_username: null\n  opts:\n    description: |\n      UserName to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source username\n- nuget_source_password: null\n  opts:\n    description: Password to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source password\n"
  },
  {
    "path": "steps/cakebuild/1.0.9/step.yml",
    "content": "title: Cake Script\nsummary: Cake (C# Make) is a cross platform build automation system\ndescription: \"Cake (C# Make) is a cross platform build automation system with a C#\n  DSL to do things like compiling code, \\ncopy files/folders, running unit tests,\n  compress files and build NuGet packages. \\nMore info: https://cakebuild.net/\"\nwebsite: https://github.com/cake-build/bitrise-cake-step\nsource_code_url: https://github.com/cake-build/bitrise-cake-step\nsupport_url: https://github.com/cake-build/bitrise-cake-step/issues\npublished_at: 2018-04-19T12:41:36.550613+02:00\nsource:\n  git: https://github.com/cake-build/bitrise-cake-step.git\n  commit: 16714950bb1c90c02a0bf3b5219a5a92dabc1e4c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Name of the script to execute. Default is build.cake\n    is_expand: true\n    is_required: true\n    title: Script\n  script: build.cake\n- opts:\n    description: |\n      Target name to execute. Default is Default\n    is_expand: true\n    is_required: true\n    title: Target\n  target: Default\n- configuration: Release\n  opts:\n    description: |\n      Configuration to build. Default is Release.\n    is_expand: true\n    is_required: true\n    title: Configuration\n- opts:\n    description: |\n      Specifies the amount of information to be displayed (quiet, minimal, normal, verbose, diagnostic).\n    is_expand: true\n    is_required: true\n    title: Verbosity\n    value_options:\n    - quiet\n    - minimal\n    - normal\n    - verbose\n    - diagnostic\n  verbosity: normal\n- custom_args: null\n  opts:\n    description: |\n      Custom arguments to add to the build script\n    is_expand: false\n    is_required: false\n    title: Custom arguments\n- nuget_source_name: null\n  opts:\n    description: |\n      Name to use for specified NuGet private source in the NuGet source list.\n    summary: \"\"\n    title: NuGet private source name\n- nuget_source_path_or_url: null\n  opts:\n    description: |\n      Path or URL of the NuGet private package(s) source.\n    summary: \"\"\n    title: NuGet private source path / url\n- nuget_source_username: null\n  opts:\n    description: |\n      UserName to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source username\n- nuget_source_password: null\n  opts:\n    description: |\n      Password to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source password\n"
  },
  {
    "path": "steps/cakebuild/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/calabash-android-uitest/0.9.0/step.yml",
    "content": "title: Step Calabash android UITest\nsummary: Step Calabash android UITest\ndescription: Step Calabash android UITest\nwebsite: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest/issues\npublished_at: 2015-12-21T12:47:57.895124084+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-android-uitest.git\n  commit: b8a99d76d2552a52619f725448dfd429a54aacf7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- testing\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: null\n  opts:\n    description: |\n      APK path\n    is_expand: true\n    is_required: true\n    title: APK path\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-android-uitest/0.9.1/step.yml",
    "content": "title: Calabash Android UI test\nsummary: Calabash Android UI test step\ndescription: Calabash Android UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest/issues\npublished_at: 2016-03-09T15:44:21.785795151+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-android-uitest.git\n  commit: d1fd87aacdbeb76be7aaf6fc3a21305821ac6ab5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- testing\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      APK path\n    is_expand: true\n    is_required: true\n    title: APK path\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-android-uitest/1.0.0/step.yml",
    "content": "title: Calabash Android UI test\nsummary: Calabash Android UI test step\ndescription: Calabash Android UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest/issues\npublished_at: 2016-10-26T14:24:38.950120692+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-android-uitest.git\n  commit: f2d52945390ddef84a0cbf6609bcd337c2cd6099\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-android-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      APK path\n    is_expand: true\n    is_required: true\n    title: APK path\n- calabash_android_version: null\n  opts:\n    description: |\n      calabash-android gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_android_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-android gem, latest version will be used\n    title: calabash-android gem version\n- gem_file_path: $BITRISE_SOURCE_DIR/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-android gem.\n\n      If Gemfile not exist or does not contain calabash-android gem:\n\n      - if `calabash_android_version` not specified, latest version will be used\n    title: Gemfile path\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-android-uitest/1.1.0/step.yml",
    "content": "title: Calabash Android UI test\nsummary: Calabash Android UI test step\ndescription: Calabash Android UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest/issues\npublished_at: 2017-01-23T09:59:49.804675278+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-android-uitest.git\n  commit: 6cbd08c4d181f39c6af2cbc1206fe270d5fa167f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-android-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.Droid/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.Droid`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-android gem.\n\n      If Gemfile not exist or does not contain calabash-android gem:\n\n      - if `calabash_android_version` not specified, latest version will be used\n    title: Gemfile path\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      Path to the APK to test.\n\n      __The APK should have Internet permission.__\n\n      In case of Xamarin:\n\n      Use an APK, which not built using Shared mono runtime (_Shared mono runtime is enabled by default in DEBUG builds_).\n    is_expand: true\n    is_required: true\n    title: APK path\n- android_home: $ANDROID_HOME\n  opts:\n    description: |\n      Path to the Android Home Directory.\n    is_expand: true\n    is_required: true\n    title: Android Home Directory\n- calabash_android_version: null\n  opts:\n    description: |\n      calabash-android gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_android_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-android gem, latest version will be used\n    title: calabash-android gem version\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-android-uitest/1.2.0/step.yml",
    "content": "title: Calabash Android UI test\nsummary: Calabash Android UI test step\ndescription: Calabash Android UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest/issues\npublished_at: 2017-02-20T16:10:28.208396213+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-android-uitest.git\n  commit: 14c3f17b46b0160ef7123d5a9c1da61512b17637\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-android-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.Droid/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.Droid`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-android gem.\n\n      If Gemfile not exist or does not contain calabash-android gem:\n\n      - if `calabash_android_version` not specified, latest version will be used\n    title: Gemfile path\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      Path to the APK to test.\n\n      __The APK should have Internet permission.__\n\n      In case of Xamarin:\n\n      Use an APK, which not built using Shared mono runtime (_Shared mono runtime is enabled by default in DEBUG builds_).\n    is_expand: true\n    is_required: true\n    title: APK path\n- additional_options: --format html --out $BITRISE_DEPLOY_DIR/calabash-android_report.html\n  opts:\n    description: |\n      Options added to the end of the `calabash-android run` call.\n    title: Additional options for `calabash-android run` call\n- android_home: $ANDROID_HOME\n  opts:\n    description: |\n      Path to the Android Home Directory.\n    is_expand: true\n    is_required: true\n    title: Android Home Directory\n- calabash_android_version: null\n  opts:\n    description: |\n      calabash-android gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_android_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-android gem, latest version will be used\n    title: calabash-android gem version\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-android-uitest/1.2.1/step.yml",
    "content": "title: Calabash Android UI test\nsummary: Calabash Android UI test step\ndescription: Calabash Android UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-android-uitest/issues\npublished_at: 2017-03-06T13:24:40.160003636+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-android-uitest.git\n  commit: f18958faae9b475932a6ece9facf9c11ab6ceb18\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-android-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.Droid/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.Droid`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-android gem.\n\n      If Gemfile not exist or does not contain calabash-android gem:\n\n      - if `calabash_android_version` not specified, latest version will be used\n    title: Gemfile path\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      Path to the APK to test.\n\n      __The APK should have Internet permission.__\n\n      In case of Xamarin:\n\n      Use an APK, which not built using Shared mono runtime (_Shared mono runtime is enabled by default in DEBUG builds_).\n    is_expand: true\n    is_required: true\n    title: APK path\n- additional_options: --format html --out $BITRISE_DEPLOY_DIR/calabash-android_report.html\n  opts:\n    description: |\n      Options added to the end of the `calabash-android run` call.\n    title: Additional options for `calabash-android run` call\n- android_home: $ANDROID_HOME\n  opts:\n    description: |\n      Path to the Android Home Directory.\n    is_expand: true\n    is_required: true\n    title: Android Home Directory\n- calabash_android_version: null\n  opts:\n    description: |\n      calabash-android gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_android_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-android gem, latest version will be used\n    title: calabash-android gem version\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-android-uitest/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/calabash-ios-uitest/0.9.0/step.yml",
    "content": "title: Step Calabash iOS UITest\nsummary: Step Calabash iOS UITest\ndescription: Step Calabash iOS UITest\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2015-12-21T10:55:20.13729491+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: c2323838b7f9ac7d55b2838996aaaf2b6588cb9f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.1\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/0.9.1/step.yml",
    "content": "title: Calabash iOS UI test\nsummary: Calabash iOS UI test step\ndescription: Calabash iOS UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2016-03-09T15:46:53.800915637+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: 70365e88315188fd71c7436136eb74012eb302d1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- testing\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.1\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/1.0.0/step.yml",
    "content": "title: Calabash iOS UI test\nsummary: Calabash iOS UI test step\ndescription: Calabash iOS UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2016-10-25T17:03:37.369897394+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: c562fb7161e2a7893961e5c442111f382fa90d15\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-ios-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- calabash_cucumber_version: null\n  opts:\n    description: |\n      calabash-cucumber gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_cucumber_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-cucumber gem, latest version will be used\n    title: calabash-cucumber gem version\n- gem_file_path: $BITRISE_SOURCE_DIR/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-cucumber gem.\n\n      If Gemfile not exist or does not contain calabash-cucumber gem:\n\n      - if `calabash_cucumber_version` not specified, latest version will be used\n    title: Gemfile path\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/1.1.0/step.yml",
    "content": "title: Calabash iOS UI test\nsummary: Calabash iOS UI test step\ndescription: Calabash iOS UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2016-10-26T13:43:26.361846907+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: 676177084935c23b65c5fc3dd6dba01ebbd869fa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-ios-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- calabash_cucumber_version: null\n  opts:\n    description: |\n      calabash-cucumber gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_cucumber_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-cucumber gem, latest version will be used\n    title: calabash-cucumber gem version\n- gem_file_path: $BITRISE_SOURCE_DIR/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-cucumber gem.\n\n      If Gemfile not exist or does not contain calabash-cucumber gem:\n\n      - if `calabash_cucumber_version` not specified, latest version will be used\n    title: Gemfile path\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/1.2.1/step.yml",
    "content": "title: Calabash iOS UI test\nsummary: Calabash iOS UI test step\ndescription: Calabash iOS UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2017-01-20T15:39:38.273636469+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: 4a557b5451e851799642e56208c3dcd952c7bf1e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-ios-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.iOS/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.iOS`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-cucumber gem.\n\n      If Gemfile not exist or does not contain calabash-cucumber gem:\n\n      - if `calabash_cucumber_version` input not specified, latest version will be used\n    title: Gemfile path\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to the iOS .app file, which supports selected simulator `Device` architecture.\n\n      __In case of Xamarin .app file:__\n\n      You can ensure `Supported architectures` in your project's `Project Options/Code Generation and Runtime/Supported architectures`.\n\n      If `i386` architecture is selected, simulator device should be a 32-bit device.\n      If `x86_64` architecture is selected, simulator device should be a 64-bit device.\n      If `i386 + x86_64` architecture is selected, simulator can be both 32-bit and 64-bit device.\n    title: Path to the iOS .app file to test\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- calabash_cucumber_version: null\n  opts:\n    description: |\n      calabash-cucumber gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_cucumber_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-cucumber gem, latest version will be used\n    title: calabash-cucumber gem version\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/1.3.0/step.yml",
    "content": "title: Calabash iOS UI test\nsummary: Calabash iOS UI test step\ndescription: Calabash iOS UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2017-02-20T16:59:24.195495186+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: 5e2f25353acb8a58178f6ac21970341a57515164\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- testing\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-ios-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.iOS/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.iOS`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-cucumber gem.\n\n      If Gemfile not exist or does not contain calabash-cucumber gem:\n\n      - if `calabash_cucumber_version` input not specified, latest version will be used\n    title: Gemfile path\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to the iOS .app file, which supports selected simulator `Device` architecture.\n\n      __In case of Xamarin .app file:__\n\n      You can ensure `Supported architectures` in your project's `Project Options/Code Generation and Runtime/Supported architectures`.\n\n      If `i386` architecture is selected, simulator device should be a 32-bit device.\n      If `x86_64` architecture is selected, simulator device should be a 64-bit device.\n      If `i386 + x86_64` architecture is selected, simulator can be both 32-bit and 64-bit device.\n    title: Path to the iOS .app file to test\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- additional_options: --format html --out $BITRISE_DEPLOY_DIR/calabash-android_report.html\n  opts:\n    description: |\n      Options added to the end of the `cucumber` call.\n    title: Additional options for `cucumber` call\n- calabash_cucumber_version: null\n  opts:\n    description: |\n      calabash-cucumber gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_cucumber_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-cucumber gem, latest version will be used\n    title: calabash-cucumber gem version\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/1.3.1/step.yml",
    "content": "title: Calabash iOS UI test\nsummary: Calabash iOS UI test step\ndescription: Calabash iOS UI test step\nwebsite: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsource_code_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest\nsupport_url: https://github.com/bitrise-steplib/steps-calabash-ios-uitest/issues\npublished_at: 2017-03-06T11:02:04.98460934+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-calabash-ios-uitest.git\n  commit: 0e89afb3532d79fefe9e14e99e771f85d12c3fef\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-calabash-ios-uitest\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.iOS/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.iOS`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-cucumber gem.\n\n      If Gemfile not exist or does not contain calabash-cucumber gem:\n\n      - if `calabash_cucumber_version` input not specified, latest version will be used\n    title: Gemfile path\n- app_path: $BITRISE_APP_PATH\n  opts:\n    description: |-\n      Path to the iOS .app file, which supports selected simulator `Device` architecture.\n\n      __In case of Xamarin .app file:__\n\n      You can ensure `Supported architectures` in your project's `Project Options/Code Generation and Runtime/Supported architectures`.\n\n      If `i386` architecture is selected, simulator device should be a 32-bit device.\n      If `x86_64` architecture is selected, simulator device should be a 64-bit device.\n      If `i386 + x86_64` architecture is selected, simulator can be both 32-bit and 64-bit device.\n    title: Path to the iOS .app file to test\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- additional_options: --format html --out $BITRISE_DEPLOY_DIR/calabash-ios_report.html\n  opts:\n    description: |\n      Options added to the end of the `cucumber` call.\n    title: Additional options for `cucumber` call\n- calabash_cucumber_version: null\n  opts:\n    description: |\n      calabash-cucumber gem version to use.\n\n      __If this input specifies the gem version, this version will be used, even `gem_file_path` provided.__\n\n      If `calabash_cucumber_version` not specified:\n\n      - gem version will be used specified by Gemfile at `gem_file_path`\n      - if Gemfile not exist with calabash-cucumber gem, latest version will be used\n    title: calabash-cucumber gem version\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/calabash-ios-uitest/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/carthage/1.0.0/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2015-09-30T10:11:10.013990903-07:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 832df9d4d8ee954b962f6e7f907951e5783fc413\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndependencies:\n- manager: brew\n  name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/carthage/1.0.1/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2015-10-27T16:10:16.581565978+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 4011cb9de65bc3561e0d137b8d40bd44ed93d217\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- carthage_version: default\n  opts:\n    summary: Specify system default, or latest (0.9.4) Carthage to use\n    title: Carthage version\n    value_options:\n    - default\n    - 0.9.4\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n"
  },
  {
    "path": "steps/carthage/1.0.2/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2015-11-06T08:32:58.942443976+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: daf9135550fb65ed0f9d291e357d9259d4ff5ba6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- carthage_version: default\n  opts:\n    summary: Specify system default, or latest (0.9.4) Carthage to use\n    title: Carthage version\n    value_options:\n    - default\n    - 0.9.4\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n"
  },
  {
    "path": "steps/carthage/1.0.3/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2015-11-25T11:16:52.17736794+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 5825a8ce53dc8ea91b6240295ba6ec88b3a1517c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n"
  },
  {
    "path": "steps/carthage/1.0.4/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2015-11-28T23:15:53.627741292+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: f955d6f6393bd1b1daf2a9479b6e116fc99dfcb1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n  platform: iOS\n"
  },
  {
    "path": "steps/carthage/1.0.5/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2015-12-13T14:00:54.436772834-05:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 6e5c311f8addc58dacbfab8370171c0debf5b7df\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n  platform: iOS\n"
  },
  {
    "path": "steps/carthage/1.0.6/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-01-09T15:03:54.312100561+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: c116e5609903706f284347b3028f9d19ad68e2c9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/1.0.7/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-01-27T09:03:45.204827659+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 833b276a303381122d8c16aaddd4ac75ff2863ce\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/1.0.8/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-02-04T13:23:53.000208105+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 1effd0f4e354a63eae96f43de288f8bd0e54f56d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.0.0/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-02-16T13:24:47.516629701+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 11a34efd1d91bf3526c55e9774712810656a2617\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.0.1/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-03-01T20:09:00.543133063+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 703f0c9f27c1e1a8d5e0f3fd4a6ad114ebd5a899\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.0.2/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-04-25T15:22:11.293557635+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 9b018394627823f766201a7d89f117b55af8b5c0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.1.0/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-05-07T17:11:48.64762042+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 6c2119092ca2fe493828c699ec1c59f76f5dd0a7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.1.1/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-05-19T23:17:26.811712728+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 21df866eb148bb9ed76066f9d99dfae8bd4d14d5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.1.2/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-07-12T11:39:42.182725985+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: c6d3aabf1c567b5ed8822b3f265ece1332ca35ab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.2.0/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-08-09T12:23:30.703108963+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 0f957ebf25ab188ce5826fb77be89d003a648e9e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n    - checkout\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.3.0/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-09-12T15:25:29.585572924+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 0dd1ff3bfceb57753f413a00c2008d5363104fc3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n    - checkout\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/2.4.0/step.yml",
    "content": "title: Carthage\nsummary: Installs and updates Carthage to the latest available version and runs selected\n  Carthage command.\ndescription: |-\n  Installs and updates Carthage to the latest available version and runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-09-26T12:51:47.073843718+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: d956cbaae5af18832a049a8f7926cf4e67248318\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- github_access_token: null\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n      * `bootstrap`: initializes the project with checking out & building all dependencies. (default)\n      * `update`: updates all dependencies.\n      * `build`: builds all checked out items.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n    value_options:\n    - bootstrap\n    - update\n    - build\n    - checkout\n- no_use_binaries: \"false\"\n  opts:\n    summary: |-\n      Use this flag to make sure Carthage checks out all dependencies (otherwise\n      it defaults to binary framework releases). False by default.\n    title: Set no use binaries flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    summary: Use this flag to have a verbose output of the carthage command. False\n      by default.\n    title: Set verbose output flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_output: \"false\"\n- opts:\n    summary: Use this flag to use ssh when cloning the repos. False by default.\n    title: Set ssh flag\n    value_options:\n    - \"true\"\n    - \"false\"\n  ssh_output: \"false\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the carthage command.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    title: Platform\n    value_options:\n    - iOS\n    - Mac\n    - iOS,Mac\n    - tvOS\n    - all\n  platform: iOS\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space\n      character.\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.0/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-11-18T12:28:37.362873487+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: e8e99608cd4dbf06b49ef79447faf654cbe97c1b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.1/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-12-12T15:55:59.430230419+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: e7af260128212d47ce353ef964d6a4b00de2ea08\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- carthage\n- system\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.2/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2016-12-19T15:49:57.840253427+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 1f253bcf19c7277fcdf428ed14d77573a48c5429\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- carthage\n- system\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.3/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2017-01-03T11:34:18.819624914+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: e84925394a76566594848fcc387292617baa4984\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- carthage\n- system\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: update\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.4/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2017-01-11T15:45:54.117541909+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 19048885d49d1429d8998f5eb0c7dbdab12086e8\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- carthage\n- system\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.5/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2017-02-01T13:57:24.375055358+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 39303ea45753d75082554f0a54a17921e25f2023\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- carthage\n- system\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.0.6/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2017-03-06T14:14:57.06436769+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 22804da8e664ce140aab0818fc7087b39d9ce2c4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.1.2/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2017-06-08T11:25:53.64580968+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 1fa4d7b2849ce0b5594591a0143b7c14424c769d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.1.3/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2017-12-04T12:18:05.545729597+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 79218595dd57a97c50e442f10e8163f07efafec7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with. The step will cache\n      your dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n"
  },
  {
    "path": "steps/carthage/3.1.4/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: !!timestamp 2018-05-07T15:35:42.565180175+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: e03a1aeda9ed7307ee5e0a171d197c2a6e665dfb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies with.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies with. The step will cache\n      your dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call: `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    title: Github Personal Access Token\n"
  },
  {
    "path": "steps/carthage/3.1.5/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2018-08-22T11:49:19.177848396Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 0b9a4a3c9617a8382567237ffd6eab12b27a883c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n"
  },
  {
    "path": "steps/carthage/3.1.6/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2018-12-14T15:03:32.614119707Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: cd8fba24290cf52d48ac947681cd179686d6cce3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n"
  },
  {
    "path": "steps/carthage/3.1.7/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2019-01-04T14:41:50.191277284Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 4fd1c3c8a64f3cd694e25b2e5f758827803b8ca7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n"
  },
  {
    "path": "steps/carthage/3.2.0/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2019-04-16T09:18:12.267124112Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: c7fd0c7768b7752b28e9f9d59546bd922fe9f72c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/carthage/3.2.1/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2019-06-17T09:54:13.248592987Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 16195e3c0c71ecbe27da75824068c6809cde0199\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/carthage/3.2.2/step.yml",
    "content": "title: Carthage\nsummary: Runs selected Carthage command.\ndescription: |-\n  Runs selected Carthage command. The step will cache your dependencies only when using `bootstrap` as `carthage_command` and you have `cache-pull` and `cache-push` steps in your workflow.\n  For more information about Carthage, visit the [Carthage GitHub page](https://github.com/Carthage/Carthage).\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2019-10-11T08:33:34.056777359Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: b77ae268a51afba1028176fc8425599399c21e83\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/carthage/3.2.3/step.yml",
    "content": "title: Carthage\nsummary: Runs the selected Carthage command.\ndescription: |-\n  Downloads and builds the dependencies your Cocoa application needs.\n\n  ### Configuring the Step\n  1. Add the **Carthage** Step in your Workflow.\n  2. Select `bootstrap` Carthage command in the **Carthage command to run** input. Make sure you have the **Bitrise.io Cache:Pull** Step before and the **Bitrise.io Cache:Push** Step after the **Carthage** Step in your Workflow to cache files and speed up your Bitrise build.\n  2. Provide your GitHub credentials in the **GitHub Personal Access Token** input to avoid GitHub rate limit issues. Don't worry, your credentials are safe with us since we store them encrypted and do not print them out in build logs.\n  3. Optionally, you can provide any extra flag for the Carthage command you wish to run in the **Additional options for Carthage command** input.\n  5. To get more information printed out, set the **Enable verbose logging** to `yes`.\n\n  ### Troubleshooting\n  It is important that you use `bootstrap` Carthage command, as this is the only command that can leverage the cache! If you run, for example, the `update` command, it won't generate the required cache information, because the `update` command will disregard the available files or the cache.\n\n  ### Useful links\n  - [Official Carthage documentation](https://github.com/Carthage/Carthage)\n  - [About Secrets and Env Vars ](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n\n  ### Related Steps\n  - [Bitrise.io Cache Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Bitrise.io Cache Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2020-05-28T09:17:16.783444487Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 499b84ff2a0a0d48e14e6973e64daacc9face68f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/carthage/3.2.4/step.yml",
    "content": "title: Carthage\nsummary: Runs the selected Carthage command.\ndescription: |-\n  Downloads and builds the dependencies your Cocoa application needs.\n\n  ### Configuring the Step\n  1. Add the **Carthage** Step in your Workflow.\n  2. Select `bootstrap` Carthage command in the **Carthage command to run** input. Make sure you have the **Bitrise.io Cache:Pull** Step before and the **Bitrise.io Cache:Push** Step after the **Carthage** Step in your Workflow to cache files and speed up your Bitrise build.\n  2. Provide your GitHub credentials in the **GitHub Personal Access Token** input to avoid GitHub rate limit issues. Don't worry, your credentials are safe with us since we store them encrypted and do not print them out in build logs.\n  3. Optionally, you can provide any extra flag for the Carthage command you wish to run in the **Additional options for Carthage command** input.\n  5. To get more information printed out, set the **Enable verbose logging** to `yes`.\n\n  ### Troubleshooting\n  It is important that you use `bootstrap` Carthage command, as this is the only command that can leverage the cache! If you run, for example, the `update` command, it won't generate the required cache information, because the `update` command will disregard the available files or the cache.\n\n  ### Useful links\n  - [Official Carthage documentation](https://github.com/Carthage/Carthage)\n  - [About Secrets and Env Vars ](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n\n  ### Related Steps\n  - [Bitrise.io Cache Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Bitrise.io Cache Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2020-10-20T09:33:47.410039459Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: 6702c999b3e387404abad0bfd8bc8a05a18d08de\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: go\n  - name: carthage\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: \"Options added to the end of the Carthage call.\\nYou can use multiple\n      options, separated by a space character.\\n\\nTo see available command's options,\n      call `carthage help COMMAND` \\n\\nFormat example: `--platform ios`\"\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: \"Use this input to avoid Github rate limit issues.\\n\\nSee the github's\n      guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      \\  \\nhow to create Personal Access Token.\\n\\n__UNCHECK EVERY SCOPE BOX__ when\n      creating this token. There is no reason this token needs access to private information.\"\n    is_sensitive: true\n    title: Github Personal Access Token\n- opts:\n    description: |-\n      Use this input to provide an `xcconfig` file as a workaround for the Xcode 12 issue. For more information, see [the Github issue](https://github.com/Carthage/Carthage/issues/3019).\n\n      Can either be a local file provided with the `file://` scheme (like `file://path/to/file.xcconfig`) or an URL (like https://domain.com/file.xconfig).\n    title: Custom xcconfig file to add to Carthage environment\n  xcconfig: null\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/carthage/3.2.5/step.yml",
    "content": "title: Carthage\nsummary: Runs the selected Carthage command.\ndescription: |-\n  Downloads and builds the dependencies your Cocoa application needs.\n\n  ### Configuring the Step\n  1. Add the **Carthage** Step in your Workflow.\n  2. Select `bootstrap` Carthage command in the **Carthage command to run** input. Make sure you have the **Bitrise.io Cache:Pull** Step before and the **Bitrise.io Cache:Push** Step after the **Carthage** Step in your Workflow to cache files and speed up your Bitrise build.\n  2. Provide your GitHub credentials in the **GitHub Personal Access Token** input to avoid GitHub rate limit issues. Don't worry, your credentials are safe with us since we store them encrypted and do not print them out in build logs.\n  3. Optionally, you can provide any extra flag for the Carthage command you wish to run in the **Additional options for Carthage command** input.\n  5. To get more information printed out, set the **Enable verbose logging** to `yes`.\n\n  ### Troubleshooting\n  It is important that you use `bootstrap` Carthage command, as this is the only command that can leverage the cache! If you run, for example, the `update` command, it won't generate the required cache information, because the `update` command will disregard the available files or the cache.\n\n  ### Useful links\n  - [Official Carthage documentation](https://github.com/Carthage/Carthage)\n  - [About Secrets and Env Vars ](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n\n  ### Related Steps\n  - [Bitrise.io Cache Push](https://www.bitrise.io/integrations/steps/cache-push)\n  - [Bitrise.io Cache Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\nwebsite: https://github.com/bitrise-steplib/steps-carthage\nsource_code_url: https://github.com/bitrise-steplib/steps-carthage\nsupport_url: https://github.com/bitrise-steplib/steps-carthage/issues\npublished_at: 2025-11-11T08:08:56.609293873Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-carthage.git\n  commit: d5fcfc35dbc106cb3de574e0f527d033cc7fe373\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-carthage\ndeps:\n  brew:\n  - name: carthage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- carthage_command: bootstrap\n  opts:\n    description: |-\n      Select a command to set up your dependencies.\n\n      The step will cache your dependencies only when using `bootstrap` in this input and you have `cache-pull` and `cache-push` steps in your workflow.\n\n      To see available commands run: `carthage help` on your local machine.\n    is_required: true\n    summary: Select a command to set up your dependencies. The step will cache your\n      dependencies only when using `bootstrap` in this input and you have `cache-pull`\n      and `cache-push` steps in your workflow.\n    title: Carthage command to run\n- carthage_options: null\n  opts:\n    description: |-\n      Options added to the end of the Carthage call.\n      You can use multiple options, separated by a space character.\n\n      To see available command's options, call `carthage help COMMAND`\n\n      Format example: `--platform ios`\n    title: Additional options for `carthage` command\n- github_access_token: $GITHUB_ACCESS_TOKEN\n  opts:\n    description: |-\n      Use this input to avoid Github rate limit issues.\n\n      See the github's guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/),\n      how to create Personal Access Token.\n\n      __UNCHECK EVERY SCOPE BOX__ when creating this token. There is no reason this token needs access to private information.\n    is_sensitive: true\n    title: Github Personal Access Token\n- opts:\n    description: |-\n      Use this input to provide an `xcconfig` file as a workaround for the Xcode 12 issue. For more information, see [the Github issue](https://github.com/Carthage/Carthage/issues/3019).\n\n      Can either be a local file provided with the `file://` scheme (like `file://path/to/file.xcconfig`) or an URL (like https://domain.com/file.xconfig).\n    title: Custom xcconfig file to add to Carthage environment\n  xcconfig: null\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/carthage/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.1.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-09-08T20:42:31.613406136+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 70d1670d587d826de7aca508d1d870e2cfb8b5e4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.1.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-09-12T13:09:48.258176257+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: dc2daacc26007f8f2f8ae98eba0afd7548d2cc19\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the certificate and the mobile provisioning profiles\ndescription: |-\n  Need to use your Provisioning Profiles and Certificates? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2018-07-05T15:08:56.053716284+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 95edb3f054d2f1ccab2b8b80dcc4282e4931a488\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the certificate and the mobile provisioning profiles\ndescription: |-\n  Need to use your Provisioning Profiles and Certificates? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2018-08-22T12:12:24.145450751Z\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: a03d4cd955e177eed8e95b9c3fc6bd61601d16da\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Certificate passphrase of the default certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2019-12-12T14:10:49.438785564Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: adeac771f6a22a2cdd36e764998192f1107bf338\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Certificate passphrase of the default certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.3/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2020-02-13T16:15:38.518433934Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 2bba6a2304ffd0abfdf440d79b1e4fa261a31517\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Certificate passphrase of the default certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.4/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2022-01-27T14:37:51.004599045Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 102f49f39f5169ecad39f12e0c0c2c0fb3994d5e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Certificate passphrase of the default certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.5/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2022-05-31T14:59:25.895869739Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 280c4dad6f93346ac49c7e00e36053c9d3adea3d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.10.6/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2023-01-06T14:13:54.216752147Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: b113c98f09ce02e1bc7c60c87d9b53ed25605c97\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.11.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2023-08-30T06:21:35.689533933Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 904379c99832962da0a591f0bc7902acb4f687a1\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.11.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2024-01-29T19:03:49.983090072Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: b4a283a10b90e6e591856b0d70656df0b75fc923\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.11.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2024-02-15T08:41:39.358309133Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 2184d651f98a082eae3ebe0bb962c349866ad8eb\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.11.3/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2024-02-16T09:53:29.801866375Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 6eb01257fcc50554f09ab3ebfcb72b6db6f75788\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.11.4/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2024-08-23T12:58:34.654804507Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: ae6aadf210f01b414e43b94f603d59d2813b1ed9\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.11.5/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Downloads and installs the Apple code signing certificates and provisioning\n  profiles.\ndescription: |-\n  The Step installs those .p12 certificate files and provisioning profiles that you uploaded to your app's **Code Signing** tab. You can upload multiple versions of any code signing file.\n\n  ### Configuring the Step\n\n  By default, the Step requires no configuration. To be able to use it, you only need to upload a .p12 certificate and a matching provisioning profile to the **Code signing** tab.\n\n  However, if your certificates have passphrases, you need to make sure that passphrase is available for the Step.\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) that contains the passphrase.\n  1. Insert that Secret to the **Certificate passphrase** input.\n\n  Similarly, you can set the path to the Keychain that should be used in the **Keychain path** input, and set a password for the Keychain in the **Keychain's password** input.\n\n  ### Troubleshooting\n\n  In the case of most code signing issues, it's the **Xcode Archive & Export for iOS** Step that fails, not this one. If this Step fails, there's a couple of things you can do first.\n\n  - Check the certificate passphrase, the Keychain path and the Keychain password.\n  - Make sure you uploaded the required code signing files.\n\n  ### Useful links\n  - [iOS code signing](https://devcenter.bitrise.io/code-signing/ios-code-signing/code-signing-index/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer/issues\npublished_at: 2025-11-13T08:24:19.181689181Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-certificate-and-profile-installer.git\n  commit: 0536140cd8f5a8257e07e695d44f77bb349e2b12\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-certificate-and-profile-installer\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe character (`|`).\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n      Pipe characters in passphrases are not supported.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    is_sensitive: true\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./Cert.p12`\n    is_sensitive: true\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Passphrase of the default Certificate.\n    is_sensitive: true\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example `file://./BuildAnything.mobileprovision`\n    is_sensitive: true\n    title: Default Provisioning profile URL\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.2.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-09-14T14:15:22.562810649+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 38cc056cb996ea63daaba8044ce6abc16a9ded07\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.2.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: Certificate and profile installer\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-09-24T21:02:51.766572121+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 57f127a6366b7308241d7f84764be0ee5102281a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.2.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-11-06T19:18:07.468318355+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: f61d71f413ddb2b6ee6d4c6f8ba6f847a477e881\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.3.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-11-23T14:33:44.221787557+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 49a3fc24a1402a43e5d8db20ea891168be9e383d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.4.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2015-12-11T13:52:56.343779626+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 5da704a8b7ec72c1d03be1c17188aabf98f829aa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.4.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-04-21T19:53:55.517140135+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 78f3f0d3e9fb48331612da1a13e351e7d0d0ab35\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.4.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-04-22T17:22:25.903151648+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 2f5b45a3ff5a7df7521bef111717b15f6aeb5be5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    description: |-\n      **Will only export the Profile ID if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile ID\n- BITRISE_PROVISIONING_PROFILE_PATH: null\n  opts:\n    description: |-\n      **Will only export the Profile Path if you specify\n      a single Provisioning Profile!**\n    title: Activated Provisioning Profile Path\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Certificate ID\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.5.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-06-01T12:57:53.050189478+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 0c9db391991a27838a43509c7b77c9cdc4acf779\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    is_required: true\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    is_required: true\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    summary: \"\"\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    summary: \"\"\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    is_required: true\n    summary: \"\"\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.5.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-06-07T13:59:04.104192547+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: e8ea2f15b6763db491d48faa1a854d0ff4bd7096\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    summary: \"\"\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    summary: \"\"\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    summary: \"\"\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    summary: \"\"\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    summary: \"\"\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    summary: \"\"\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.6.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-07-12T12:27:06.700374181+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: d68aa75337a6c94d34b7ab2a7bda0939ae7ea470\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n- export_certificate_and_profile_infos: \"false\"\n  opts:\n    description: \"Set this input to `\\\"true\\\"` to allow exporting:\\n\\n-  `BITRISE_PROVISIONING_PROFILE_ID`\\n-\n      \\ `BITRISE_PROVISIONING_PROFILE_PATH`\\n-  `BITRISE_CODE_SIGN_IDENTITY`\\n\\n__Notes__:\\n\\n-\n      BITRISE_PROVISIONING_PROFILE_ID and BITRISE_PROVISIONING_PROFILE_PATH:    \\n\n      \\ Will only export the Profile ID and path if you specify a __single__ Provisioning\n      Profile URL as `provisioning_profile_url` input value, or\\n  if you leave `provisioning_profile_url`\n      empty, then Default Provisioning Profile will be exported (if defined)!\\n- BITRISE_CODE_SIGN_IDENTITY:\n      \\ \\n  Will export the Certificate Identity defined with `certificate_url`, if\n      `certificate_url` is empty, then \\n  default Certificate Identity will be exported\n      (if defined)!\\n- __Do not use this input if it is not neccessery__, instead\n      specify the profiles direct where you want to use them:  \\n  __Code Signing\n      Identity may contains special characters, exporting these as an environment\n      variable could break the next steps.__\\n\"\n    title: Should export Certificate and Provisioning Profile infos\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_PROVISIONING_PROFILE_ID: null\n  opts:\n    title: Activated Provisioning Profile ID\n- BITRISE_PROVISIONING_PROFILE_PATH: null\n  opts:\n    title: Activated Provisioning Profile Path\n- BITRISE_CODE_SIGN_IDENTITY: null\n  opts:\n    title: Activated Code Signing Identity\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.7.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-09-15T16:06:13.359204541+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 3b93dbdc063cbf68ef79e936cd12602768b8f2c0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-10-25T14:29:17.041202838+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 48466c9990a833337c72f37585042288453d4725\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-10-28T17:54:34.898391536+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: e018fc70b01a7ef014b6a8bb1b474c7b26947776\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- security\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2016-12-20T13:42:23.047198886+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 71d1deaf3627ff4ee73175a8800dade1197aa43d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- security\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.3/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-03-03T13:56:10.46146506+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 7de9c807a6386da8aa41e1d318dff7eb244cbdfe\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- security\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.4/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-03-10T12:31:55.848765014+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: a4bb22a04885827bb1cb75e69841dd895fa80178\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- security\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.5/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-04-13T16:16:58.592052244+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: e3f15723924295822594dc9ebf1f6f5c01d423a3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- \"code sign\"\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.6/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-06-12T15:11:14.675803995+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 0f42d5b101d0bcf3754b8a18087df2a57467de2b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Config\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Config\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    category: Config\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Debug\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.7/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-07-24T17:15:14.117067266+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 3c6dd1cf1e3ebdc44e4888c035b6be735ab61c59\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Config\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Config\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    category: Config\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Debug\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.8.8/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-08-11T10:29:44.475244016+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 31a5db1ac71e1c4e25450fef9e0181b0d344bef0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Config\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Config\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    category: Config\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Debug\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.9.0/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-09-29T13:33:45.791847322+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 1b0e0a5984c01f503006e5160dfebb77d648f6a0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Config\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Config\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    category: Config\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Debug\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.9.1/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profile and Certificate? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-10-06T17:31:39.56672712+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 822430417b0eb2c105271064b657dc4dd9c866a7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Config\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Config\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    category: Config\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Debug\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.9.2/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profiles and Certificates? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: 2017-10-20T17:36:05.282296374+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: 2af25e7ce666deac70968b71aa7bd276f104481d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Config\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Config\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    category: Config\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    is_required: true\n    title: Keychain's password\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Debug\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Debug\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/1.9.3/step.yml",
    "content": "title: Certificate and profile installer\nsummary: |-\n  Need to use your Provisioning Profiles and Certificates? Use this Step to\n  add them to the keychain and use it as you wish! No worries, as our security\n  policy goes, the VM is reverted after running the workflow so there's no\n  trace of these left on them.\ndescription: Downloads and installs the certificate and the mobile provisioning profiles\nwebsite: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsource_code_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer\nsupport_url: https://github.com/bitrise-io/steps-certificate-and-profile-installer/issues\npublished_at: !!timestamp 2018-05-07T13:14:05.692541576+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-certificate-and-profile-installer.git\n  commit: d482bca5fd93d5163509e092e999c50ac87638fb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-certificate-and-profile-installer\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- certificate_url: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: |\n      URL of the certificate to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Certificate URL\n- certificate_passphrase: $BITRISE_CERTIFICATE_PASSPHRASE\n  opts:\n    description: |\n      Certificate passphrase. Multiple passphrases can be\n      specified, separated by a pipe (`|`) character.\n\n      Specified Certificate passphrase count should match the count of the certificate urls.\n\n      Format example:\n\n      - 1 certificate provided with passphrase: `PASS`\n      - 1 certificate provided without passphrase: ``\n      - 3 certificates provided, none of them has passphrase: `||`\n      - 3 certificates provided, only the 2. one has passphrase: `|PASS|`\n    title: Certificate passphrase\n- opts:\n    description: |\n      URL of the provisioning profile to download. Multiple URLs can be\n      specified, separated by a pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Provisioning profile URL\n  provisioning_profile_url: $BITRISE_PROVISION_URL\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    is_required: true\n    title: Keychain Path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    is_required: true\n    title: Keychain's password\n- install_defaults: \"yes\"\n  opts:\n    category: Default Codesign Files\n    description: Installs default (Bitrise) Wildcard Provisioning Profile and Codesign\n      Certificate for testing.\n    summary: Installs default (Bitrise) Wildcard Codesign Files.\n    title: Installs default Codesign Files\n    value_options:\n    - \"no\"\n    - \"yes\"\n- default_certificate_url: $BITRISE_DEFAULT_CERTIFICATE_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default certificate.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./Cert.p12`\n    title: Default Certificate URL\n- default_certificate_passphrase: $BITRISE_DEFAULT_CERTIFICATE_PASSPHRASE\n  opts:\n    category: Default Codesign Files\n    description: |\n      Certificate passphrase of the default certificate.\n    title: Default Certificate passphrase\n- default_provisioning_profile_url: $BITRISE_DEFAULT_PROVISION_URL\n  opts:\n    category: Default Codesign Files\n    description: |\n      URL of the default provisioning profile to download.\n\n      You can specify a local path as well, using the `file://` scheme.\n      Example: `file://./BuildAnything.mobileprovision`\n    title: Default Provisioning profile URL\n"
  },
  {
    "path": "steps/certificate-and-profile-installer/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/change-android-applicationid/1.0.0/step.yml",
    "content": "title: Change Android applicationId\nsummary: Updates the Android applicationId in your project's `build.gradle` file.\ndescription: |-\n  Modifies the applicationId of your Android app by updating applicationId in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android applicationId** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the applicationId attributes.\n  4. Provide a new applicationId in the **New applicationId** input. If you leave this input empty, the previous applicationId will be displayed on Google Play Store. The input's value must be a string in this format.\n\n  ### Troubleshooting\n\n  The **Change Android applicationId** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right applicationId to Google Play Store.\n\n  ### Related Steps\n\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/gambit66/bitrise-steps-change-android-applicationId\nsource_code_url: https://github.com/gambit66/bitrise-steps-change-android-applicationId\nsupport_url: https://github.com/gambit66/bitrise-steps-change-android-applicationId\npublished_at: 2022-01-27T16:09:21.626071+02:00\nsource:\n  git: https://github.com/gambit66/bitrise-steps-change-android-applicationId.git\n  commit: 108a5c7494319d12a11f50b34105600ac7fc73d0\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/gambit66/bitrise-steps-change-android-applicationId\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the applicationId setting.\n    title: Path to the build.gradle file\n- new_application_id: null\n  opts:\n    description: \"New applicationId to set.  \\nSpecify a string value, such as `com.mycompany.myapp`.\"\n    is_required: true\n    summary: New applicationId to set.\n    title: New applicationId\noutputs:\n- ANDROID_APPLICATION_ID: null\n  opts:\n    title: Final Android applicationId in build.gradle file\n"
  },
  {
    "path": "steps/change-android-applicationid/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/0.9.0/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Set or bump your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2017-06-08T15:44:52.93020351+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname.git\n  commit: de6981df8233a356a3694a540598a2cc40a3090f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: Path to the build.gradle file shows the versionCode and versionName\n    settings\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_code: null\n  opts:\n    description: |-\n      New versionCode to set.\n      Leave this input empty to do not modify versionCode.\n    summary: New versionCode to set.\n    title: New versionCode\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n      Leave this input empty to do not modify versionName.\n    summary: New versionName to set.\n    title: New versionName\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.0.0/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Change your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2018-01-24T14:39:59.791566+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname.git\n  commit: ab1e3600b7962b1dfbece8607acc1d8ffcfa93ff\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: null\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n      Leave this input empty to do not modify versionName.\n    summary: New versionName to set.\n    title: New versionName\n- new_version_code: null\n  opts:\n    description: |-\n      New versionCode to set.\n      Leave this input empty to do not modify versionCode.\n    summary: New versionCode to set.\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n      Leave this input empty to do not modify versionCode.\n    summary: Offset value for versionCode.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.0.1/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Change your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: !!timestamp 2018-03-29T15:22:52.276541532+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname.git\n  commit: bce347f8236432c5a1546ba24d52a33190e0dc60\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty to do not modify versionName.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty to do not modify versionName.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.1.0/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Change your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: !!timestamp 2018-04-26T13:08:38.136734716+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname.git\n  commit: a84f5a93c71e940e9f87e06ec77d140db4411855\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty to do not modify versionName.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty to do not modify versionName.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.1.1/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Change your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2018-05-30T14:30:28.617480918+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname.git\n  commit: a54ad9f155890423d6bff0e74b567a47b7838090\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty to do not modify versionName.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty to do not modify versionName.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.2.0/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Change your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\npublished_at: 2019-11-08T13:54:54.514943446Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: 638551a410bd4355239d3f669cad7c80a1ee29ca\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      so that versionCode remains unchanged. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.2.1/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Change Android versionCode and versionName in build.gradle file.\ndescription: Change your Android project's versionCode and versionName in build.gradle\n  file.\nwebsite: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\npublished_at: 2019-11-11T10:41:38.513157243Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: 13dbe83cefc3b674d09a3cab96f434ba3d3343a3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      so that versionCode remains unchanged. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.2.2/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Updates the Android versionCode and versionName in your project's `build.gradle`\n  file.\ndescription: |-\n  Modifies the version information of your Android app by updating versionCode and versionName attributes in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android versionCode and versionName** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the versionCode and versionName attributes.\n  4. Provide a new versionName in the **New versionName** input. If you leave this input empty, the previous versionName will be displayed on Google Play Store. The input's value must be a string in this format `<major>.<minor>.<point>`.\n  5. Provide a versionCode in the **New versionCode** input to track app versions. If you leave this input empty, you will release your app with the version that is already set in the `build.gradle` file's `versionCode` attribute. The input's value must be an integer.\n  If you wish to offset the value you set in the **New versionCode** input, then you can use the **versionCode Offset** input to add the offset integer value here. This number will be added to the versionCode's value.\n\n  ### Troubleshooting\n\n  The **Change Android versionCode and versionName** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right versionCode and versionName to Google Play Store.\n\n\n  ### Useful links\n\n  [About Android versionCode and versionNumber](https://developer.android.com/studio/publish/versioning)\n  [Build versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)\n\n\n  ### Related Steps\n\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2020-01-09T09:40:05.826373216Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: ad7b04b90c323444a9bd119115ac752a4cb485cd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      so that versionCode remains unchanged. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.2.3/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Updates the Android versionCode and versionName in your project's `build.gradle`\n  file.\ndescription: |-\n  Modifies the version information of your Android app by updating versionCode and versionName attributes in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android versionCode and versionName** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the versionCode and versionName attributes.\n  4. Provide a new versionName in the **New versionName** input. If you leave this input empty, the previous versionName will be displayed on Google Play Store. The input's value must be a string in this format `<major>.<minor>.<point>`.\n  5. Provide a versionCode in the **New versionCode** input to track app versions. If you leave this input empty, you will release your app with the version that is already set in the `build.gradle` file's `versionCode` attribute. The input's value must be an integer.\n  If you wish to offset the value you set in the **New versionCode** input, then you can use the **versionCode Offset** input to add the offset integer value here. This number will be added to the versionCode's value.\n\n  ### Troubleshooting\n\n  The **Change Android versionCode and versionName** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right versionCode and versionName to Google Play Store.\n\n\n  ### Useful links\n\n  - [About Android versionCode and versionNumber](https://developer.android.com/studio/publish/versioning)\n  - [Build versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)\n\n\n  ### Related Steps\n\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2020-02-13T16:14:22.671904901Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: 00d989bfc8a69a834b70222e4499d81cf9582556\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    summary: |-\n      New versionName to set.\n\n      For example: 1.0.0\n\n      Leave this input empty so that versionName remains unchanged.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      so that versionCode remains unchanged. \"\n    summary: \"New versionCode to set.\\n\\nFor example: 1\\n\\nLeave this input empty\n      to do not modify versionCode. \"\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    summary: |-\n      Offset value for versionCode.\n\n      For example: 1\n\n      Leave this input empty if you want the exact value you set in\n      `New versionCode` input otherwise it will be added to it.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.2.4/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Updates the Android versionCode and versionName in your project's `build.gradle`\n  file.\ndescription: |-\n  Modifies the version information of your Android app by updating versionCode and versionName attributes in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android versionCode and versionName** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the versionCode and versionName attributes.\n  4. Provide a new versionName in the **New versionName** input. If you leave this input empty, the previous versionName will be displayed on Google Play Store. The input's value must be a string in this format `<major>.<minor>.<point>`.\n  5. Provide a versionCode in the **New versionCode** input to track app versions. If you leave this input empty, you will release your app with the version that is already set in the `build.gradle` file's `versionCode` attribute. The input's value must be an integer.\n  If you wish to offset the value you set in the **New versionCode** input, then you can use the **versionCode Offset** input to add the offset integer value here. This number will be added to the versionCode's value.\n\n  ### Troubleshooting\n\n  The **Change Android versionCode and versionName** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right versionCode and versionName to Google Play Store.\n\n\n  ### Useful links\n\n  - [About Android versionCode and versionNumber](https://developer.android.com/studio/publish/versioning)\n  - [Build versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)\n\n\n  ### Related Steps\n\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2021-04-09T13:11:32.158824109Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: 40c2b0c1d5b2e3946d672f0785b38339ed0a4cc2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: \"New versionName to set.  \\nSpecify a string value, such as `\\\"1.0.0\\\"`.\n      \\ \\nIf the specified value is not surranded by double quote (`\\\"`) characters,\n      the step will add them.  \\nLeave this input empty so that versionName remains\n      unchanged.\"\n    summary: New versionName to set.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.  \\nSpecify a positive integer value, such\n      as `1`.  \\nThe greatest value Google Play allows for versionCode is 2100000000.\n      \\ \\nLeave this input empty so that versionCode remains unchanged.\"\n    summary: New versionCode to set.\n    title: New versionCode\n- opts:\n    description: \"Offset value to add to `New versionCode`, for example: `1`.  \\nLeave\n      this input empty if you want the exact value you set in `New versionCode` input.\"\n    summary: Offset value to add to `New versionCode`.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.3.0/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Updates the Android versionCode and versionName in your project's `build.gradle`\n  file.\ndescription: |-\n  Modifies the version information of your Android app by updating versionCode and versionName attributes in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android versionCode and versionName** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the versionCode and versionName attributes.\n  4. Provide a new versionName in the **New versionName** input. If you leave this input empty, the previous versionName will be displayed on Google Play Store. The input's value must be a string in this format `<major>.<minor>.<point>`.\n  5. Provide a versionCode in the **New versionCode** input to track app versions. If you leave this input empty, you will release your app with the version that is already set in the `build.gradle` file's `versionCode` attribute. The input's value must be an integer.\n  If you wish to offset the value you set in the **New versionCode** input, then you can use the **versionCode Offset** input to add the offset integer value here. This number will be added to the versionCode's value.\n\n  ### Troubleshooting\n\n  The **Change Android versionCode and versionName** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right versionCode and versionName to Google Play Store.\n\n\n  ### Useful links\n\n  - [About Android versionCode and versionNumber](https://developer.android.com/studio/publish/versioning)\n  - [Build versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)\n\n\n  ### Related Steps\n\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2021-08-31T09:20:13.535442016Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: b76a3241af83dc8cc474d4988eb0c33c8e3cc6e6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: \"New versionName to set.  \\nSpecify a string value, such as `\\\"1.0.0\\\"`.\n      \\ \\nIf the specified value is not surranded by double quote (`\\\"`) characters,\n      the step will add them.  \\nLeave this input empty so that versionName remains\n      unchanged.\"\n    summary: New versionName to set.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.  \\nSpecify a positive integer value, such\n      as `1`.  \\nThe greatest value Google Play allows for versionCode is 2100000000.\n      \\ \\nClear this input's default value to leave the versionCode unchanged.\"\n    summary: New versionCode to set.\n    title: New versionCode\n- opts:\n    description: \"Offset value to add to `New versionCode`, for example: `1`.  \\nLeave\n      this input empty if you want the exact value you set in `New versionCode` input.\"\n    summary: Offset value to add to `New versionCode`.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.3.1/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Updates the Android versionCode and versionName in your project's `build.gradle`\n  file.\ndescription: |-\n  Modifies the version information of your Android app by updating versionCode and versionName attributes in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android versionCode and versionName** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the versionCode and versionName attributes.\n  4. Provide a new versionName in the **New versionName** input. If you leave this input empty, the previous versionName will be displayed on Google Play Store. The input's value must be a string in this format `<major>.<minor>.<point>`.\n  5. Provide a versionCode in the **New versionCode** input to track app versions. If you leave this input empty, you will release your app with the version that is already set in the `build.gradle` file's `versionCode` attribute. The input's value must be an integer.\n  If you wish to offset the value you set in the **New versionCode** input, then you can use the **versionCode Offset** input to add the offset integer value here. This number will be added to the versionCode's value.\n\n  ### Troubleshooting\n\n  The **Change Android versionCode and versionName** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right versionCode and versionName to Google Play Store.\n\n\n  ### Useful links\n\n  - [About Android versionCode and versionNumber](https://developer.android.com/studio/publish/versioning)\n  - [Build versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)\n\n\n  ### Related Steps\n\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2024-04-16T10:25:23.340008099Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: aafc3a83555497f47c9fd69bb34afef06886f6f1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: \"New versionName to set.  \\nSpecify a string value, such as `\\\"1.0.0\\\"`.\n      \\ \\nIf the specified value is not surranded by double quote (`\\\"`) characters,\n      the step will add them.  \\nLeave this input empty so that versionName remains\n      unchanged.\"\n    summary: New versionName to set.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: \"New versionCode to set.  \\nSpecify a positive integer value, such\n      as `1`.  \\nThe greatest value Google Play allows for versionCode is 2100000000.\n      \\ \\nClear this input's default value to leave the versionCode unchanged.\"\n    summary: New versionCode to set.\n    title: New versionCode\n- opts:\n    description: \"Offset value to add to `New versionCode`, for example: `1`.  \\nLeave\n      this input empty if you want the exact value you set in `New versionCode` input.\"\n    summary: Offset value to add to `New versionCode`.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/1.3.2/step.yml",
    "content": "title: Change Android versionCode and versionName\nsummary: Updates the Android versionCode and versionName in your project's `build.gradle`\n  file.\ndescription: |-\n  Modifies the version information of your Android app by updating versionCode and versionName attributes in your project's `build.gradle` file before you'd publish your app to Google Play Store.\n\n  ### Configuring the Step\n\n  1. Insert the **Change Android versionCode and versionName** Step before a build Step such as **Android Build** or **Gradle Runner** in your Workflow.\n  2. Click the Step to modify its input fields.\n  3. Add the file path to the **Path to the build.gradle file** so that the Step knows where to find the file that contains the versionCode and versionName attributes.\n  4. Provide a new versionName in the **New versionName** input. If you leave this input empty, the previous versionName will be displayed on Google Play Store. The input's value must be a string in this format `<major>.<minor>.<point>`.\n  5. Provide a versionCode in the **New versionCode** input to track app versions. If you leave this input empty, you will release your app with the version that is already set in the `build.gradle` file's `versionCode` attribute. The input's value must be an integer.\n  If you wish to offset the value you set in the **New versionCode** input, then you can use the **versionCode Offset** input to add the offset integer value here. This number will be added to the versionCode's value.\n\n  ### Troubleshooting\n\n  The **Change Android versionCode and versionName** Step must be inserted BEFORE the **Android Build** Step as the former makes sure you  upload the build with the right versionCode and versionName to Google Play Store.\n\n  ### Useful links\n\n  - [About Android versionCode and versionNumber](https://developer.android.com/studio/publish/versioning)\n  - [Build versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)\n\n  ### Related Steps\n\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsource_code_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\nsupport_url: https://github.com/bitrise-community/steps-change-android-versioncode-and-versionname\npublished_at: 2025-11-14T12:45:22.30645714Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname.git\n  commit: 33b9248fe360b008d2a056d13cafdc96c87acc6f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-android-versioncode-and-versionname\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the build.gradle file shows the versionCode and versionName settings.\n    title: Path to the build.gradle file\n- new_version_name: null\n  opts:\n    description: |-\n      New versionName to set.\n      Specify a string value, such as `\"1.0.0\"`.\n      If the specified value is not surranded by double quote (`\"`) characters, the step will add them.\n      Leave this input empty so that versionName remains unchanged.\n    summary: New versionName to set.\n    title: New versionName\n- new_version_code: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |-\n      New versionCode to set.\n      Specify a positive integer value, such as `1`.\n      The greatest value Google Play allows for versionCode is 2100000000.\n      Clear this input's default value to leave the versionCode unchanged.\n    summary: New versionCode to set.\n    title: New versionCode\n- opts:\n    description: |-\n      Offset value to add to `New versionCode`, for example: `1`.\n      Leave this input empty if you want the exact value you set in `New versionCode` input.\n    summary: Offset value to add to `New versionCode`.\n    title: versionCode Offset\n  version_code_offset: null\noutputs:\n- ANDROID_VERSION_NAME: null\n  opts:\n    description: The final Android versionName set in the build.gradle file after\n      the Step execution.\n    title: Final Android versionName in build.gradle file\n- ANDROID_VERSION_CODE: null\n  opts:\n    description: The final Android versionCode set in the build.gradle file after\n      the Step execution.\n    title: Final Android versionCode in build.gradle file\n"
  },
  {
    "path": "steps/change-android-versioncode-and-versionname/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/change-value/1.0.1/step.yml",
    "content": "title: Change value in file\nsummary: Change value in file. (e.g. constants)\ndescription: Change value in file. (e.g. constants)\nwebsite: https://github.com/bitrise-community/steps-change-value\nsource_code_url: https://github.com/bitrise-community/steps-change-value\nsupport_url: https://github.com/bitrise-community/steps-change-value/issues\npublished_at: 2016-06-15T21:38:10.028822047+03:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-value.git\n  commit: ccdfb68e12dc54683f6b4f7deef1fa9fa9702da6\ntype_tags:\n- utility\ninputs:\n- file: null\n  opts:\n    description: |\n      The file that you want to change a value.\n    is_required: true\n    summary: \"\"\n    title: File path\n- old_value: null\n  opts:\n    description: |\n      current value in file\n    is_required: true\n    summary: For replace\n    title: Old value\n- new_value: null\n  opts:\n    description: |\n      new value\n    is_required: true\n    summary: To replace\n    title: New value\n- opts:\n    is_required: false\n    summary: For debug\n    title: Show old and new file content\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_file: \"false\"\n- notfound_exit: \"true\"\n  opts:\n    is_required: false\n    summary: To mark a step as \"Failed\" if value for replacing isn't found.\n    title: Mark as \"Failed\" if value isn't found.\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-value/1.1.0/step.yml",
    "content": "title: Change value in file\nsummary: Change value in file. (e.g. constants)\ndescription: Change value in file. (e.g. constants)\nwebsite: https://github.com/bitrise-community/steps-change-value\nsource_code_url: https://github.com/bitrise-community/steps-change-value\nsupport_url: https://github.com/bitrise-community/steps-change-value/issues\npublished_at: 2017-06-01T22:39:23.437467209+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-change-value.git\n  commit: 9ee4c026ecba828de47220536f2c4f86b60ff6f1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-change-value\ninputs:\n- file: null\n  opts:\n    description: |\n      The file that you want to change a value.\n    is_required: true\n    summary: \"\"\n    title: File path\n- old_value: null\n  opts:\n    description: |\n      current value in file\n    is_required: true\n    summary: For replace\n    title: Old value\n- new_value: null\n  opts:\n    description: |\n      new value\n    is_required: true\n    summary: To replace\n    title: New value\n- opts:\n    summary: For debug\n    title: Show old and new file content\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_file: \"false\"\n- notfound_exit: \"true\"\n  opts:\n    summary: To mark a step as \"Failed\" if value for replacing isn't found.\n    title: Mark as \"Failed\" if value isn't found.\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-value/1.1.1/step.yml",
    "content": "title: Change value in file\nsummary: Change value in file. (e.g. constants)\ndescription: Change value in file. (e.g. constants)\nwebsite: https://github.com/bitrise-steplib/steps-change-value\nsource_code_url: https://github.com/bitrise-steplib/steps-change-value\nsupport_url: https://github.com/bitrise-steplib/steps-change-value/issues\npublished_at: 2020-09-21T09:31:06.524544486Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-value.git\n  commit: 0e1b11a92d02ab6524b1a21db0bdda58b0ae0379\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-value\ninputs:\n- file: null\n  opts:\n    description: |\n      The file that you want to change a value.\n    is_required: true\n    summary: \"\"\n    title: File path\n- old_value: null\n  opts:\n    description: |\n      current value in file\n    is_required: true\n    summary: For replace\n    title: Old value\n- new_value: null\n  opts:\n    description: |\n      new value\n    is_required: true\n    summary: To replace\n    title: New value\n- opts:\n    summary: For debug\n    title: Show old and new file content\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_file: \"false\"\n- notfound_exit: \"true\"\n  opts:\n    summary: To mark a step as \"Failed\" if value for replacing isn't found.\n    title: Mark as \"Failed\" if value isn't found.\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-value/1.1.3/step.yml",
    "content": "title: Change value in file\nsummary: Change value in file. (e.g. constants)\ndescription: Change value in file. (e.g. constants)\nwebsite: https://github.com/bitrise-steplib/steps-change-value\nsource_code_url: https://github.com/bitrise-steplib/steps-change-value\nsupport_url: https://github.com/bitrise-steplib/steps-change-value/issues\npublished_at: 2020-10-01T11:54:18.09757465Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-value.git\n  commit: f4ef12c326b23c6fa4b7b14b77d0c95b41cfad3c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-value\ninputs:\n- file: null\n  opts:\n    description: |\n      The file in which you want to change a value.\n    is_required: true\n    summary: Target file path\n    title: File path\n- old_value: null\n  opts:\n    description: |\n      current value in file\n    is_required: true\n    summary: For replace\n    title: Old value\n- new_value: null\n  opts:\n    description: |\n      new value\n    is_required: true\n    summary: To replace\n    title: New value\n- opts:\n    summary: For debug\n    title: Show old and new file content\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_file: \"false\"\n- notfound_exit: \"true\"\n  opts:\n    summary: To mark a step as \"Failed\" if value for replacing isn't found.\n    title: Mark as \"Failed\" if value isn't found.\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-value/2.0.0/step.yml",
    "content": "title: Change value in file\nsummary: Changes a selected value in a targeted file.\ndescription: |-\n  This Step changes a selected value in a targeted file, for example, constants.\n\n  ### Configuring the Step\n\n  1. Set the **File path** in which you want to change a value.\n  2. Set the **Current value** which needs to be changed.\n  3. Set the **New value**.\n\n  ### Troubleshooting\n  Please make sure that your targeted file path is correct, existing and relative from the root folder.\n  Please make sure that you set a correct **Current value** which exists in the the targeted file. You must define this value.\n  Please make sure that you define the New value.\n\n  ### Related Steps\n  - [Change Working Directory for subsequent Steps](https://www.bitrise.io/integrations/steps/change-workdir)\nwebsite: https://github.com/bitrise-steplib/steps-change-value\nsource_code_url: https://github.com/bitrise-steplib/steps-change-value\nsupport_url: https://github.com/bitrise-steplib/steps-change-value/issues\npublished_at: 2021-09-21T11:28:01.237472945Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-value.git\n  commit: fd31ec09f72d2264fce82c7f8d65ed40c651830e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-change-value\ninputs:\n- file: null\n  opts:\n    is_required: true\n    summary: The target file path in which you want to change a value.\n    title: File path\n- old_value: null\n  opts:\n    is_required: true\n    summary: The current value which needs to be changed in the target file.\n    title: Current value\n- new_value: null\n  opts:\n    is_required: true\n    summary: The new value you want to write to the target file.\n    title: New value\n- opts:\n    title: Print file content before and after the value change\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_file: \"false\"\n- notfound_exit: \"true\"\n  opts:\n    title: Mark the Step as \"Failed\" if the selected value isn't found\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-value/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/change-workdir/1.0.0/step.yml",
    "content": "title: Change Working Directory for subsequent Steps\nsummary: Set bitrise source directory (BITRISE_SOURCE_DIR) to specified path.\ndescription: |-\n  By setting `$BITRISE_SOURCE_DIR` to the specified path every subsequent\n  Step will run with this path as it's base Working Directory.\n\n  Useful for projects which expect a fixed project/workspace hierarchy,\n  like `Go` which requires the project inside a \"workspace\" with\n  the structure: `$GOPATH/src/domain/user/project`.\nwebsite: https://github.com/bitrise-io/steps-change-workdir\nsource_code_url: https://github.com/bitrise-io/steps-change-workdir\nsupport_url: https://github.com/bitrise-io/steps-change-workdir/issues\npublished_at: 2015-09-29T13:13:55.78560927+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-change-workdir.git\n  commit: 0c1593a490c834cee8468dd4a32ae7bec5d417ad\nhost_os_tags:\n- osx-10.10\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: New working directory path\n    title: Directory path\n    value_options: []\n  path: null\n- is_create_path: \"true\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: Enable/disable the creation of the directory path in case it doesn't\n      exist yet.\n    title: Create path if doesn't exist?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-workdir/1.0.1/step.yml",
    "content": "title: Change Working Directory for subsequent Steps\nsummary: Set bitrise source directory (BITRISE_SOURCE_DIR) to specified path.\ndescription: |-\n  By setting `$BITRISE_SOURCE_DIR` to the specified path every subsequent\n  Step will run with this path as it's base Working Directory.\n\n  Useful for projects which expect a fixed project/workspace hierarchy,\n  like `Go` which requires the project inside a \"workspace\" with\n  the structure: `$GOPATH/src/domain/user/project`.\nwebsite: https://github.com/bitrise-io/steps-change-workdir\nsource_code_url: https://github.com/bitrise-io/steps-change-workdir\nsupport_url: https://github.com/bitrise-io/steps-change-workdir/issues\npublished_at: 2016-05-02T17:42:03.858229042+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-change-workdir.git\n  commit: 94c58915edb11972def5c266396613b7fb35a686\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: New working directory path\n    title: Directory path\n    value_options: []\n  path: null\n- is_create_path: \"true\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: Enable/disable the creation of the directory path in case it doesn't\n      exist yet.\n    title: Create path if doesn't exist?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-workdir/1.0.2/step.yml",
    "content": "title: Change Working Directory for subsequent Steps\nsummary: Set bitrise source directory (BITRISE_SOURCE_DIR) to a specified path.\ndescription: |-\n  By setting `$BITRISE_SOURCE_DIR` to the specified path every subsequent\n  Step will run with this path as its base Working Directory.\n\n  Useful for projects which expect a fixed project/workspace hierarchy,\n  like `Go` which requires the project inside a \"workspace\" with\n  the structure: `$GOPATH/src/domain/user/project`.\nwebsite: https://github.com/bitrise-io/steps-change-workdir\nsource_code_url: https://github.com/bitrise-io/steps-change-workdir\nsupport_url: https://github.com/bitrise-io/steps-change-workdir/issues\npublished_at: 2018-12-20T12:33:58.172380707Z\nsource:\n  git: https://github.com/bitrise-io/steps-change-workdir.git\n  commit: ff6b146dc48366c37b1f5db0e3c213aa4f16fe69\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: New working directory path\n    title: Directory path\n    value_options: []\n  path: null\n- is_create_path: \"true\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: Enable/disable the creation of the directory path in case it doesn't\n      exist yet.\n    title: Create path if doesn't exist?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-workdir/1.0.3/step.yml",
    "content": "title: Change Working Directory for subsequent Steps\nsummary: Set bitrise source directory (`BITRISE_SOURCE_DIR`) to a specified path.\ndescription: |-\n  By setting `$BITRISE_SOURCE_DIR` to the specified path every subsequent\n  Step will run with this path as its base Working Directory.\n\n  Useful for projects which expect a fixed project/workspace hierarchy,\n  like `Go` which requires the project inside a \"workspace\" with\n  the structure: `$GOPATH/src/domain/user/project`.\nwebsite: https://github.com/bitrise-io/steps-change-workdir\nsource_code_url: https://github.com/bitrise-io/steps-change-workdir\nsupport_url: https://github.com/bitrise-io/steps-change-workdir/issues\npublished_at: 2020-09-03T09:09:53.735576754Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-change-workdir.git\n  commit: 5a24bad8029a435421dafddb73c9c80e6b7767da\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: New working directory path\n    title: Directory path\n    value_options: []\n  path: null\n- is_create_path: \"true\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: Enable/disable the creation of the directory path in case it doesn't\n      exist yet.\n    title: Create path if doesn't exist?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/change-workdir/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/check-certificate/1.0.0/step.yml",
    "content": "title: Check certificate against host\nsummary: This step allows you to check a certificate against a host, and send an email\n  in the case it is invalid.\ndescription: This step allows you to check a certificate against a host, and send\n  an email in the case it is invalid.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-check-certificate\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-check-certificate.git\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-check-certificate/issues\npublished_at: 2019-10-25T23:24:54.650585+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-check-certificate.git\n  commit: d985c6d08ee9098b2d9798162962736858d9f5ba\nproject_type_tags:\n- ios\n- macos\n- android\n- react-native\n- xamarin\ntype_tags:\n- utility\n- notification\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: SMTP server used to send the notification email\n    is_expand: true\n    is_required: true\n    summary: SMTP server used to send the notification email\n    title: SMTP server\n  smtp_server: \"\"\n- opts:\n    description: In case that the certificate is invalid, this email will be used\n      to send the notification email\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The email that will be used to send the error notification\n    title: Sender email\n  sender_email: \"\"\n- opts:\n    description: The password that will be used to authenticate the sender\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The password that will be used to authenticate the sender\n    title: Sender password\n  sender_password: \"\"\n- certificate_file: \"\"\n  opts:\n    description: The path to the certificate file that will be used to check\n    is_expand: true\n    is_required: true\n    summary: The path to the certificate file that will be used to check\n    title: Certificate file path\n- host: \"\"\n  opts:\n    description: Host of the server that will be validated against\n    is_expand: true\n    is_required: true\n    summary: Host of the server that will be validated against\n    title: Server host\n- opts:\n    description: Port of the server that will be validated against\n    is_expand: true\n    is_required: true\n    summary: Port of the server that will be validated against\n    title: Server port\n  port: \"443\"\n- opts:\n    description: Number of months were the certificate becomes invalid\n    is_expand: true\n    is_required: true\n    summary: Number of months were the certificate becomes invalid\n    title: Number of months were the certificate becomes invalid\n  validation: \"3\"\n- notification_target: \"\"\n  opts:\n    description: Email that will receive the notification in the case of an invalid\n      certificate\n    is_expand: true\n    is_required: true\n    summary: Email that will receive the notification in the case of an invalid certificate\n    title: Email to notify\n- opts:\n    description: Name of the project were this certificate is used. This is used in\n      the notification email to give more context\n    is_expand: true\n    is_required: false\n    summary: Name of the project were this certificate is used\n    title: Project name\n  project: \"\"\n"
  },
  {
    "path": "steps/check-certificate/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/chuck-norris/1.0.1/step.yml",
    "content": "title: Chuck Norris\nsummary: |\n  Adds random Chuck Norris jokes to build log.\ndescription: |\n  Uses [Chuck Norris Jokes Api](https://api.chucknorris.io) or other compatible one to add random joke to build log.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-chuck-norris\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-chuck-norris\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-chuck-norris/issues\npublished_at: 2018-10-17T02:45:14.651508066+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-chuck-norris.git\n  commit: f8b862507775742d7c952f293b27ef97db1000df\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-chuck-norris\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- category: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Optional category of the joke, see [list of available categories](https://api.chucknorris.io/jokes/categories).\n      If empty joke won't be restricted to any category.\n    title: Joke category, optional.\n- api_base_url: https://api.chucknorris.io\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      Base URL of the API. Defaults to _https://api.chucknorris.io_. See\n      [chuck-api](https://github.com/chucknorris-io/chuck-api) for more info about running your own backend.\n    title: API base URL\noutputs:\n- CHUCK_NORRIS_JOKE: null\n  opts:\n    summary: Random joke about Chuck Norris from API\n    title: Random Chuck Norris joke text\n"
  },
  {
    "path": "steps/chuck-norris/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/close-jira-tasks/1.0.0/step.yml",
    "content": "title: close-jira-tasks\nsummary: |\n  Step moves Jira tasks from given initial state to target state if their ids are in git log\ndescription: |\n  Step searches Jira project for tasks that are in `from_status` (e.g. `Deploying`) state\n  and after successful build moves them to `to_status` (e.g. `Stabilization on QA`) state.\n\n  This is useful if you use smart commits in Jira, e.g. if your commit message\n  includes `TEST-123 #Do`.\n  This would cause the issue TEST-123 to transition according to `Do` keyword.\n\n  The step works for multiple issues mentioned in last 100 commits, so if\n  you finished multiple tasks it should move all of them to the `to_status` state\n  provided they are in `from_status` at the moment of execution.\n\n  The step can also add custom value to the custom field in the Jira issue e.g. version of the app.\nwebsite: https://github.com/orestesgaolin/bitrise-close-jira-tasks\nsource_code_url: https://github.com/orestesgaolin/bitrise-close-jira-tasks\nsupport_url: https://github.com/orestesgaolin/bitrise-close-jira-tasks/issues\npublished_at: 2019-10-17T22:06:57.040904+02:00\nsource:\n  git: https://github.com/orestesgaolin/bitrise-close-jira-tasks.git\n  commit: d870ad85bb907c116429b2dada5324b0a5a8f6bc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: jq\n  apt_get:\n  - name: git\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- jira_project_name: \"\"\n  opts:\n    description: |\n      This will be used by script to determine tasks ids in git log e.g. TEST-123\n    is_expand: true\n    is_required: true\n    summary: Acronym used in Jira e.g. TEMP, GAS, TEST\n    title: Jira project name\n- jira_url: \"\"\n  opts:\n    description: |\n      This can be e.g. https://company.atlassian.net\n    is_expand: true\n    is_required: true\n    summary: Base URL to company Jira\n    title: Jira project URL\n- jira_token: $JIRA_TOKEN\n  opts:\n    description: |\n      You should use secret environment variable\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Token used to authenticate to Jira\n    title: Jira API token\n- from_status: Deploying\n  opts:\n    description: |\n      Status of tasks which are closed by developer and are currently being dpeloyed (may be a column name in Jira)\n    is_expand: true\n    is_required: true\n    summary: Status of tasks which are closed by developer\n    title: Initial status\n- opts:\n    description: |\n      Status of tasks which were deployed successfully (may be a column name in Jira)\n    is_expand: true\n    is_required: true\n    summary: Status of tasks which were deployed successfully\n    title: Initial status\n  to_status: Stabilization on QA\n- custom_jira_field: \"\"\n  opts:\n    description: |\n      This should be in format `customfield_xxxxx`\n    is_expand: true\n    is_required: false\n    summary: Current version number will be set in this custom field of Jira issues\n    title: Custom field to update version number\n- opts:\n    description: |\n      You should use Bitrise env variable\n    is_expand: true\n    is_required: false\n    summary: Current version number will be set in `custom_jira_field` of Jira issues\n    title: App version\n  version: $BITRISE_BUILD_NUMBER\n"
  },
  {
    "path": "steps/close-jira-tasks/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cocoapod-key/1.0.1/step.yml",
    "content": "title: Install cocoapod keys\nsummary: This step allows you to install & configure a set of keys\ndescription: Through the use of the gem cocoapod-keys, this step creates secure values\n  to be useb by your application\nwebsite: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key/issues\npublished_at: 2019-02-19T16:12:18.759751+01:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\n  commit: 4a16ba1032f16cc8698b833a2251c0f77bdbf0b6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- xamarin\ntype_tags:\n- installer\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: In case that your workspace has multiple projects, and multiple targets,\n      a `pod key` command may fail because of the conflict in the configuration list.\n      This solves this issue\n    is_expand: true\n    is_required: false\n    summary: The name of the project. It will be used to resolve project conflict,\n      in the case of multiple targets in the workspace\n    title: Project name\n  project_name: \"\"\n- keys: \"\"\n  opts:\n    description: The list of keys that will be set. With `|` as a separator. It needs\n      to match the order and size of the `values` property\n    is_expand: true\n    is_required: true\n    summary: The list of keys that will be set. With `|` as a separator\n    title: Keys\n- opts:\n    description: The list of values that will be set. With `|` as a separator. It\n      needs to match the order and size of the `keys` property\n    is_expand: true\n    is_required: true\n    summary: The list of values that will be set. With `|` as a separator.\n    title: Values\n  values: \"\"\n"
  },
  {
    "path": "steps/cocoapod-key/1.0.2/step.yml",
    "content": "title: Install cocoapod keys\nsummary: This step allows you to install & configure a set of keys\ndescription: Through the use of the gem cocoapod-keys, this step creates secure values\n  to be useb by your application\nwebsite: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key/issues\npublished_at: 2019-10-25T19:04:45.353733+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\n  commit: d3e24368a33dde7e5f9779140a5cc944f784e4fe\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- xamarin\ntype_tags:\n- installer\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: In case that your workspace has multiple projects, and multiple targets,\n      a `pod key` command may fail because of the conflict in the configuration list.\n      This solves this issue\n    is_expand: true\n    is_required: false\n    summary: The name of the project. It will be used to resolve project conflict,\n      in the case of multiple targets in the workspace\n    title: Project name\n  project_name: \"\"\n- opts:\n    description: In case where the Podfile is not hosted at the root of the repo,\n      this variable can be used to point to the right place\n    is_expand: true\n    is_required: true\n    summary: Path where the Podfile configuration is hosted\n    title: Podfile path\n  podfile_path: ./\n- keys: \"\"\n  opts:\n    description: The list of keys that will be set. With `|` as a separator. It needs\n      to match the order and size of the `values` property\n    is_expand: true\n    is_required: true\n    summary: The list of keys that will be set. With `|` as a separator\n    title: Keys\n- opts:\n    description: The list of values that will be set. With `|` as a separator. It\n      needs to match the order and size of the `keys` property\n    is_expand: true\n    is_required: true\n    summary: The list of values that will be set. With `|` as a separator.\n    title: Values\n  values: \"\"\n"
  },
  {
    "path": "steps/cocoapod-key/1.1.0/step.yml",
    "content": "title: Install cocoapod keys\nsummary: This step allows you to install & configure a set of keys\ndescription: Through the use of the gem cocoapod-keys, this step creates secure values\n  to be useb by your application\nwebsite: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key/issues\npublished_at: 2020-07-17T18:06:55.794907+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\n  commit: 3fa8087566dbf90ea595af77e895331a84c7c1af\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- xamarin\ntype_tags:\n- installer\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: In case that your workspace has multiple projects, and multiple targets,\n      a `pod key` command may fail because of the conflict in the configuration list.\n      This solves this issue\n    is_expand: true\n    is_required: false\n    summary: The name of the project. It will be used to resolve project conflict,\n      in the case of multiple targets in the workspace\n    title: Project name\n  project_name: \"\"\n- opts:\n    description: In case where the Podfile is not hosted at the root of the repo,\n      this variable can be used to point to the right place\n    is_expand: true\n    is_required: true\n    summary: Path where the Podfile configuration is hosted\n    title: Podfile path\n  podfile_path: ./\n- keys: \"\"\n  opts:\n    description: The list of keys that will be set. With `|` as a separator. It needs\n      to match the order and size of the `values` property\n    is_expand: true\n    is_required: false\n    summary: The list of keys that will be set. With `|` as a separator. If you leave\n      this empty, the step will only install the necessary gems\n    title: Keys\n- opts:\n    description: The list of values that will be set. With `|` as a separator. It\n      needs to match the order and size of the `keys` property\n    is_expand: true\n    is_required: false\n    summary: The list of values that will be set. With `|` as a separator. If you\n      leave this empty, the step will only install the necessary gems\n    title: Values\n  values: \"\"\n"
  },
  {
    "path": "steps/cocoapod-key/2.0.0/step.yml",
    "content": "title: Install cocoapod keys\nsummary: This step allows you to install cocoapo-keys\ndescription: This step simply install the dependecies of cocoapo-keys, so the plugin\n  can be used by a following cocoapods step.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key/issues\npublished_at: 2021-04-14T23:56:28.084761+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-cocoapod-key.git\n  commit: e790310c83b68665d3084a08244ab64b99c02e34\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- xamarin\ntype_tags:\n- installer\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: In case that your workspace has multiple projects, and multiple targets,\n      a `pod key` command may fail because of the conflict in the configuration list.\n      This solves this issue\n    is_expand: true\n    is_required: false\n    summary: The name of the project. It will be used to resolve project conflict,\n      in the case of multiple targets in the workspace\n    title: Project name\n  project_name: \"\"\n- opts:\n    description: In case where the Podfile is not hosted at the root of the repo,\n      this variable can be used to point to the right place\n    is_expand: true\n    is_required: true\n    summary: Path where the Podfile configuration is hosted\n    title: Podfile path\n  podfile_path: ./\n- keys: \"\"\n  opts:\n    category: Ignored\n    description: |-\n      Previously, this was used to run `pod keys set $KEY $VALUE`, but, on a CI environment, it is better if this is store in the SECRETS of the application.\n      Cocoapod-keys can fetch values from the environment. So, if you have a key named `MyKey`, you just need to create a secret with the same name: `MeyKey = Value`.\n      This is safer since the value never leaves Bitrise secrets, and avoids having it leaked on logs.\n\n      This variable is still listed in the step to avoid that someone that upgrades looses its info. But, it is no longer used.\n    is_expand: true\n    is_required: false\n    summary: Given that this is not the best approach to cocoapod-keys on CI, the\n      list of keys is no longer used.\n    title: Keys (No longer used)\n- opts:\n    category: Ignored\n    description: |-\n      Previously, this was used to run `pod keys set $KEY $VALUE`, but, on a CI environment, it is better if this is store in the SECRETS of the application.\n      Cocoapod-keys can fetch values from the environment. So, if you have a key named `MyKey`, you just need to create a secret with the same name: `MeyKey = Value`.\n      This is safer since the value never leaves Bitrise secrets, and avoids having it leaked on logs.\n\n      This variable is still listed in the step to avoid that someone that upgrades looses its info. But, it is no longer used.\n    is_expand: true\n    is_required: false\n    summary: Given that this is not the best approach to cocoapod-keys on CI, the\n      list of values is no longer used.\n    title: Values (No longer used)\n  values: \"\"\n"
  },
  {
    "path": "steps/cocoapod-key/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cocoapods-dependency-check/0.0.1/step.yml",
    "content": "title: cocoapods-dependency-check\nsummary: |\n  OWASP dependency analysis for iOS / CocoaPods\ndescription: |\n  Uses jeremylong/DependencyCheck to search Podfile.lock for CVE vulnerabilites.\n\n  The generated HTML document will be placed into BITRISE_DEPLOY_DIR by default.\n  Remember to run the \"Deploy to bitrise.io\" step in order to persist artifacts.\nwebsite: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker\nsource_code_url: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker\nsupport_url: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker/issues\npublished_at: 2018-08-02T18:41:13.220054924+09:30\nsource:\n  git: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker.git\n  commit: 539aff879569d0d78ee2c5df527ad19c849164d0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: dependency-check\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path\n  source_root_path: $BITRISE_SOURCE_DIR\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_required: true\n    title: App title\n- deploy_dir: $BITRISE_DEPLOY_DIR\n  opts:\n    is_required: true\n    title: Deploy directory to output scan artifacts\n- opts:\n    description: |\n      (Optional) will default to $BITRISE_SOURCE_DIR/Podfile.lock\n    is_expand: true\n    is_required: false\n    summary: The path to your Podfile.lock file.\n    title: Podfile.lock path\n    value_options: []\n  podfile_lock_path: $BITRISE_SOURCE_DIR/Podfile.lock\n- fail_on_cvss_level: 11\n  opts:\n    description: |-\n      (Optional) Specifies if the build should be failed\n      if a CVSS score above a specified level is identified.\n\n      The default is 11; since\n      the CVSS scores are 0-10, by default the\n      build will never fail.\n    is_expand: true\n    is_required: false\n    summary: Sepcifies what level of CVSS should trigger a build failure\n    title: Fail on CVSS Level\n    value_options: []\n"
  },
  {
    "path": "steps/cocoapods-dependency-check/0.0.2/step.yml",
    "content": "title: cocoapods-dependency-check\nsummary: |\n  OWASP dependency analysis for iOS / CocoaPods\ndescription: |\n  Uses jeremylong/DependencyCheck to search Podfile.lock for CVE vulnerabilites.\n\n  The generated HTML document will be placed into BITRISE_DEPLOY_DIR by default.\n  Remember to run the \"Deploy to bitrise.io\" step in order to persist artifacts.\nwebsite: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker\nsource_code_url: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker\nsupport_url: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker/issues\npublished_at: 2021-05-20T21:00:56.062738+09:30\nsource:\n  git: https://github.com/johnjcsmith/bitrise-step-cocoapods-dependency-checker.git\n  commit: b5a3e927b2a6d67a541e93ad979f46c2f57e56e5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: dependency-check\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path\n  source_root_path: $BITRISE_SOURCE_DIR\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_required: true\n    title: App title\n- deploy_dir: $BITRISE_DEPLOY_DIR\n  opts:\n    is_required: true\n    title: Deploy directory to output scan artifacts\n- opts:\n    description: |\n      (Optional) will default to $BITRISE_SOURCE_DIR/Podfile.lock\n    is_expand: true\n    is_required: false\n    summary: The path to your Podfile.lock file.\n    title: Podfile.lock path\n    value_options: []\n  podfile_lock_path: $BITRISE_SOURCE_DIR/Podfile.lock\n- fail_on_cvss_level: 11\n  opts:\n    description: |-\n      (Optional) Specifies if the build should be failed\n      if a CVSS score above a specified level is identified.\n\n      The default is 11; since\n      the CVSS scores are 0-10, by default the\n      build will never fail.\n    is_expand: true\n    is_required: false\n    summary: Sepcifies what level of CVSS should trigger a build failure\n    title: Fail on CVSS Level\n    value_options: []\n"
  },
  {
    "path": "steps/cocoapods-dependency-check/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cocoapods-install/1.0.0/step.yml",
    "content": "title: Run CocoaPods install\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2015-09-03T21:53:22.634653249+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: eafe1df6d114b263142450105ee434775b19fbaf\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"true\"\n  opts:\n    description: |\n      Should update the installed CocoaPods version before using it?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.0.1/step.yml",
    "content": "title: Run CocoaPods install\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2015-09-03T22:06:42.215452936+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 4365217c355a830c0127a643c62c804b6706ff79\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"true\"\n  opts:\n    description: |\n      Should update the installed CocoaPods version before using it?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.0.2/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2015-09-21T14:46:55.154530128+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: d2b3466ae88bc7b86581120d9d2c54ade94438a7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"true\"\n  opts:\n    description: |\n      Should update the installed CocoaPods version before using it?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.0.3/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2015-10-05T14:24:34.792859893+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 1a9b6077b32debef39e2999f00a046cd9f5c110f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"true\"\n  opts:\n    description: |\n      Should update the installed CocoaPods version before using it?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.1.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-01-11T10:42:25.932239552+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: b2f6195fb6f136fad10c55b0683eebdf4de68dfa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.10.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2019-11-08T15:40:08.92570964Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: d4de433402427fae3b084a103d5242956e045379\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.10.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo. Simply add this Step\n  and Bitrise will do the pod install for you on the VM!\ndescription: \"\\nCocoaPods is a dependency manager for Swift and Objective-C projects.\n  This Step uses CocoaPods' `pod install` command to install your dependencies on\n  the virtual machine where your Bitrise build runs.   \\nCocoaPods version is determined\n  based on the Podfile.lock file or on the Gemfile.lock file. If the version is specified\n  in the Podfile.lock file and the version range specified in the Gemfile.lock file\n  \\ \\ncontains that version, then that version will be installed. Otherwise, the Cocoapods\n  version in the Podfile.lock will be installed as a global gem.  \\nIf no Cocoapods\n  version is defined in the Podfile.lock, the preinstalled sytem Cocoapods version\n  will be used.\\n\\n### Configuring the Step\\n\\n1. Set the **Source Code Directory\n  path** to the path of your app's source code.\\n\\n1. Optionally, provide a Podfile\n  in the **Podfile path** input.\\n\\n   Without a specific Podfile, the Step does a\n  recursive search for the Podfile in the root of your app's directory, and uses the\n  first Podfile it finds.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check out the\n  Podfile and the Gemfile of your app. Make sure there is no compatibility issue with\n  the different versions of your Pods.  \\nCheck that both Podfile.lock and Gemfile.lock\n  is committed and the Cocoapods versions defined in both match.\\n\\nYou can set the\n  **Execute cocoapods in verbose mode?** input to true to get detailed logs of the\n  Step.\\n\\n### Useful links\\n\\n* [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n*\n  [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\\n\\n###\n  Related Steps\\n\\n* [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n*\n  [Carthage](https://www.bitrise.io/integrations/steps/carthage)\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2020-01-14T15:31:47.625216571Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: b1b2c84add0d26c2d1a7b965722ecd73ca5473fe\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.11.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo. Simply add this Step\n  and Bitrise will do the pod install for you on the VM!\ndescription: \"\\nCocoaPods is a dependency manager for Swift and Objective-C projects.\n  This Step uses CocoaPods' `pod install` command to install your dependencies on\n  the virtual machine where your Bitrise build runs.   \\nCocoaPods version is determined\n  based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock\n  file contains the `cocoapods` gem then the step will call `pod install` with `bundle\n  exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as\n  a global gem.\\nIf no Cocoapods version is defined in Podfile.lock or Gemfile.lock,\n  the preinstalled sytem Cocoapods version will be used.\\n\\n### Configuring the Step\\n\\n1.\n  Set the **Source Code Directory path** to the path of your app's source code.\\n\\n1.\n  Optionally, provide a Podfile in the **Podfile path** input.\\n\\n   Without a specific\n  Podfile, the Step does a recursive search for the Podfile in the root of your app's\n  directory, and uses the first Podfile it finds.\\n\\n### Troubleshooting\\n\\nIf the\n  Step fails, check out the Podfile and the Gemfile of your app. Make sure there is\n  no compatibility issue with the different versions of your Pods.  \\nCheck that both\n  Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in\n  both match.\\n\\nYou can set the **Execute cocoapods in verbose mode?** input to true\n  to get detailed logs of the Step.\\n\\n### Useful links\\n\\n* [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n*\n  [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\\n\\n###\n  Related Steps\\n\\n* [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n*\n  [Carthage](https://www.bitrise.io/integrations/steps/carthage)\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2020-03-19T08:48:21.376090196Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 84faecd4c459175bc0246cceeb34fb4d838d70d8\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.2.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-04-13T17:42:41.972675095+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 27ee14cae1562c1f62d71edb796f8f95140898da\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.2.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-05-19T11:47:12.983878172+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 3cf12db215cab82304764193d03e48139638c82a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.3.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-05-21T14:08:17.560682779+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 3bde37937e59fe987b4845c929b23e411969876b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for Podfiles,\n      and run `pod install` with every `Podfile` it finds.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods version?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.4.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-05-24T14:17:47.613423406+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 168af0c0cff69be6c702a052f9dfd1161a1ee098\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for Podfiles,\n      and run `pod install` with every `Podfile` it finds.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      [Deprecated!] Use `install_cocoapods_version` input instead of this.\n\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      Install specified CocoaPods version.\n\n      Leave it empty to use system installed version of CocoaPods.\n\n      Format examles:\n\n      - 0.39.0.beta.1\n      - 1.0.0\n      - latest\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.4.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-06-13T15:44:04.143616284+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: f8327bb4b51c02aaa047c6e2632ec138b5991eda\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for Podfiles,\n      and run `pod install` with every `Podfile` it finds.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      [Deprecated!] Use `install_cocoapods_version` input instead of this.\n\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      Install specified CocoaPods version.\n\n      Leave it empty to use system installed version of CocoaPods.\n\n      Format examles:\n\n      - 0.39.0.beta.1\n      - 1.0.0\n      - latest\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.4.2/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-06-14T10:47:47.979146336+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 09bc0fcd7dbdee24cd07a2c3bcd1fae72eed2ad5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for Podfiles,\n      and run `pod install` with every `Podfile` it finds.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      [Deprecated!] Use `install_cocoapods_version` input instead of this.\n\n      Should update the system installed CocoaPods\n      to the latest version?\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      Install specified CocoaPods version.\n\n      Leave it empty to use system installed version of CocoaPods.\n\n      Format examles:\n\n      - 0.39.0.beta.1\n      - 1.0.0\n      - latest\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-06-29T12:11:34.056164837+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: f47861fd1127fc39ce704680fc204e6888a8f88f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-06-29T14:20:23.965654195+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: d3edec56c8c4c55a351b38f37685b522bad33bf0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.2/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-06-30T16:34:26.013453549+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: f95316811feb396f431832f9c0cd8ad3ec8183dd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.3/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-07-13T12:54:42.497504685+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: e174573f1e63e654569991a8523f50be8f6158e3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.4/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-07-20T13:28:54.316939496+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 1ca4ad3cf3cebd492e8e08df9cfd2f3793a803d3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.5/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-08-11T15:44:36.911707651+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 25cdf57f3c941d92b17ebbb8edc1efd95fe9bb13\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.6/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-08-19T15:38:10.89274923+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 84937421683c9073f2590e4dfcb0d8cb7bfa3b10\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.7/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: Run CocoaPods install (`$ pod install`) in your App's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-09-07T08:47:56.957111565+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: e58541432fcb37e90dc075c0537a834bebb70169\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.8/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: \"Run CocoaPods install (`$ pod install`) in your App's directory.\\n\\nCocoaPods\n  version is determined based on the Gemfile.lock or (if not exists or does not contain\n  cocoapods gem)  \\non the Podfile.lock in the Podfile's directory.\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-12-05T16:35:04.476558335+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 549511f511075290a92ee07eac2ac03665911151\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- cocoapods\n- pod\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.5.9/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: \"Run CocoaPods install (`$ pod install`) in your App's directory.\\n\\nCocoaPods\n  version is determined based on the Gemfile.lock or (if not exists or does not contain\n  cocoapods gem)  \\non the Podfile.lock in the Podfile's directory.\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2016-12-19T16:23:13.293331236+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: a6e6a66565a1bb30023015607889e12dd8e07cc9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- xcode\n- cocoapods\n- pod\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Gemfile.lock or the Podfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.6.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2017-01-10T15:19:32.344773291+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: fb82227760bf4cc7d750fe5e2cc260ecd10a85c8\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- xcode\n- cocoapods\n- pod\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.6.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2017-01-16T13:37:35.216464982+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: a99782e9604f4cc8a002618e4d54ca351b2048a7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.7.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2017-06-08T11:52:46.033477265+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 17fbf1707eb09af9347ccff20ac4e42e7045e330\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.7.2/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2017-10-27T14:43:52.576400543+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-cocoapods-install.git\n  commit: 46db2b4643b74326901641d95003677320c9ed07\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.8.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2019-07-18T11:45:19.628717016Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 1a276f4ffcf6efd1fcff11fdbcacb9c08993723f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.9.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2019-10-07T13:04:28.289296742Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: b9b0fe33f245f2ef636d77337e7081504dbef8cb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/1.9.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo, simply add this step\n  and Bitrise will do the pod install for you on the VM!\ndescription: |-\n  Run CocoaPods install (`$ pod install`) in your App's directory.\n\n  CocoaPods version is determined based on the Podfile.lock or\n  on the Gemfile.lock (if Podfile.lock does not exist in the Podfile's\n  directory and Gemfile.lock contains cocoapods gem)\n  in the Podfile's directory.\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2019-10-15T09:16:46.24261624Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 173de380033e9364c810864cdd2577800a55adf9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-cocoapods-install\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- is_update_cocoapods: \"false\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    is_expand: false\n    is_required: true\n    title: Update CocoaPods to the latest version?\n    value_options:\n    - \"true\"\n    - \"false\"\n- install_cocoapods_version: \"\"\n  opts:\n    description: |\n      __Deprecated!__\n\n      CocoaPods version is determined based on the Podfile.lock or the Gemfile.lock in the Podfile's directory.\n    title: Install specified CocoaPods version\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.0.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo. Simply add this Step\n  and Bitrise will do the pod install for you on the VM!\ndescription: \"\\nCocoaPods is a dependency manager for Swift and Objective-C projects.\n  This Step uses CocoaPods' `pod install` command to install your dependencies on\n  the virtual machine where your Bitrise build runs.   \\nCocoaPods version is determined\n  based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock\n  file contains the `cocoapods` gem then the step will call `pod install` with `bundle\n  exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as\n  a global gem.\\nIf no Cocoapods version is defined in Podfile.lock or Gemfile.lock,\n  the preinstalled sytem Cocoapods version will be used.\\n\\n### Configuring the Step\\n\\n1.\n  Set the **Source Code Directory path** to the path of your app's source code.\\n\\n1.\n  Optionally, provide a Podfile in the **Podfile path** input.\\n\\n   Without a specific\n  Podfile, the Step does a recursive search for the Podfile in the root of your app's\n  directory, and uses the first Podfile it finds.\\n\\n### Troubleshooting\\n\\nIf the\n  Step fails, check out the Podfile and the Gemfile of your app. Make sure there is\n  no compatibility issue with the different versions of your Pods.  \\nCheck that both\n  Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in\n  both match.\\n\\nYou can set the **Execute cocoapods in verbose mode?** input to true\n  to get detailed logs of the Step.\\n\\n### Useful links\\n\\n* [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n*\n  [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\\n\\n###\n  Related Steps\\n\\n* [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n*\n  [Carthage](https://www.bitrise.io/integrations/steps/carthage)\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2021-02-08T12:02:01.818811936Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: ce4795f317e3d48e9f3ca0e759875d33562f5f6b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"true\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"True to disable pods caching \\n\"\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.1.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed pods in your repo. Simply add this Step\n  and Bitrise will do the pod install for you on the VM!\ndescription: \"\\nCocoaPods is a dependency manager for Swift and Objective-C projects.\n  This Step uses CocoaPods' `pod install` command to install your dependencies on\n  the virtual machine where your Bitrise build runs.   \\nCocoaPods version is determined\n  based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock\n  file contains the `cocoapods` gem then the step will call `pod install` with `bundle\n  exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as\n  a global gem.\\nIf no Cocoapods version is defined in Podfile.lock or Gemfile.lock,\n  the preinstalled sytem Cocoapods version will be used.\\n\\n### Configuring the Step\\n\\n1.\n  Set the **Source Code Directory path** to the path of your app's source code.\\n\\n1.\n  Optionally, provide a Podfile in the **Podfile path** input.\\n\\n   Without a specific\n  Podfile, the Step does a recursive search for the Podfile in the root of your app's\n  directory, and uses the first Podfile it finds.\\n\\n### Troubleshooting\\n\\nIf the\n  Step fails, check out the Podfile and the Gemfile of your app. Make sure there is\n  no compatibility issue with the different versions of your Pods.  \\nCheck that both\n  Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in\n  both match.\\n\\nYou can set the **Execute cocoapods in verbose mode?** input to true\n  to get detailed logs of the Step.\\n\\n### Useful links\\n\\n* [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n*\n  [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\\n\\n###\n  Related Steps\\n\\n* [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n*\n  [Carthage](https://www.bitrise.io/integrations/steps/carthage)\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2021-02-17T15:09:37.029036098Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: eef47b51862962c967572fbb77686bdcd25a00c6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      (optional) `Podfile` path, relative to the `source_root_path`.\n\n      If not provided, the Step will search for root Podfile,\n      and run `pod install` with.\n    summary: (optional) Podfile path, relative to the source_root_path\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      (optional) True to execute the command in verbose mode or false to execute it without verbose\n    is_expand: false\n    is_required: false\n    title: Execute cocoapods in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      True to disable pods caching\n    is_expand: false\n    is_required: false\n    title: Disable built-in cache\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.2.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: |-\n  You don't need to keep the installed Pods in your repo. Simply add this Step\n  and Bitrise will do the Pod install for you on the VM!\ndescription: \"\\nCocoaPods is a dependency manager for Swift and Objective-C projects.\n  This Step uses CocoaPods' `pod install` or `pod update` command to install your\n  dependencies on the virtual machine where your Bitrise build runs.   \\nCocoaPods\n  version is determined based on the Podfile.lock file or on the Gemfile.lock file.\n  If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call\n  the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in\n  the Podfile.lock will be installed as a global gem.\\nIf no Cocoapods version is\n  defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version\n  will be used.\\n\\n### Configuring the Step\\n\\n1. Set the **Source Code Directory\n  path** to the path of your app's source code.\\n\\n1. Optionally, provide a Podfile\n  in the **Podfile path** input.\\n\\n   Without a specific Podfile, the Step does a\n  recursive search for the Podfile in the root of your app's directory, and uses the\n  first Podfile it finds.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check out the\n  Podfile and the Gemfile of your app. Make sure there is no compatibility issue with\n  the different versions of your Pods.  \\nCheck that both Podfile.lock and Gemfile.lock\n  is committed and the Cocoapods versions defined in both match.\\n\\nYou can set the\n  **Execute cocoapods in verbose mode?** input to true to get detailed logs of the\n  Step.\\n\\n### Useful links\\n\\n* [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\\n*\n  [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\\n\\n###\n  Related Steps\\n\\n* [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\\n*\n  [Carthage](https://www.bitrise.io/integrations/steps/carthage)\"\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2021-05-12T13:06:14.534918413Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 3fc15ef88c794827fc6fc38e3a5cb52f5a03c339\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: \"Use pod `install` to download the explicit version listed in the\n      Podfile.lock without trying to check if a newer version is available.  \\nUse\n      pod `update` to update every Pod listed in your Podfile to the latest version\n      possible.\"\n    is_required: true\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: \"Directory path where the project's Podfile (and optionally Gemfile)\n      is placed.  \\nCocoaPods commands will be executed in this directory.\"\n    is_required: true\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: By specifying this input `Workdir` gets overriden by the provided\n      file's directory path.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    title: Execute all CocoaPods commands in verbose mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: \"By default the Step adds the Pods directory in the `Workdir` to\n      the Bitrise Build Cache.  \\nSet this input to disable automatic cache item collection\n      for this Step.\\n\"\n    title: Disable automatic cache item collection\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.2.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2022-02-22T16:12:47.014794064Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: dd4b16b082e0e74f87c1ebba92cc15ae165a8cb1\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.3.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2022-06-09T18:53:11.895220784Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: ec9bc34b5c7884e7e347f1ffa25afae948943cda\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.3.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2022-11-30T16:25:57.72341754Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 1ae8eacb3cf5081f71037385e2d56ffbf3f00b45\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.3.2/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2023-02-07T08:53:15.871754629Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: ad1981e92c9792e26d735360928f147a71dcfa12\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.3.3/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2023-03-29T07:50:14.341128984Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 53dc1dd5ce7cb9da27c8ca7631735be374e05bc5\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.3.4/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2023-08-22T13:26:59.824813463Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 75dd45d47a09aecdec2f90738ebb78afc677a8dd\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.3.5/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2023-08-30T06:19:36.719282348Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: b29272c16b6af54fc59402185221ffa40668b7a7\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.4.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2023-09-11T11:13:21.967268586Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: b2a6b7fe17795a9921406becf31c6fc4caadc3f7\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.4.1/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2024-04-16T10:17:25.14647669Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 6506fe8f51893cb1b18f0f5b94fda608d5b8b249\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.4.2/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2024-04-19T12:39:07.730497932Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: a3b881e11d1f5ade2d0b7e76190890c535595649\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/2.4.3/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Caching Cocoapods](https://devcenter.bitrise.io/builds/caching/caching-cocoapods/)\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2025-11-11T08:06:42.785703149Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: 83cec746b299af6644131610aba0791344c1dbb0\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_cache_disabled: \"false\"\n  opts:\n    description: |\n      Disables automatic cache content collection.\n\n      By default the Step adds the Pods directory in the `Workdir` to the Bitrise Build Cache.\n\n      Set this input to disable automatic cache item collection for this Step.\n    summary: Disables automatic cache content collection.\n    title: Disable collecting cache content\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/3.0.0/step.yml",
    "content": "title: Run CocoaPods install\nsummary: This Step uses CocoaPods' `pod install` or `pod update` command to install\n  your dependencies.\ndescription: |2-\n\n  CocoaPods is a dependency manager for Swift and Objective-C projects. This Step uses CocoaPods' `pod install` or `pod update` command to install your dependencies on the virtual machine where your Bitrise build runs.\n\n  CocoaPods version is determined based on the Podfile.lock file or on the Gemfile.lock file. If your Gemfile.lock file contains the `cocoapods` gem, then the Step will call the pod `install` command with `bundle exec`. Otherwise, the Cocoapods version in the Podfile.lock will be installed as a global gem.\n  If no Cocoapods version is defined in Podfile.lock or Gemfile.lock, the preinstalled sytem Cocoapods version will be used.\n\n  ### Configuring the Step\n\n  1. Set the **Source Code Directory path** to the path of your app's source code.\n\n  1. Optionally, provide a Podfile in the **Podfile path** input.\n\n     Without a specific Podfile, the Step does a recursive search for the Podfile in the root of your app's directory, and uses the first Podfile it finds.\n\n  ### Troubleshooting\n\n  If the Step fails, check out the Podfile and the Gemfile of your app. Make sure there is no compatibility issue with the different versions of your Pods.\n\n  Check that both Podfile.lock and Gemfile.lock is committed and the Cocoapods versions defined in both match.\n\n  You can set the **Execute cocoapods in verbose mode?** input to true to get detailed logs of the Step.\n\n  ### Useful links\n\n  * [Cache save](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache) steps\n  * [Include your dependencies in your repository](https://devcenter.bitrise.io/tips-and-tricks/optimize-your-build-times/#include-your-dependencies-in-your-repository)\n\n  ### Related Steps\n\n  * [Run yarn command](https://www.bitrise.io/integrations/steps/yarn)\n  * [Carthage](https://www.bitrise.io/integrations/steps/carthage)\nwebsite: https://github.com/bitrise-io/steps-cocoapods-install\nsource_code_url: https://github.com/bitrise-io/steps-cocoapods-install\nsupport_url: https://github.com/bitrise-io/steps-cocoapods-install/issues\npublished_at: 2026-01-29T10:52:46.298540752Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cocoapods-install.git\n  commit: a4f132a11a5c32e9db998c63f04cce639e7dd848\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cocoapods-install\nis_always_run: false\nis_skippable: false\ninputs:\n- command: install\n  opts:\n    description: |\n      CocoaPods command to use for installing dependencies.\n\n      Available options:\n      - `install`: Use `pod install` to download the explicit version listed in the Podfile.lock without trying to check if a newer version is available.\n      - `update`: Use `pod update` to update every Pod listed in your Podfile to the latest version possible.\n    is_required: true\n    summary: CocoaPods command to use for installing dependencies.\n    title: CocoaPods command\n    value_options:\n    - install\n    - update\n- opts:\n    description: |\n      Directory path where the project's Podfile (and optionally Gemfile) is placed.\n\n      CocoaPods commands will be executed in this directory.\n    is_required: true\n    summary: Directory path where the project's Podfile (and optionally Gemfile) is\n      placed.\n    title: Workdir\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Path of the project's Podfile.\n\n      By specifying this input `Workdir` gets overriden by the provided file's directory path.\n    summary: Path of the project's Podfile.\n    title: Podfile path\n  podfile_path: \"\"\n- opts:\n    description: |\n      Execute all CocoaPods commands in verbose mode.\n\n      If enabled the `--verbose` flag will be appended to all CocoaPods commands.\n    summary: Execute all CocoaPods commands in verbose mode.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/cocoapods-install/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/cocoaseeds-install/1.0.0/step.yml",
    "content": "title: Run CocoaSeeds install\nsummary: |-\n  You don't need to keep the installed seeds in your repo, simply add this step\n  and Bitrise will do the seed install for you on the VM!\ndescription: Run CocoaSeeds install (`$ seed install`) in your App's directory.\nwebsite: https://github.com/Frugghi/cocoaseeds-bitrise\nsource_code_url: https://github.com/Frugghi/cocoaseeds-bitrise\nsupport_url: https://github.com/Frugghi/cocoaseeds-bitrise/issues\npublished_at: 2016-05-09T04:06:27.666182532+02:00\nsource:\n  git: https://github.com/Frugghi/cocoaseeds-bitrise.git\n  commit: 110014bb17d8d761647b2146619923f524fe4250\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- dependency\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/cocoaseeds-install/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/code-signing-setting-patch/1.0.4/step.yml",
    "content": "title: Code Signing Setting Patch\nsummary: |\n  Patch xcode's signing config for specific key and provisioning profile\ndescription: |\n  Patch xcode's signing config for specific key and provisioning profile\nwebsite: https://github.com/j796160836/bitrise-step-code-signing-setting-patch\nsource_code_url: https://github.com/j796160836/bitrise-step-code-signing-setting-patch\nsupport_url: https://github.com/j796160836/bitrise-step-code-signing-setting-patch/issues\npublished_at: 2019-12-05T14:56:04.819635+08:00\nsource:\n  git: https://github.com/j796160836/bitrise-step-code-signing-setting-patch.git\n  commit: 99a14f5751560cd6fb1737907a1bc698a62394a1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Your project.xcodeproj file path. (e.g. MyAwesomeProject/MyAwesomeProject.xcodeproj)\n      \\ \\nEven if provide `.xcodeproj` path even if using `.xcworkspace`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: Your project.xcodeproj file path.\n    title: Xcode project.xcodeproj Path\n    value_options: []\n  xcode_xcodeproj_file: null\n- opts:\n    description: |\n      Your target name of your xcode project. (e.g. MyAwesomeProject)\n    is_expand: true\n    is_required: true\n    summary: Project Target Name\n    title: Project Target\n    value_options: []\n  project_target: null\n- code_sign_style: Automatic\n  opts:\n    description: \"The **CODE__SIGN__STYLE** value will be replaced.  \\nValue either\n      `Automatic` or `Manual`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **CODE__SIGN__STYLE** value will be replaced.\n    title: Code Sign Style\n    value_options:\n    - Automatic\n    - Manual\n- debug_development_team: null\n  opts:\n    description: \"The **debug configurations** of **DEVELOPMENT_TEAM** value will\n      be replaced.  \\nLeft blank means `None`.\\n\"\n    is_expand: true\n    is_required: false\n    summary: The **debug configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n    title: Development Team (Debug)\n    value_options: []\n- debug_code_sign_identity: null\n  opts:\n    description: \"The **debug configurations** of **CODE__SIGN__IDENTITY** value will\n      be replaced.   \\nValue will be `iPhone Developer`, `iPhone Distribution` or\n      others.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **debug configurations** of **CODE__SIGN__IDENTITY** value will be\n      replaced.\n    title: Code Sign Identity (Debug)\n    value_options: []\n- debug_provisioning_profile_specifier: null\n  opts:\n    description: \"The **debug configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.  \\nPlease specify the provisioning profile name which\n      is same as one created at **Certificates, Identifiers & Profiles** at **Apple\n      Developer Program**.  \\nDon't foget to upload that provisioning profile file.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **debug configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.\n    title: Provisioning Profile Specifier (Debug)\n    value_options: []\n- opts:\n    description: \"The **release configurations** of **DEVELOPMENT_TEAM** value will\n      be replaced.  \\nLeft blank means `None`.\\n\"\n    is_expand: true\n    is_required: false\n    summary: The **release configurations** of **DEVELOPMENT_TEAM** value will be\n      replaced.\n    title: Development Team (Release)\n    value_options: []\n  release_development_team: null\n- opts:\n    description: \"The **release configurations** of **CODE__SIGN__IDENTITY** value\n      will be replaced.   \\nValue will be `iPhone Developer`, `iPhone Distribution`\n      or others.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **release configurations** of **CODE__SIGN__IDENTITY** value will\n      be replaced.\n    title: Code Sign Identity (Release)\n    value_options: []\n  release_code_sign_identity: null\n- opts:\n    description: \"The **release configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.  \\nPlease specify the provisioning profile name which\n      is same as one created at **Certificates, Identifiers & Profiles** at **Apple\n      Developer Program**.  \\nDon't foget to upload that provisioning profile file.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **release configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.\n    title: Provisioning Profile Specifier (Release)\n    value_options: []\n  release_provisioning_profile_specifier: null\n- dry_run: \"no\"\n  opts:\n    description: |\n      If set this value `yes`, it will Dry-run this steps to preview the signing settings.\n    is_expand: true\n    is_required: true\n    summary: If set this value `yes`, it will Dry-run this steps to preview the signing\n      settings.\n    title: Dry-run preview (settings preview)\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/code-signing-setting-patch/1.0.5/step.yml",
    "content": "title: Code Signing Setting Patch\nsummary: |\n  Patch xcode's signing config for specific key and provisioning profile\ndescription: |\n  Patch xcode's signing config for specific key and provisioning profile\nwebsite: https://github.com/j796160836/bitrise-step-code-signing-setting-patch\nsource_code_url: https://github.com/j796160836/bitrise-step-code-signing-setting-patch\nsupport_url: https://github.com/j796160836/bitrise-step-code-signing-setting-patch/issues\npublished_at: 2025-02-02T22:42:26.764028+08:00\nsource:\n  git: https://github.com/j796160836/bitrise-step-code-signing-setting-patch.git\n  commit: b3310ccb1c8bbc2eeddd7337441220b4ef9a0574\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Your project.xcodeproj file path. (e.g. MyAwesomeProject/MyAwesomeProject.xcodeproj)\n      \\ \\nEven if provide `.xcodeproj` path even if using `.xcworkspace`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: Your project.xcodeproj file path.\n    title: Xcode project.xcodeproj Path\n    value_options: []\n  xcode_xcodeproj_file: null\n- opts:\n    description: |\n      Your target name of your xcode project. (e.g. MyAwesomeProject)\n    is_expand: true\n    is_required: true\n    summary: Project Target Name\n    title: Project Target\n    value_options: []\n  project_target: null\n- code_sign_style: Automatic\n  opts:\n    description: \"The **CODE__SIGN__STYLE** value will be replaced.  \\nValue either\n      `Automatic` or `Manual`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **CODE__SIGN__STYLE** value will be replaced.\n    title: Code Sign Style\n    value_options:\n    - Automatic\n    - Manual\n- debug_development_configuration: null\n  opts:\n    description: |\n      The **debug configuration** value will be replaced.\n      Please set your value, or by default you have to use `Debug`.\n    is_expand: true\n    is_required: true\n    summary: The **debug configuration** value will be replaced.\n    title: Development Configuration (Debug)\n    value_options: []\n- debug_development_team: null\n  opts:\n    description: |\n      The **debug configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n      Left blank means `None`.\n    is_expand: true\n    is_required: false\n    summary: The **debug configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n    title: Development Team (Debug)\n    value_options: []\n- debug_code_sign_identity: null\n  opts:\n    description: \"The **debug configurations** of **CODE__SIGN__IDENTITY** value will\n      be replaced.   \\nValue will be `iPhone Developer`, `iPhone Distribution` or\n      others.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **debug configurations** of **CODE__SIGN__IDENTITY** value will be\n      replaced.\n    title: Code Sign Identity (Debug)\n    value_options: []\n- debug_provisioning_profile_specifier: null\n  opts:\n    description: \"The **debug configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.  \\nPlease specify the provisioning profile name which\n      is same as one created at **Certificates, Identifiers & Profiles** at **Apple\n      Developer Program**.  \\nDon't foget to upload that provisioning profile file.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **debug configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.\n    title: Provisioning Profile Specifier (Debug)\n    value_options: []\n- opts:\n    description: |\n      The **release configuration** value will be replaced.\n      Please set your value, or by default you have to use `Release`.\n    is_expand: true\n    is_required: true\n    summary: The **release configuration** value will be replaced.\n    title: Release Configuration (Release)\n    value_options: []\n  release_configuration: null\n- opts:\n    description: \"The **release configurations** of **DEVELOPMENT_TEAM** value will\n      be replaced.  \\nLeft blank means `None`.\\n\"\n    is_expand: true\n    is_required: false\n    summary: The **release configurations** of **DEVELOPMENT_TEAM** value will be\n      replaced.\n    title: Development Team (Release)\n    value_options: []\n  release_development_team: null\n- opts:\n    description: \"The **release configurations** of **CODE__SIGN__IDENTITY** value\n      will be replaced.   \\nValue will be `iPhone Developer`, `iPhone Distribution`\n      or others.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **release configurations** of **CODE__SIGN__IDENTITY** value will\n      be replaced.\n    title: Code Sign Identity (Release)\n    value_options: []\n  release_code_sign_identity: null\n- opts:\n    description: \"The **release configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.  \\nPlease specify the provisioning profile name which\n      is same as one created at **Certificates, Identifiers & Profiles** at **Apple\n      Developer Program**.  \\nDon't foget to upload that provisioning profile file.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **release configurations** of **PROVISIONING__PROFILE__SPECIFIER**\n      value will be replaced.\n    title: Provisioning Profile Specifier (Release)\n    value_options: []\n  release_provisioning_profile_specifier: null\n- dry_run: \"no\"\n  opts:\n    description: |\n      If set this value `yes`, it will Dry-run this steps to preview the signing settings.\n    is_expand: true\n    is_required: true\n    summary: If set this value `yes`, it will Dry-run this steps to preview the signing\n      settings.\n    title: Dry-run preview (settings preview)\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/code-signing-setting-patch/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/codecov/1.0.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: Reduce technical debt with visualized test performance, faster code reviews\n  and workflow enhancements. You can now upload your code coverage files to Codecov\n  every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2015-10-28T16:54:02.524489434Z\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: be8d5b2e4a0a49f1db7d3c2ff758b3562eae7d41\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\n- code_coverage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_expand: true\n    is_required: true\n    title: Codecov.io token\n"
  },
  {
    "path": "steps/codecov/1.0.1/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  You can now upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2016-04-28T16:38:51.519615349+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: 8d358bd1097328e459609053acd856200d3abf6e\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- code_coverage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    title: Codecov.io token\n"
  },
  {
    "path": "steps/codecov/1.1.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  You can now upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2016-07-11T17:24:49.447100846+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: 69f404fbbd740092d667f7244f783e46a4272ea2\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- code_coverage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      Example: `--codecov -F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: --codecov\n"
  },
  {
    "path": "steps/codecov/1.1.1/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  You can now upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2016-07-13T12:03:19.662386335+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: 344275f40f99507cb3b992ed6063467a2078f82f\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- code_coverage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      Example: `--codecov -F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: --codecov\n"
  },
  {
    "path": "steps/codecov/1.1.2/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  You can now upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2016-07-15T17:40:04.615161953+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: 3f61db9b48088e5a9d34a27a8021802cd331284f\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- code_coverage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      Example: `--codecov -F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: null\n"
  },
  {
    "path": "steps/codecov/1.1.3/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  You can now upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2016-07-19T14:43:50.145455121+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: e245505a2069a8e9fce6e13d743d0930847808cd\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- code_coverage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      Example: `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: null\n"
  },
  {
    "path": "steps/codecov/1.1.4/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  You can now upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2017-03-20T11:14:29.540634683+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: ee08758b36b54b8d1aab3b70519a27adff4542b4\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      Example: `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: null\n"
  },
  {
    "path": "steps/codecov/1.1.5/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2018-09-11T13:53:17.863038343Z\nsource:\n  git: https://github.com/bitrise-io/steps-codecov.git\n  commit: b4a7715b6b80f69b8eb39ea4ff432f0a08f19ea1\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      For example, `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: null\n"
  },
  {
    "path": "steps/codecov/1.1.6/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://github.com/bitrise-io/steps-codecov\nsource_code_url: https://github.com/bitrise-io/steps-codecov\nsupport_url: https://github.com/bitrise-io/steps-codecov/issues\npublished_at: 2019-08-15T14:28:40.435575278Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-codecov.git\n  commit: abb26e0a2a1e7feefee0982e13c07f2da00cfb07\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      For example, `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/2.0.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2020-09-16T18:12:34.566646-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 238e44c7c53a19327d1262ff87fe14ebd6f188a5\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      For example, `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/2.0.1/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2020-11-16T14:11:31.606197-05:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 3b298fe8b9de89b884e0a9ab1704eaf431e22700\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      For example, `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/2.0.2/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2021-05-04T10:41:06.65984-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 04929d3db1d00a97cd84d5ad4fb8d77da7a02da2\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/codecov-bash\n      For example, `-F unittests -J '^Project'`\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/3.0.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2021-08-06T12:32:31.826056-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 31f43b1ede55e770d642280d97e16e4a166c4d16\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/3.0.1/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2021-08-30T16:12:16.005905-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 269473d94131c80d70d7a2e2c52ab32b70f0e6ec\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/3.1.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2021-09-13T09:20:23.565651-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 60c8786caa552e69dae61ef9bb94a68a7d686ac5\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.1.0_8880`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/3.1.1/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2021-09-24T10:04:16.692375-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 6e8817d21009d9aabf9ca67bdf684fcc6afdc257\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.1.0_8880`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/3.1.2/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2021-10-05T08:44:25.695726-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: cdc645fdb07dcf05f1d170de0a4de2dd891fa929\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.1.0_8880`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $BITRISE_GIT_COMMIT\n"
  },
  {
    "path": "steps/codecov/3.1.3/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2022-03-21T14:12:20.467504-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 32742fd32ec5a23ea1b66d58345e1120b906d0d7\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.1.0_8880`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $GIT_CLONE_COMMIT_HASH\n"
  },
  {
    "path": "steps/codecov/3.2.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2022-10-12T14:50:29.30384-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: a8c71eac593f622e49d26fceed644cb2feac3992\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.1.0_8880`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- XCODE_ARCHIVE_PATH: null\n  opts:\n    description: |\n      Specify the xcode archive path. Likely specified as the -resultBundlePath and should end in .xcresult. Only needed if running with xcode support\n    is_required: false\n    is_sensitive: false\n    title: Xcode archive path\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $GIT_CLONE_COMMIT_HASH\n"
  },
  {
    "path": "steps/codecov/3.3.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2023-06-27T09:35:26.180619-04:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 133598e022aca08c75e8af1d32a4a794010336c0\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.6.1`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- XCODE_ARCHIVE_PATH: null\n  opts:\n    description: |\n      --Deprecating-- Specify the xcode archive path. Likely specified as the -resultBundlePath and should end in .xcresult. Only needed if running with xcode support\n    title: '[Deprecating] Xcode archive path'\n- ENABLE_SWIFT_CONVERSION: \"false\"\n  opts:\n    description: |\n      Enable swift coverage conversation.\n    is_required: false\n    is_sensitive: false\n    title: Enable swift coverage\n    value_options:\n    - \"true\"\n    - \"false\"\n- SWIFT_PROJECT: null\n  opts:\n    description: |\n      Specify the swift project. Will only work properly if ENABLE_SWIFT_CONVERSION is set to `true`\n    is_required: false\n    is_sensitive: false\n    title: Swift project name\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $GIT_CLONE_COMMIT_HASH\n"
  },
  {
    "path": "steps/codecov/3.3.1/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2023-08-01T08:05:02.04114-07:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 8227aa35554f73cc9069890acd077db4e76ba2f6\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.6.1`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- XCODE_ARCHIVE_PATH: null\n  opts:\n    description: |\n      --Deprecating-- Specify the xcode archive path. Likely specified as the -resultBundlePath and should end in .xcresult. Only needed if running with xcode support\n    title: '[Deprecating] Xcode archive path'\n- ENABLE_SWIFT_CONVERSION: null\n  opts:\n    description: |\n      Enable swift coverage conversation by setting to 'true'.\n    is_required: false\n    is_sensitive: false\n    title: Enable swift coverage\n- SWIFT_PROJECT: null\n  opts:\n    description: |\n      Specify the swift project. Will only work properly if ENABLE_SWIFT_CONVERSION is set to `true`\n    is_required: false\n    is_sensitive: false\n    title: Swift project name\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $GIT_CLONE_COMMIT_HASH\n"
  },
  {
    "path": "steps/codecov/3.3.2/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2023-08-30T10:15:25.114054-07:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 3eb71a9c1046c65138b5ef3d4b651806383d3e62\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.6.1`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- XCODE_ARCHIVE_PATH: null\n  opts:\n    description: |\n      --Deprecating-- Specify the xcode archive path. Likely specified as the -resultBundlePath and should end in .xcresult. Only needed if running with xcode support\n    title: '[Deprecating] Xcode archive path'\n- ENABLE_SWIFT_CONVERSION: null\n  opts:\n    description: |\n      Enable swift coverage conversation by setting to 'true'.\n    is_required: false\n    is_sensitive: false\n    title: Enable swift coverage\n- SWIFT_PROJECT: null\n  opts:\n    description: |\n      Specify the swift project. Will only work properly if ENABLE_SWIFT_CONVERSION is set to `true`\n    is_required: false\n    is_sensitive: false\n    title: Swift project name\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $GIT_CLONE_COMMIT_HASH\n"
  },
  {
    "path": "steps/codecov/3.3.3/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2023-09-15T09:34:57.29313-07:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: e8d493c4251ae0d9032d54f17b97ff9351982bf3\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CODECOV_TOKEN: null\n  opts:\n    description: |\n      Codecov.io repository upload token\n    is_required: true\n    is_sensitive: true\n    title: Codecov.io token\n- OS: null\n  opts:\n    description: |\n      Name of the OS being used (options are \"alpine\" | \"linux\" | \"macos\")\n    is_required: true\n    is_sensitive: false\n    title: OS Name\n- VERSION: latest\n  opts:\n    description: |\n      Version of the Codecov Uploader to use (e.g. `v0.6.1`)\n    is_required: false\n    is_sensitive: false\n    title: Uploader Version\n- XCODE_ARCHIVE_PATH: null\n  opts:\n    description: |\n      --Deprecating-- Specify the xcode archive path. Likely specified as the -resultBundlePath and should end in .xcresult. Only needed if running with xcode support\n    title: '[Deprecating] Xcode archive path'\n- ENABLE_SWIFT_CONVERSION: null\n  opts:\n    description: |\n      Enable swift coverage conversation by setting to 'true'.\n    is_required: false\n    is_sensitive: false\n    title: Enable swift coverage\n- SWIFT_PROJECT: null\n  opts:\n    description: |\n      Specify the swift project. Will only work properly if ENABLE_SWIFT_CONVERSION is set to `true`\n    is_required: false\n    is_sensitive: false\n    title: Swift project name\n- opts:\n    description: |-\n      Options to pass along to the Codecov uploader.\n      You can use multiple options, separated by a space.\n      Review all options at https://github.com/codecov/uploader\n    title: Additional options for Codecov call\n  other_options: -C $GIT_CLONE_COMMIT_HASH\n"
  },
  {
    "path": "steps/codecov/4.0.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov\n  every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2024-10-18T09:37:03.510925-05:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: ed2fe9c5c9b9a87e07d4e3547ffb6000651b35d8\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CC_BINARY: null\n  opts:\n    description: The file location of a pre-downloaded version of the CLI. If specified,\n      integrity checking will be bypassed.\n    is_required: false\n    is_sensitive: false\n    title: binary\n- CC_BRANCH: null\n  opts:\n    description: Branch to which this commit belongs\n    is_required: false\n    is_sensitive: false\n    title: branch\n- CC_BUILD: null\n  opts:\n    description: Specify the build number manually\n    is_required: false\n    is_sensitive: false\n    title: build\n- CC_BUILD_URL: null\n  opts:\n    description: The URL of the build where this is running\n    is_required: false\n    is_sensitive: false\n    title: build_url\n- CC_CODE: null\n  opts:\n    description: The code of the report if using local upload. If unsure, leave default.\n      Read more here https://docs.codecov.com/docs/the-codecov-cli#how-to-use-local-upload\n    is_required: false\n    is_sensitive: false\n    title: code\n- CC_DIR: null\n  opts:\n    description: Folder to search for coverage files. Default to the current working\n      directory\n    is_required: false\n    is_sensitive: false\n    title: dir\n- CC_DISABLE_FILE_FIXES: \"false\"\n  opts:\n    description: Disable file fixes to ignore common lines from coverage (e.g. blank\n      lines or empty brackets). Read more here https://docs.codecov.com/docs/fixing-reports\n    is_required: false\n    is_sensitive: false\n    title: disable_file_fixes\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_DISABLE_SEARCH: \"false\"\n  opts:\n    description: Disable search for coverage files. This is helpful when specifying\n      what files you want to upload with the files option.\n    is_required: false\n    is_sensitive: false\n    title: disable_search\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_DRY_RUN: \"false\"\n  opts:\n    description: Don't upload files to Codecov.\n    is_required: false\n    is_sensitive: false\n    title: dry_run\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_ENTERPRISE_URL: null\n  opts:\n    description: Set to the Codecov instance URl. Only applicable to some Enterprise\n      users.\n    is_required: false\n    is_sensitive: false\n    title: enterprise_url\n- CC_ENV: null\n  opts:\n    description: Specify environment variables to be included with this build\n    is_required: false\n    is_sensitive: false\n    title: env\n- CC_EXCLUDES: null\n  opts:\n    description: Comma-separated list of folders to exclude from search.\n    is_required: false\n    is_sensitive: false\n    title: excludes\n- CC_FAIL_ON_ERROR: \"false\"\n  opts:\n    description: Exit with non-zero code in case of error.\n    is_required: false\n    is_sensitive: false\n    title: fail_on_error\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_FILES: null\n  opts:\n    description: Comma-separated list of explicit files to upload. These will be added\n      to the coverage files found for upload. If you wish to only upload the specified\n      files, please consider using disable-search to disable uploading other files.\n    is_required: false\n    is_sensitive: false\n    title: files\n- CC_FLAGS: null\n  opts:\n    description: Comma-separated list of flags to upload to group coverage metrics.\n    is_required: false\n    is_sensitive: false\n    title: flags\n- CC_GCOV_ARGS: null\n  opts:\n    description: Extra arguments to pass to gcov\n    is_required: false\n    is_sensitive: false\n    title: gcov_args\n- CC_GCOV_EXECUTABLE: null\n  opts:\n    description: gcov executable to run. Defaults to 'gcov'\n    is_required: false\n    is_sensitive: false\n    title: gcov_executable\n- CC_GCOV_IGNORE: null\n  opts:\n    description: Paths to ignore during gcov gathering\n    is_required: false\n    is_sensitive: false\n    title: gcov_ignore\n- CC_GCOV_INCLUDE: null\n  opts:\n    description: Paths to include during gcov gathering\n    is_required: false\n    is_sensitive: false\n    title: gcov_include\n- CC_GIT_SERVICE: null\n  opts:\n    description: One of [github|gitlab|bitbucket|github_enterprise|gitlab_enterprise|bitbucket_server]\n    is_required: false\n    is_sensitive: false\n    title: git_service\n- CC_HANDLE_NO_REPORTS_FOUND: \"false\"\n  opts:\n    description: Raise no exceptions when no coverage reports are found.\n    is_required: false\n    is_sensitive: false\n    title: handle_no_reports_found\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_JOB_CODE: null\n  opts:\n    description: \"\"\n    is_required: false\n    is_sensitive: false\n    title: job_code\n- CC_LEGACY: \"false\"\n  opts:\n    description: Use the legacy upload endpoint.\n    is_required: false\n    is_sensitive: false\n    title: legacy\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_NAME: null\n  opts:\n    description: Custom defined name of the upload. Visible in Codecov UI\n    is_required: false\n    is_sensitive: false\n    title: name\n- CC_NETWORK_FILTER: null\n  opts:\n    description: Specify a filter on the files listed in the network section of the\n      Codecov report. This will only add files whose path begin with the specified\n      filter. Useful for upload-specific path fixing.\n    is_required: false\n    is_sensitive: false\n    title: network_filter\n- CC_NETWORK_PREFIX: null\n  opts:\n    description: Specify a prefix on files listed in the network section of the Codecov\n      report. Useful to help resolve path fixing.\n    is_required: false\n    is_sensitive: false\n    title: network_prefix\n- CC_NETWORK_ROOT_FOLDER: null\n  opts:\n    description: Root folder from which to consider paths on the network section.\n      Defaults to current working directory.\n    is_required: false\n    is_sensitive: false\n    title: network_root_folder\n- CC_PARENT_SHA: null\n  opts:\n    description: SHA (with 40 chars) of what should be the parent of this commit.\n    is_required: false\n    is_sensitive: false\n    title: parent_sha\n- CC_PLUGINS: null\n  opts:\n    description: Comma-separated list of plugins to run. Specify `noop` to turn off\n      all plugins\n    is_required: false\n    is_sensitive: false\n    title: plugins\n- CC_PR: null\n  opts:\n    description: Specify the pull request number manually. Used to override pre-existing\n      CI environment variables.\n    is_required: false\n    is_sensitive: false\n    title: pr\n- CC_REPORT_TYPE: null\n  opts:\n    description: The type of file to upload, coverage by default. Possible values\n      are \"testing\", \"coverage\".\n    is_required: false\n    is_sensitive: false\n    title: report_type\n- CC_SHA: null\n  opts:\n    description: Commit SHA (with 40 chars)\n    is_required: false\n    is_sensitive: false\n    title: sha\n- CC_SKIP_VALIDATION: \"false\"\n  opts:\n    description: Skip integrity checking of the CLI. This is NOT recommended.\n    is_required: false\n    is_sensitive: false\n    title: skip_validation\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_SLUG: null\n  opts:\n    description: Set to the owner/repo slug used instead of the private repo token.\n      Only applicable to some Enterprise users.\n    is_required: false\n    is_sensitive: false\n    title: slug\n- CC_SWIFT_PROJECT: null\n  opts:\n    description: Specify the swift project name. Useful for optimization.\n    is_required: false\n    is_sensitive: false\n    title: swift_project\n- CC_TOKEN: null\n  opts:\n    description: The repository upload token given in Codecov.io\n    is_required: false\n    is_sensitive: false\n    title: token\n- CC_VERBOSE: \"false\"\n  opts:\n    description: Use verbose logging in the CLI\n    is_required: false\n    is_sensitive: false\n    title: verbose\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_VERSION: latest\n  opts:\n    description: Which version of the Codecov CLI to use (defaults to 'latest')\n    is_required: false\n    is_sensitive: false\n    title: version\n"
  },
  {
    "path": "steps/codecov/4.1.0/step.yml",
    "content": "title: Codecov\nsummary: Upload your code coverage files to Codecov.io\ndescription: |-\n  Reduce technical debt with visualized test performance,\n  faster code reviews and workflow enhancements.\n  Now you can upload your code coverage files to Codecov\n  every time you kick off a build!\nwebsite: https://codecov.io\nsource_code_url: https://github.com/codecov/codecov-bitrise\nsupport_url: https://community.codecov.io\npublished_at: 2024-12-05T18:13:55.079548-03:00\nsource:\n  git: https://github.com/codecov/codecov-bitrise.git\n  commit: 38be381ae4d5ee1b0909e3211e4460e0ff441526\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- CC_BINARY: null\n  opts:\n    description: The file location of a pre-downloaded version of the CLI. If specified,\n      integrity checking will be bypassed.\n    is_required: false\n    is_sensitive: false\n    title: binary\n- CC_BRANCH: null\n  opts:\n    description: Branch to which this commit belongs\n    is_required: false\n    is_sensitive: false\n    title: branch\n- CC_BUILD: null\n  opts:\n    description: Specify the build number manually\n    is_required: false\n    is_sensitive: false\n    title: build\n- CC_BUILD_URL: null\n  opts:\n    description: The URL of the build where this is running\n    is_required: false\n    is_sensitive: false\n    title: build_url\n- CC_CODE: null\n  opts:\n    description: The code of the report if using local upload. If unsure, leave default.\n      Read more here https://docs.codecov.com/docs/the-codecov-cli#how-to-use-local-upload\n    is_required: false\n    is_sensitive: false\n    title: code\n- CC_DIR: null\n  opts:\n    description: Folder to search for coverage files. Default to the current working\n      directory\n    is_required: false\n    is_sensitive: false\n    title: dir\n- CC_DISABLE_FILE_FIXES: \"false\"\n  opts:\n    description: Disable file fixes to ignore common lines from coverage (e.g. blank\n      lines or empty brackets). Read more here https://docs.codecov.com/docs/fixing-reports\n    is_required: false\n    is_sensitive: false\n    title: disable_file_fixes\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_DISABLE_SEARCH: \"false\"\n  opts:\n    description: Disable search for coverage files. This is helpful when specifying\n      what files you want to upload with the files option.\n    is_required: false\n    is_sensitive: false\n    title: disable_search\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_DRY_RUN: \"false\"\n  opts:\n    description: Don't upload files to Codecov.\n    is_required: false\n    is_sensitive: false\n    title: dry_run\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_ENTERPRISE_URL: null\n  opts:\n    description: Set to the Codecov instance URl. Only applicable to some Enterprise\n      users.\n    is_required: false\n    is_sensitive: false\n    title: enterprise_url\n- CC_ENV: null\n  opts:\n    description: Specify environment variables to be included with this build\n    is_required: false\n    is_sensitive: false\n    title: env\n- CC_EXCLUDES: null\n  opts:\n    description: Comma-separated list of folders to exclude from search.\n    is_required: false\n    is_sensitive: false\n    title: excludes\n- CC_FAIL_ON_ERROR: \"false\"\n  opts:\n    description: Exit with non-zero code in case of error.\n    is_required: false\n    is_sensitive: false\n    title: fail_on_error\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_FILES: null\n  opts:\n    description: Comma-separated list of explicit files to upload. These will be added\n      to the coverage files found for upload. If you wish to only upload the specified\n      files, please consider using disable-search to disable uploading other files.\n    is_required: false\n    is_sensitive: false\n    title: files\n- CC_FLAGS: null\n  opts:\n    description: Comma-separated list of flags to upload to group coverage metrics.\n    is_required: false\n    is_sensitive: false\n    title: flags\n- CC_GCOV_ARGS: null\n  opts:\n    description: Extra arguments to pass to gcov\n    is_required: false\n    is_sensitive: false\n    title: gcov_args\n- CC_GCOV_EXECUTABLE: null\n  opts:\n    description: gcov executable to run. Defaults to 'gcov'\n    is_required: false\n    is_sensitive: false\n    title: gcov_executable\n- CC_GCOV_IGNORE: null\n  opts:\n    description: Paths to ignore during gcov gathering\n    is_required: false\n    is_sensitive: false\n    title: gcov_ignore\n- CC_GCOV_INCLUDE: null\n  opts:\n    description: Paths to include during gcov gathering\n    is_required: false\n    is_sensitive: false\n    title: gcov_include\n- CC_GIT_SERVICE: null\n  opts:\n    description: One of [github|gitlab|bitbucket|github_enterprise|gitlab_enterprise|bitbucket_server]\n    is_required: false\n    is_sensitive: false\n    title: git_service\n- CC_HANDLE_NO_REPORTS_FOUND: \"false\"\n  opts:\n    description: Raise no exceptions when no coverage reports are found.\n    is_required: false\n    is_sensitive: false\n    title: handle_no_reports_found\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_JOB_CODE: null\n  opts:\n    description: \"\"\n    is_required: false\n    is_sensitive: false\n    title: job_code\n- CC_LEGACY: \"false\"\n  opts:\n    description: Use the legacy upload endpoint.\n    is_required: false\n    is_sensitive: false\n    title: legacy\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_NAME: null\n  opts:\n    description: Custom defined name of the upload. Visible in Codecov UI\n    is_required: false\n    is_sensitive: false\n    title: name\n- CC_NETWORK_FILTER: null\n  opts:\n    description: Specify a filter on the files listed in the network section of the\n      Codecov report. This will only add files whose path begin with the specified\n      filter. Useful for upload-specific path fixing.\n    is_required: false\n    is_sensitive: false\n    title: network_filter\n- CC_NETWORK_PREFIX: null\n  opts:\n    description: Specify a prefix on files listed in the network section of the Codecov\n      report. Useful to help resolve path fixing.\n    is_required: false\n    is_sensitive: false\n    title: network_prefix\n- CC_NETWORK_ROOT_FOLDER: null\n  opts:\n    description: Root folder from which to consider paths on the network section.\n      Defaults to current working directory.\n    is_required: false\n    is_sensitive: false\n    title: network_root_folder\n- CC_PARENT_SHA: null\n  opts:\n    description: SHA (with 40 chars) of what should be the parent of this commit.\n    is_required: false\n    is_sensitive: false\n    title: parent_sha\n- CC_PLUGINS: null\n  opts:\n    description: Comma-separated list of plugins to run. Specify `noop` to turn off\n      all plugins\n    is_required: false\n    is_sensitive: false\n    title: plugins\n- CC_PR: null\n  opts:\n    description: Specify the pull request number manually. Used to override pre-existing\n      CI environment variables.\n    is_required: false\n    is_sensitive: false\n    title: pr\n- CC_REPORT_TYPE: null\n  opts:\n    description: The type of file to upload, coverage by default. Possible values\n      are \"testing\", \"coverage\".\n    is_required: false\n    is_sensitive: false\n    title: report_type\n- CC_SHA: null\n  opts:\n    description: Commit SHA (with 40 chars)\n    is_required: false\n    is_sensitive: false\n    title: sha\n- CC_SKIP_VALIDATION: \"false\"\n  opts:\n    description: Skip integrity checking of the CLI. This is NOT recommended.\n    is_required: false\n    is_sensitive: false\n    title: skip_validation\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_SLUG: null\n  opts:\n    description: Set to the owner/repo slug used instead of the private repo token.\n      Only applicable to some Enterprise users.\n    is_required: false\n    is_sensitive: false\n    title: slug\n- CC_SWIFT_PROJECT: null\n  opts:\n    description: Specify the swift project name. Useful for optimization.\n    is_required: false\n    is_sensitive: false\n    title: swift_project\n- CC_TOKEN: null\n  opts:\n    description: The repository upload token given in Codecov.io\n    is_required: false\n    is_sensitive: false\n    title: token\n- CC_VERBOSE: \"false\"\n  opts:\n    description: Use verbose logging in the CLI\n    is_required: false\n    is_sensitive: false\n    title: verbose\n    value_options:\n    - \"true\"\n    - \"false\"\n- CC_VERSION: latest\n  opts:\n    description: Which version of the Codecov CLI to use (defaults to 'latest')\n    is_required: false\n    is_sensitive: false\n    title: version\n"
  },
  {
    "path": "steps/codecov/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/codified-security-bitrise/1.0.0/step.yml",
    "content": "title: Codified Security\nsummary: This step uploads your app to Codified Security for automated mobile app\n  security testing\ndescription: |-\n  This step uploads your app to Codified Security for automated mobile app security testing.\n\n  https://codifiedsecurity.com\nwebsite: https://bitbucket.org/codifiedldn/codified-security-bitrise\npublished_at: 2017-04-24T11:19:06.686290651+02:00\nsource:\n  git: https://bitbucket.org/codifiedldn/codified-security-bitrise.git\n  commit: d941c0e648ec869b99ea746fb423482903a8a069\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\ninputs:\n- codified_security_api_key: $CODIFIED_SECURITY_API_KEY\n  opts:\n    description: You can obtain your key from https://dashboard.codifiedsecurity.com/settings.\n      You'll find it under Integrations tab as Api Key.\n    is_required: true\n    title: Codified Security API Key\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    is_required: false\n    title: IPA path\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    is_required: false\n    title: APK path\n"
  },
  {
    "path": "steps/codified-security-bitrise/1.0.1/step.yml",
    "content": "title: Codified Security\nsummary: This step uploads your app to Codified Security for automated mobile app\n  security testing\ndescription: |-\n  This step uploads your app to Codified Security for automated mobile app security testing.\n\n  https://codifiedsecurity.com\nwebsite: https://bitbucket.org/codifiedldn/codified-security-bitrise\npublished_at: 2017-05-26T15:43:23.984921125+02:00\nsource:\n  git: https://bitbucket.org/codifiedldn/codified-security-bitrise.git\n  commit: c8fccd8db19339f1fd9bdf80712f0c03b3c84ea8\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\ninputs:\n- codified_security_api_key: $CODIFIED_SECURITY_API_KEY\n  opts:\n    description: You can obtain your key from https://dashboard.codifiedsecurity.com/settings.\n      You'll find it under Integrations tab as Api Key.\n    is_required: true\n    title: Codified Security API Key\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    is_required: false\n    title: IPA path\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    is_required: false\n    title: APK path\n"
  },
  {
    "path": "steps/codified-security-bitrise/2.0.0/step.yml",
    "content": "title: Codified Security\nsummary: This step uploads your app to Codified Security for automated mobile app\n  security testing\ndescription: |-\n  This step uploads your app to Codified Security for automated mobile app security testing.\n\n  https://codifiedsecurity.com\nwebsite: https://bitbucket.org/codifiedldn/codified-security-bitrise\npublished_at: 2017-06-29T15:45:26.487157365+02:00\nsource:\n  git: https://bitbucket.org/codifiedldn/codified-security-bitrise.git\n  commit: 9e4a89d93d5fe903a9b73b929706552a2e216b0f\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\ninputs:\n- codified_security_api_key: $CODIFIED_SECURITY_API_KEY\n  opts:\n    description: You can get your key from https://dashboard.codifiedsecurity.com/settings.\n      You'll find it under Integrations tab as Api Key.\n    is_required: true\n    title: Codified Security API Key\n- app_path: $BITRISE_APK_PATH\n  opts:\n    is_required: false\n    title: Path to your IPA or APK file\n- is_xamarin_ios: \"false\"\n  opts:\n    description: |-\n      You'll need to specify the path to your iOS project directory. Also make sure to build your Xamarin project in Debug mode! Instructions for this are in the User Guide.\n      Options:\n      * \"true\"\n      * \"false\"\n    is_required: false\n    title: Select true if you want to upload a Xamarin.iOS app\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: false\n    title: Path to your iOS project folder\n  xamarin_ios_project_folder: \"\"\n"
  },
  {
    "path": "steps/codified-security-bitrise/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.10.0/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a new or update an existing comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2021-04-07T23:26:39.794231+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: 2be634ec1b191490629f7046da33986fb7ceb154\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo(Full control of private repositories) scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n- api_base_url: https://api.github.com\n  opts:\n    description: The URL for GitHub or GitHub Enterprise API\n    is_required: true\n    title: GitHub API Base URL\n- opts:\n    description: |\n      If set and a commment with the given tag exists, it updates the comment instead of posting a new one.\n      If no comment with the given tag exists, a new comment is posted.\n\n      The tag should be a unique string that will be added to end of the comment's content. The step automatically extends the tag to be enclosed in square brackets.\n    is_required: false\n    title: Update comment tag\n  update_comment_tag: null\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.10.1/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a new or update an existing comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2022-01-12T15:48:34.293359+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: b55f8aa3e25aaf5c4831cc8dd793e14ad26badb7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo(Full control of private repositories) scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n- api_base_url: https://api.github.com\n  opts:\n    description: The URL for GitHub or GitHub Enterprise API\n    is_required: true\n    title: GitHub API Base URL\n- opts:\n    description: |\n      If set and a commment with the given tag exists, it updates the comment instead of posting a new one.\n      If no comment with the given tag exists, a new comment is posted.\n\n      The tag should be a unique string that will be added to end of the comment's content. The step automatically extends the tag to be enclosed in square brackets.\n    is_required: false\n    title: Update comment tag\n  update_comment_tag: null\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.11.0/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a new or update an existing comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2022-01-26T13:09:52.992066+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: 2210ec500688c8d1abe503e93e946f4529724dde\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo(Full control of private repositories) scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n- api_base_url: https://api.github.com\n  opts:\n    description: The URL for GitHub or GitHub Enterprise API\n    is_required: true\n    title: GitHub API Base URL\n- opts:\n    description: |\n      If set and a commment with the given tag exists, it updates the comment instead of posting a new one.\n      If no comment with the given tag exists, a new comment is posted.\n\n      The tag should be a unique string that will be added to end of the comment's content. The step automatically extends the tag to be enclosed in square brackets.\n    is_required: false\n    title: Update comment tag\n  update_comment_tag: null\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.9.0/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a any comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2018-10-29T15:54:43.074321937+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: b35e1ddf95b4ef2b254312db4438b31dc3719aee\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo/repo:status scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.9.1/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2018-11-07T11:59:16.01073495+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: 2e76dfe6fded792627688529aca2f2f4bdff7184\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo/repo:status scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.9.2/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2018-12-05T22:20:32.738919158+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: f5b99e126d901e77066b963e311be53af6de482d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo(Full control of private repositories) scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.9.3/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2019-02-15T12:18:36.816506201+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: 37a692511ecaa1d369d44b7ce5284d6961258d4d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo(Full control of private repositories) scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n- api_base_url: https://api.github.com\n  opts:\n    description: The URL for GitHub or GitHub Enterprise API\n    is_required: true\n    title: GitHub API Base URL\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/0.9.4/step.yml",
    "content": "title: Comment on GitHub Pull Request\nsummary: |\n  Comment on [GitHub](https://github.com) Pull Request or Issue\ndescription: |\n  You can send a comment on [GitHub](https://github.com) Pull Request or Issue.\n\n  To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\nwebsite: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsource_code_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nsupport_url: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request/issues\npublished_at: 2020-09-10T01:06:46.649843+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-comment-on-github-pull-request.git\n  commit: c6a68e01e1bbf57b6a00ed7e75deb21c4bcf16f2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-comment-on-github-pull-request\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      To setup a **GitHub personal access token** visit: https://github.com/settings/tokens\n      Add repo(Full control of private repositories) scope to the generated token, to allow to comment on GitHub Pull Request or Issue.\n    is_required: true\n    is_sensitive: true\n    title: GitHub personal access token\n  personal_access_token: null\n- body: null\n  opts:\n    description: |\n      Text of the message to send.\n    is_required: true\n    title: Body\n- opts:\n    description: |\n      The URL for target GitHub Repository.\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- issue_number: $BITRISE_PULL_REQUEST\n  opts:\n    description: |\n      Number of GitHub Pull request or Issue.\n    is_required: true\n    title: GitHub PullRequest or Issue number\n- api_base_url: https://api.github.com\n  opts:\n    description: The URL for GitHub or GitHub Enterprise API\n    is_required: true\n    title: GitHub API Base URL\n"
  },
  {
    "path": "steps/comment-on-github-pull-request/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.10/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2025-08-07T15:40:44.041101+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 53bcc2b45e399d5fafb72080509bac01f555fe53\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- exclude_keys: \"\"\n  opts:\n    summary: e.g. 'featureFlagToExclude1 featureFlagToExclude2'.\n    title: List of feature flag keys that must be excluded from the scan report\n- alias_patterns: \"\"\n  opts:\n    summary: The regex pattern must include the CC_KEY placeholder that represents\n      the actual feature flag or setting key in your code e.g. '(\\w+) = :CC_KEY,const\n      (\\w+) = feature_flags\\.enabled\\(:CC_KEY\\)'.\n    title: Comma delimited list of custom regex patterns used to search for additional\n      aliases\n- opts:\n    summary: The regex pattern must include the CC_KEY placeholder that represents\n      the actual feature flag or setting key in your code e.g. 'feature_flags\\.enabled\\(:CC_KEY\\)'.\n    title: Comma delimited list of custom regex patterns that describe additional\n      feature flag key usages\n  usage_patterns: \"\"\n- opts:\n    summary: e.g. 'subfolder/to/scan'.\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging.\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.11/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2026-02-05T22:19:15.566555+01:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 7d899575f69da8f7fe7863aecd1006d5c85285e7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- exclude_keys: \"\"\n  opts:\n    summary: e.g. 'featureFlagToExclude1 featureFlagToExclude2'.\n    title: List of feature flag keys that must be excluded from the scan report\n- alias_patterns: \"\"\n  opts:\n    summary: The regex pattern must include the CC_KEY placeholder that represents\n      the actual feature flag or setting key in your code e.g. '(\\w+) = :CC_KEY,const\n      (\\w+) = feature_flags\\.enabled\\(:CC_KEY\\)'.\n    title: Comma delimited list of custom regex patterns used to search for additional\n      aliases\n- opts:\n    summary: The regex pattern must include the CC_KEY placeholder that represents\n      the actual feature flag or setting key in your code e.g. 'feature_flags\\.enabled\\(:CC_KEY\\)'.\n    title: Comma delimited list of custom regex patterns that describe additional\n      feature flag key usages\n  usage_patterns: \"\"\n- opts:\n    summary: e.g. 'subfolder/to/scan'.\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging.\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.2/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n## Configuring the Step\\n\\n1. Log in\n  to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public Management\n  API credentials](https://app.configcat.com/my-account/public-api-credentials/) \\n1.\n  Store your credentials in the following Bitrise secret environment variables: `CONFIGCAT_API_USER`,\n  `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2022-05-05T16:54:00.310438+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 836a4f0f44149093946676e2e315c65f0592b021\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.3/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2022-05-19T16:26:12.700284+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 7a89f32f7ff97e8922c1c8c4d1059d9f47f3df28\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.4/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2022-10-09T23:36:25.104429+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: c61cbf49c9725f56eb7b590829b8e810fc53c6b3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.5/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2023-04-05T14:21:04.53816+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: e5a64660a98abd0c85f98cc2b1bf086a6230fb71\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.6/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2023-08-17T12:08:16.406568+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 23b378dc335e8c90ec5ef6c26d98688a11fc77d2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.7/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2023-10-12T21:45:01.677942+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 8c29c52d855ed7211c537485c49f8967d328942b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.8/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2024-04-11T15:23:29.986976+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: 6e5a96302954bcedf5a81974d70edd6b38c524bb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- opts:\n    summary: e.g. 'subfolder/to/scan'\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/0.0.9/step.yml",
    "content": "title: ConfigCat Feature Flag Sync\nsummary: Scans the source code for feature flags and uploads the references to the\n  ConfigCat Dashboard\ndescription: \"This Step helps you get rid of technical debt by scanning the source\n  code and highlighting the feature flag usages for each feature flag on the [ConfigCat\n  Dashboard](https://app.configcat.com/).\\n\\n[ConfigCat](https://configcat.com/) is\n  a hosted service for feature flag and configuration management. It enables you to\n  decouple feature releases from code deployments. \\n\\n## Configuring the Step\\n\\n1.\n  Log in to [ConfigCat](https://app.configcat.com/)\\n1. Create new [ConfigCat Public\n  Management API credentials](https://app.configcat.com/my-account/public-api-credentials/)\n  \\n1. Store your credentials in the following Bitrise secret environment variables:\n  `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`.\\n1. Add your [ConfigCat config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n  to the `ConfigCat Config ID` input variable of this step (`configcat_config_id`\n  in bitrise.yml). The config ID tells the step which feature flags it should search\n  for in your source code.\\n\\nFor more information about code reference scanning,\n  see the [documentation](https://configcat.com/docs/advanced/code-references/overview/).\\n\\n###\n  Code snippet on the ConfigCat Dashboard\\n![Code references](https://configcat.com/docs/assets/cli/scan/scan_report.png)\"\nwebsite: https://configcat.com/\nsource_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/\nsupport_url: https://configcat.com/support/\npublished_at: 2024-09-05T11:50:30.594669+02:00\nsource:\n  git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git\n  commit: a27868235c227bcda815ee0e1430c7fdd6c66b18\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- configcat_api_host: api.configcat.com\n  opts:\n    is_required: true\n    summary: Full domain name without protocol e.g. 'api.configcat.com'\n    title: ConfigCat Public Management API host\n- configcat_config_id: null\n  opts:\n    is_required: true\n    summary: The [config ID](https://configcat.com/docs/advanced/code-references/overview#config-id)\n      tells the step which feature flags it should search for in your source code.\n    title: ConfigCat Config ID\n- line_count: 4\n  opts:\n    summary: The ConfigCat Dashboard will display a few lines of your source code\n      around the feature flag reference. You can set here how many lines of code you\n      want to include before and after the reference line.\n    title: 'Code snippet line count before and after the reference line (min: 1, max:\n      10)'\n- exclude_keys: \"\"\n  opts:\n    summary: e.g. 'featureFlagToExclude1 featureFlagToExclude2'.\n    title: List of feature flag keys that must be excluded from the scan report\n- alias_patterns: \"\"\n  opts:\n    summary: The regex pattern must include the CC_KEY placeholder that represents\n      the actual feature flag or setting key in your code e.g. '(\\w+) = :CC_KEY,const\n      (\\w+) = feature_flags\\.enabled\\(:CC_KEY\\)'.\n    title: Comma delimited list of custom regex patterns used to search for additional\n      aliases\n- opts:\n    summary: The regex pattern must include the CC_KEY placeholder that represents\n      the actual feature flag or setting key in your code e.g. 'feature_flags\\.enabled\\(:CC_KEY\\)'.\n    title: Comma delimited list of custom regex patterns that describe additional\n      feature flag key usages\n  usage_patterns: \"\"\n- opts:\n    summary: e.g. 'subfolder/to/scan'.\n    title: Sub-folder to scan, relative to the repository root folder\n  sub_folder: null\n- opts:\n    summary: Turns on or off detailed logging.\n    title: Detailed logging\n    value_options:\n    - \"false\"\n    - \"true\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/configcat-feature-flag-sync/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/connect-to-fortigate-sslvpn/1.0.0/step.yml",
    "content": "title: Connect to Fortigate SSLVPN\nsummary: |\n  Connect to Fortigate SSL VPN\ndescription: |\n  Bitrise step to connect to Fortigate SSL VPN\nwebsite: https://github.com/vielasis/bitrise-step-connect-to-fortigate-sslvpn\nsource_code_url: https://github.com/vielasis/bitrise-step-connect-to-fortigate-sslvpn\nsupport_url: https://github.com/vielasis/bitrise-step-connect-to-fortigate-sslvpn/issues\npublished_at: 2022-04-22T17:58:29.568466499+08:00\nsource:\n  git: https://github.com/vielasis/bitrise-step-connect-to-fortigate-sslvpn.git\n  commit: 269900157ef7ca8a1cb2808871757ef9d3c5f7e8\nhost_os_tags:\n- osx-10.10\n- ubuntu-20.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openfortivpn\n  apt_get:\n  - name: openfortivpn\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ftg_host: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Can be an IPv4 address on a FQDN\n    title: Remote Gateway\n- ftg_port: 443\n  opts:\n    is_expand: true\n    is_required: true\n    summary: 'VPN Port (default: 443)'\n    title: Remote Gateway Port\n- ftg_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Fortigate username\n    title: Username\n- ftg_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Fortigate password\n    title: Password\n- ftg_trusted_certs: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Passed to --trusted-cert option. Split cert entries with a newline `\\n.`\n      *DO NOT* end with newline\n    title: Trusted certs\n- ftg_logfile: $BITRISE_DEPLOY_DIR/fortigate.log\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Defaults to `$BITRISE_DEPLOY_DIR/fortigate.log`\n    title: Log file path\n- ip_hosts: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Lits of entries to be appended to /etc/hosts. Separate entries with a\n      newline `\\n`\n    title: /etc/hosts\n- ip_routes: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of IP Addresses to route to the ppp gateway. Separate entries with\n      a newline `\\n.` *DO NOT* end with newline\n    title: IP Addresses to route\n"
  },
  {
    "path": "steps/connect-to-fortigate-sslvpn/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cordova-android/0.9.0/step.yml",
    "content": "title: Cordova Android\nsummary: This step allows you to build cordova-based Android projects.\ndescription: |-\n  The Cordova CLI is the main tool to use for the cross-platform workflow\n  described in the [Overview](https://cordova.apache.org/docs/en/latest/guide/overview/index.html).\nwebsite: https://github.com/donvigo/steps-cordova-install\nsource_code_url: https://github.com/donvigo/steps-cordova-install\nsupport_url: https://github.com/donvigo/steps-cordova-install/issues\npublished_at: 2016-02-15T22:19:45.080250673+02:00\nsource:\n  git: https://github.com/donvigo/steps-cordova-android.git\n  commit: 04a6e4c317927c7b50a0cf143c4619a5030fe2a4\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- cordova\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- cordova_command: build\n  opts:\n    description: Run `cordova --help` to check list of available commands.\n    is_required: true\n    title: Cordova command to run.\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    is_required: true\n    title: Platform to build.\n    value_options:\n    - android\n  platform: android\n- build_options: --verbose\n  opts:\n    description: |-\n      Options added to the end of the Cordova call.\n      You can use multiple options, separated by a space\n      character. For example: `--verbose`; `--debug`\n      `--release --buildConfig=..\\myBuildConfig.json`\n    is_required: false\n    title: Additional options for `cordova` command\n"
  },
  {
    "path": "steps/cordova-android/0.9.1/step.yml",
    "content": "title: Cordova Android\nsummary: This step allows you to build cordova-based Android projects.\ndescription: |-\n  The Cordova CLI is the main tool to use for the cross-platform workflow\n  described in the [Overview](https://cordova.apache.org/docs/en/latest/guide/overview/index.html).\nwebsite: https://github.com/vgaidarji/steps-cordova-android\nsource_code_url: https://github.com/vgaidarji/steps-cordova-android\nsupport_url: https://github.com/vgaidarji/steps-cordova-android/issues\npublished_at: 2016-02-28T14:49:58.572507477+02:00\nsource:\n  git: https://github.com/vgaidarji/steps-cordova-android.git\n  commit: 788167433919e56b4232c021673c481130d80f44\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- cordova\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- cordova_command: build\n  opts:\n    description: Run `cordova --help` to check list of available commands.\n    is_required: true\n    title: Cordova command to run.\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    is_required: true\n    title: Platform to build.\n    value_options:\n    - android\n  platform: android\n- build_options: --verbose\n  opts:\n    description: |-\n      Options added to the end of the Cordova call.\n      You can use multiple options, separated by a space\n      character. For example: `--verbose`; `--debug`\n      `--release --buildConfig=..\\myBuildConfig.json`\n    is_required: false\n    title: Additional options for `cordova` command\n"
  },
  {
    "path": "steps/cordova-android/0.9.2/step.yml",
    "content": "title: Cordova Android\nsummary: This step allows you to build cordova-based Android projects.\ndescription: |-\n  The Cordova CLI is the main tool to use for the cross-platform workflow\n  described in the [Overview](https://cordova.apache.org/docs/en/latest/guide/overview/index.html).\nwebsite: https://github.com/vgaidarji/steps-cordova-android\nsource_code_url: https://github.com/vgaidarji/steps-cordova-android\nsupport_url: https://github.com/vgaidarji/steps-cordova-android/issues\npublished_at: 2016-02-28T18:03:02.902627117+02:00\nsource:\n  git: https://github.com/vgaidarji/steps-cordova-android.git\n  commit: 4a5490fb1d1ab65b77a6287742bf9d064d7b7258\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- cordova\ntype_tags:\n- build\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- cordova_command: build\n  opts:\n    description: Run `cordova --help` to check list of available commands.\n    is_required: true\n    title: Cordova command to run.\n- opts:\n    description: |\n      Choose which platform to build your dependencies for.\n    is_required: true\n    title: Platform to build.\n    value_options:\n    - android\n  platform_name: android\n- build_options: --verbose\n  opts:\n    description: |-\n      Options added to the end of the Cordova call.\n      You can use multiple options, separated by a space\n      character. For example: `--verbose`; `--debug`\n      `--release --buildConfig=..\\myBuildConfig.json`\n    is_required: false\n    title: Additional options for `cordova` command\n"
  },
  {
    "path": "steps/cordova-android/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cordova-archive/0.9.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2017-04-27T16:43:54.212250194+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 1dc4368a29133df02e4826ca2d4e70c6c3446238\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/0.9.1/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2017-04-28T15:22:04.504982933+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: b938c2c3503ef8754b0cb97cf3eaf91fb2c3fb68\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/0.9.2/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2017-05-25T16:54:22.262135603+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 30035e80b2596941b263fc0b96efafee47fdc074\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/0.9.3/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2017-08-09T15:00:09.496671528+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: b7718917e90b7e7e030668b9240fdea516557d73\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/1.0.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2017-10-02T14:03:26.318499115+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: e39d64e77951f2de2c0790946853f74c30f88454\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/1.0.1/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2017-12-18T16:07:24.787327714+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 56137b9802075cd8c2896740bd2c62b9e539de7b\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/1.1.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2018-02-13T13:42:26.891039899+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 72c27b335d4b87cf0683158daa586c8b642608a8\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/1.1.1/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  For first the step prepare your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2018-03-05T11:53:35.022717+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 5625552ad051b91f58963d3795b047a228cdb0a6\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/1.2.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: \"Archives your Cordova project.\\n\\nFirst, the step prepare your Cordova\n  project by calling either:\\n\\n- `cordova \\\"platform\\\" \\\"rm\\\" \\\"<platform>\\\"`\\n-\n  `cordova \\\"platform\\\" \\\"add\\\" \\\"<platform>\\\"`\\n\\nOr: \\n\\n- `cordova \\\"prepare\\\"\n  \\\"<platform>\\\"`\\n\\nThen it archives the project by calling:\\n\\n- `cordova \\\"build\\\"\n  \\\"--debug|--release\\\" \\\"--device|--emulator\\\" \\\"<platform>\\\" \\\"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\\\"`\"\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2018-10-26T12:09:57.028090822+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 1e872120c8990fe15db05af655a078f736930277\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- add_platform: \"true\"\n  opts:\n    description: |-\n      Specify whether to add platforms during prepare. If false, prepare command will be used instead.\n\n      `cordova platform add <platform>` or `cordova prepare <platform>`\n    is_required: true\n    title: Should add platforms as part of the prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      Only applies if _\"Should add platforms as prepare step?\"_ is `true`.\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as part of the prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      For Xcode 10 build issues add `--buildFlag=\"-UseModernBuildSystem=0\"` to options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/1.2.1/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: \"Archives your Cordova project.\\n\\nFirst, the step prepare your Cordova\n  project by calling either:\\n\\n- `cordova \\\"platform\\\" \\\"rm\\\" \\\"<platform>\\\"`\\n-\n  `cordova \\\"platform\\\" \\\"add\\\" \\\"<platform>\\\"`\\n\\nOr: \\n\\n- `cordova \\\"prepare\\\"\n  \\\"<platform>\\\"`\\n\\nThen it archives the project by calling:\\n\\n- `cordova \\\"build\\\"\n  \\\"--debug|--release\\\" \\\"--device|--emulator\\\" \\\"<platform>\\\" \\\"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\\\"`\"\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2018-11-07T12:44:30.363913092+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 062927fdd284a46cd97b6c67f4e8be11bbd44328\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- add_platform: \"true\"\n  opts:\n    description: |-\n      Specify whether to add platforms during prepare. If false, prepare command will be used instead.\n\n      `cordova platform add <platform>` or `cordova prepare <platform>`\n    is_required: true\n    title: Should add platforms as part of the prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      Only applies if _\"Should add platforms as prepare step?\"_ is `true`.\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as part of the prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      For Xcode 10 build issues add `--buildFlag=\"-UseModernBuildSystem=0\"` to options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.0.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  First, the step prepares your Cordova project by calling:\n\n  - `cordova \"prepare\" \"<platform>\"`\n\n  Then it archives the project by calling:\n\n  - `cordova \"compile\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2018-12-14T11:00:30.805598872Z\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-archive.git\n  commit: 3095639b003c278870bdba1c67dd8c1f1bdb76c3\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Cordova does not yet support the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.1.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  First, the step prepares your Cordova project by calling:\n\n  - `cordova \"prepare\" \"<platform>\"`\n\n  Then it archives the project by calling:\n\n  - `cordova \"compile\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2019-09-23T08:44:57.626931011Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 186a448946a263b9a8df5d768cafbe88a5cdba1d\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Cordova does not yet support the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.1.1/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  First, the step prepares your Cordova project by calling:\n\n  - `cordova \"prepare\" \"<platform>\"`\n\n  Then it archives the project by calling:\n\n  - `cordova \"compile\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2020-05-07T08:03:51.244809194Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: c50d99250d37dd50655568c2a3f5d3f7879e6b6a\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Cordova does not yet support the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.2.0/step.yml",
    "content": "title: Cordova archive\nsummary: Archives your Cordova project\ndescription: |-\n  Archives your Cordova project.\n\n  First, the step prepares your Cordova project by calling:\n\n  - `cordova \"prepare\" \"<platform>\"`\n\n  Then it archives the project by calling:\n\n  - `cordova \"compile\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2020-05-28T10:49:57.448804131Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 4e18940442eac2c08c98d5964daaa8f9fc518a9e\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Add `-- --packageType=\"bundle\"` to build an Android bundle (aab). (https://github.com/apache/cordova-android/pull/764)\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.2.1/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: \"\\nThe Step creates an archive of your Cordova project: it prepares the\n  project by calling `cordova prepare` and then archives it by calling `cordova compile`\n  with the Cordova CLI.\\n\\nIf you want to perform code signing on your app, the Step\n  requires the **Generate Cordova build configuration** Step: this Step provides the\n  configuration for the **Cordova Archive** Step.\\n\\n### Configuring the Step\\n\\nThe\n  Step needs to know the platform (iOS, Android, or both), the mode (release or debug),\n  and the target (device or emulator) of your build. You decide whether you want the\n  Step to run the `cordova prepare` command or you want to use the **Cordova Prepare**\n  Step.\\n\\n1. In the **Platform to use in cordova-cli commands** input, set the platforms\n  you need.\\n1. In the **Build command configuration** input, set the build mode for\n  the app.\\n\\n   This can be either `release` or `debug`.\\n\\n1. In the **Build command\n  target** input, set whether you want to build the app for a device or an emulator.\\n\\n1.\n  If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed\n  before `cordova compile`?** input to `false`.\\n\\n1. If you want to deploy your app,\n  the **Build configuration path to describe code signing properties** input should\n  be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\\n\\n   This Environment Variable\n  is exposed by the **Generate Cordova build configuration** Step.\\n\\n### Troubleshooting\\n\\n-\n  If you run a `release` build, make sure that your code signing configurations are\n  correct. The Step will fail if the **Generate Cordova build configuration** Step\n  does not have the required code signing inputs - for example, if you mean to deploy\n  an iOS app to the App Store, you need a Distribution code signing identity. And\n  of course check the code signing files that you uploaded to Bitrise! \\n\\n\\n### Useful\n  links\\n\\n- [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n\\n###\n  Related Steps\\n\\n- [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\\n-\n  [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\"\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2020-11-20T20:14:28.635492968Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 3a2e2fa0563a1932515385ac844db716946d452a\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Add `-- --packageType=\"bundle\"` to build an Android bundle (aab). (https://github.com/apache/cordova-android/pull/764)\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.3.0/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: \"\\nThe Step creates an archive of your Cordova project: it prepares the\n  project by calling `cordova prepare` and then archives it by calling `cordova compile`\n  with the Cordova CLI.\\n\\nIf you want to perform code signing on your app, the Step\n  requires the **Generate Cordova build configuration** Step: this Step provides the\n  configuration for the **Cordova Archive** Step.\\n\\n### Configuring the Step\\n\\nThe\n  Step needs to know the platform (iOS, Android, or both), the mode (release or debug),\n  and the target (device or emulator) of your build. You decide whether you want the\n  Step to run the `cordova prepare` command or you want to use the **Cordova Prepare**\n  Step.\\n\\n1. In the **Platform to use in cordova-cli commands** input, set the platforms\n  you need.\\n1. In the **Build command configuration** input, set the build mode for\n  the app.\\n\\n   This can be either `release` or `debug`.\\n\\n1. In the **Build command\n  target** input, set whether you want to build the app for a device or an emulator.\\n\\n1.\n  If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed\n  before `cordova compile`?** input to `false`.\\n\\n1. If you want to deploy your app,\n  the **Build configuration path to describe code signing properties** input should\n  be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\\n\\n   This Environment Variable\n  is exposed by the **Generate Cordova build configuration** Step.\\n\\n### Troubleshooting\\n\\n-\n  If you run a `release` build, make sure that your code signing configurations are\n  correct. The Step will fail if the **Generate Cordova build configuration** Step\n  does not have the required code signing inputs - for example, if you mean to deploy\n  an iOS app to the App Store, you need a Distribution code signing identity. And\n  of course check the code signing files that you uploaded to Bitrise! \\n\\n\\n### Useful\n  links\\n\\n- [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n\\n###\n  Related Steps\\n\\n- [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\\n-\n  [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\"\nwebsite: https://github.com/bitrise-community/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-community/steps-cordova-archive\nsupport_url: https://github.com/bitrise-community/steps-cordova-archive/issues\npublished_at: 2021-05-12T12:56:19.570748707Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: e6c828de732f8133f0364d04f16218671d24e565\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      Add `-- --packageType=\"bundle\"` to build an Android bundle (aab). (https://github.com/apache/cordova-android/pull/764)\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/2.4.0/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: \"\\nThe Step creates an archive of your Cordova project: it prepares the\n  project by calling `cordova prepare` and then archives it by calling `cordova compile`\n  with the Cordova CLI.\\n\\nIf you want to perform code signing on your app, the Step\n  requires the **Generate Cordova build configuration** Step: this Step provides the\n  configuration for the **Cordova Archive** Step.\\n\\n### Configuring the Step\\n\\nThe\n  Step needs to know the platform (iOS, Android, or both), the mode (release or debug),\n  and the target (device or emulator) of your build. You decide whether you want the\n  Step to run the `cordova prepare` command or you want to use the **Cordova Prepare**\n  Step.\\n\\n1. In the **Platform to use in cordova-cli commands** input, set the platforms\n  you need.\\n1. In the **Build command configuration** input, set the build mode for\n  the app.\\n\\n   This can be either `release` or `debug`.\\n\\n1. In the **Build command\n  target** input, set whether you want to build the app for a device or an emulator.\\n\\n1.\n  If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed\n  before `cordova compile`?** input to `false`.\\n\\n1. If you want to deploy your app,\n  the **Build configuration path to describe code signing properties** input should\n  be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\\n\\n   This Environment Variable\n  is exposed by the **Generate Cordova build configuration** Step.\\n\\n### Troubleshooting\\n\\n-\n  If you run a `release` build, make sure that your code signing configurations are\n  correct. The Step will fail if the **Generate Cordova build configuration** Step\n  does not have the required code signing inputs - for example, if you mean to deploy\n  an iOS app to the App Store, you need a Distribution code signing identity. And\n  of course check the code signing files that you uploaded to Bitrise! \\n\\n\\n### Useful\n  links\\n\\n- [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n\\n###\n  Related Steps\\n\\n- [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\\n-\n  [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\"\nwebsite: https://github.com/bitrise-steplib/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-cordova-archive\nsupport_url: https://github.com/bitrise-steplib/steps-cordova-archive/issues\npublished_at: 2021-08-02T15:13:06.834521845Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 8cf33557d25ac32ace74ee33e218c9e2623386ff\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `--buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_app_type: apk\n  opts:\n    category: Android\n    description: Distribution type when building the Android app\n    is_required: true\n    summary: Distribution type when building the Android app\n    title: Android app type\n    value_options:\n    - apk\n    - aab\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/3.0.0/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: \"\\nThe Step creates an archive of your Cordova project: it prepares the\n  project by calling `cordova prepare` and then archives it by calling `cordova compile`\n  with the Cordova CLI.\\n\\nIf you want to perform code signing on your app, the Step\n  requires the **Generate Cordova build configuration** Step: this Step provides the\n  configuration for the **Cordova Archive** Step.\\n\\n### Configuring the Step\\n\\nThe\n  Step needs to know the platform (iOS, Android, or both), the mode (release or debug),\n  and the target (device or emulator) of your build. You decide whether you want the\n  Step to run the `cordova prepare` command or you want to use the **Cordova Prepare**\n  Step.\\n\\n1. In the **Platform to use in cordova-cli commands** input, set the platforms\n  you need.\\n1. In the **Build command configuration** input, set the build mode for\n  the app.\\n\\n   This can be either `release` or `debug`.\\n\\n1. In the **Build command\n  target** input, set whether you want to build the app for a device or an emulator.\\n\\n1.\n  If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed\n  before `cordova compile`?** input to `false`.\\n\\n1. If you want to deploy your app,\n  the **Build configuration path to describe code signing properties** input should\n  be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\\n\\n   This Environment Variable\n  is exposed by the **Generate Cordova build configuration** Step.\\n\\n### Troubleshooting\\n\\n-\n  If you run a `release` build, make sure that your code signing configurations are\n  correct. The Step will fail if the **Generate Cordova build configuration** Step\n  does not have the required code signing inputs - for example, if you mean to deploy\n  an iOS app to the App Store, you need a Distribution code signing identity. And\n  of course check the code signing files that you uploaded to Bitrise! \\n\\n\\n### Useful\n  links\\n\\n- [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n\\n###\n  Related Steps\\n\\n- [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\\n-\n  [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\"\nwebsite: https://github.com/bitrise-steplib/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-cordova-archive\nsupport_url: https://github.com/bitrise-steplib/steps-cordova-archive/issues\npublished_at: 2021-10-06T07:02:52.614653452Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 1535ba35e5a72e34865599bc4d63dd9a81bc34a1\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- build_system: modern\n  opts:\n    description: |-\n      The Xcode build system to use.\n\n      - legacy: Use the legacy build system.\n      - modern: Use the new Xcode build system.\n    is_required: true\n    title: Xcode build system\n    value_options:\n    - legacy\n    - modern\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_app_type: apk\n  opts:\n    category: Android\n    description: Distribution type when building the Android app\n    is_required: true\n    summary: Distribution type when building the Android app\n    title: Android app type\n    value_options:\n    - apk\n    - aab\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/3.0.1/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: \"\\nThe Step creates an archive of your Cordova project: it prepares the\n  project by calling `cordova prepare` and then archives it by calling `cordova compile`\n  with the Cordova CLI.\\n\\nIf you want to perform code signing on your app, the Step\n  requires the **Generate Cordova build configuration** Step: this Step provides the\n  configuration for the **Cordova Archive** Step.\\n\\n### Configuring the Step\\n\\nThe\n  Step needs to know the platform (iOS, Android, or both), the mode (release or debug),\n  and the target (device or emulator) of your build. You decide whether you want the\n  Step to run the `cordova prepare` command or you want to use the **Cordova Prepare**\n  Step.\\n\\n1. In the **Platform to use in cordova-cli commands** input, set the platforms\n  you need.\\n1. In the **Build command configuration** input, set the build mode for\n  the app.\\n\\n   This can be either `release` or `debug`.\\n\\n1. In the **Build command\n  target** input, set whether you want to build the app for a device or an emulator.\\n\\n1.\n  If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed\n  before `cordova compile`?** input to `false`.\\n\\n1. If you want to deploy your app,\n  the **Build configuration path to describe code signing properties** input should\n  be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\\n\\n   This Environment Variable\n  is exposed by the **Generate Cordova build configuration** Step.\\n\\n### Troubleshooting\\n\\n-\n  If you run a `release` build, make sure that your code signing configurations are\n  correct. The Step will fail if the **Generate Cordova build configuration** Step\n  does not have the required code signing inputs - for example, if you mean to deploy\n  an iOS app to the App Store, you need a Distribution code signing identity. And\n  of course check the code signing files that you uploaded to Bitrise! \\n\\n\\n### Useful\n  links\\n\\n- [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n\\n###\n  Related Steps\\n\\n- [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\\n-\n  [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\"\nwebsite: https://github.com/bitrise-steplib/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-cordova-archive\nsupport_url: https://github.com/bitrise-steplib/steps-cordova-archive/issues\npublished_at: 2023-09-20T09:17:51.498334614Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: b7df5527ea47b34e9009ea2dad15a1e98d373620\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- build_system: modern\n  opts:\n    description: |-\n      The Xcode build system to use.\n\n      - legacy: Use the legacy build system.\n      - modern: Use the new Xcode build system.\n    is_required: true\n    title: Xcode build system\n    value_options:\n    - legacy\n    - modern\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_app_type: apk\n  opts:\n    category: Android\n    description: Distribution type when building the Android app\n    is_required: true\n    summary: Distribution type when building the Android app\n    title: Android app type\n    value_options:\n    - apk\n    - aab\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/3.0.2/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: \"\\nThe Step creates an archive of your Cordova project: it prepares the\n  project by calling `cordova prepare` and then archives it by calling `cordova compile`\n  with the Cordova CLI.\\n\\nIf you want to perform code signing on your app, the Step\n  requires the **Generate Cordova build configuration** Step: this Step provides the\n  configuration for the **Cordova Archive** Step.\\n\\n### Configuring the Step\\n\\nThe\n  Step needs to know the platform (iOS, Android, or both), the mode (release or debug),\n  and the target (device or emulator) of your build. You decide whether you want the\n  Step to run the `cordova prepare` command or you want to use the **Cordova Prepare**\n  Step.\\n\\n1. In the **Platform to use in cordova-cli commands** input, set the platforms\n  you need.\\n1. In the **Build command configuration** input, set the build mode for\n  the app.\\n\\n   This can be either `release` or `debug`.\\n\\n1. In the **Build command\n  target** input, set whether you want to build the app for a device or an emulator.\\n\\n1.\n  If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed\n  before `cordova compile`?** input to `false`.\\n\\n1. If you want to deploy your app,\n  the **Build configuration path to describe code signing properties** input should\n  be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\\n\\n   This Environment Variable\n  is exposed by the **Generate Cordova build configuration** Step.\\n\\n### Troubleshooting\\n\\n-\n  If you run a `release` build, make sure that your code signing configurations are\n  correct. The Step will fail if the **Generate Cordova build configuration** Step\n  does not have the required code signing inputs - for example, if you mean to deploy\n  an iOS app to the App Store, you need a Distribution code signing identity. And\n  of course check the code signing files that you uploaded to Bitrise! \\n\\n\\n### Useful\n  links\\n\\n- [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n\\n###\n  Related Steps\\n\\n- [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\\n-\n  [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\"\nwebsite: https://github.com/bitrise-steplib/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-cordova-archive\nsupport_url: https://github.com/bitrise-steplib/steps-cordova-archive/issues\npublished_at: 2023-10-10T13:14:43.115522193Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: 45cbb9715948d10aab813ad52e627b455fb97df6\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- build_system: modern\n  opts:\n    description: |-\n      The Xcode build system to use.\n\n      - legacy: Use the legacy build system.\n      - modern: Use the new Xcode build system.\n    is_required: true\n    title: Xcode build system\n    value_options:\n    - legacy\n    - modern\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_app_type: apk\n  opts:\n    category: Android\n    description: Distribution type when building the Android app\n    is_required: true\n    summary: Distribution type when building the Android app\n    title: Android app type\n    value_options:\n    - apk\n    - aab\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/3.0.3/step.yml",
    "content": "title: Cordova Archive\nsummary: Creates an archive of your Cordova project by calling `cordova prepare` and\n  then `cordova compile`, using your Cordova build configuration.\ndescription: |2-\n\n  The Step creates an archive of your Cordova project: it prepares the project by calling `cordova prepare` and then archives it by calling `cordova compile` with the Cordova CLI.\n\n  If you want to perform code signing on your app, the Step requires the **Generate Cordova build configuration** Step: this Step provides the configuration for the **Cordova Archive** Step.\n\n  ### Configuring the Step\n\n  The Step needs to know the platform (iOS, Android, or both), the mode (release or debug), and the target (device or emulator) of your build. You decide whether you want the Step to run the `cordova prepare` command or you want to use the **Cordova Prepare** Step.\n\n  1. In the **Platform to use in cordova-cli commands** input, set the platforms you need.\n  1. In the **Build command configuration** input, set the build mode for the app.\n\n     This can be either `release` or `debug`.\n\n  1. In the **Build command target** input, set whether you want to build the app for a device or an emulator.\n\n  1. If you use the **Cordova Prepare** Step, set the **Should `cordova prepare` be executed before `cordova compile`?** input to `false`.\n\n  1. If you want to deploy your app, the **Build configuration path to describe code signing properties** input should be set to `$BITRISE_CORDOVA_BUILD_CONFIGURATION`.\n\n     This Environment Variable is exposed by the **Generate Cordova build configuration** Step.\n\n  ### Troubleshooting\n\n  - If you run a `release` build, make sure that your code signing configurations are correct. The Step will fail if the **Generate Cordova build configuration** Step does not have the required code signing inputs - for example, if you mean to deploy an iOS app to the App Store, you need a Distribution code signing identity. And of course check the code signing files that you uploaded to Bitrise!\n\n  ### Useful links\n\n  - [Getting started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\n\n  ### Related Steps\n\n  - [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\n  - [Cordova Prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\n  - [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\nwebsite: https://github.com/bitrise-steplib/steps-cordova-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-cordova-archive\nsupport_url: https://github.com/bitrise-steplib/steps-cordova-archive/issues\npublished_at: 2024-03-06T12:04:19.369107766Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-archive.git\n  commit: add8d31c54cd664df04f3e927c3d916de9fe1071\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-cordova-archive\ndeps:\n  brew:\n  - name: node\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path to describe code signing properties\n- opts:\n    description: |-\n      Should be left at the default (true) value, except if the cordova-prepare step is used.\n\n      - true: `cordova prepare <platform>` followed by `cordova compile <platform>`\n      - false: `cordova compile <platform>`\n    is_required: true\n    title: Should `cordova prepare` be executed before `cordova compile`?\n    value_options:\n    - \"true\"\n    - \"false\"\n  run_cordova_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If the value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input field empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the cordova-cli build command.\n\n      The new Xcode build system is now supported in cordova-ios@5.0.0 (https://github.com/apache/cordova-ios/issues/407).\n      Example:\n      - `--browserify`\n\n      `cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the cordova-cli build command\n- build_system: modern\n  opts:\n    description: |-\n      The Xcode build system to use.\n\n      - legacy: Use the legacy build system.\n      - modern: Use the new Xcode build system.\n    is_required: true\n    title: Xcode build system\n    value_options:\n    - legacy\n    - modern\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_app_type: apk\n  opts:\n    category: Android\n    description: Distribution type when building the Android app\n    is_required: true\n    summary: Distribution type when building the Android app\n    title: Android app type\n    value_options:\n    - apk\n    - aab\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created android .aab file's path\n"
  },
  {
    "path": "steps/cordova-archive/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/cordova-config/0.0.3/step.yml",
    "content": "title: Manipulate cordova config.xml\nsummary: |\n  Manipulate cordova config.xml\ndescription: |\n  Manipulate cordova config.xml\nwebsite: https://github.com/platanus/bitrise-step-cordova-config\nsource_code_url: https://github.com/platanus/bitrise-step-cordova-config\nsupport_url: https://github.com/platanus/bitrise-step-cordova-config/issues\npublished_at: 2017-12-07T10:42:17.822211-05:00\nsource:\n  git: https://github.com/platanus/bitrise-step-cordova-config.git\n  commit: c70527e8d200c3ee2b66a44c5da80c3977a0e941\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- name: $CORDOVA_NAME\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Modify the element `<name></name>` in the config.xml file\n    title: Cordova application name\n- id: $CORDOVA_ID\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Modify the attribute `id` the config.xml file\n    title: Cordova ID\n- android_version_code: $CORDOVA_ANDROID_VERSION_CODE\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Modify the attribute `android-versionCode` in the config.xml file\n    title: Android version code\n- android_package_name: $CORDOVA_ANDROID_PACKAGE_NAME\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Modify the attribute `android-packageName` in the config.xml file\n    title: Android package name\n- ios_bundle_version: $CORDOVA_IOS_BUNDLE_VERSION\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Modify the attribute `ios-CFBundleVersion` in the config.xml file\n    title: iOS bundle version\n- ios_bundle_identifier: $CORDOVA_IOS_BUNDLE_IDENTIFIER\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Modify the attribute `ios-CFBundleIdentifier` in the config.xml file\n    title: iOS bundle identifier\n- config_path: $CORDOVA_CONFIG_PATH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Define the location of the config.xml files. Defaults to `./config.xml`\n    title: Cordova config.xml file location\n"
  },
  {
    "path": "steps/cordova-config/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cordova-ios/0.1.0/step.yml",
    "content": "title: Cordova iOS\nsummary: This step allows you to build cordova-based iOS projects.\ndescription: |-\n  The Cordova CLI is the main tool to use for the cross-platform workflow\n  described in the [Overview](https://cordova.apache.org/docs/en/latest/guide/overview/index.html).\nwebsite: https://github.com/nhammond101/steps-cordova-ios\nsource_code_url: https://github.com/nhammond101/steps-cordova-ios\nsupport_url: https://github.com/nhammond101/steps-cordova/issues-ios\npublished_at: 2016-12-01T17:07:00.811198062Z\nsource:\n  git: https://github.com/nhammond101/steps-cordova-ios.git\n  commit: 4d4c1ac316c912620c9438c9c1303abb00aaa61c\nhost_os_tags:\n- macosx\nproject_type_tags:\n- ios\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: npm\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- cordova_dir: $CORDOVA_APP_PATH\n  opts:\n    description: Change the base directory to run Cordova from.\n    is_required: false\n    title: The directory of the Cordova application.\n- cordova_command: build\n  opts:\n    description: Run `cordova --help` to check list of available commands.\n    is_required: true\n    title: Cordova command to run.\n    value_options:\n    - build\n    - platform add\n- opts:\n    description: Choose which platform to build your dependencies for.\n    is_required: true\n    title: Platform to build.\n    value_options:\n    - ios\n  platform_name: ios\n- build_options: --verbose\n  opts:\n    description: |-\n      Options added to the end of the Cordova call.\n      You can use multiple options, separated by a space\n      character. For example: `--verbose`; `--debug`\n      `--release --buildConfig=..\\myBuildConfig.json`\n    is_required: false\n    title: Additional options for `cordova` command\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/cordova-ios/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/cordova-prepare/0.9.1/step.yml",
    "content": "title: Cordova prepare\nsummary: Prepares your Cordova project\ndescription: |-\n  Prepares your Cordova project.\n\n  The step prepares your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-prepare\nsource_code_url: https://github.com/bitrise-community/steps-cordova-prepare\nsupport_url: https://github.com/bitrise-community/steps-cordova-prepare/issues\npublished_at: !!timestamp 2018-04-09T13:02:48.45053564+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-prepare.git\n  commit: 3196db678da7afcd9605dc7fbca4e98a29941f6f\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-prepare\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/cordova-prepare/0.9.2/step.yml",
    "content": "title: Cordova prepare\nsummary: Prepares your Cordova project\ndescription: |-\n  Prepares your Cordova project.\n\n  The step prepares your Cordova project by calling:\n\n  - `cordova \"platform\" \"rm\" \"<platform>\"`\n  - `cordova \"platform\" \"add\" \"<platform>\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-prepare\nsource_code_url: https://github.com/bitrise-community/steps-cordova-prepare\nsupport_url: https://github.com/bitrise-community/steps-cordova-prepare/issues\npublished_at: 2018-05-11T16:26:38.753556141+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-prepare.git\n  commit: b84d73f896de887da305e7723a999e837bf7f243\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-prepare\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `cordova platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/cordova-prepare/1.0.0/step.yml",
    "content": "title: Cordova prepare\nsummary: Prepares your Cordova project\ndescription: |-\n  Prepares your Cordova project.\n\n  The step prepares your Cordova project by calling:\n\n  - `cordova \"prepare\" \"<platform>\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-prepare\nsource_code_url: https://github.com/bitrise-community/steps-cordova-prepare\nsupport_url: https://github.com/bitrise-community/steps-cordova-prepare/issues\npublished_at: 2018-12-14T11:01:33.015288121Z\nsource:\n  git: https://github.com/bitrise-community/steps-cordova-prepare.git\n  commit: a0928009e8ad38a23e600db4005143ca420dc8b8\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-prepare\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/cordova-prepare/1.1.0/step.yml",
    "content": "title: Cordova prepare\nsummary: Prepares your Cordova project\ndescription: |-\n  Prepares your Cordova project.\n\n  The step prepares your Cordova project by calling:\n\n  - `cordova \"prepare\" \"<platform>\"`\nwebsite: https://github.com/bitrise-community/steps-cordova-prepare\nsource_code_url: https://github.com/bitrise-community/steps-cordova-prepare\nsupport_url: https://github.com/bitrise-community/steps-cordova-prepare/issues\npublished_at: 2019-09-20T11:59:17.703041062Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-prepare.git\n  commit: 193701e71ed6539695956dd7126668fd5e4ea72a\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-prepare\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cordova-prepare/1.1.1/step.yml",
    "content": "title: Cordova Prepare\nsummary: Runs Cordova Prepare for your project\ndescription: \"Prepares your Cordova project. \\n\\nThe Step prepares your Cordova project\n  by calling `cordova prepare` and copying files into platform(s), making the project\n  ready to be built.\\n\\n### Configuring the Step\\n\\n1. Make sure the selected platform\n  (iOS, Android, or both) matches your project in the **Platform to use in cordova-cli\n  commands** Step input.\\n2. The **Cordova version** input can be used to install\n  a specific version of Cordova. By default the pre-installed version will be used\n  which can differ from stack to stack. Check the current stack images [here](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports).\\n3.\n  For the **Working directory** input, make sure you have your `config.xml` file at\n  the root of your repository, or in case it's located elsewhere, make sure this input\n  points to that directory.\\n4. Caching can be enabled for `node_modules` provided\n  you have the [Cache Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  and [Cache Push](https://www.bitrise.io/integrations/steps/cache-push) Steps set\n  up.  \\n\\n### Troubleshooting\\n\\nMake sure your platforms are added to your `config.xml`\n  & `package.json` before running `cordova prepare` as that is a prerequisite of running\n  this command.\\n\\n### Useful links\\n\\n- [Cordova CLI Reference](https://cordova.apache.org/docs/en/latest/reference/cordova-cli/)\\n\\n###\n  Related Steps\\n\\n- [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-android)\\n-\n  [Generate Cordova build configuration](https://www.bitrise.io/integrations/steps/generate-cordova-build-configuration)\"\nwebsite: https://github.com/bitrise-community/steps-cordova-prepare\nsource_code_url: https://github.com/bitrise-community/steps-cordova-prepare\nsupport_url: https://github.com/bitrise-community/steps-cordova-prepare/issues\npublished_at: 2020-11-19T16:53:39.499893585Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-cordova-prepare.git\n  commit: 236d755160ae7fb67e256e8aa93345c92db663e2\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-cordova-prepare\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply cordova-cli commands to the desired platforms only.\n\n      `cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in cordova-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Cordova project, where your Cordova config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/cordova-prepare/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/create-a-new-release-in-jira/1.0.1/step.yml",
    "content": "title: Create a new release in JIRA\nsummary: |\n  Create a new release in JIRA.\ndescription: |\n  This steps create a Release in your JIRA project, with the start date, publication and description you need.\nwebsite: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira\nsource_code_url: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira\nsupport_url: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira/issues\npublished_at: 2021-10-07T10:40:41.960748-03:00\nsource:\n  git: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira.git\n  commit: 33aff55ee19bd1e089c9bf90273f3ee58fed5ff9\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Jira project prefix to search for tasks.\n\n      e.g. \"PROJ\"\n    is_expand: true\n    is_required: true\n    summary: Jira project prefix to search for tasks.\n    title: Jira project prefix\n  project_prefix: null\n- jira_domain: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    summary: Jira company domain\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_sensitive: true\n    summary: Jira user used to authenticate with Jira API\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_sensitive: true\n    summary: Jira user token used to authenticate with Jira API\n    title: Jira user token\n- opts:\n    description: |\n      Version description.\n\n      e.g. \"An excellent version\"\n    is_expand: true\n    is_required: true\n    summary: Version description\n    title: Version  description\n  version_description: null\n- opts:\n    description: |\n      Version name.\n\n      e.g. \"v1.0.0\"\n    is_expand: true\n    is_required: true\n    summary: Version name\n    title: Version  name\n  version_name: null\n- opts:\n    description: |\n      If the version is Released.\n    is_required: true\n    summary: If the version is Released\n    title: If the version is Released?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  version_released: \"no\"\n"
  },
  {
    "path": "steps/create-a-new-release-in-jira/1.0.2/step.yml",
    "content": "title: Create a new release in JIRA\nsummary: |\n  Create a new release in JIRA.\ndescription: |\n  This Step creates a Release in your JIRA project, with the start date, publication and description you need.\nwebsite: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira\nsource_code_url: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira\nsupport_url: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira/issues\npublished_at: 2021-11-25T17:50:16.408957-03:00\nsource:\n  git: https://github.com/Emalober/bitrise-step-create-a-new-release-in-jira.git\n  commit: 87abc7c45691d0d6d9cddceb09124d51eb27c9f1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Jira project prefix to search for tasks.\n\n      e.g. \"PROJ\"\n    is_expand: true\n    is_required: true\n    summary: Jira project prefix to search for tasks.\n    title: Jira project prefix\n  project_prefix: null\n- jira_domain: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    summary: Jira company domain\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_required: true\n    is_sensitive: true\n    summary: Jira user used to authenticate with Jira API\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_required: true\n    is_sensitive: true\n    summary: Jira user token used to authenticate with Jira API\n    title: Jira user token\n- opts:\n    description: |\n      Version description.\n\n      e.g. \"An excellent version\"\n    is_required: true\n    summary: Version description\n    title: Version  description\n  version_description: null\n- opts:\n    description: |\n      Version name.\n\n      e.g. \"v1.0.0\"\n    is_expand: true\n    is_required: true\n    summary: Version name\n    title: Version  name\n  version_name: null\n- opts:\n    description: |\n      If the version is Released.\n    is_required: true\n    summary: If the version is Released\n    title: If the version is Released?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  version_released: \"no\"\n"
  },
  {
    "path": "steps/create-a-new-release-in-jira/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/create-android-emulator/0.9.0/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2016-02-11T11:45:48.560557859+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: fa86cca7a9810f52f20eac178018dae463612f90\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n\n      Example: android-19\n    is_required: true\n    title: Target platform of the new AVD\n  platform: null\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/0.9.1/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2016-02-12T11:48:12.655133511+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: c963e2bea57dbf2a29df8239622bf213061cb76c\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.0.0/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2016-11-29T11:00:45.657228431+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: 350e006047d8138d1509c77f78aa35024781f0d7\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\n- options: \"\"\n  opts:\n    description: |-\n      Options added to the end of the `android create avd` call:\n\n      `android create avd --force --name name --target platform --abi abi options`\n\n      You can use multiple options, separated by a space\n      character. Example: `--skin WVGA800`\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.0/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2017-03-22T13:57:19.491966667+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: 6872bcd3a3036c635925e3f0ef0ca23da5d4f9bf\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.1/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2017-03-29T15:23:37.750021556+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: 8b50e45e2fb4b7ed98a87ba4053a31b530ffd0cf\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.2/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2017-05-02T14:57:53.086038073+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: 5e99d8cf613b5a2cccad8f73632432817e0872b1\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.3/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2017-05-16T10:36:37.33995105+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: e87911ec2f44a761268db85b382ddd5948ab2423\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.4/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2017-05-23T15:01:15.518228449+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: 963074076fc7d88065577155a8aa7b0026676674\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |\n      The ABI to use for the AVD.\n    is_dont_change_value: true\n    is_required: true\n    title: The ABI to use for the AVD\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.5/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2017-06-20T10:25:30.799462068+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: c3a04df055a03d42c5e0e7f8ae690abce2d10414\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |-\n      The ABI to use for the AVD. Availability depends on API level:\n      - `armeabi-v7a` - entire API levels\n      - `arm64-v8a` - 24 or newer\n      - `mips` - 15, 16, 17\n      - `x86` - entire API levels\n      - `x86_64` - 21 or newer\n      Note that x86 and x86_64 emulators won't work on default bitrise.io stack.\n    is_required: true\n    title: The ABI to use for the AVD\n    value_options:\n    - armeabi-v7a\n    - arm64-v8a\n    - x86\n    - x86_64\n    - mips\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n    - google_apis_playstore\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/1.1.6/step.yml",
    "content": "title: Create Android emulator\nsummary: Creates a new Android Virtual Device\ndescription: Creates a new Android Virtual Device.\nwebsite: https://github.com/bitrise-steplib/steps-create-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-create-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-create-android-emulator/issues\npublished_at: 2018-06-28T14:00:18.87765986+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-android-emulator.git\n  commit: 7a8602834c1ddd26c8efba11ed1a20541c3ff450\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- name: null\n  opts:\n    description: |\n      Name of the new AVD.\n    is_required: true\n    title: Name of the new AVD\n- opts:\n    description: |\n      Target platform of the new AVD.\n    is_required: true\n    title: Target platform of the new AVD\n  platform: android-19\n- abi: armeabi-v7a\n  opts:\n    description: |-\n      The ABI to use for the AVD. Availability depends on API level:\n      - `armeabi-v7a` - entire API levels\n      - `arm64-v8a` - 24 or newer\n      - `mips` - 15, 16, 17\n      - `x86` - entire API levels\n      - `x86_64` - 21 or newer\n      Note that x86 and x86_64 emulators won't work on default bitrise.io stack.\n    is_required: true\n    title: The ABI to use for the AVD\n    value_options:\n    - armeabi-v7a\n    - arm64-v8a\n    - x86\n    - x86_64\n    - mips\n- opts:\n    description: |\n      The sys-img tag to use for the AVD.\n    is_required: true\n    title: The sys-img tag to use for the AVD\n    value_options:\n    - default\n    - google_apis\n    - android-tv\n    - android-wear\n    - google_apis_playstore\n  tag: default\n- options: \"\"\n  opts:\n    description: \"Options added to the end of the `android create avd` or `avdmanager\n      create avd` call:\\n\\n`android create avd --force --name name --target platform\n      --abi abi options`\\n\\nor \\n\\n`avdmanager create avd --force --package PACKAGE\n      --name name --abi abi options`\\n\\nYou can use multiple options, separated by\n      a space\\ncharacter. Example: `--skin WVGA800`\"\n    title: Additional options for `android create avd` call\n- custom_hardware_profile_content: null\n  opts:\n    description: |-\n      The value of this input will be written into `${name}.avd/config.ini` file,\n      to let the created emulator use your custom hardware profile.\n\n      Format example:\n      ```\n      avd.ini.encoding=UTF-8\n      abi.type=armeabi-v7a\n      hw.cpu.arch=arm\n      hw.cpu.model=cortex-a8\n      hw.lcd.density=240\n      hw.ramSize=512\n      image.sysdir.1=system-images/android-21/default/armeabi-v7a/\n      skin.name=WVGA800\n      skin.path=platforms/android-21/skins/WVGA800\n      tag.display=Default\n      tag.id=default\n      vm.heapSize=48\n      ```\n    title: Custom Hardware Profile Content\noutputs:\n- BITRISE_EMULATOR_NAME: null\n  opts:\n    description: Name of the new AVD\n    title: Name of the new AVD\n"
  },
  {
    "path": "steps/create-android-emulator/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, use [AVD Manager](https://github.com/bitrise-steplib/steps-avd-manager) Step instead.\nmaintainer: bitrise\nremoval_date: \"2019-08-25\"\n"
  },
  {
    "path": "steps/create-apple-documentation/1.0.0/step.yml",
    "content": "title: Create Apple's documentation\nsummary: |\n  This step helps to create a HTML representation of the Framework documentation, using Jazzy as engine\ndescription: |\n  This step helps to create a HTML representation of the Framework documentation, using Jazzy as engine.\n  Objective-C and Swift are supported, but there is no declared supported for mixed language projects.\n  This was created with the goal to export as a reach HTML documents for Frameworks.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation/issues\npublished_at: 2019-11-26T12:26:43.172354+01:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation.git\n  commit: 822497f09f328a439c89158cfbc3fbce685b0632\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Path in where the script will be run\n    title: Project path\n  project_path: .\n- language: swift\n  opts:\n    description: |\n      Language used in the project. Either 'swift', or 'objc'.\n\n      At the moment, the step do not support the generation, of documentation\n      for project with mixed language, even if it is a supported feature on Jazzy.\n    is_expand: true\n    is_required: true\n    summary: Language used in the project.\n    title: Language\n    value_options:\n    - objc\n    - swift\n- author: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Author of the Framework\n    title: Author\n- opts:\n    is_expand: true\n    is_required: true\n    summary: SDK to which the code is directed\n    title: SDK\n    value_options:\n    - iphone\n    - mac\n    - tv\n    - none\n  sdk: iphone\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Version string that will be used as Module Version in the documentation\n    title: Module Version\n  version: 1.0.0\n- framework_root: .\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Root path of where the Framework is\n    title: Root path of the Framework\n- module: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Name of the module (also used as scheme)\n    title: Module name\n- acl: public\n  opts:\n    is_expand: true\n    is_required: true\n    title: The minimun ACL used to list the included classes on the doc set\n    value_options:\n    - open\n    - public\n    - internal\n    - private\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Path to where the generated files will be saved\n    title: Output of the doc set\n  output: ./docs\n- opts:\n    description: |\n      This is used to compose the final documentation with a reach index page. The Markdown file is placed as the initial page\n      and all classes are accessible through the class index. By default, the tool uses any README.md file placed in the root of the command,\n      but this can be overwritten with this input.\n    is_expand: true\n    is_required: true\n    summary: Path to the Markdown file that will be used as index of the documentation.\n    title: README file path\n  readme: ./README.md\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Message used as header title in the doc set\n    title: Title of the project\n  title: null\n- copyright: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Copyright message\n- opts:\n    is_expand: true\n    is_required: false\n    summary: This is used by Objective-C documentation generation. Optional for Swift\n    title: Path to the Framework umbrella header\n  umbrella_header: null\noutputs:\n- DOCUMENTATION_PATH: null\n  opts:\n    summary: This variable exposes the path created with the documentation, to be\n      used on further steps\n    title: Path with the generated files\n"
  },
  {
    "path": "steps/create-apple-documentation/1.1.0/step.yml",
    "content": "title: Create Apple's documentation\nsummary: |\n  This step helps to create a HTML representation of the Framework documentation, using Jazzy as engine\ndescription: |\n  This step helps to create a HTML representation of the Framework documentation, using Jazzy as engine.\n  Objective-C and Swift are supported, but there is no declared supported for mixed language projects.\n  This was created with the goal to export as a reach HTML documents for Frameworks.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation/issues\npublished_at: 2020-03-31T10:52:10.974107+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation.git\n  commit: 0ad3978dd78bf6204600fb030d2a104ce03a6c33\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- jazzy_configuration: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the jazzy.yaml file used to configure the build. If none is provided,\n      a new one may be created\n    title: Path to the jazzy configuration\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Path in where the script will be run\n    title: Project path\n  project_path: .\n- language: swift\n  opts:\n    description: |\n      Language used in the project. Either 'swift', or 'objc'.\n\n      At the moment, the step do not support the generation, of documentation\n      for project with mixed language, even if it is a supported feature on Jazzy.\n    is_expand: true\n    is_required: true\n    summary: Language used in the project.\n    title: Language\n    value_options:\n    - objc\n    - swift\n- author: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Author of the Framework\n    title: Author\n- opts:\n    is_expand: true\n    is_required: true\n    summary: SDK to which the code is directed\n    title: SDK\n    value_options:\n    - iphone\n    - mac\n    - tv\n    - none\n  sdk: iphone\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Version string that will be used as Module Version in the documentation\n    title: Module Version\n  version: 1.0.0\n- framework_root: .\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Root path of where the Framework is\n    title: Root path of the Framework\n- module: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Name of the module (also used as scheme)\n    title: Module name\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Name of the scheme that will be used to build the project. Optional for\n      Objective-C\n    title: Scheme name\n  scheme: null\n- acl: public\n  opts:\n    is_expand: true\n    is_required: true\n    title: The minimun ACL used to list the included classes on the doc set\n    value_options:\n    - open\n    - public\n    - internal\n    - private\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Path to where the generated files will be saved\n    title: Output of the doc set\n  output: ./docs\n- opts:\n    description: |\n      This is used to compose the final documentation with a reach index page. The Markdown file is placed as the initial page\n      and all classes are accessible through the class index. By default, the tool uses any README.md file placed in the root of the command,\n      but this can be overwritten with this input.\n    is_expand: true\n    is_required: true\n    summary: Path to the Markdown file that will be used as index of the documentation.\n    title: README file path\n  readme: ./README.md\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Message used as header title in the doc set\n    title: Title of the project\n  title: null\n- copyright: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Copyright message\n- opts:\n    is_expand: true\n    is_required: false\n    summary: This is used by Objective-C documentation generation. Optional for Swift\n    title: Path to the Framework umbrella header\n  umbrella_header: null\noutputs:\n- DOCUMENTATION_PATH: null\n  opts:\n    summary: This variable exposes the path created with the documentation, to be\n      used on further steps\n    title: Path with the generated files\n"
  },
  {
    "path": "steps/create-apple-documentation/1.1.1/step.yml",
    "content": "title: Create Apple's documentation\nsummary: |\n  This step helps to create a HTML representation of the Framework documentation, using Jazzy as engine\ndescription: |\n  This step helps to create a HTML representation of the Framework documentation, using Jazzy as engine.\n  Objective-C and Swift are supported, but there is no declared supported for mixed language projects.\n  This was created with the goal to export as a reach HTML documents for Frameworks.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation/issues\npublished_at: 2020-06-12T14:02:09.857363+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-create-apple-documentation.git\n  commit: 250e1818fab00f490105afe5bd9875c82fdfc380\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- jazzy_configuration: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the jazzy.yaml file used to configure the build. If none is provided,\n      a new one may be created\n    title: Path to the jazzy configuration\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Path in where the script will be run\n    title: Project path\n  project_path: ./\n- language: swift\n  opts:\n    description: |\n      Language used in the project. Either 'swift', or 'objc'.\n\n      At the moment, the step do not support the generation, of documentation\n      for project with mixed language, even if it is a supported feature on Jazzy.\n    is_expand: true\n    is_required: true\n    summary: Language used in the project.\n    title: Language\n    value_options:\n    - objc\n    - swift\n- author: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Author of the Framework\n    title: Author\n- opts:\n    is_expand: true\n    is_required: true\n    summary: SDK to which the code is directed\n    title: SDK\n    value_options:\n    - iphone\n    - mac\n    - tv\n    - none\n  sdk: iphone\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Version string that will be used as Module Version in the documentation\n    title: Module Version\n  version: 1.0.0\n- framework_root: ./\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Root path of where the Framework is\n    title: Root path of the Framework\n- module: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Name of the module (also used as scheme)\n    title: Module name\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Name of the scheme that will be used to build the project. Optional for\n      Objective-C\n    title: Scheme name\n  scheme: null\n- acl: public\n  opts:\n    is_expand: true\n    is_required: true\n    title: The minimun ACL used to list the included classes on the doc set\n    value_options:\n    - open\n    - public\n    - internal\n    - private\n- opts:\n    description: You can set this to $BITRISE_DEPLOY_DIR/Docs if you want to have\n      the docs as artifacts\n    is_expand: true\n    is_required: true\n    summary: Path to where the generated files will be saved\n    title: Output of the doc set\n  output: ./docs\n- opts:\n    description: |\n      This is used to compose the final documentation with a reach index page. The Markdown file is placed as the initial page\n      and all classes are accessible through the class index. By default, the tool uses any README.md file placed in the root of the command,\n      but this can be overwritten with this input.\n    is_expand: true\n    is_required: true\n    summary: Path to the Markdown file that will be used as index of the documentation.\n    title: README file path\n  readme: ./README.md\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Message used as header title in the doc set\n    title: Title of the project\n  title: null\n- copyright: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Copyright message\n- opts:\n    is_expand: true\n    is_required: false\n    summary: This is used by Objective-C documentation generation. Optional for Swift\n    title: Path to the Framework umbrella header\n  umbrella_header: null\noutputs:\n- DOCUMENTATION_PATH: null\n  opts:\n    summary: This variable exposes the path created with the documentation, to be\n      used on further steps\n    title: Path with the generated files\n"
  },
  {
    "path": "steps/create-apple-documentation/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/create-github-app-token/1.0.0/step.yml",
    "content": "title: Create GitHub app token\nsummary: |\n  Create GitHub app token\ndescription: |\n  Create GitHub app token\nwebsite: https://github.com/tdrk18/bitrise-step-create-github-app-token\nsource_code_url: https://github.com/tdrk18/bitrise-step-create-github-app-token\nsupport_url: https://github.com/tdrk18/bitrise-step-create-github-app-token/issues\npublished_at: 2024-06-21T13:00:15.853079+09:00\nsource:\n  git: https://github.com/tdrk18/bitrise-step-create-github-app-token.git\n  commit: 763547761aaf4b2fc86c915b3efd6251b4134707\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- github_repository: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: \"\"\n    title: GitHub repository name\n- client_id: null\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client ID of GitHub App\n    title: Client ID\n- opts:\n    description: Please download the private key before running this step\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: The local path for the private key of GitHub App\n    title: Private key path\n  private_key_path: null\noutputs:\n- GITHUB_APP_TOKEN: null\n  opts:\n    summary: Token for a GitHub App\n    title: Token\n"
  },
  {
    "path": "steps/create-github-app-token/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/create-github-pull-request/0.0.1/step.yml",
    "content": "title: |\n  Create GitHub Pull Request\nsummary: |\n  Creates a pull request on GitHub with the specified details.\ndescription: |\n  This step creates a pull request on GitHub using the provided branch names, title, body, and GitHub token.\nwebsite: https://github.com/Ahmadalsofi/bitrise-step-create-github-pull-request\nsource_code_url: https://github.com/Ahmadalsofi/bitrise-step-create-github-pull-request\nsupport_url: https://github.com/Ahmadalsofi/bitrise-step-create-github-pull-request/issues\npublished_at: 2024-03-11T11:27:23.275188+03:00\nsource:\n  git: https://github.com/Ahmadalsofi/bitrise-step-create-github-pull-request.git\n  commit: 75ae3e84c3dca68b07eb755da34aa50ead94163c\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: \"\"\ninputs:\n- from_branch: \"\"\n  opts:\n    description: Enter the name of the source branch from which changes will be pulled.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Specify the source branch for the pull request.\n    title: From Branch\n- opts:\n    description: Enter the name of the target branch to which changes will be merged.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Specify the target branch for the pull request.\n    title: To Branch\n  to_branch: \"\"\n- opts:\n    description: Enter a descriptive title for the pull request.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Provide a title for the pull request.\n    title: Pull Request Title\n  pr_title: \"\"\n- opts:\n    description: Enter a detailed description for the pull request.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Provide a description for the pull request.\n    title: Pull Request Body\n  pr_body: \"\"\n- github_token: \"\"\n  opts:\n    description: Enter the GitHub token used to authenticate the API request.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Provide the GitHub token for authentication.\n    title: GitHub Token\n- opts:\n    description: Enter the name of the GitHub repository where the pull request will\n      be created. Make sure to include both the organization name and the repository\n      name.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Provide the name of the GitHub repository.\n    title: Repository Name\n  repo_name: \"\"\noutputs:\n- PR_HTML_URL: null\n  opts:\n    summary: URL of the created pull request.\n    title: Pull Request URL\n"
  },
  {
    "path": "steps/create-github-pull-request/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/create-install-page-qr-code/0.1.0/step.yml",
    "content": "title: Install page QR code\nsummary: Create install page QR code\ndescription: Create install page QR code\nwebsite: https://github.com/dag-io/create-install-page-qr-code-step\nsource_code_url: https://github.com/dag-io/create-install-page-qr-code-step.git\nsupport_url: https://github.com/dag-io/create-install-page-qr-code-step/issues\npublished_at: 2016-05-01T17:33:36.088194107+02:00\nsource:\n  git: https://github.com/dag-io/create-install-page-qr-code-step.git\n  commit: 39e6f156cdf00e661b14f7e4f4ec427765b79805\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: homebrew/php/php56\n  apt_get:\n  - name: php5\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- opts:\n    description: The full path to the application file (.app or .apk)\n    is_expand: true\n    is_required: true\n    summary: The full path to the application file (.app or .apk)\n    title: Public Install Page URL\n  public_install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n- opts:\n    description: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    is_expand: true\n    is_required: false\n    summary: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    title: Public Install Page QR Code Image size\n  qr_code_size: 150x150\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_QR_CODE_IMAGE_URL: null\n  opts:\n    description: |-\n      QR Code Image URL for the public install page, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page QR Code Image URL\n"
  },
  {
    "path": "steps/create-install-page-qr-code/0.1.2/step.yml",
    "content": "title: Install page QR code\nsummary: Create install page QR code\ndescription: Create install page QR code\nwebsite: https://github.com/dag-io/create-install-page-qr-code-step\nsource_code_url: https://github.com/dag-io/create-install-page-qr-code-step.git\nsupport_url: https://github.com/dag-io/create-install-page-qr-code-step/issues\npublished_at: 2016-06-02T17:19:53.339051248+02:00\nsource:\n  git: https://github.com/dag-io/create-install-page-qr-code-step.git\n  commit: 7f7e1d08423963ab9736b9ecedf2d8f2281ec1a7\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- opts:\n    description: The full path to the application file (.app or .apk)\n    is_expand: true\n    is_required: true\n    summary: The full path to the application file (.app or .apk)\n    title: Public Install Page URL\n  public_install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n- opts:\n    description: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    is_expand: true\n    is_required: false\n    summary: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    title: Public Install Page QR Code Image size\n  qr_code_size: 150x150\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_QR_CODE_IMAGE_URL: null\n  opts:\n    description: |-\n      QR Code Image URL for the public install page, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page QR Code Image URL\n"
  },
  {
    "path": "steps/create-install-page-qr-code/1.0.0/step.yml",
    "content": "title: Create install page QR code\nsummary: Generates an URL for a QR code which points to the install page.\ndescription: Generates an URL for a QR code which points to the install page.\nwebsite: https://github.com/bitrise-steplib/steps-create-install-page-qr-code\nsource_code_url: https://github.com/bitrise-steplib/steps-create-install-page-qr-code\nsupport_url: https://github.com/bitrise-steplib/steps-create-install-page-qr-code/issues\npublished_at: !!timestamp 2018-04-25T16:32:09.874995974+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-install-page-qr-code.git\n  commit: 3cbc5059ec8280822f62f5d6d834d4530bf534cb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-install-page-qr-code\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: Public install page URL can be generated by `Deploy to Bitrise.io`\n      step\n    is_required: true\n    summary: The public install page URL\n    title: Public Install Page URL\n  public_install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n- opts:\n    description: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    is_required: true\n    summary: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    title: Public Install Page QR Code Image size\n  qr_code_size: 150x150\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_QR_CODE_IMAGE_URL: null\n  opts:\n    description: QR Code Image URL for the public install page.\n    title: Public Install Page QR Code Image URL\n"
  },
  {
    "path": "steps/create-install-page-qr-code/1.0.1/step.yml",
    "content": "title: Create install page QR code\nsummary: Generates a QR code which points to the public install page.\ndescription: \"The Step generates a QR code from a URL using the GoQR API. \\n\\n###\n  Configuring the Step\\n\\n1. The **Public install page URL** input has the URL automatically\n  assigned, but you can modify this value for a different URL if you want to.\\n2.\n  You can also modify the **Public install page QR Code Image size**.  By default\n  it is 150x150 pixels. \\n\\n### Troubleshooting\\n\\nMake sure the Step is placed after\n  the **Deploy to Bitrise.io** Step, otherwise the `$BITRISE_PUBLIC_INSTALL_PAGE_URL`\n  variable won't be available.\\nThis Step can only create a QR code from a single\n  link. If you want to generate multiple ones, you can add the Step multiple times.\\n\\n###\n  Useful links\\n\\n- [GoQR Documentation](http://goqr.me/api/)\\n\\n### Related Steps\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-create-install-page-qr-code\nsource_code_url: https://github.com/bitrise-steplib/steps-create-install-page-qr-code\nsupport_url: https://github.com/bitrise-steplib/steps-create-install-page-qr-code/issues\npublished_at: 2020-11-19T17:13:53.150869749Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-install-page-qr-code.git\n  commit: f46ef00cc4ec1ffa0a62103e5468cee8dd824d9b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-install-page-qr-code\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: Public install page URL can be generated by the **Deploy to Bitrise.io**\n      Step.\n    is_required: true\n    summary: The public install page URL\n    title: Public install page URL\n  public_install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n- opts:\n    description: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    is_required: true\n    summary: 'The size of the QR Code image using the format : WIDTHxHEIGHT'\n    title: Public install page QR Code Image size\n  qr_code_size: 150x150\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_QR_CODE_IMAGE_URL: null\n  opts:\n    description: QR Code Image URL for the public install page.\n    title: Public install page QR Code Image URL\n"
  },
  {
    "path": "steps/create-install-page-qr-code/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/create-new-app-store-release/1.0.0/step.yml",
    "content": "title: Prepare App Store Release\nsummary: The Step creates an App Store release with the Release Management feature.\ndescription: |-\n  The \"Prepare App Store Release\" Step allows you to streamline the process of preparing a new release for your iOS app in the Release Management. This Step leverages the Bitrise Public API to facilitate the creation and configuration of an App Store release in the Release Management.\n\n  By utilizing this Step, you can automate the initial stages of the release process and ensure a consistent and efficient deployment experience. Instead of manually navigating through the Release Management interface to create a release, the Step empowers you to initiate the release setup programmatically, saving valuable time and effort.\n\n  It's important to note that this Step doesn't create a release directly in the App Store Connect. Instead, it streamlines the process by generating a release in the [Release Management](https://devcenter.bitrise.io/en/release-management.html).\nwebsite: https://github.com/bitrise-steplib/bitrise-step-create-new-app-store-release\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-create-new-app-store-release\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-create-new-app-store-release/issues\npublished_at: 2023-07-10T16:13:11.947188+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-create-new-app-store-release.git\n  commit: 099b671ea84514380f9f00672da41c7b354a5a9f\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/tmp-bitrise-step-create-new-app-store-release\ninputs:\n- bundle_id: null\n  opts:\n    description: |-\n      The bundle ID of the app to be released.\n\n      Release Management requires the bundle ID of the iOS application being released to the App Store Connect.\n    is_required: true\n    summary: The bundle ID of the app to be released.\n    title: Bundle identifier\n- opts:\n    description: |-\n      The version number of the app you are releasing.\n\n      Numbering should follow software versioning conventions (1.0, 1.0.0).\n    is_required: true\n    summary: The version number of the app you are releasing.\n    title: Release version number\n  release_version_number: null\n- automatic_testflight_upload: \"false\"\n  opts:\n    category: Release configuration\n    description: |-\n      Indicates whether or not to upload every release candidate build automatically to TestFlight.\n\n      Release Management will deploy each release candidate to TestFlight automatically if this setting is enabled.\n      Note: This feature requires the release branch and Workflow to be set.\n    is_required: true\n    summary: Indicates whether or not to upload every release candidate build automatically\n      to TestFlight.\n    title: Automatic Testflight upload\n    value_options:\n    - \"true\"\n    - \"false\"\n- description: null\n  opts:\n    category: Release configuration\n    description: |-\n      An internal description of the release, it won't be propagated to the App Store.\n\n      This description will not be visible on the App Store Connect or available for the end user.\n    summary: An internal description of the release, it won't be propagated to the\n      App Store.\n    title: Release description\n- opts:\n    category: Release configuration\n    description: |-\n      The branch you created for this version of your app.\n\n      This branch is called mostly: release-1.0, release-october, main, etc.\n    summary: The branch you created for this version of your app.\n    title: Release branch\n  release_branch: null\n- opts:\n    category: Release configuration\n    description: |-\n      The workflow that generates your an .xcarchive or an App Store signed .ipa artifact.\n\n      Make sure that the Workflow generates the artifact for the same Bundle Identifier you provided for this Step as a step input. Release Management will ignore any other .xcarchive App Store signed .ipa with different bundle ID.\n    summary: The workflow that generates your an .xcarchive or an App Store signed\n      .ipa artifact.\n    title: Release Workflow\n  workflow: null\n- opts:\n    category: Notification\n    description: |-\n      The Slack webhook URL to use for sending Slack notifications.\n\n      By providing a Slack webhook URL, Release Management will send automatic messages for the following events:\n      ```\n      ┌─────────────────────┬───────────────────────────────────────┐\n      │ Stage               │ Event                                 │\n      ├─────────────────────┼───────────────────────────────────────┤\n      │ Release candidate   │ Release candidate changed             │\n      │ TestFlight upload   │ Upload and processing finished        │\n      │ Approvals           │ Release approved                      │\n      │ App Store review    │ Release sent for review               │\n      │                     │ Status of review submission changed   │\n      │ Release             │ Release started                       │\n      │                     │ Release finished                      │\n      └─────────────────────┴───────────────────────────────────────┘\n      ```\n      For more information go to our [devcenter notification page.](https://devcenter.bitrise.io/en/release-management/enabling-slack-notifications-for-release-management-events.html)\n    summary: The Slack webhook URL to use for sending Slack notifications.\n    title: Slack webhook URL\n  slack_webhook_url: null\n- opts:\n    category: Notification\n    description: |-\n      The Teams webhook URL to use for sending Teams notifications.\n\n      By providing a Teams webhook URL, Release Management will send automatic messages for the following events:\n      ```\n      ┌─────────────────────┬───────────────────────────────────────┐\n      │ Stage               │ Event                                 │\n      ├─────────────────────┼───────────────────────────────────────┤\n      │ Release candidate   │ Release candidate changed             │\n      │ TestFlight upload   │ Upload and processing finished        │\n      │ Approvals           │ Release approved                      │\n      │ App Store review    │ Release sent for review               │\n      │                     │ Status of review submission changed   │\n      │ Release             │ Release started                       │\n      │                     │ Release finished                      │\n      └─────────────────────┴───────────────────────────────────────┘\n      ```\n      For more information go to our [devcenter notification page.](https://devcenter.bitrise.io/en/release-management/enabling-slack-notifications-for-release-management-events.html)\n    summary: The Teams webhook URL to use for sending Teams notifications.\n    title: Teams webhook URL\n  teams_webhook_url: null\n- bitrise_api_access_token: null\n  opts:\n    description: |-\n      Your access token.\n\n      To acquire a `Personal Access Token` for your user, sign in with that user on [bitrise.io](https://bitrise.io),\n      go to your `Account Settings` page, and select the [Security tab](https://www.bitrise.io/me/profile#/security) on the left side.\n    is_required: true\n    is_sensitive: true\n    summary: Your access token.\n    title: Bitrise Access Token\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    category: API settings\n    description: |-\n      The base URL of the Bitrise API used to process the download requests.\n\n      By default the step will use the official Bitrise Public API, you don’t need to change this setting.\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    category: API settings\n    description: |-\n      The identifier of the Bitrise app for which to create a new release.\n\n      By default, the Step will create a new release for the same Bitrise App.\n    is_dont_change_value: true\n    is_required: true\n    summary: The identifier of the Bitrise app for which to create a new release.\n    title: Bitrise app identifier\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_RELEASE_SLUG: null\n  opts:\n    summary: Unique identifier of the newly created release.\n    title: Release slug\n"
  },
  {
    "path": "steps/create-new-app-store-release/step-info.yml",
    "content": "deprecate_notes: |\n  This step is no longer supported. You can get similar results with one of our new features: create release bash script\n  in Release Management API recipes. It can be used from a terminal or copied into a script step in Bitrise CI.\n  [More info](https://github.com/bitrise-io/release-management-recipes)\nmaintainer: bitrise\nremoval_date: \"2025-03-07\""
  },
  {
    "path": "steps/create-zip/0.9.0/step.yml",
    "content": "title: |\n  Create ZIP\nsummary: |\n  Creates a ZIP from the given file/dir to the given destination.\ndescription: \"Creates a ZIP from the given file/dir to the given destination. \\nIt\n  stores symlinks as symlinks ( it will not copy the file which the symlink is pointing\n  ).\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-create-zip\nsource_code_url: https://github.com/bitrise-steplib/steps-create-zip\nsupport_url: https://github.com/bitrise-steplib/steps-create-zip\npublished_at: !!timestamp 2018-04-05T16:20:31.312822517+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-zip.git\n  commit: e8bb7e0c7d9adf3a2f3057d31994d64d9f67be59\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/birmachera/bitrise-step-create-zip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The path of the directory which you want to compress with zip.\n    is_expand: true\n    is_required: true\n    summary: The path of the directory which you want to compress with zip.\n    title: Source directory path\n    value_options: []\n  source_path: null\n- destination: null\n  opts:\n    description: The path of the directory where you want to move the compressed file.\n    is_expand: true\n    is_required: true\n    summary: The path of the directory where you want to move the compressed file.\n    title: Target directory path\n    value_options: []\n"
  },
  {
    "path": "steps/create-zip/0.9.1/step.yml",
    "content": "title: |\n  Create ZIP\nsummary: |\n  Creates a ZIP from the given file/dir to the given destination.\ndescription: |\n  Creates a ZIP from the given file/dir to the given destination.\n  It stores symlinks as symlinks (it will not copy the file which the symlink is pointing to).\nwebsite: https://github.com/bitrise-steplib/steps-create-zip\nsource_code_url: https://github.com/bitrise-steplib/steps-create-zip\nsupport_url: https://github.com/bitrise-steplib/steps-create-zip\npublished_at: 2020-07-23T09:03:07.544658192Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-zip.git\n  commit: 3fcc1a7c2fd324dacf9f826f33409860074375be\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/birmachera/bitrise-step-create-zip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The path of the directory which you want to compress with zip.\n    is_expand: true\n    is_required: true\n    summary: The path of the directory which you want to compress with zip.\n    title: Source directory path\n    value_options: []\n  source_path: null\n- destination: null\n  opts:\n    description: |\n      The path where you want to move the compressed file.\n\n      Can be a direcory or the archive path.\n\n      The `.zip` extension will be added automatically if it was omitted.\n    is_expand: true\n    is_required: true\n    summary: The path where you want to move the compressed file.\n    title: Target directory path\n    value_options: []\n"
  },
  {
    "path": "steps/create-zip/0.9.2/step.yml",
    "content": "title: Create ZIP\nsummary: Creates a ZIP from the given file/dir to the given destination.\ndescription: \"It stores symlinks as symlinks (it will not copy the file which the\n  symlink is pointing to).\\n\\n### Configuring the Step\\n\\n1. In the **Source directory**\n  path, provide the directory you want to compress.          \\n2. In the **Target\n  directory path** input, you can select where to output the compressed file. \\n\\n###\n  Troubleshooting\\n\\nIf the **Source directory** path does not exist, there will be\n  an error.\\nIf the folder structure belonging to the destination does not exist,\n  you will be notified with a warning in the log and then the Step will create it.\\nIf\n  a ZIP exists on the specified destination, the user will be notified with a warning\n  in the log and then the previous file will be overwritten.\\n\\n### Related Steps\\n\\n\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-create-zip\nsource_code_url: https://github.com/bitrise-steplib/steps-create-zip\nsupport_url: https://github.com/bitrise-steplib/steps-create-zip\npublished_at: 2020-11-19T17:21:33.355606447Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-zip.git\n  commit: ae17119fbd6676f0a17436ae1eb8de69c4d164f3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/birmachera/bitrise-step-create-zip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The path of the directory which you want to compress with zip.\n    is_expand: true\n    is_required: true\n    summary: The path of the directory which you want to compress with zip.\n    title: Source directory path\n    value_options: []\n  source_path: null\n- destination: null\n  opts:\n    description: |\n      The path where you want to move the compressed file.\n\n      Can be a direcory or the archive path.\n\n      The `.zip` extension will be added automatically if it was omitted.\n    is_expand: true\n    is_required: true\n    summary: The path where you want to move the compressed file.\n    title: Target directory path\n    value_options: []\n"
  },
  {
    "path": "steps/create-zip/1.0.0/step.yml",
    "content": "title: Create ZIP\nsummary: Creates a ZIP from the given file/dir to the given destination.\ndescription: |-\n  It stores symlinks as symlinks (it will not copy the file which the symlink is pointing to).\n\n  ### Configuring the Step\n\n  1. In the **Source directory** path, provide the directory you want to compress.\n  2. In the **Target directory path** input, you can select where to output the compressed file.\n\n  ### Troubleshooting\n\n  If the **Source directory** path does not exist, there will be an error.\n  If the folder structure belonging to the destination does not exist, you will be notified with a warning in the log and then the Step will create it.\n  If a ZIP exists on the specified destination, the user will be notified with a warning in the log and then the previous file will be overwritten.\n\n  ### Related Steps\n\n   - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-create-zip\nsource_code_url: https://github.com/bitrise-steplib/steps-create-zip\nsupport_url: https://github.com/bitrise-steplib/steps-create-zip\npublished_at: 2026-05-11T19:24:40.98606668Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-create-zip.git\n  commit: a1eb897a310f28e875d657f87d7c5ca06b2ca914\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/create-zip/1.0.0/bin/create-zip-darwin-amd64\n    hash: sha256-74103124f28ea85be710e5393be4d34209465fde69ab7de2acfd2761f1cc6f96\n  darwin-arm64:\n    storage_uri: steps/create-zip/1.0.0/bin/create-zip-darwin-arm64\n    hash: sha256-79d43f20ebeaa91b444a55f48eadf4b8b84b026e9a502c5a09f5b04519bfe43d\n  linux-amd64:\n    storage_uri: steps/create-zip/1.0.0/bin/create-zip-linux-amd64\n    hash: sha256-943df4f8d776375f7812005d67b78d0bb50041b64b87ced8dc3cbfdaca5d9dac\n  linux-arm64:\n    storage_uri: steps/create-zip/1.0.0/bin/create-zip-linux-arm64\n    hash: sha256-7ed2f6148744eaee1791c04564689342241654238711d0995434ab57ef5697fb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-create-zip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The path of the directory which you want to compress with zip.\n    is_expand: true\n    is_required: true\n    summary: The path of the directory which you want to compress with zip.\n    title: Source directory path\n    value_options: []\n  source_path: null\n- destination: null\n  opts:\n    description: |\n      The path where you want to move the compressed file.\n\n      Can be a direcory or the archive path.\n\n      The `.zip` extension will be added automatically if it was omitted.\n    is_expand: true\n    is_required: true\n    summary: The path where you want to move the compressed file.\n    title: Target directory path\n    value_options: []\noutputs:\n- BITRISE_ZIP_PATH: null\n  opts:\n    description: |-\n      Absolute path of the ZIP file produced by the Step.\n\n      This is the destination path after any normalization the Step applies,\n      such as appending `.zip` when omitted or joining the source's basename\n      when the destination is an existing directory.\n    summary: Absolute path of the ZIP file produced by the Step.\n    title: Path of the created ZIP archive\n"
  },
  {
    "path": "steps/create-zip/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/curl-ping/2.0.0/step.yml",
    "content": "title: Ping an URL with cURL\ndescription: |-\n  Performs a [cURL](http://curl.haxx.se/) request on the given URL\n  and reports the result (success / failed) of the response.\nsummary: Ping an URL using cURL. You can also add optional parameters.\nwebsite: https://github.com/bitrise-io/steps-curl-ping\nsource_code_url: https://github.com/bitrise-io/steps-curl-ping\nsupport_url: https://github.com/bitrise-io/steps-curl-ping/issues\npublished_at: 2015-09-07T14:02:39.346943329+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-curl-ping.git\n  commit: 026f81518c50ca68323212f9029f2cf24ba2a58a\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Full URL\n  ping_url: \"\"\n- curl_params: \"\"\n  opts:\n    description: 'cURL parameters (like: `-dx ''key=some_data''`)'\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: (optional) cURL parameters\n"
  },
  {
    "path": "steps/curl-ping/2.0.1/step.yml",
    "content": "title: Ping an URL with cURL\nsummary: Ping an URL using cURL. You can also add optional parameters.\ndescription: |-\n  Performs a [cURL](http://curl.haxx.se/) request on the given URL\n  and reports the result (success/failed) of the response.\nwebsite: https://github.com/bitrise-steplib/steps-curl-ping\nsource_code_url: https://github.com/bitrise-steplib/steps-curl-ping\nsupport_url: https://github.com/bitrise-steplib/steps-curl-ping/issues\npublished_at: 2020-10-01T07:52:25.283285964Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-curl-ping.git\n  commit: c18362a18872573b2f8308d4fddf44b2bb401a37\nhost_os_tags:\n- osx-10.9\nproject_type_tags:\n- web\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Full URL\n  ping_url: \"\"\n- curl_params: \"\"\n  opts:\n    description: 'cURL parameters (like: `-dx ''key=some_data''`)'\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: (optional) cURL parameters\n"
  },
  {
    "path": "steps/curl-ping/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/custom-test-results-export/0.1.0/step.yml",
    "content": "title: Custom Test Results Export\nsummary: |\n  This step is used to search for test results and to export them for the 'Deploy to Bitrise.io' step. The deploy step can then be used to pick up results and import them into the testing add-on.\ndescription: |\n  This step is used to search for test results and to export them for the 'Deploy to Bitrise.io' step. The deploy step can then be used to pick up results and import them into the testing add-on.\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2020-03-11T09:54:38.980754129Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: 59c19f05b12a19937aec96c0569e85ded711b0c8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed on the tab of the Test Reports page.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path where the custom test results reside, you can provide a file path\n      or a directory path and filter for files using a pattern\n    title: Path where custom test results reside\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the step will produce a warning displaying all matches.\n      The matched file should be in a supported format.\n    is_expand: true\n    is_required: true\n    summary: A glob used to match a single test report.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/0.1.1/step.yml",
    "content": "title: Export test results to the Test Reports add-on\nsummary: |\n  This Step is used to search for test results and export them for the **Deploy to Bitrise.io** Step which can export the results to the testing add-on.\ndescription: \"Not all testing Steps automatically export their results to the Test\n  Reports add-on. This Step is designed to export the results of those Steps that\n  do not do this automatically. The Step creates the required `test-info.json` file\n  and deploys the test results in the correct directory for export.\\n\\n### Configuring\n  the Step\\n\\nTo use this Step to export the results of a testing Step - for example,\n  **Flutter Test** -, you need to make sure that:\\n\\n- The Step knows which folder\n  to look for your test results.\\n- The Step knows which file to look for.\\n- The\n  Step exports to the correct directory.\\n\\n1. In the **The name of the test** input,\n  set the name you want to be shown in the Test Reports add-on.\\n\\n1. In the **Path\n  where custom test results reside** input, set the path where your test results can\n  be found.\\n\\n   This input determines where Bitrise will look for your test results.\n  We recommend setting a folder here though you can also set a specific filepath.\\n\\n1.\n  In the **Test result search pattern** input, set a pattern that matches a single\n  test result output file.  \\n\\n   This search pattern is used to search every file\n  and folder of the provided base path which was set in the Path where custom test\n  results reside input. If there is more than one match, you will receive a warning.\\n\\n\n  \\  If you set a specific filepath in the previous input, just set * here.\\n\\n1.\n  In the **Step's test result directory** input, make sure the path is correct.\\n\\n\n  \\  By default, do NOT modify this input’s value. It should be set to the $BITRISE_TEST_RESULT_DIR\n  Env Var.\\n\\n1. Make sure you have a Deploy to Bitrise.io Step in your Workflow.\\n\\n###\n  Troubleshooting\\n\\n- You always need a **Deploy to Bitrise.io** Step in your Workflow\n  to export test results to the Test Reports add-on. If you can't see your results\n  in Test Reports, check that you have the Step in your Workflow.\\n\\n- If more than\n  one file matches the pattern set in the **Test result search pattern** input, you\n  will receive a warning. It should only match a single file in the base path.\\n\\n-\n  If either the **Path where custom test results reside** input or the **Test result\n  search pattern** input isn't set correctly or if either is left empty, the Step\n  will fail.\\n\\n### Useful links\\n\\n[Test reports](https://devcenter.bitrise.io/testing/test-reports/)\\n[Exporting\n  custom tests to test reports](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\\n\\n###\n  Related Steps\\n\\n[Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\\n\"\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2020-05-08T14:49:17.468622626Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: 3989d5ec33d7d9c7871b27c62d877ef67df75118\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed on the tab of the Test Reports page.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: \"\\\"This is the base path where the Step will look for your test results.\n      We recommend using a relative path to the results:\\n\\n`app/build/test-results/testDemoDebugUnitTest/`\\n\\nor\n      \\n\\n`./app/build/test-results/testDemoDebugUnitTest/`\\n\"\n    is_expand: true\n    is_required: true\n    summary: Path where the custom test results reside. You can provide a file path\n      or a directory path and filter for files using a pattern.\n    title: Path where custom test results reside\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the Step will produce a warning displaying all matches.\n      The matched file should be in a supported format. If you set a specific file path in the **Path where custom test results reside** input, set this value to *.\n\n      **Examples**:\n\n      Matching all files within the base path: `*`\n\n      Matching all files within a given directory of the base path: `*/build/test-results/testDemoDebugUnitTest/*`\n    is_expand: true\n    is_required: true\n    summary: A glob used to match a single test report.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/0.1.2/step.yml",
    "content": "title: Export test results to the Test Reports add-on\nsummary: |\n  This Step is used to search for test results and export them for the **Deploy to Bitrise.io** Step which can export the results to the testing add-on.\ndescription: \"Not all testing Steps automatically export their results to the Test\n  Reports add-on. This Step is designed to export the results of those Steps that\n  do not do this automatically. The Step creates the required `test-info.json` file\n  and deploys the test results in the correct directory for export.\\n\\n### Configuring\n  the Step\\n\\nTo use this Step to export the results of a testing Step - for example,\n  **Flutter Test** -, you need to make sure that:\\n\\n- The Step knows which folder\n  to look for your test results.\\n- The Step knows which file to look for.\\n- The\n  Step exports to the correct directory.\\n\\n1. In the **The name of the test** input,\n  set the name you want to be shown in the Test Reports add-on.\\n\\n1. In the **Path\n  where custom test results reside** input, set the path where your test results can\n  be found.\\n\\n   This input determines where Bitrise will look for your test results.\n  We recommend setting a folder here though you can also set a specific filepath.\\n\\n1.\n  In the **Test result search pattern** input, set a pattern that matches a single\n  test result output file.  \\n\\n   This search pattern is used to search every file\n  and folder of the provided base path which was set in the Path where custom test\n  results reside input. If there is more than one match, you will receive a warning.\\n\\n\n  \\  If you set a specific filepath in the previous input, just set * here.\\n\\n1.\n  In the **Step's test result directory** input, make sure the path is correct.\\n\\n\n  \\  By default, do NOT modify this input’s value. It should be set to the $BITRISE_TEST_RESULT_DIR\n  Env Var.\\n\\n1. Make sure you have a Deploy to Bitrise.io Step in your Workflow.\\n\\n###\n  Troubleshooting\\n\\n- You always need a **Deploy to Bitrise.io** Step in your Workflow\n  to export test results to the Test Reports add-on. If you can't see your results\n  in Test Reports, check that you have the Step in your Workflow.\\n\\n- If more than\n  one file matches the pattern set in the **Test result search pattern** input, you\n  will receive a warning. It should only match a single file in the base path.\\n\\n-\n  If either the **Path where custom test results reside** input or the **Test result\n  search pattern** input isn't set correctly or if either is left empty, the Step\n  will fail.\\n\\n### Useful links\\n\\n[Test reports](https://devcenter.bitrise.io/testing/test-reports/)\\n[Exporting\n  custom tests to test reports](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\\n\\n###\n  Related Steps\\n\\n[Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\\n\"\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2020-06-08T11:07:21.997403641Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: 7b3a3875969bb7b4f3c90e4aa6fb8b6684569811\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed on the tab of the Test Reports page.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: \"\\\"This is the base path where the Step will look for your test results.\n      We recommend using a relative path to the results:\\n\\n`app/build/test-results/testDemoDebugUnitTest/`\\n\\nor\n      \\n\\n`./app/build/test-results/testDemoDebugUnitTest/`\\n\"\n    is_expand: true\n    is_required: true\n    summary: Path where the custom test results reside. You can provide a file path\n      or a directory path and filter for files using a pattern.\n    title: Path where custom test results reside\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the Step will produce a warning displaying all matches.\n      The matched file should be in a supported format. If you set a specific file path in the **Path where custom test results reside** input, set this value to *.\n\n      **Examples**:\n\n      Matching all files within the base path: `*`\n\n      Matching all files within a given directory of the base path: `*/build/test-results/testDemoDebugUnitTest/*`\n    is_expand: true\n    is_required: true\n    summary: A glob used to match a single test report.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/0.1.3/step.yml",
    "content": "title: Export test results to Test Reports add-on\nsummary: |\n  This Step is used to search for test results and export them for the **Deploy to Bitrise.io** Step which can export the results to the testing add-on.\ndescription: |\n  Not all testing Steps automatically export their results to the Test Reports add-on. This Step is designed to export the results of those Steps that do not do this automatically. The Step creates the required `test-info.json` file and deploys the test results in the correct directory for export.\n\n  ### Configuring the Step\n\n  To use this Step to export the results of a testing Step - for example, **Flutter Test** -, you need to make sure that:\n\n  - The Step knows which folder to look for your test results.\n  - The Step knows which file to look for.\n  - The Step exports to the correct directory.\n\n  1. In the **The name of the test** input, set the name you want to see in the Test Reports add-on. Each exported results file has a separate tab with the name defined here.\n\n  2. In the **Test result base path** input, set the path where your test results can be found.\n\n     This input determines where Bitrise will look for your test results. We recommend setting a folder here, though you can also set a specific file path.\n\n  3. In the **Test result search pattern** input, set a glob pattern that matches a single test result output file.\n\n     This search pattern is used to search every file and folder of the provided base path which was set in the **Test result base path** input. If there is more than one match, you will receive a warning and the Step will export the first match.\n\n     If you set a specific file path in the previous input, just set `*` here.\n\n  4. In the **Step's test result directory** input, make sure the path points to a valid directory.\n\n     By default, do NOT modify this input’s value. It should be set to the $BITRISE_TEST_RESULT_DIR Env Var.\n\n  5. Make sure you have a Deploy to Bitrise.io Step in your Workflow. This step is responsible for deploying the exported files from the test result directory to the Test Reports add-on.\n\n  ### Troubleshooting\n\n  - You always need a **Deploy to Bitrise.io** Step in your Workflow to export test results to the Test Reports add-on. If you can't see your results in Test Reports, check that you have the Step in your Workflow.\n\n  - If more than one file matches the pattern set in the **Test result search pattern** input, you will receive a warning. It should only match a single file in the base path.\n\n  - If either the **Test result base path** input or the **Test result search pattern** input isn't set correctly or if either is left empty, the Step will fail.\n\n  ### Useful links\n\n  [Test reports](https://devcenter.bitrise.io/testing/test-reports/)\n  [Exporting custom tests to test reports](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\n\n  ### Related Steps\n\n  [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2021-04-19T12:27:14.270437228Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: dbb4443c557dae5db1315ca25bed24f89924609e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed on the tab of the Test Reports page.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: \"You can provide a path to a single file or a directory path and\n      filter for files using the **Test result search pattern** input.\\n\\nThis is\n      the base path where the Step will look for your test results. We recommend using\n      a relative path to the results:\\n\\n`app/build/test-results/testDemoDebugUnitTest/`\\n\\nor\n      \\n\\n`./app/build/test-results/testDemoDebugUnitTest/`\\n\"\n    is_expand: true\n    is_required: true\n    summary: Path where the Step should look for custom test result files\n    title: Test result base path\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the Step will produce a warning displaying all matches.\n      The matched file should be in a supported format. If you set a specific file path in the **Test result base path** input, set this value to `*`.\n\n      **Examples**:\n\n      Matching all files within the base path: `*`\n\n      Matching all files within a given directory of the base path: `*/build/test-results/testDemoDebugUnitTest/*`\n    is_expand: true\n    is_required: true\n    summary: A glob pattern to match a single test report within the base path.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/1.0.0/step.yml",
    "content": "title: Export test results to Test Reports add-on\nsummary: |\n  This Step is used to search for test results and export them for the **Deploy to Bitrise.io** Step which can export the results to the testing add-on.\ndescription: |\n  Not all testing Steps automatically export their results to the Test Reports add-on. This Step is designed to export the results of those Steps that do not do this automatically. The Step creates the required `test-info.json` file and deploys the test results in the correct directory for export.\n\n  ### Configuring the Step\n\n  To use this Step to export the results of a testing Step - for example, **Flutter Test** -, you need to make sure that:\n\n  - The Step knows which folder to look for your test results.\n  - The Step knows which file to look for.\n  - The Step exports to the correct directory.\n\n  1. In the **The name of the test** input, set the name you want to see in the Test Reports add-on. Each exported results file has a separate tab with the name defined here.\n\n  2. In the **Test result base path** input, set the path where your test results can be found.\n\n     This input determines where Bitrise will look for your test results. We recommend setting a folder here, though you can also set a specific file path.\n\n  3. In the **Test result search pattern** input, set a glob pattern that matches a single test result output file.\n\n     This search pattern is used to search every file and folder of the provided base path which was set in the **Test result base path** input. If there is more than one match, you will receive a warning and the Step will export the first match.\n\n     If you set a specific file path in the previous input, just set `*` here.\n\n  4. In the **Step's test result directory** input, make sure the path points to a valid directory.\n\n     By default, do NOT modify this input’s value. It should be set to the $BITRISE_TEST_RESULT_DIR Env Var.\n\n  5. Make sure you have a Deploy to Bitrise.io Step in your Workflow. This step is responsible for deploying the exported files from the test result directory to the Test Reports add-on.\n\n  ### Troubleshooting\n\n  - You always need a **Deploy to Bitrise.io** Step in your Workflow to export test results to the Test Reports add-on. If you can't see your results in Test Reports, check that you have the Step in your Workflow.\n\n  - If more than one file matches the pattern set in the **Test result search pattern** input, you will receive a warning. It should only match a single file in the base path.\n\n  - If either the **Test result base path** input or the **Test result search pattern** input isn't set correctly or if either is left empty, the Step will fail.\n\n  ### Useful links\n\n  [Test reports](https://devcenter.bitrise.io/testing/test-reports/)\n  [Exporting custom tests to test reports](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\n\n  ### Related Steps\n\n  [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2023-03-16T09:03:46.097400055Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: e72ec7d396caac34d962241a776931ca8c1951f0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed on the tab of the Test Reports page.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: |\n      You can provide a path to a single file or a directory path and filter for files using the **Test result search pattern** input.\n\n      This is the base path where the Step will look for your test results. We recommend using a relative path to the results:\n\n      `app/build/test-results/testDemoDebugUnitTest/`\n\n      or\n\n      `./app/build/test-results/testDemoDebugUnitTest/`\n    is_expand: true\n    is_required: true\n    summary: Path where the Step should look for custom test result files\n    title: Test result base path\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the Step will produce a warning displaying all matches.\n      The matched file should be in a supported format. If you set a specific file path in the **Test result base path** input, set this value to `*`.\n\n      **Examples**:\n\n      Matching all files within the base path: `*`\n\n      Matching all files within a given directory of the base path: `*/build/test-results/testDemoDebugUnitTest/*`\n    is_expand: true\n    is_required: true\n    summary: A glob pattern to match a single test report within the base path.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/1.0.1/step.yml",
    "content": "title: Export test results to Test Reports\nsummary: |\n  This Step is used to search for test results and export them for the **Deploy to Bitrise.io** Step which can export the results to the Test Reports.\ndescription: |\n  Not all testing Steps automatically export their results to the Test Reports. This Step is designed to export the results of those Steps that do not do this automatically. The Step creates the required `test-info.json` file and deploys the test results in the correct directory for export.\n\n  ### Configuring the Step\n\n  To use this Step to export the results of a testing Step - for example, **Flutter Test** -, you need to make sure that:\n\n  - The Step knows which folder to look for your test results.\n  - The Step knows which file to look for.\n  - The Step exports to the correct directory.\n\n  1. In the **The name of the test** input, set the name you want to see in the Test Reports. Each exported results file has a separate tab with the name defined here.\n\n  2. In the **Test result base path** input, set the path where your test results can be found.\n\n     This input determines where Bitrise will look for your test results. We recommend setting a folder here, though you can also set a specific file path.\n\n  3. In the **Test result search pattern** input, set a glob pattern that matches a single test result output file.\n\n     This search pattern is used to search every file and folder of the provided base path which was set in the **Test result base path** input. If there is more than one match, you will receive a warning and the Step will export the first match.\n\n     If you set a specific file path in the previous input, just set `*` here.\n\n  4. In the **Step's test result directory** input, make sure the path points to a valid directory.\n\n     By default, do NOT modify this input’s value. It should be set to the $BITRISE_TEST_RESULT_DIR Env Var.\n\n  5. Make sure you have a Deploy to Bitrise.io Step in your Workflow. This step is responsible for deploying the exported files from the test result directory to the Test Reports.\n\n  ### Troubleshooting\n\n  - You always need a **Deploy to Bitrise.io** Step in your Workflow to export test results to the Test Reports. If you can't see your results in Test Reports, check that you have the Step in your Workflow.\n\n  - If more than one file matches the pattern set in the **Test result search pattern** input, you will receive a warning. It should only match a single file in the base path.\n\n  - If either the **Test result base path** input or the **Test result search pattern** input isn't set correctly or if either is left empty, the Step will fail.\n\n  ### Useful links\n\n  [Test reports](https://devcenter.bitrise.io/testing/test-reports/)\n  [Exporting custom tests to test reports](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\n\n  ### Related Steps\n\n  [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2025-10-21T12:54:21.327135102Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: 2c4ed39819fb1eb41400d267e545097c7b65a465\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed in the Test Reports.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: |\n      You can provide a path to a single file or a directory path and filter for files using the **Test result search pattern** input.\n\n      This is the base path where the Step will look for your test results. We recommend using a relative path to the results:\n\n      `app/build/test-results/testDemoDebugUnitTest/`\n\n      or\n\n      `./app/build/test-results/testDemoDebugUnitTest/`\n    is_expand: true\n    is_required: true\n    summary: Path where the Step should look for custom test result files\n    title: Test result base path\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the Step will produce a warning displaying all matches.\n      The matched file should be in a supported format. If you set a specific file path in the **Test result base path** input, set this value to `*`.\n\n      **Examples**:\n\n      Matching all files within the base path: `*`\n\n      Matching all files within a given directory of the base path: `*/build/test-results/testDemoDebugUnitTest/*`\n    is_expand: true\n    is_required: true\n    summary: A glob pattern to match a single test report within the base path.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/1.1.0/step.yml",
    "content": "title: Export test results to Test Reports\nsummary: |\n  This Step is used to search for test results and export them for the **Deploy to Bitrise.io** Step which can export the results to the Test Reports.\ndescription: |\n  Not all testing Steps automatically export their results to the Test Reports. This Step is designed to export the results of those Steps that do not do this automatically. The Step creates the required `test-info.json` file and deploys the test results in the correct directory for export.\n\n  ### Configuring the Step\n\n  To use this Step to export the results of a testing Step - for example, **Flutter Test** -, you need to make sure that:\n\n  - The Step knows which folder to look for your test results.\n  - The Step knows which file to look for.\n  - The Step exports to the correct directory.\n\n  1. In the **The name of the test** input, set the name you want to see in the Test Reports. Each exported results file has a separate tab with the name defined here.\n\n  2. In the **Test result base path** input, set the path where your test results can be found.\n\n     This input determines where Bitrise will look for your test results. We recommend setting a folder here, though you can also set a specific file path.\n\n  3. In the **Test result search pattern** input, set a glob pattern that matches a single test result output file.\n\n     This search pattern is used to search every file and folder of the provided base path which was set in the **Test result base path** input. If there is more than one match, you will receive a warning and the Step will export the first match.\n\n     If you set a specific file path in the previous input, just set `*` here.\n\n  4. In the **Step's test result directory** input, make sure the path points to a valid directory.\n\n     By default, do NOT modify this input’s value. It should be set to the $BITRISE_TEST_RESULT_DIR Env Var.\n\n  5. Make sure you have a Deploy to Bitrise.io Step in your Workflow. This step is responsible for deploying the exported files from the test result directory to the Test Reports.\n\n  ### Troubleshooting\n\n  - You always need a **Deploy to Bitrise.io** Step in your Workflow to export test results to the Test Reports. If you can't see your results in Test Reports, check that you have the Step in your Workflow.\n\n  - If more than one file matches the pattern set in the **Test result search pattern** input, you will receive a warning. It should only match a single file in the base path.\n\n  - If either the **Test result base path** input or the **Test result search pattern** input isn't set correctly or if either is left empty, the Step will fail.\n\n  ### Useful links\n\n  [Test reports](https://devcenter.bitrise.io/testing/test-reports/)\n  [Exporting custom tests to test reports](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\n\n  ### Related Steps\n\n  [Android Unit Test](https://www.bitrise.io/integrations/steps/android-unit-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/step-custom-test-results-export\nsource_code_url: https://github.com/bitrise-steplib/step-custom-test-results-export\nsupport_url: https://github.com/bitrise-steplib/step-custom-test-results-export/issues\npublished_at: 2025-11-10T13:47:29.357375665Z\nsource:\n  git: https://github.com/bitrise-steplib/step-custom-test-results-export.git\n  commit: f5231d7e29d2b8de93ac642f56800ccf2882f103\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/step-custom-test-results-export\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Test name displayed in the Test Reports.\n    title: The name of the test\n    value_options: []\n  test_name: null\n- base_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: |\n      You can provide a path to a single file or a directory path and filter for files using the **Test result search pattern** input.\n\n      This is the base path where the Step will look for your test results. We recommend using a relative path to the results:\n\n      `app/build/test-results/testDemoDebugUnitTest/`\n\n      or\n\n      `./app/build/test-results/testDemoDebugUnitTest/`\n    is_expand: true\n    is_required: true\n    summary: Path where the Step should look for custom test result files\n    title: Test result base path\n    value_options: []\n- opts:\n    description: |\n      This glob should match a single file within the provided base path.\n      If it matches multiple files, the Step will produce a warning displaying all matches.\n      The matched file should be in a supported format. If you set a specific file path in the **Test result base path** input, set this value to `*`.\n\n      **Examples**:\n\n      Matching all files within the base path: `*`\n\n      Matching all files within a given directory of the base path: `*/build/test-results/testDemoDebugUnitTest/*`\n    is_expand: true\n    is_required: true\n    summary: A glob pattern to match a single test report within the base path.\n    title: Test result search pattern\n    value_options: []\n  search_pattern: null\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_required: true\n    title: Step's test result directory\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/custom-test-results-export/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/danger/0.1.1/step.yml",
    "content": "title: Run Danger\nsummary: Danger runs during your CI process, and gives teams the chance to automate\n  common code review chores.\ndescription: |\n  Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2019-04-15T08:32:36.793283646Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: 40ac26847b467272e60026748630a1e162413e0a\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: Github\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: Github\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise Github**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise Github**.\n    title: Github host\n- github_api_base_url: null\n  opts:\n    category: Github\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise Github**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise Github**.\n    title: Github API base URL\n- gitlab_api_token: null\n  opts:\n    category: Gitlab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      **NOTE:** You can read more about it:\n\n      [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: Gitlab\n    description: |-\n      The host that Gitlab is running on. You need to set this if you are using **Self Hosted Gitlab**.\n      You can work with Self Hosted Gitlab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that Gitlab is running on. You need to set this if you are using\n      **Self Hosted Gitlab**.\n    title: Gitlab host\n- gitlab_api_base_url: null\n  opts:\n    category: Gitlab\n    description: |-\n      The host that the Self Hosted Gitlab API is reachable on. You need to set this if you are using **Self Hosted Gitlab**.\n      You can work with Self Hosted Gitlab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self Hosted Gitlab API is reachable on. You need to\n      set this if you are using **Self Hosted Gitlab**.\n    title: Gitlab API base URL\n"
  },
  {
    "path": "steps/danger/1.0.0/step.yml",
    "content": "title: Run Danger\nsummary: Danger runs during your CI process, and gives teams the chance to automate\n  common code review chores.\ndescription: |\n  Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2019-09-19T07:43:58.944313965Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: 4a5c307120be154bea78e294ec655da5713c785f\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: GitHub\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise GitHub**.\n    title: GitHub host\n- github_api_base_url: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise GitHub**.\n    title: GitHub API base URL\n- gitlab_api_token: null\n  opts:\n    category: GitLab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      **NOTE:** You can read more about it:\n\n      [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that GitLab is running on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitLab is running on. You need to set this if you are using\n      **Self-Managed GitLab**.\n    title: GitLab host\n- gitlab_api_base_url: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that the Self-Managed GitLab API is reachable on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self-Managed GitLab API is reachable on. You need to\n      set this if you are using **Self-Managed GitLab**.\n    title: GitLab API base URL\n"
  },
  {
    "path": "steps/danger/1.1.0/step.yml",
    "content": "title: Run Danger\nsummary: Danger runs during your CI process, and gives teams the chance to automate\n  common code review chores.\ndescription: |\n  Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2019-10-17T13:32:59.132310278Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: c7daf33762a36c3e91d856945273f72b428cde53\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: GitHub\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise GitHub**.\n    title: GitHub host\n- github_api_base_url: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise GitHub**.\n    title: GitHub API base URL\n- gitlab_api_token: null\n  opts:\n    category: GitLab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      **NOTE:** You can read more about it:\n\n      [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that GitLab is running on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitLab is running on. You need to set this if you are using\n      **Self-Managed GitLab**.\n    title: GitLab host\n- gitlab_api_base_url: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that the Self-Managed GitLab API is reachable on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self-Managed GitLab API is reachable on. You need to\n      set this if you are using **Self-Managed GitLab**.\n    title: GitLab API base URL\n"
  },
  {
    "path": "steps/danger/2.0.0/step.yml",
    "content": "title: Run Danger\nsummary: Danger runs during your CI process, and gives teams the chance to automate\n  common code review chores.\ndescription: |\n  Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2020-02-20T08:50:44.145352554Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: 6221079c49ddef24d93b453f928e1ef4acf21d04\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: GitHub\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise GitHub**.\n    title: GitHub host\n- github_api_base_url: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise GitHub**.\n    title: GitHub API base URL\n- gitlab_api_token: null\n  opts:\n    category: GitLab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      **NOTE:** You can read more about it:\n\n      [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that GitLab is running on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitLab is running on. You need to set this if you are using\n      **Self-Managed GitLab**.\n    title: GitLab host\n- gitlab_api_base_url: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that the Self-Managed GitLab API is reachable on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self-Managed GitLab API is reachable on. You need to\n      set this if you are using **Self-Managed GitLab**.\n    title: GitLab API base URL\n- additional_options: --fail-on-errors=true\n  opts:\n    description: |-\n      Additional commands and options to append to the danger command call. The provided value will be appended to\n      the `bundle exec danger` command call, as is.\n    summary: Additional commands and options to append to the danger command call\n    title: Additional options for the command call\n"
  },
  {
    "path": "steps/danger/2.0.1/step.yml",
    "content": "title: Run Danger\nsummary: Danger runs during your CI process, and gives teams the chance to automate\n  common code review chores.\ndescription: |\n  Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2020-09-01T11:33:53.386113213Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: bcbb80b5779e0cc5832af1ef0e281f6873735e50\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: GitHub\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise GitHub**.\n    title: GitHub host\n- github_api_base_url: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise GitHub**.\n    title: GitHub API base URL\n- gitlab_api_token: null\n  opts:\n    category: GitLab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      **NOTE:** You can read more about it:\n\n      [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that GitLab is running on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitLab is running on. You need to set this if you are using\n      **Self-Managed GitLab**.\n    title: GitLab host\n- gitlab_api_base_url: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that the Self-Managed GitLab API is reachable on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self-Managed GitLab API is reachable on. You need to\n      set this if you are using **Self-Managed GitLab**.\n    title: GitLab API base URL\n- additional_options: --fail-on-errors=true\n  opts:\n    description: |-\n      Additional commands and options to append to the danger command call. The provided value will be appended to\n      the `bundle exec danger` command call, as is.\n    summary: Additional commands and options to append to the danger command call\n    title: Additional options for the command call\n"
  },
  {
    "path": "steps/danger/2.0.2/step.yml",
    "content": "title: Run Danger\nsummary: '[Danger](https://danger.systems/python/) automates common code review chores\n  during your CI process.'\ndescription: |-\n  If inserted in your Workflow on Bitrise, it runs the Danger CI to check any linting issues in your project's code.\n\n  ### Configuring the Step\n\n  1. The **Repository URL of your project** input is automatically filled out.\n  2. If you add any additional options in the **Additional options for the command call**, they will be added to your `bundle exec danger` command call.\n  3. Select a git provider's input section: GitHub or GitLab.\n  4. If you're using GitHub:\n  - Add your access token in the **Access token for your project** input. Click the input's description for more information on how to set up the access token.\n  - Add the host GitHub is running on, for example, `git.corp.evilcorp.com`. Read more about [how to set it up](https://danger.systems/guides/getting_started.html).\n  - Add the GitHub API Enterprise API URL in the **GitHub API base URL** input.\n  5. If you are using GitLab:\n  - Add your access token in the **Access token for your project** input. Click the input's description for more information on how to set up the access token.\n  - Add the host GitLab is running on in the **GitLab host** input. You must add this if you are using Self-Managed GitLab.\n  - Add the **GitLab API base URL**. You must add this if you are using Self-Managed GitLab.\n\n  ### Useful links\n  - [No activity summaries found for test with Danger](https://devcenter.bitrise.io/troubleshooting/no-activity-summaries-found-for-test-with-danger/#the-issue)\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2020-11-20T14:49:06.699834457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: 96a97cc16301fdab66ef45ef611b496cdc0125d2\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: GitHub\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise GitHub**.\n    title: GitHub host\n- github_api_base_url: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise GitHub**.\n    title: GitHub API base URL\n- gitlab_api_token: null\n  opts:\n    category: GitLab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      Find more information about Danger in their guides: [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that GitLab is running on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitLab is running on. You need to set this if you are using\n      **Self-Managed GitLab**.\n    title: GitLab host\n- gitlab_api_base_url: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that the Self-Managed GitLab API is reachable on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self-Managed GitLab API is reachable on. You need to\n      set this if you are using **Self-Managed GitLab**.\n    title: GitLab API base URL\n- additional_options: --fail-on-errors=true\n  opts:\n    description: |-\n      Additional commands and options to append to the danger command call. The provided value will be appended to\n      the `bundle exec danger` command call, as is.\n    summary: Additional commands and options to append to the danger command call\n    title: Additional options for the command call\n"
  },
  {
    "path": "steps/danger/2.0.3/step.yml",
    "content": "title: Run Danger\nsummary: '[Danger](https://danger.systems/python/) automates common code review chores\n  during your CI process.'\ndescription: |-\n  If inserted in your Workflow on Bitrise, it runs the Danger CI to check any linting issues in your project's code.\n\n  ### Configuring the Step\n\n  1. The **Repository URL of your project** input is automatically filled out.\n  2. If you add any additional options in the **Additional options for the command call**, they will be added to your `bundle exec danger` command call.\n  3. Select a git provider's input section: GitHub or GitLab.\n  4. If you're using GitHub:\n  - Add your access token in the **Access token for your project** input. Click the input's description for more information on how to set up the access token.\n  - Add the host GitHub is running on, for example, `git.corp.evilcorp.com`. Read more about [how to set it up](https://danger.systems/guides/getting_started.html).\n  - Add the GitHub API Enterprise API URL in the **GitHub API base URL** input.\n  5. If you are using GitLab:\n  - Add your access token in the **Access token for your project** input. Click the input's description for more information on how to set up the access token.\n  - Add the host GitLab is running on in the **GitLab host** input. You must add this if you are using Self-Managed GitLab.\n  - Add the **GitLab API base URL**. You must add this if you are using Self-Managed GitLab.\n\n  ### Useful links\n  - [No activity summaries found for test with Danger](https://devcenter.bitrise.io/troubleshooting/no-activity-summaries-found-for-test-with-danger/#the-issue)\nwebsite: https://github.com/bitrise-steplib/steps-danger\nsource_code_url: https://github.com/bitrise-steplib/steps-danger\nsupport_url: https://github.com/bitrise-steplib/steps-danger/issues\npublished_at: 2023-04-25T16:03:27.283094535Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-danger.git\n  commit: b6a648e32103943b95c4d727ae61646c23b00489\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-danger\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Repository URL of your project\n    title: Repository URL of your project\n  repository_url: $GIT_REPOSITORY_URL\n- github_api_token: null\n  opts:\n    category: GitHub\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      [Here’s the link](https://github.com/settings/tokens/new), you should open this in the private session where you just created the new GitHub account. Again, the rights that you give to the token depend on the openness of your projects. You’ll want to save for later, when you add a `github_api_token` to the step.\n\n      **TOKENS FOR OSS PROJECTS**\n\n      We recommend giving the token the smallest scope possible. This means just public\\_repo, this scopes limits Danger’s abilities to just writing comments on OSS projects. Because the token can be quite easily be extracted from the CI environment, this minimizes the chance for bad actors to cause chaos with it.\n\n      **TOKENS FOR CLOSED SOURCE PROJECTS**\n\n      We recommend giving access to the whole repo scope, and its children.\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- github_host: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that GitHub is running on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitHub is running on. You need to set this if you are using\n      **Enterprise GitHub**.\n    title: GitHub host\n- github_api_base_url: null\n  opts:\n    category: GitHub\n    description: |-\n      The host that the GitHub Enterprise API is reachable on. You need to set this if you are using **Enterprise GitHub**.\n      You can work with GitHub Enterprise by setting the `github_host` and the `github_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v3`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the GitHub Enterprise API is reachable on. You need to\n      set this if you are using **Enterprise GitHub**.\n    title: GitHub API base URL\n- gitlab_api_token: null\n  opts:\n    category: GitLab\n    description: |-\n      **SETTING UP AN ACCESS TOKEN**\n\n      Here’s the link, you should open this in the private session where you have just created the new GitLab account. You’ll want to copy the token for later, when you add a `gitlab_api_token` to the step.\n\n\n      If you are self hosting GitLab, you’ll need to generate an access token for the bot user. You can find the section under “Access Tokens” in the bot user’s profile.\n\n      Find more information about Danger in their guides: [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    is_sensitive: true\n    summary: Access token for your project\n    title: Access token for your project\n- gitlab_host: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that GitLab is running on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `git.corp.evilcorp.com`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that GitLab is running on. You need to set this if you are using\n      **Self-Managed GitLab**.\n    title: GitLab host\n- gitlab_api_base_url: null\n  opts:\n    category: GitLab\n    description: |-\n      The host that the Self-Managed GitLab API is reachable on. You need to set this if you are using **Self-Managed GitLab**.\n      You can work with Self-Managed GitLab by setting the `gitlab_host` and the `gitlab_api_base_url` inputs.\n\n      **For example:** `https://git.corp.evilcorp.com/api/v4`\n\n      **You can read more about it here:** [https://danger.systems/guides/getting_started.html](https://danger.systems/guides/getting_started.html)\n    summary: The host that the Self-Managed GitLab API is reachable on. You need to\n      set this if you are using **Self-Managed GitLab**.\n    title: GitLab API base URL\n- additional_options: --fail-on-errors=true\n  opts:\n    description: |-\n      Additional commands and options to append to the danger command call. The provided value will be appended to\n      the `bundle exec danger` command call, as is.\n    summary: Additional commands and options to append to the danger command call\n    title: Additional options for the command call\n"
  },
  {
    "path": "steps/danger/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/data-theorem-mobile-secure/0.0.1/step.yml",
    "content": "title: Data Theorem Mobile Secure\nsummary: |\n  Perform automated security analysis on every build.\ndescription: |\n  Data Theorem's Mobile Secure will scan each pre-production release automatically (up to 7000 releases/day)\n  for security & privacy issues using static, dynamic, and behavioral analysis for both iOS and Android applications.\n  More information can be found here: https://www.datatheorem.com/products/mobile-secure\n\n  Enabling this integration requires a valid Data Theorem API Key.\n  To find your API Key, connect to https://www.securetheorem.com/sdlc using your Data Theorem account.\nwebsite: https://www.datatheorem.com/products/mobile-secure\nsource_code_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\nsupport_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\npublished_at: 2021-01-29T20:44:54.044159663+01:00\nsource:\n  git: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\n  commit: b02bda458cf9729b789975a8cb7a8cf0ad13a4db\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      This variable can for example be set to:\n\n      $BITRISE\\_APK\\_PATH after the \"Android Build\" step\n      $BITRISE\\_APK\\_PATH or $BITRISE\\_SIGNED\\_APK\\_PATH after the \"Android Sign\" step\n\n      $BITRISE\\_IPA\\_PATH after the \"Xcode Archive & Export for iOS\" step\n    is_expand: true\n    is_required: true\n    summary: File path to the APK or IPA to upload\n    title: File path to the APK or IPA to upload\n    value_options: []\n- dt_api_upload_key: \"\"\n  opts:\n    description: |\n      Instruction to retreive your upload API key:\n      [https://datatheorem.atlassian.net/servicedesk/customer/portal/1/article/557063]\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Data Theorem Upload API Key\n    title: Data Theorem Upload API Key\n    value_options: []\n"
  },
  {
    "path": "steps/data-theorem-mobile-secure/1.0.0/step.yml",
    "content": "title: Data Theorem Mobile Secure\nsummary: |\n  Perform automated security analysis on every build.\ndescription: |\n  Data Theorem's Mobile Secure will scan each pre-production release automatically (up to 7000 releases/day)\n  for security & privacy issues using static, dynamic, and behavioral analysis for both iOS and Android applications.\n  More information can be found here: https://www.datatheorem.com/products/mobile-secure\n\n  Enabling this integration requires a valid Data Theorem API Key.\n  To find your API Key, connect to https://www.securetheorem.com/sdlc using your Data Theorem account.\nwebsite: https://www.datatheorem.com/products/mobile-secure\nsource_code_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\nsupport_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\npublished_at: 2021-08-05T10:39:30.5438758+02:00\nsource:\n  git: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\n  commit: 0c1bd932a8d579555ed5067fde1d158e1ef2fa77\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      This variable can for example be set to:\n\n      $BITRISE\\_APK\\_PATH after the \"Android Build\" step\n      $BITRISE\\_APK\\_PATH or $BITRISE\\_SIGNED\\_APK\\_PATH after the \"Android Sign\" step\n\n      $BITRISE\\_IPA\\_PATH after the \"Xcode Archive & Export for iOS\" step\n    is_expand: true\n    is_required: true\n    summary: File path to the APK or IPA to upload\n    title: File path to the APK or IPA to upload\n    value_options: []\n- dt_upload_api_key: \"\"\n  opts:\n    description: |\n      Instruction to retreive your upload API key:\n      [https://datatheorem.atlassian.net/servicedesk/customer/portal/1/article/557063]\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Data Theorem Upload API Key\n    title: Data Theorem Upload API Key\n    value_options: []\n"
  },
  {
    "path": "steps/data-theorem-mobile-secure/1.1.0/step.yml",
    "content": "title: Data Theorem Mobile Secure\nsummary: |\n  Perform automated security analysis on every build.\ndescription: |\n  Data Theorem's Mobile Secure will scan each pre-production release automatically (up to 7000 releases/day)\n  for security & privacy issues using static, dynamic, and behavioral analysis for both iOS and Android applications.\n  More information can be found here: https://www.datatheorem.com/products/mobile-secure\n\n  Enabling this integration requires a valid Data Theorem API Key.\n  To find your API Key, connect to https://www.securetheorem.com/sdlc using your Data Theorem account.\nwebsite: https://www.datatheorem.com/products/mobile-secure\nsource_code_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\nsupport_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\npublished_at: 2022-11-04T18:18:14.202720565+01:00\nsource:\n  git: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\n  commit: e486ac1676b6be38dd5ee87409933a28542e07d0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      This variable can for example be set to:\n\n      $BITRISE\\_APK\\_PATH after the \"Android Build\" step\n      $BITRISE\\_APK\\_PATH or $BITRISE\\_SIGNED\\_APK\\_PATH after the \"Android Sign\" step\n\n      $BITRISE\\_IPA\\_PATH after the \"Xcode Archive & Export for iOS\" step\n    is_expand: true\n    is_required: true\n    summary: File path to the APK or IPA to upload\n    title: File path to the APK or IPA to upload\n    value_options: []\n- dt_upload_api_key: \"\"\n  opts:\n    description: |\n      Instruction to retrieve your upload API key:\n      [https://datatheorem.atlassian.net/servicedesk/customer/portal/1/article/557063]\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Data Theorem Upload API Key\n    title: Data Theorem Upload API Key\n    value_options: []\n"
  },
  {
    "path": "steps/data-theorem-mobile-secure/1.2.0/step.yml",
    "content": "title: Data Theorem Mobile Secure\nsummary: |\n  Perform automated security analysis on every build.\ndescription: |\n  Data Theorem's Mobile Secure will scan each pre-production release automatically (up to 7000 releases/day)\n  for security & privacy issues using static, dynamic, and behavioral analysis for both iOS and Android applications.\n  More information can be found here: https://www.datatheorem.com/products/mobile-secure\n\n  Enabling this integration requires a valid Data Theorem API Key.\n  To find your API Key, connect to https://www.securetheorem.com/sdlc using your Data Theorem account.\nwebsite: https://www.datatheorem.com/products/mobile-secure\nsource_code_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\nsupport_url: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\npublished_at: 2023-07-19T16:09:42.419114+02:00\nsource:\n  git: https://bitbucket.org/datatheorem/dt-bitrise-integration.git\n  commit: cc77463e96a2228340b94ea8986542aba2749cd4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      This variable can for example be set to:\n\n      $BITRISE\\_APK\\_PATH after the \"Android Build\" step\n      $BITRISE\\_APK\\_PATH or $BITRISE\\_SIGNED\\_APK\\_PATH after the \"Android Sign\" step\n\n      $BITRISE\\_IPA\\_PATH after the \"Xcode Archive & Export for iOS\" step\n    is_expand: true\n    is_required: true\n    summary: File path to the APK or IPA to upload\n    title: File path to the APK or IPA to upload\n    value_options: []\n- dt_upload_api_key: \"\"\n  opts:\n    description: |\n      Instruction to retrieve your upload API key:\n      [https://datatheorem.atlassian.net/servicedesk/customer/portal/1/article/557063]\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Data Theorem Upload API Key\n    title: Data Theorem Upload API Key\n    value_options: []\n- opts:\n    description: |\n      An optional Java mapping.txt file for deobfuscating Android binaries.\n    is_expand: true\n    is_required: false\n    skip_if_empty: true\n    summary: Mapping file for deobfuscating Android binaries\n    title: Android mapping file\n    value_options: []\n  sourcemap: \"\"\n"
  },
  {
    "path": "steps/data-theorem-mobile-secure/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/decrypt-file/0.9.0/step.yml",
    "content": "title: Decrypt file\nsummary: This step decrypts a file encrypted with `gpg`, using the default AES128\n  symmetric cypher.\ndescription: |\n  You can use this step to decrypt a file.\n\n  How to create an encrypted file:\n\n  1. Create a secure passphrase of at least 22 alphanumeric characters: `pwgen -s 22 1`\n  2. Encrypt the file: `gpg -c my_secret.txt`\nwebsite: https://github.com/bitrise-steplib/bitrise-step-decrypt-file\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-decrypt-file\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-decrypt-file/issues\npublished_at: 2018-11-20T09:36:17.79758689Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-decrypt-file.git\n  commit: 07216d3f4dcaa15517716dcd7659fa361865f40a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-decrypt-file\ndeps:\n  brew:\n  - name: gpg\n  apt_get:\n  - name: gpg\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- decrypt_passphrase: null\n  opts:\n    description: |\n      The passphrase is used as a parameter for gpg.\n    is_required: true\n    is_sensitive: true\n    title: Passphrase for file decryption\n- encrypted_file_path: null\n  opts:\n    description: |\n      File path to encrypted (input) file, to be decrypted.\n    is_required: true\n    title: Enrypted file path\n- opts:\n    description: \"The decrypted file will be placed at this path. If there already\n      exists a file at this location, it will be removed first. \\n\"\n    is_required: true\n    title: Output (decrypted) file path\n  output_file_path: null\n"
  },
  {
    "path": "steps/decrypt-file/0.9.1/step.yml",
    "content": "title: Decrypt file\nsummary: This Step decrypts a file encrypted with `gpg`, using the default AES128\n  symmetric cypher.\ndescription: |\n  The Step decrypts a file encrypted with `gpg`. This can be helpful if you would like to store an encrypted file in your repository, like a `google-services.json` file used to authenticate your project. Using this Step, you can decrypt that file and use it in your Workflow.\n\n  To create an encrypted file with `gpg`:\n  1. Create a secure passphrase of at least 32 alphanumeric characters: `pwgen -s 32 1`\n  2. Encrypt the file; in this example, the file is called `my_secret.txt`: `gpg -c my_secret.txt`\n\n  For more information, check out our guide on [Using encrypted files in your builds](https://devcenter.bitrise.io/en/builds/managing-build-files/using-encrypted-files-in-your-builds.html).\n\n  ### Configuring the Step\n\n  1. Add the generated passphrase as a **Secret to the Passphrase for file decryption** input.\n  1. Specify the location of the encrypted file in the **Encrypted file path** input.\n  1. Specify the location where you would like to place the decrypted file in the **Output (decrypted) file path** input.\n\n  ### Useful links\n\n  * [Using encrypted files in your builds](https://devcenter.bitrise.io/en/builds/managing-build-files/using-encrypted-files-in-your-builds.html#ot-lst-cnt)\n  * [Bitrise Blog: New step available - Decrypt file](https://blog.bitrise.io/post/new-step-available-decrypt-file)\n  * [Encrypting and decrypting documents](https://www.gnupg.org/gph/en/manual/x110.html)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-decrypt-file\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-decrypt-file\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-decrypt-file/issues\npublished_at: 2022-08-09T10:21:16.75842151Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-decrypt-file.git\n  commit: 1bd58c09d170d546bcf69682c713d49d46a74be9\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-decrypt-file\ndeps:\n  brew:\n  - name: gpg\n  apt_get:\n  - name: gpg\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- decrypt_passphrase: null\n  opts:\n    description: |\n      The passphrase is used as a parameter for gpg.\n    is_required: true\n    is_sensitive: true\n    title: Passphrase for file decryption\n- encrypted_file_path: null\n  opts:\n    description: |\n      File path to encrypted (input) file, to be decrypted.\n    is_required: true\n    title: Path to the encrypted input file\n- opts:\n    description: \"The decrypted file will be placed at this path. If there already\n      exists a file at this location, it will be removed first. \\n\"\n    is_required: true\n    title: Output (decrypted) file path\n  output_file_path: null\n"
  },
  {
    "path": "steps/decrypt-file/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/dependency-installer/1.0.1/step.yml",
    "content": "title: Dependency Installer\nsummary: Installs dependencies from tool version files in your repo.\ndescription: |\n  This wrapper for the bitrise CLI tool installs dependencies\n  defined in the tool version file(s) in your repo.\n\n  To learn more about defining tool versions as code, read our\n  [documentation](https://bitrise.io/stacks/tips/tool-versions).\n\n  Tool version files supported by this step include:\n  * .tool-versions\n  * .ruby-version\n  * .node-version\n  * .python-version\n  * .java-version\n  * .go-version\n  * .terraform-version\n  * .kubectl-version\n  * bitrise.yml (with a `tools:` section)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-dependency-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-dependency-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-dependency-installer/issues\npublished_at: 2026-02-11T14:59:17.846129-06:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-dependency-installer.git\n  commit: fad97b7587ef49538336e1f706abdc7a1154ea24\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-dependency-installer\ninputs:\n- opts:\n    description: |\n      The tool version file contains the version(s) of the tool(s)\n      for the step to install. See the step description for the\n      list of supported tool version files.\n    is_expand: true\n    is_required: true\n    summary: The tool version file path.\n    title: Tool Version File Path\n  tool_version_file: .tool-versions\n- opts:\n    description: |\n      If enabled, the step will output additional debug\n      information during execution.\n    is_expand: false\n    is_required: true\n    summary: Enable verbose output for debugging.\n    title: Verbose Output\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- bitrise_workflow_id: \"\"\n  opts:\n    description: |\n      This input is only used when passing a bitrise.yml file as a\n      tool version file and rather than using the global `tools:`\n      block, you want to use the `tools:` block defined under\n      specific workflows. The step accepts a workflow ID and\n      installs the tools defined under that workflow's `tools:`\n      block.\n    is_expand: true\n    is_required: false\n    summary: The Bitrise Workflow ID to use for installing tools.\n    title: Bitrise Workflow ID\n"
  },
  {
    "path": "steps/dependency-installer/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/deploy-react-native-update-to-appzung-codepush/1.0.0/step.yml",
    "content": "title: Deploy React Native updates to AppZung CodePush\nsummary: |\n  This step uses AppZung CLI to deploy your React Native update to AppZung CodePush\ndescription: |\n  This installs the AppZung CLI and use it to deploy your React Native update to AppZung CodePush. This way, your new features or bug fixes will become available to your users much earlier than if you were going through the app store reviews. Sign up first at https://appzung.com\nwebsite: https://appzung.com\nsource_code_url: https://github.com/appzung/bitrise-step-deploy-react-native-update-to-appzung-codepush\nsupport_url: https://github.com/appzung/bitrise-step-deploy-react-native-update-to-appzung-codepush\npublished_at: 2025-02-24T20:03:56.678348+01:00\nsource:\n  git: https://github.com/appzung/bitrise-step-deploy-react-native-update-to-appzung-codepush.git\n  commit: fc84c53adcbe494ec674f875bdb8337171184e04\nproject_type_tags:\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\ninputs:\n- api_key: null\n  opts:\n    description: |\n      An API key that has access to this project.\n    is_required: true\n    is_sensitive: true\n    summary: AppZung API key for authentication\n    title: API Key\n- opts:\n    description: |\n      Release channel (eg. \"myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e\")\n    is_required: true\n    summary: The release channel ID to deploy to\n    title: Release channel\n  release_channel: null\n- mandatory: \"no\"\n  opts:\n    description: |\n      Specifies whether this release should be considered mandatory\n    summary: Whether this release should be considered mandatory\n    title: Mandatory update\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Percentage points of users this release should be available to (eg. 95 for 95%)\n    is_required: false\n    summary: Percentage of users who should receive this update\n    title: Rollout percentage\n  rollout: null\n- opts:\n    description: |\n      Semver version that specifies the binary app version this release is compatible with. If left unspecified, it will try to find the correct version.\n    is_required: false\n    summary: App version this release is compatible with\n    title: Target binary version\n  target_binary_version: null\n- opts:\n    description: |\n      Specifies the location of a private key to sign the release with.\n      This should be a path relative to your project root.\n    is_required: false\n    summary: Path to the private key file for code signing\n    title: Code signing private key path\n  private_key_path: null\n- description_from_git: \"no\"\n  opts:\n    description: |\n      Use the current git commit message as the release description\n    summary: Use the current git commit message as release description\n    title: Use Git Commit Message\n    value_options:\n    - \"yes\"\n    - \"no\"\n- extra_flags: \"\"\n  opts:\n    description: |\n      Any additional command line flags you want to pass to the deploy command.\n      Example: \"--disable-duplicate-release-error --use-hermes\"\n    is_required: false\n    summary: Additional command line flags\n    title: Additional Flags\n"
  },
  {
    "path": "steps/deploy-react-native-update-to-appzung-codepush/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.0.7/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\n\\n### Configuring the Step\\n\\n1. Set the value for the **Deploy\n  directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR`\n  Env Var which is exposed by the Bitrise CLI.\\nIf you provide a directory, everything\n  in that directory, excluding sub-directories, gets uploaded. \\nIf you provide only\n  a file, then only that file gets uploaded. \\nTo upload a directory's content recursively,\n  you should use the **Compress the artifacts into one file?** which will compress\n  the whole directory, with every sub-directory included.\\n2. Set the value of the\n  **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n#### Configuring the Debug section of the Step\\n\\nIf you wish\n  to use any of the Step’s debug features, set the following inputs:\\n1. In the **Name\n  of the compressed artifact (without .zip extension)** input you can add a custom\n  name for the compressed artifact. If you leave this input empty, the default `Deploy\n  directory` name is used.\\nPlease note that this input only works if you set the\n  **Compress the artifacts into one file?** input to `true`.\\n2. The **Bitrise Build\n  URL** and the **Bitrise Build API Token** inputs are automatically populated.\\n3.\n  If **The Enable Debug Mode** required input is set to `true`, the Step prints more\n  verbose logs. It is `false` by default. \\n4. If you need a specific [bundletool\n  version](https://github.com/google/bundletool/releases) other than the default value,\n  you can modify the value of the **Bundletool version** required input. \\nBundletool\n  generates an APK from an Android App Bundle so that you can test the APK.\\n\\n###\n  Troubleshooting\\n\\n- If your users did not get notified via email, check the **Enable\n  public page for the App?** input. If it is set to `false`, no email notifications\n  will be sent.\\n- If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**,\n  then check the logs to see if the directory you used in the **Deploy directory or\n  file path** input contained any artifacts. \\n- If the email is not received, we\n  recommend, that you check if the email is associated with Bitrise account and if\n  so, if the account is “watching” the app.\\n\\n### Useful links\\n\\n- [Deployment on\n  Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n- [Watching an\n  app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-04-12T15:05:20.817178386Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: addc2a7d545e75f23acf1df72f64dc3faa49ca1a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    is_required: true\n    title: Deploy directory or file path\n- notify_user_groups: everyone\n  opts:\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- is_compress: \"false\"\n  opts:\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Debug\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- debug_mode: \"false\"\n  opts:\n    category: Debug\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Debug\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n      you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.0.8/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\n\\n### Configuring the Step\\n\\n1. Set the value for the **Deploy\n  directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR`\n  Env Var which is exposed by the Bitrise CLI.\\nIf you provide a directory, everything\n  in that directory, excluding sub-directories, gets uploaded. \\nIf you provide only\n  a file, then only that file gets uploaded. \\nTo upload a directory's content recursively,\n  you should use the **Compress the artifacts into one file?** which will compress\n  the whole directory, with every sub-directory included.\\n2. Set the value of the\n  **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n#### Configuring the Debug section of the Step\\n\\nIf you wish\n  to use any of the Step’s debug features, set the following inputs:\\n1. In the **Name\n  of the compressed artifact (without .zip extension)** input you can add a custom\n  name for the compressed artifact. If you leave this input empty, the default `Deploy\n  directory` name is used.\\nPlease note that this input only works if you set the\n  **Compress the artifacts into one file?** input to `true`.\\n2. The **Bitrise Build\n  URL** and the **Bitrise Build API Token** inputs are automatically populated.\\n3.\n  If **The Enable Debug Mode** required input is set to `true`, the Step prints more\n  verbose logs. It is `false` by default. \\n4. If you need a specific [bundletool\n  version](https://github.com/google/bundletool/releases) other than the default value,\n  you can modify the value of the **Bundletool version** required input. \\nBundletool\n  generates an APK from an Android App Bundle so that you can test the APK.\\n\\n###\n  Troubleshooting\\n\\n- If your users did not get notified via email, check the **Enable\n  public page for the App?** input. If it is set to `false`, no email notifications\n  will be sent.\\n- If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**,\n  then check the logs to see if the directory you used in the **Deploy directory or\n  file path** input contained any artifacts. \\n- If the email is not received, we\n  recommend, that you check if the email is associated with Bitrise account and if\n  so, if the account is “watching” the app.\\n\\n### Useful links\\n\\n- [Deployment on\n  Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n- [Watching an\n  app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-06-02T11:03:48.848749216Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 9d4bf8cdb5123906b033d81689fb2c5746e47103\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    is_required: true\n    title: Deploy directory or file path\n- notify_user_groups: everyone\n  opts:\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- is_compress: \"false\"\n  opts:\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Debug\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- debug_mode: \"false\"\n  opts:\n    category: Debug\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Debug\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n      you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.0.9/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\n\\n### Configuring the Step\\n\\n1. Set the value for the **Deploy\n  directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR`\n  Env Var which is exposed by the Bitrise CLI.\\nIf you provide a directory, everything\n  in that directory, excluding sub-directories, gets uploaded. \\nIf you provide only\n  a file, then only that file gets uploaded. \\nTo upload a directory's content recursively,\n  you should use the **Compress the artifacts into one file?** which will compress\n  the whole directory, with every sub-directory included.\\n2. Set the value of the\n  **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n#### Configuring the Debug section of the Step\\n\\nIf you wish\n  to use any of the Step’s debug features, set the following inputs:\\n1. In the **Name\n  of the compressed artifact (without .zip extension)** input you can add a custom\n  name for the compressed artifact. If you leave this input empty, the default `Deploy\n  directory` name is used.\\nPlease note that this input only works if you set the\n  **Compress the artifacts into one file?** input to `true`.\\n2. The **Bitrise Build\n  URL** and the **Bitrise Build API Token** inputs are automatically populated.\\n3.\n  If **The Enable Debug Mode** required input is set to `true`, the Step prints more\n  verbose logs. It is `false` by default. \\n4. If you need a specific [bundletool\n  version](https://github.com/google/bundletool/releases) other than the default value,\n  you can modify the value of the **Bundletool version** required input. \\nBundletool\n  generates an APK from an Android App Bundle so that you can test the APK.\\n\\n###\n  Troubleshooting\\n\\n- If your users did not get notified via email, check the **Enable\n  public page for the App?** input. If it is set to `false`, no email notifications\n  will be sent.\\n- If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**,\n  then check the logs to see if the directory you used in the **Deploy directory or\n  file path** input contained any artifacts. \\n- If the email is not received, we\n  recommend, that you check if the email is associated with Bitrise account and if\n  so, if the account is “watching” the app.\\n\\n### Useful links\\n\\n- [Deployment on\n  Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n- [Watching an\n  app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-07-07T12:33:03.656113949Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: c34f21f8dde227a7cbfa85f9d09020b499bc02d4\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    is_required: true\n    title: Deploy directory or file path\n- notify_user_groups: everyone\n  opts:\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- is_compress: \"false\"\n  opts:\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Debug\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- debug_mode: \"false\"\n  opts:\n    category: Debug\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Debug\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n      you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-08-05T13:29:31.536684136Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: ac0a59d52c8c1c63d6b341d6d227d88e44c38f0b\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-09-12T10:12:32.121823093Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 5b0771afeba7a33e79e295f9178c59c732adcc2a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-10-19T14:22:21.014341823Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: ff22f96d2c7d8afcaa60e92df0cdcc447d769ce5\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.3/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-10-27T14:57:14.562174491Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 49590723600277f11b219ef4318434a42b08d06e\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.4/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2022-11-25T11:13:36.555834355Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: b210ef286b75049ed48308b860d4d2227844c9a0\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.5/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-01-19T15:47:35.897205544Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 26396b4a5bbf6f1f403c135e1b89f6cfbc7d41f3\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.6/step.yml",
    "content": "title: Deploy to Bitrise.io - Apps, Logs, Artifacts\nsummary: Deploys build artifacts to make them available for the user on the build's\n  **APPS & ARTIFACTS** tab. Sends test results to the Test Reports add-on.\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **APPS & ARTIFACTS** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share intermediate files. These files are\n  build artifacts generated by Workflows in a Pipeline intended to be shared with\n  subsequent Workflows.\\n\\n### Configuring the Build Artifact Deployment section of\n  the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-01-20T12:42:38.440961159Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: cc1a8ecea9c761d0bb269b23926cef3baba79dea\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    summary: \"Intermediate files to share between pipeline stages. \\n\\nThe value needs\n      to be a newline separated list of colon separated items with the following structure:\n      \\n\\n**&lt;path>:&lt;env_key>**\\n        \\nThe `path` is the path to the file\n      or folder. The `env_key` is the name of the environment variable with which\n      this value is associated.\"\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.7/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-02-16T09:42:15.279445391Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 3b006d48b0e3e33bfb067bab25e3466b9158ab30\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.1.8/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\\nThe\n  directories you specify will be archived and uploaded as a single file.\\n\\n####\n  Configuring the Debug section of the Step\\n\\nIf you wish to use any of the Step’s\n  debug features, set the following inputs:\\n1. In the **Name of the compressed artifact\n  (without .zip extension)** input you can add a custom name for the compressed artifact.\n  If you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n\\n###\n  Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-03-17T09:00:32.795141755Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 4cfb69bca46ed9187e0ff630c828bfad76cff5b7\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.10.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-01-17T09:20:57.355740398Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: fb5ec6162874117287f249f10bfdffdd0bccb9a3\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.11.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-02-24T13:07:35.738272139Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: e8facaf671252b044967174815a1438669ce8aad\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.12.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-04-09T06:41:25.726253648Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 9a1a2964a60245265bac26c4bc9b34a63f16f635\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.13.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-05-19T09:19:30.455665328Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: e4d5c6f0ca51d225883e2ddc8267e94fecd57f10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.14.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-05-20T07:21:34.306034399Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: f6b32298dafccd2d9d31c0385c3ceccefd96cb7e\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.15.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-05-23T12:56:09.370269509Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 2d9d239ada1a7c867d7c6368f7fa7ce4d1dc0520\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.16.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-05-30T07:03:43.845020994Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 111d5b2ab811c7ffa52844b44e074cc97df97ef8\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.16.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-06-04T11:27:49.97718492Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 4506704e5638ffaeb00a143afbd5f66ef5cdaab2\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.17.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-07-01T07:19:12.5507384Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: d1e254049e1cdc71cb3a4777e496fe26293cb749\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.18.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-07-10T07:33:38.340568589Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 2d1faa94e4fe765a34d87c3e48367e747b68caf3\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.18.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-07-17T12:06:39.402417355Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 69546b2e988ddaf96bc5904bb081d763ad516a68\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.18.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-07-24T08:14:19.203920543Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 5c44571424095570f0ac67cf9516a18b7ea577d9\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.19.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-08-04T13:52:23.654103341Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 7f17ac03a8b4b93a57bdaf13458c0f56b9c58a83\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.19.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-08-15T08:34:08.545499626Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 707250d2d130e110b214da37da2860fed04fa3d0\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.19.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-08-19T06:10:54.212347459Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: f91469ccdac2b6d3eaa03ccbc3a5262370c9771a\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.19.3/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-08-27T10:51:45.090409154Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: a1c224d25778ab24bd08c2b96644ff2df445727d\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.19.4/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-09-11T09:07:08.928118426Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 9740741d15ebff5c681b8388fe9bcd1852cf37e5\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.2.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `$env_var` for `$env_var:env_var`, when the `$env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-03-23T07:01:59.339670641Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: d58ca9017d839331edc6b66fd2cf0be5fe73e978\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `$ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n$BITRISE_IPA_PATH\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.2.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-03-23T12:48:59.672625296Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 965273a665e1a00634b92a460382fe0062fee106\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.2.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-03-27T15:25:22.431505881Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: bbc213a9d8c1ab161c7b31a6fa7660e847e2849c\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.2.3/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-05-04T13:45:27.714090256Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 5719c7a18519ad55aa49875e4bf185b404d260b2\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.8.1\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.20.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These are files generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-09-29T12:19:03.756041033Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 2ba5846bb6acb213a85e79374f610e622ed332ec\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.20.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-09-30T13:49:30.534036457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: d91d7876c3b4a7ab7e11ce2f6cb56da1b1452e6e\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.20.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-10-21T12:54:03.966980725Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 009ec83de6a387bea5e454e7a9570a49a549fea3\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.20.4/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-10-30T09:07:09.641363405Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: cb239c9ad139cf9c0b74675c6f070dda71bc2882\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.21.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-11-19T11:04:44.268385016Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: e5fa275bac50be8d29959c5b4796d5adb3854665\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.21.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2025-11-27T15:49:16.201142264Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: af4e22835a1230bf575e4352b63b3bbeeaba8df6\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.21.1/bin/deploy-to-bitrise-io-darwin-amd64\n    hash: sha256-d54d8bdb579da0a115804f0fc3a607e95b94850058c54c59f300a815e254996a\n  darwin-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.21.1/bin/deploy-to-bitrise-io-darwin-arm64\n    hash: sha256-7734c88a3b34ff1a2e4047ee4c8ce7d716a66fa8106751ea44a162edcbefcfe7\n  linux-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.21.1/bin/deploy-to-bitrise-io-linux-amd64\n    hash: sha256-ce997ac8a4d27f90d84ad0e7644659c96ec26d508ef241238d14ffd7817e3e25\n  linux-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.21.1/bin/deploy-to-bitrise-io-linux-arm64\n    hash: sha256-23ca16104bd8fb2d958885c34315df3445bc04634aecbd8fc18b75ec2266b249\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.22.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2026-01-05T13:05:46.060315824Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 5583d1ed06c4a5d321e26c62de6ab43fa7e73d2c\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.22.0/bin/deploy-to-bitrise-io-darwin-amd64\n    hash: sha256-11ed52bcbe32d2d97b562ade9d9ca22f94e374e071f6822f0c209c1ab40da0d3\n  darwin-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.22.0/bin/deploy-to-bitrise-io-darwin-arm64\n    hash: sha256-134dd2a216069165415c207ff83f7615fb03a718682f0099c410a26395639166\n  linux-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.22.0/bin/deploy-to-bitrise-io-linux-amd64\n    hash: sha256-0fe07b2a614f21b7a53a02b14b4eae4f2e814418d475ad34829aa2feef95c23d\n  linux-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.22.0/bin/deploy-to-bitrise-io-linux-arm64\n    hash: sha256-bc15882a24331a94b47152f8cfeaf5bbde08df556fa8a8b6c52feccfe5c21c00\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.23.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2026-02-10T13:44:07.442765496Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 3c731dedceed7ba76e8a221363ad21712da08211\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.0/bin/deploy-to-bitrise-io-darwin-amd64\n    hash: sha256-b9989485c73615c920177e9b9aa9fe8c55418a4471d0c70ad86100739847366c\n  darwin-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.0/bin/deploy-to-bitrise-io-darwin-arm64\n    hash: sha256-19388f35a260d2cb30c194f91577e6bc94c0f18db62e360bfc1cece777fe0acb\n  linux-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.0/bin/deploy-to-bitrise-io-linux-amd64\n    hash: sha256-b6ef379bb8ff3b298a19a8b504399ab978525451d6b6a3023fb1584f479220bf\n  linux-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.0/bin/deploy-to-bitrise-io-linux-arm64\n    hash: sha256-079a0c6582dd58d32616ad252b1ff9ed3de495cc8346b18f8910104d9399d7bf\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.23.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2026-02-20T13:37:20.964463278Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 0d345ceffe0eae858a3ff21f1b41916b79db5619\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.1/bin/deploy-to-bitrise-io-darwin-amd64\n    hash: sha256-98fa6f1c4111feb0e72acf0bcdca6b7240d4c02ac73b1f870483fd338b906b69\n  darwin-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.1/bin/deploy-to-bitrise-io-darwin-arm64\n    hash: sha256-7aab9ec4f1f32ebc9ad8d9929ee70176cb7ef58668c2887bd7ff18542757a997\n  linux-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.1/bin/deploy-to-bitrise-io-linux-amd64\n    hash: sha256-73b2135d0275a3ea2845666b036810a98273465dafda0823632b79da423a2ceb\n  linux-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.1/bin/deploy-to-bitrise-io-linux-arm64\n    hash: sha256-cad56545360f043bb427d0643426d3bb140893ab85339c01a1c84871d665424d\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.23.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.\n  The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between Pipeline Workflows** input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent Workflows.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Sharing files between Workflows in a Pipeline](https://devcenter.bitrise.io/en/steps-and-workflows/build-pipelines/configuring-a-bitrise-pipeline.html#sharing-files-between-workflows-in-a-pipeline)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2026-03-26T13:16:39.22451156Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 7b3d0d262fe12a140844bbc8288f8af4fb41e9ff\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.2/bin/deploy-to-bitrise-io-darwin-amd64\n    hash: sha256-a7310f721466c0c5e4386cfe83f8a6c41254f2c99e272a446e4789df8c04f3d0\n  darwin-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.2/bin/deploy-to-bitrise-io-darwin-arm64\n    hash: sha256-316b1ae22a53e06199b68a3ddf008345aa9e3690abcd57243085a56ccdc57159\n  linux-amd64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.2/bin/deploy-to-bitrise-io-linux-amd64\n    hash: sha256-0514c8be73684bad1adfb7a6972339ea3b33e4fff3cf41fbe084f7e1c9cb8716\n  linux-arm64:\n    storage_uri: steps/deploy-to-bitrise-io/2.23.2/bin/deploy-to-bitrise-io-linux-arm64\n    hash: sha256-1fa62b79cddc4c54f0c5924691605d55cc3cfee3362866cf8e0ba3668da40ad2\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify.\n    title: 'Notify: User Roles'\n- always_notify_user_groups: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify regardless of the users' project watching preferences.\n      Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * platform engineers\n      * admins\n      * owners\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    summary: Your App's user roles you want to notify regardless of the users' project\n      watching preferences.\n    title: 'Notify: User Roles regardless of project watching preferences'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between Pipeline Workflows\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debugging\n    description: |-\n      The Step will try to extract the test results with the Xcode 15 extraction method.\n\n      Some Xcode test results are not compatible with the new extraction method and cannot extract the test results.\n      If you encounter this issue, please set this input to `true` and try again.\n\n      What does this input does is that it calls the `xcresulttool` command with the `--legacy` flag.\n    is_required: true\n    summary: The Step will try to extract the test results with the Xcode 15 extraction\n      method.\n    title: Legacy extraction method for Xcode test results\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_legacy_xcresult_extraction_method: \"false\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.3.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-07-03T15:00:27.59893723Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 2a1144acd0d3acd9410f7c5c3216017eba935ebd\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.4.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-08-30T06:23:31.483500646Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 1a13f7fd761d373d56a94f226beb8dd3aca02685\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.5.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-09-14T14:26:22.078089517Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: a699eb807dc025859defaf3d5caed0e3f14adfd1\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.5.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-10-11T12:19:56.348306214Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 357d16300ac1c56d48145bc1555ce7e2662af654\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.6.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2023-10-31T13:29:21.613203891Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: e630e3ef2ad349453d3872ec723240250a665620\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.6.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-01-10T09:49:55.741783086Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: a74fc7ab27db6a01004f3ddbab5d800196a1a91b\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-02-01T09:09:00.506160458Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 379ed5c8e6bd6e7ad03e001b1cc919a7204d84e0\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab),  \\nand uploads Pipeline intermediate files to make them available in subsequent\n  Stages.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\n\\n### Configuring the Build Artifact Deployment section\n  of the Step\\n\\n1. Set the value for the **Deploy directory or file path** required\n  input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by\n  the Bitrise CLI.\\nIf you provide a directory, everything in that directory, excluding\n  sub-directories, gets uploaded. \\nIf you provide only a file, then only that file\n  gets uploaded. \\nTo upload a directory's content recursively, you should use the\n  **Compress the artifacts into one file?** which will compress the whole directory,\n  with every sub-directory included.\\n2. Set the value of the **Notify: User Roles**\n  input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n\\n### Configuring the Pipeline Intermediate File Sharing section\n  of the Step\\n\\nThe **Files to share between pipeline stages** input specifies the\n  files meant to be intermediate files shared between the Pipeline Stages. When uploading\n  the Pipeline intermediate files, you must assign environment variable keys to them\n  in the **Files to share between pipeline stages** input.\\nThe inputs `path:env_key`\n  values will be saved together with the file and later automatically reconstructed\n  by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-02-08T11:15:34.386581335Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: d02797b45b576a631c981602a961713551dd9f70\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-02-13T09:06:06.137581196Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: e710da5d3834c00e7f27e7f8f14a86310d65c859\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.3/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-02-14T15:06:45.80162069Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 54d460cfbaba1d68678a1f21dcd46984196907c8\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.4/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-02-21T13:42:38.268396355Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 2a49db699e82687b19591ebad80121cab539b03d\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.5/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-03-01T13:27:26.530065133Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 9e8abfd33a50e2518bdad94a6df2476277196334\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.6/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-03-05T13:55:13.432854549Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 03ba0caae2c1782164d2f0f5da7a41af998e8ae3\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.7/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-04-18T09:24:43.457921696Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 5ae9364b59cac2837bf0d7fc05a2833461d0f321\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.7.8/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-06-03T11:56:29.761171107Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 3c37618d0a5436c65692753d622542aa83bd1c79\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.8.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-06-04T13:30:46.472009045Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 8831a883c9f94acbe7a1fb9c8b082548027d5bcf\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: \"Details Page URLs by the artifact's path. \\n\\nThe default format\n      is `KEY1=>VALUE\\\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format`\n      input\\n\\nExamples:\\n\\n- $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\\n-\n      $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\"\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.8.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: \"Deploys build artifacts to make them available for the user on the build's\n  **Artifacts** tab.  \\nSends test results to the Test Reports add-on (build's **Tests**\n  tab).\\nUploads Pipeline intermediate files to make them available in subsequent\n  Stages and also uploads Bitrise and user generated html reports.\"\ndescription: \"The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR`\n  where artifacts generated by previous Steps gets stored. \\nThese artifacts are then\n  uploaded on the **Artifacts** tab of any given build. For installable artifacts,\n  such as IPAs or APKs, the Step can create a public install page that allows testers\n  to install the app on their devices. \\nYou can also use the Step to notify users\n  about the build. If you wish to use the Test Reports add-on, you must add this Step\n  in your Workflow since the Step converts test results to the right format and sends\n  them to the add-on.\\nThe Step can also share Pipeline intermediate files. These\n  files are build artifacts generated by Workflows in a Pipeline intended to be shared\n  with subsequent Stages.\\nAlso it collects and uploads all of the html reports located\n  in the `BITRISE_HTML_REPORT_DIR` folder.\\n\\n### Configuring the Build Artifact Deployment\n  section of the Step\\n\\n1. Set the value for the **Deploy directory or file path**\n  required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is\n  exposed by the Bitrise CLI.\\nIf you provide a directory, everything in that directory,\n  excluding sub-directories, gets uploaded. \\nIf you provide only a file, then only\n  that file gets uploaded. \\nTo upload a directory's content recursively, you should\n  use the **Compress the artifacts into one file?** which will compress the whole\n  directory, with every sub-directory included.\\n2. Set the value of the **Notify:\n  User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/)\n  to those Bitrise users whose roles are included in this field. \\nThe default value\n  is `everyone`. If you wish to notify based on user roles, add one or more roles\n  and separate them with commas, for example, `developers`, `admins`. If you don't\n  want to notify anyone, set the input to `none`.\\n3. Set the **Notify: Emails** sensitive\n  input. It sends the public install URL in an email to the email addresses provided\n  here. If you’re adding multiple email address, make sure to separate them with commas.\n  \\nThe recipients do not have to be in your Bitrise team. Please note that if the\n  email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  the app.\\n4. The **Enable public page for the App?** required input is set to `true`\n  by default. It creates a long and random URL which can be shared with those who\n  do not have a Bitrise account. \\nIf you set this input to `false`, the **Notify:\n  Emails** input will be ignored and the **Notify: User Roles** will receive the build\n  URL instead of the public install URL.\\n5. With the **Compress the artifacts into\n  one file?** required input set to `true`, you can compress the artifacts found in\n  the Deploy directory into a single file.\\nYou can specify a custom name for the\n  zip file with the `zip_name` option. If you don't specify one, the default `Deploy\n  directory` name will be used. \\nIf the **Compress the artifacts into one file?**\n  is set to `false`, the artifacts in the Deploy directory will be deployed separately.\\n6.\n  With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required\n  input field, you can customize the output format of the public install page’s multiple\n  artifact URLs so that the next Step can render the output (for example, our **Send\n  a Slack message** Step). \\nProvide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n7.\n  With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input,\n  you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n  so that the next Step can render the output.\\nThe next Steps will use this input\n  to generate the related output in the specified format. The output contains multiple\n  permanent URLs for multiple artifacts.\\nProvide a language template description\n  using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template)\n  so that the **Deploy to Bitrise.io** Step can build the required custom output.\\n8.\n  The **Test API's base URL** and the **API Token** input fields are automatically\n  populated for you.\\n9. The html report upload does not have any specific settings\n  because it will happen automatically.\\n\\n### Configuring the Pipeline Intermediate\n  File Sharing section of the Step\\n\\nThe **Files to share between pipeline stages**\n  input specifies the files meant to be intermediate files shared between the Pipeline\n  Stages. When uploading the Pipeline intermediate files, you must assign environment\n  variable keys to them in the **Files to share between pipeline stages** input.\\nThe\n  inputs `path:env_key` values will be saved together with the file and later automatically\n  reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  \\nYou can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var`\n  holds the path to the file(s) you want to share with subsequent stages.\\nThe directories\n  you specify will be archived and uploaded as a single file.\\n\\n#### Configuring\n  the Debug section of the Step\\n\\nIf you wish to use any of the Step’s debug features,\n  set the following inputs:\\n1. In the **Name of the compressed artifact (without\n  .zip extension)** input you can add a custom name for the compressed artifact. If\n  you leave this input empty, the default `Deploy directory` name is used.\\nPlease\n  note that this input only works if you set the **Compress the artifacts into one\n  file?** input to `true`.\\n2. The **Bitrise Build URL** and the **Bitrise Build API\n  Token** inputs are automatically populated.\\n3. If **The Enable Debug Mode** required\n  input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  \\n4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases)\n  other than the default value, you can modify the value of the **Bundletool version**\n  required input. \\nBundletool generates an APK from an Android App Bundle so that\n  you can test the APK.\\n\\n### Troubleshooting\\n\\n- If your users did not get notified\n  via email, check the **Enable public page for the App?** input. If it is set to\n  `false`, no email notifications will be sent.\\n- If there are no artifacts uploaded\n  on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you\n  used in the **Deploy directory or file path** input contained any artifacts. \\n-\n  If the email is not received, we recommend, that you check if the email is associated\n  with Bitrise account and if so, if the account is “watching” the app.\\n\\n### Useful\n  links\\n\\n- [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\\n-\n  [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\\n-\n  [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\\n-\n  [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\\n\n  \\ \\n  ### Related Steps\\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\\n-\n  [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-06-05T08:45:40.770036373Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 45842c8d910ffd036a494cfb7456a730f6c7a0b5\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\\n\\nYou\n      can specify a custom name for the ZIP using the `zip_name`\\noption. If you do\n      not specify a custom name, the default `Deploy directory` name will be used.\\n\\nIf\n      this option is set to `false`, the artifacts\\nfound in the Deploy directory\n      folder will be deployed\\nseparately.\"\n    is_expand: false\n    is_required: true\n    summary: \"If this option is set to `true` and a Deploy directory was specified,\n      \\nthe artifacts in that directory will be compressed into a single ZIP file.\"\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: \"If you do not specify a custom name, the Deploy directory name will\n      be used.\\nYou can specify a custom name for the ZIP using the `zip_name`\\noption.\n      \\n\\nThis option only works if you selected *true* for *is_compress*.\"\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: \"Email addresses to notify. Separate them with commas.\\n\\nYou can\n      specify any email address, the recipients\\ndon't have to be in your team.\\n\\nPlease\n      note that if the email address is associated with a Bitrise account, \\nthe user\n      must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n      the app.\\n\"\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you need a specific [bundletool version]((https://github.com/google/bundletool/releases) other than the default version,\n        you can modify the value of the **Bundletool version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: \"A newline (`\\\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\\n\\nThe\n      input uses a `{path}:{env_key}` syntax.\\nThe colon character (`:`) is the delimiter\n      between the file path and the environment variable key.\\nA shorthand syntax\n      of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var\n      in the current workflow will become the shared env_key. \\n\\nThe file path can\n      be specified with environment variables or direct paths,  \\nand can point to\n      both a local file or directory:\\n```\\n$BITRISE_IPA_PATH:BITRISE_IPA_PATH\\nBITRISE_IPA_PATH\\n$BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\\n./path/to/test_reports:TEST_REPORTS_DIR\\n$BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\\n```\"\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: \"Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\\nso\n      that the **Deploy to Bitrise.io** Step can build the required custom output\n      for the permanent download URL.  \"\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: \"A newline (`\\\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\\n\\nThe file path can be specified with environment\n      variables or direct paths:\\n```\\n$XCODE_BUILD_RAW_RESULT_TEXT_PATH\\n./path/to/build_log.xml\\n```\\n\\nThe\n      step will fail (and potentially also fail the build) if there is any error during\n      the redaction process. \\nThis will prevent secrets in files accidentally leaking\n      out of builds.\"\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: \"Details Page URLs by the artifact's path. \\n\\nThe default format\n      is `KEY1=>VALUE\\\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format`\n      input\\n\\nExamples:\\n\\n- $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\\n-\n      $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\"\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.8.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-07-23T14:17:53.336532174Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: d3b1275ac5c915b8b0ebce2e42770a053513184f\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.8.3/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-08-02T09:44:55.001496794Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 2242bfb91bd19e17b44ea2202dbb6824062e88ed\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.9.0/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-08-08T12:32:02.449872412Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 04a173ad4aec20892740ca18de99c0292c13a06c\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.9.1/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-08-23T09:06:37.021316802Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: f14128c67ab643f251e262dcd26a4680330ababd\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/2.9.2/step.yml",
    "content": "title: Deploy to Bitrise.io - Build Artifacts, Test Reports, and Pipeline intermediate\n  files\nsummary: |-\n  Deploys build artifacts to make them available for the user on the build's **Artifacts** tab.\n  Sends test results to the Test Reports add-on (build's **Tests** tab).\n  Uploads Pipeline intermediate files to make them available in subsequent Stages and also uploads Bitrise and user generated html reports.\ndescription: |-\n  The Step accesses artifacts from a directory specified as the `$BITRISE_DEPLOY_DIR` where artifacts generated by previous Steps gets stored.\n  These artifacts are then uploaded on the **Artifacts** tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.\n  You can also use the Step to notify users about the build. If you wish to use the Test Reports add-on, you must add this Step in your Workflow since the Step converts test results to the right format and sends them to the add-on.\n  The Step can also share Pipeline intermediate files. These files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Stages.\n  Also it collects and uploads all of the html reports located in the `BITRISE_HTML_REPORT_DIR` folder.\n\n  ### Configuring the Build Artifact Deployment section of the Step\n\n  1. Set the value for the **Deploy directory or file path** required input. The default value is the `$BITRISE_DEPLOY_DIR` Env Var which is exposed by the Bitrise CLI.\n  If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.\n  If you provide only a file, then only that file gets uploaded.\n  To upload a directory's content recursively, you should use the **Compress the artifacts into one file?** which will compress the whole directory, with every sub-directory included.\n  2. Set the value of the **Notify: User Roles** input. It sends an email with the [public install URL](https://devcenter.bitrise.io/deploy/bitrise-app-deployment/) to those Bitrise users whose roles are included in this field.\n  The default value is `everyone`. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, `developers`, `admins`. If you don't want to notify anyone, set the input to `none`.\n  3. Set the **Notify: Emails** sensitive input. It sends the public install URL in an email to the email addresses provided here. If you’re adding multiple email address, make sure to separate them with commas.\n  The recipients do not have to be in your Bitrise team. Please note that if the email address is associated with a Bitrise account, the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n  4. The **Enable public page for the App?** required input is set to `true` by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.\n  If you set this input to `false`, the **Notify: Emails** input will be ignored and the **Notify: User Roles** will receive the build URL instead of the public install URL.\n  5. With the **Compress the artifacts into one file?** required input set to `true`, you can compress the artifacts found in the Deploy directory into a single file.\n  You can specify a custom name for the zip file with the `zip_name` option. If you don't specify one, the default `Deploy directory` name will be used.\n  If the **Compress the artifacts into one file?** is set to `false`, the artifacts in the Deploy directory will be deployed separately.\n  6. With the **Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output** required input field, you can customize the output format of the public install page’s multiple artifact URLs so that the next Step can render the output (for example, our **Send a Slack message** Step).\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  7. With the **Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output** required input, you can customize the output format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP` so that the next Step can render the output.\n  The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.\n  Provide a language template description using [https://golang.org/pkg/text/template](https://golang.org/pkg/text/template) so that the **Deploy to Bitrise.io** Step can build the required custom output.\n  8. The **Test API's base URL** and the **API Token** input fields are automatically populated for you.\n  9. The html report upload does not have any specific settings because it will happen automatically.\n\n  ### Configuring the Pipeline Intermediate File Sharing section of the Step\n\n  The **Files to share between pipeline stages** input specifies the files meant to be intermediate files shared between the Pipeline Stages. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  The inputs `path:env_key` values will be saved together with the file and later automatically reconstructed by the [Pull Pipeline intermediate files Step](https://www.bitrise.io/integrations/steps/pull-intermediate-files).\n  You can use a shorthand of just `env_var` for `$env_var:env_var`, when the `env_var` holds the path to the file(s) you want to share with subsequent stages.\n  The directories you specify will be archived and uploaded as a single file.\n\n  #### Configuring the Debug section of the Step\n\n  If you wish to use any of the Step’s debug features, set the following inputs:\n  1. In the **Name of the compressed artifact (without .zip extension)** input you can add a custom name for the compressed artifact. If you leave this input empty, the default `Deploy directory` name is used.\n  Please note that this input only works if you set the **Compress the artifacts into one file?** input to `true`.\n  2. The **Bitrise Build URL** and the **Bitrise Build API Token** inputs are automatically populated.\n  3. If **The Enable Debug Mode** required input is set to `true`, the Step prints more verbose logs. It is `false` by default.\n  4. If you need a specific [bundletool version](https://github.com/google/bundletool/releases) other than the default value, you can modify the value of the **Bundletool version** required input.\n  Bundletool generates an APK from an Android App Bundle so that you can test the APK.\n\n  ### Troubleshooting\n\n  - If your users did not get notified via email, check the **Enable public page for the App?** input. If it is set to `false`, no email notifications will be sent.\n  - If there are no artifacts uploaded on the **APPS & ARTIFACTS tab**, then check the logs to see if the directory you used in the **Deploy directory or file path** input contained any artifacts.\n  - If the email is not received, we recommend, that you check if the email is associated with Bitrise account and if so, if the account is “watching” the app.\n\n  ### Useful links\n\n  - [Deployment on Bitrise](https://devcenter.bitrise.io/deploy/deployment-index/)\n  - [Watching an app](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app)\n  - [Using artifacts from different Stages](https://devcenter.bitrise.io/en/builds/build-pipelines/configuring-a-bitrise-pipeline.html#using-artifacts-from-different-stages)\n  - [Viewing HTML reports](https://devcenter.bitrise.io/en/builds/build-data-and-troubleshooting/viewing-html-reports)\n\n    ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [Pull Pipeline intermediate files](https://www.bitrise.io/integrations/steps/pull-intermediate-files)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues\npublished_at: 2024-08-26T13:35:53.021558172Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io.git\n  commit: 133584195a5da86f4f4f9ed8f70e5f6d327dc70e\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-bitrise-io\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- deploy_path: $BITRISE_DEPLOY_DIR\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Specify the directory or file path which will be deployed.\n\n      If the specified path is a directory, then every file\n      in the specified directory, excluding sub-directories, will be deployed.\n\n      To upload the directory's content\n      recursively, you should use the **Compress the artifacts into one file?** option\n      which compresses the whole directory, with\n      every sub-directory included.\n\n      If you specify a file path, then only the specified\n      file will be deployed.\n    title: Deploy directory or file path\n- is_compress: \"false\"\n  opts:\n    category: Build Artifact Deployment\n    description: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n\n      You can specify a custom name for the ZIP using the `zip_name`\n      option. If you do not specify a custom name, the default `Deploy directory` name will be used.\n\n      If this option is set to `false`, the artifacts\n      found in the Deploy directory folder will be deployed\n      separately.\n    is_expand: false\n    is_required: true\n    summary: |-\n      If this option is set to `true` and a Deploy directory was specified,\n      the artifacts in that directory will be compressed into a single ZIP file.\n    title: Compress the artifacts into one file?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    category: Build Artifact Deployment\n    description: |-\n      If you do not specify a custom name, the Deploy directory name will be used.\n      You can specify a custom name for the ZIP using the `zip_name` option.\n\n      This option only works if you selected *true* for *is_compress*.\n    summary: Specify a custom name for the compressed artifact.\n    title: Name of the compressed artifact (without .zip extension)\n  zip_name: null\n- notify_user_groups: everyone\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Your App's user roles you want to notify. Separate the role names with commas.\n      Possible role names:\n\n      * none\n      * testers\n      * developers\n      * admins\n      * owner\n      * everyone\n\n      An example to notify your developers and testers:\n\n      `testers, developers`\n\n      If you want to notify everyone in the app's team, just specify `everyone`.\n\n      If you don't want to notify anyone, set this to `none`.\n    title: 'Notify: User Roles'\n- notify_email_list: null\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      Email addresses to notify. Separate them with commas.\n\n      You can specify any email address, the recipients\n      don't have to be in your team.\n\n      Please note that if the email address is associated with a Bitrise account,\n      the user must be [watching](https://devcenter.bitrise.io/builds/configuring-notifications/#watching-an-app) the app.\n    is_sensitive: true\n    title: 'Notify: Emails'\n- is_enable_public_page: \"true\"\n  opts:\n    category: Build Artifact Deployment\n    description: |\n      If this option is enabled, a public install page\n      will be available with a long and random URL which can be shared\n      with others who are not registered on Bitrise.\n\n      If you disable this option, the **Notify: Emails** option will\n      be ignored and the **Notify: User Roles** users will receive the build's\n      URL instead of the public page's URL!\n    is_expand: false\n    is_required: true\n    title: Enable public page for the App?\n    value_options:\n    - \"true\"\n    - \"false\"\n- bundletool_version: 1.15.0\n  opts:\n    category: Build Artifact Deployment\n    description: If you need a specific [bundletool version]((https://github.com/google/bundletool/releases)\n      other than the default version, you can modify the value of the **Bundletool\n      version** required input.\n    is_required: true\n    summary: The specific bundletool version you want to use.\n    title: Bundletool version\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build Artifact Deployment\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build Artifact Deployment\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Pipeline Intermediate File Sharing\n    description: |-\n      A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n\n      The input uses a `{path}:{env_key}` syntax.\n      The colon character (`:`) is the delimiter between the file path and the environment variable key.\n      A shorthand syntax of `ENV_VAR` can be used for `$ENV_VAR:ENV_VAR` when the name of the env var in the current workflow will become the shared env_key.\n\n      The file path can be specified with environment variables or direct paths,\n      and can point to both a local file or directory:\n      ```\n      $BITRISE_IPA_PATH:BITRISE_IPA_PATH\n      BITRISE_IPA_PATH\n      $BITRISE_APK_PATH:DEVELOPMENT_APK_PATH\n      ./path/to/test_reports:TEST_REPORTS_DIR\n      $BITRISE_SOURCE_DIR/deploy_dir:DEPLOY_DIR\n      ```\n    summary: A newline (`\\n`) separated list of file path - env key pairs (`{path}:{env_key}`).\n    title: Files to share between pipeline stages\n  pipeline_intermediate_files: null\n- addon_api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Test Reports Addon\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- addon_api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Test Reports Addon\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP output\n  public_install_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the permanent download URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_PERMANENT_DOWNLOAD_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_PERMANENT_DOWNLOAD_URL_MAP output\n  permanent_download_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n- details_page_url_map_format: '{{range $index, $element := .}}{{if $index}}|{{end}}{{$element.File}}=>{{$element.URL}}{{end}}'\n  opts:\n    category: Step output configuration\n    description: |-\n      Provide a language template description using [Golang templates](https://golang.org/pkg/text/template)\n      so that the **Deploy to Bitrise.io** Step can build the required custom output for the details page URL.\n    is_expand: false\n    is_required: true\n    summary: You can customize the format of the `BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP`\n      output so that the next Step can render the output.\n    title: Format for the BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP output\n- files_to_redact: null\n  opts:\n    description: A newline (`\\n`) separated list of file paths to redact secrets from\n      before the step deploys them.\n    is_required: false\n    summary: |-\n      A newline (`\\n`) separated list of file paths to redact secrets from before the step deploys them.\n\n      The file path can be specified with environment variables or direct paths:\n      ```\n      $XCODE_BUILD_RAW_RESULT_TEXT_PATH\n      ./path/to/build_log.xml\n      ```\n\n      The step will fail (and potentially also fail the build) if there is any error during the redaction process.\n      This will prevent secrets in files accidentally leaking out of builds.\n    title: Files to redact\n- debug_mode: \"false\"\n  opts:\n    category: Debugging\n    description: The Step will print more verbose logs if enabled.\n    is_required: true\n    summary: The Step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- BITRISE_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: |-\n      Public Install Page's URL, if the\n      *Enable public page for the App?* option was *enabled*.\n    title: Public Install Page URL\n- BITRISE_PUBLIC_INSTALL_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Public Install Page URLs by the artifact's file path.\n      Only set it if the *Enable public page for the App?* option was *enabled*.\n\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` but is controlled by the `public_install_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://android_app/public/install/page|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://ios_app/public/install/page\n    title: Map of filenames and Public Install Page URLs\n- BITRISE_PERMANENT_DOWNLOAD_URL_MAP: null\n  opts:\n    description: |-\n      The output contains permanent Download URLs for each artifact. The URLs can be shared in any communication channel and they won't expire.\n      The default format is `KEY1=>VALUE|KEY2=>VALUE` where key is the filename and the value is the URL.\n      If you change `permanent_download_url_map_format` input then that will modify the format of this Env Var.\n      You can customize the format of the multiple URLs.\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/artifacts/apk-slug/download|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/artifacts/ipa-slug/download\n    title: Map of filenames and Permanent Download URLs\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL: null\n  opts:\n    description: |-\n      Details Page's URL.\n\n      At the moment, only installable artifacts (.aab, .apk, .ipa) have details page URL.\n    title: Details Page URL\n- BITRISE_ARTIFACT_DETAILS_PAGE_URL_MAP: null\n  opts:\n    description: |-\n      Details Page URLs by the artifact's path.\n\n      The default format is `KEY1=>VALUE\\|KEY2=>VALUE` but is controlled by the `details_page_url_map_format` input\n\n      Examples:\n\n      - $BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n      - $BITRISE_DEPLOY_DIR/android_app.apk=>https://app.bitrise.io/apps/android_app/installable-artifacts/apk-slug|$BITRISE_DEPLOY_DIR/ios_app.ipa=>https://app.bitrise.io/apps/ios_app/installable-artifacts/ipa-slug\n    title: Map of filenames and Public Install Page URLs\n"
  },
  {
    "path": "steps/deploy-to-bitrise-io/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.10.1/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the\n  **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect must have a **unique build and version number** pair (*increment\n  either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2019-10-03T13:34:54.468730382Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: fa267631c5087c41e0c610a8e4222c1ca863442b\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required when itunescon_user is specified.\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required when itunescon_user is specified.\n    is_sensitive: true\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the environment variable for the file here.\n      For example: `$BITRISEIO_MYKEY_URL`\n\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: |-\n      Issuer ID. Required if api_key_path is specified.\n\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: Issuer ID\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.11.0/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the\n  **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect must have a **unique build and version number** pair (*increment\n  either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2020-06-17T19:11:36.292772489Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: d6004c4a8cedecfea2973574092e5cb3c1857b11\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required when itunescon_user is specified.\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required when itunescon_user is specified.\n    is_sensitive: true\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the environment variable for the file here.\n      For example: `$BITRISEIO_MYKEY_URL`\n\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: |-\n      Issuer ID. Required if api_key_path is specified.\n\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: Issuer ID\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.11.1/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of iTunes Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to iTunes Connect must have a unique build and\n  version number pair. Increment either or both before a new deploy to iTunes Connect.\\n\\nTo\n  deploy your app with the Step: \\n1. Make sure that either the **IPA path** or the\n  **PKG path** input has a valid value. The default value is perfect for most cases:\n  it points to the output generated by the **Xcode Archive** Step.\\n1. In the **Platform**\n  input, set the platform of your app. If, for example, you have an iOS app, set it\n  to `ios`. The Step will fail if this input isn't set correctly.\\n1. Set up your\n  connection depending on which authentication method you wish to use: with Apple\n  ID or with the App Store Connet API key. Use only one of the authentication methods.\n  \\n  - For the Apple ID: Fill out the **Apple ID**, **Password**. Optionally, add\n  the **Application specific password** if you wish to bypass two-factor authentication\n  on iTunesConnect.\\n  - For the App Store Connect API: Provide your **API Key URL**\n  (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **Issuer ID** inputs. Please note that connecting with the App Store Connect\n  API works with XCode 11.0 and above releases.  \\n\\n### Troubleshooting\\n\\nUse only\n  one of the authentication methods, if you add both the Apple ID and the API key\n  inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct. Be\n  aware that if you use two-factor authentication, you need to submit an application-specific\n  password.\\n\\nAlways make sure that **Platform** input is set to the correct value.\\n\\nThe\n  Step can also fail if the **Xcode Archive** Step - or any other Step that builds\n  your binary - did not generate an IPA or PKG with a `app-store` export method. \\n\\n###\n  Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2020-11-20T12:44:16.0231941Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: fffcca0fdc7ce694ca984d9e02d9d582b5b68a06\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required when itunescon_user is specified.\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required when itunescon_user is specified.\n    is_sensitive: true\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the environment variable for the file here.\n      For example: `$BITRISEIO_MYKEY_URL`\n\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: |-\n      Issuer ID. Required if api_key_path is specified.\n\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: Issuer ID\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.9.1/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select\n  the **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect have to have a **unique build and version number** pair\n  (*increment either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2018-05-31T11:20:55.80403363+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: bb14a42ae75c8b2d90040df55b338d543e5af063\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required\n    is_required: false\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required\n    is_required: false\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file, to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file, to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.9.2/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select\n  the **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect have to have a **unique build and version number** pair\n  (*increment either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2018-07-04T15:25:13.227201534+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 925cba23fe4bc90cd3a165c63a195bcc01bea863\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required\n    is_required: false\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required\n    is_required: false\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file, to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file, to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.9.3/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select\n  the **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect have to have a **unique build and version number** pair\n  (*increment either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2018-07-30T14:42:35.976433071+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: dba616a4c2f7311a8d84dac98efad224422b57d2\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required\n    is_required: false\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required\n    is_required: false\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file, to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file, to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.9.4/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the\n  **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect must have a **unique build and version number** pair (*increment\n  either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2018-08-31T08:29:37.331218933Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 8af9b455a231d50737cd038fa676984f40f4a160\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required.\n    is_required: false\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.9.5/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the\n  **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect must have a **unique build and version number** pair (*increment\n  either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2019-09-12T15:36:24.566291551Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: edc75f0949cf0eeda0d765b084eda1a0c1311568\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required.\n    is_required: false\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/0.9.6/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/)\\nusing\n  the Apple's Application Loader.\\n\\nSetup guide and notes:\\n  \\n* Register an app\n  on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the\n  **New App** option. This requires an **admin** account.\\n* Requires an app signed\n  with **App Store distibution Provisioning Profile**.\\n* Every build which you want\n  to push to iTunes Connect must have a **unique build and version number** pair (*increment\n  either or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2019-09-16T13:43:53.824968318Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 90b1bd4674ab375a5b6324e268b1541efa7ecd95\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: |-\n      Password for the specified Apple ID.\n      **NOTE:** Password or Application specific password is required.\n    is_required: false\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n      **NOTE:** Password or Application specific password is required.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.0.0/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Fill out the **Apple\n  ID: Email** and the **Apple ID: Password**  (or **Apple ID: Application-specific\n  password** if two-factor authentication is enabled) inputs.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to submit an application-specific\n  password.\\n\\nAlways make sure that **Platform** input is set to the correct value.\\n\\nThe\n  Step can also fail if the **Xcode Archive** Step - or any other Step that builds\n  your binary - did not generate an IPA or PKG with a `app-store` export method. \\n\\n###\n  Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-02-05T09:05:52.208880351Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: d172dc4a0d41897a8febb430e376dca263315e16\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Required if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.1.0/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-02-26T09:11:29.977561345Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 00ee9f188406713306239a8879f81a7a25554b01\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.1.1/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-05-10T13:05:49.328739792Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 90d0768a73c88ab547b31f3ba20be67ef0776075\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.2.0/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-07-08T16:38:19.5296666Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: ab64fc3300863c0b8db193f89b3c53622aa36c9e\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.3.0/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-07-26T14:56:10.735498277Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 4019470b4e4df80532a649243423ee052860f3c8\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.3.1/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-08-12T07:49:44.392519378Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: f16c4d9b892099760d1eef91a9a7faffcfb11497\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.3.2/step.yml",
    "content": "title: Deploy to iTunes Connect - Application Loader\nsummary: Uploads binaries (.ipa / .pkg files) to [iTunes Connect](https://itunesconnect.apple.com/).\ndescription: \"Upload your binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to iTunesConnect** Step.\\n\\nThis Step,\n  however, does NOT build your binary: to create an IPA or PKG file, you need the\n  right version of the **Xcode Archive** Step, or any other Step that is capable of\n  building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-10-29T08:13:33.346704886Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 245a973d4c4655ddf37ff491c3e52d17ebec6259\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.3.3/step.yml",
    "content": "title: Deploy to App Store Connect - Application Loader (formerly iTunes Connect)\nsummary: Uploads binaries (.ipa / .pkg files) to [App Store Connect](https://appstoreconnect.apple.com/).\ndescription: \"Upload your binaries to [App Store Connect](https://appstoreconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to App Store Connect with Deliver** Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2021-12-03T11:20:16.314473499Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 6a15bceffa130da790786f91485948280c534bf2\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.3.4/step.yml",
    "content": "title: Deploy to App Store Connect - Application Loader (formerly iTunes Connect)\nsummary: Uploads binaries (.ipa / .pkg files) to [App Store Connect](https://appstoreconnect.apple.com/).\ndescription: \"Upload your binaries to [App Store Connect](https://appstoreconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to App Store Connect with Deliver** Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2022-02-03T09:41:32.195928604Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 3222d1431e563cf8843274497ce75c337326af10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.4.0/step.yml",
    "content": "title: Deploy to App Store Connect - Application Loader (formerly iTunes Connect)\nsummary: Uploads binaries (.ipa / .pkg files) to [App Store Connect](https://appstoreconnect.apple.com/).\ndescription: \"Upload your binaries to [App Store Connect](https://appstoreconnect.apple.com/)\n  using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with\n  the Step. The Step does not upload metadata, screenshots, nor does it submit your\n  app for review. For that, use the **Deploy to App Store Connect with Deliver** Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the **plus** sign and select the **New App**\n  option. This requires an **admin** account.\\n* This Step requires an app signed\n  with App Store Distibution provisioning profile. Make sure that you use the correct\n  code signing files and the correct export method with the Step that builds your\n  binary.\\n* Every build that you want to push to the App Store Connect must have\n  a unique build and version number pair. Increment either or both before a new deploy\n  to the App Store Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that\n  either the **IPA path** or the **PKG path** input has a valid value. The default\n  value is perfect for most cases: it points to the output generated by the **Xcode\n  Archive** Step.\\n1. Set up your connection depending on which authentication method\n  you wish to use:\\n    - Use a previously configured Bitrise Apple Developer connection:\n  Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default\n  setting), `api_key` or `apple_id`.\\n    - Provide manual Step inputs: Add authentication\n  data depending on which authentication method you wish to use, either Apple ID or\n  API key authentication. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods.\\n        * For API key: Provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: Use the Apple Developer\n  connection based on Apple ID authentication. If no app-specific password has been\n  added to the used connection, the **Apple ID: App-specific password** Step input\n  will be used. Other authentication-related Step inputs are ignored.\\n\\n### Troubleshooting\\n\\nUse\n  only one of the authentication methods, if you add both the Apple ID and the API\n  key inputs the step will fail.\\n\\nMake sure your Apple ID credentials are correct.\n  Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2022-03-11T15:20:10.540296499Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 2e859520a4966690156a3ca38ff8acb0fa82f019\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- opts:\n    description: Retry times when failed, set to `0` for infinite retry\n    title: Retry times\n  retries: \"10\"\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/1.5.0/step.yml",
    "content": "title: Deploy to App Store Connect - Application Loader (formerly iTunes Connect)\nsummary: Uploads binaries (.ipa / .pkg files) to [App Store Connect](https://appstoreconnect.apple.com/).\ndescription: |-\n  Upload your binaries to [App Store Connect](https://appstoreconnect.apple.com/) using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with the Step. The Step does not upload metadata, screenshots, nor does it submit your app for review. For that, use the **Deploy to App Store Connect with Deliver** Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the **plus** sign and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to the App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to the App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously configured Bitrise Apple Developer connection: Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: Add authentication data depending on which authentication method you wish to use, either Apple ID or API key authentication. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: Provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n\n  ### Troubleshooting\n\n  Use only one of the authentication methods, if you add both the Apple ID and the API key inputs the step will fail.\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2023-08-30T07:08:27.757457353Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 672ae8c03d3397664781785f061a83a6dea1b046\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- opts:\n    description: Retry times when failed, set to `0` for infinite retry\n    title: Retry times\n  retries: \"10\"\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example: `--notarize-app --asc-provider\" <<provider_id>>`\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/2.0.0/step.yml",
    "content": "title: Deploy to App Store Connect - Application Loader (formerly iTunes Connect)\nsummary: Uploads binaries (.ipa / .pkg files) to [App Store Connect](https://appstoreconnect.apple.com/).\ndescription: |-\n  Upload your binaries to [App Store Connect](https://appstoreconnect.apple.com/) using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with the Step. The Step does not upload metadata, screenshots, nor does it submit your app for review. For that, use the **Deploy to App Store Connect with Deliver** Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the **plus** sign and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to the App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to the App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously configured Bitrise Apple Developer connection: Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: Add authentication data depending on which authentication method you wish to use, either Apple ID or API key authentication. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: Provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n\n  ### Troubleshooting\n\n  Use only one of the authentication methods, if you add both the Apple ID and the API key inputs the step will fail.\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2025-09-17T12:16:04.56336519Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: b4e1950f2d0e1cad9d20281292a7f79264c9b71c\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Use Inputs under \"App Store Connect connection override\" to configure athentication, as only these are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- app_id: \"\"\n  opts:\n    category: App details\n    description: |-\n      Specifies the Apple ID of the app.\n\n      Available on the **App Information** page of your app in App Store Connect. For example: `1023456789`.\n    is_required: false\n    summary: Specifies the Apple ID of the app.\n    title: App's Apple ID in App Store Connect\n- bundle_id: \"\"\n  opts:\n    category: App details\n    description: |-\n      The bundle identifier of the app to be deployed.\n\n      When *App's Apple ID in App Store Connect* (`app_id`) is provided, will read it from `Info.plist` when not provided.\n    is_required: false\n    summary: The bundle identifier of the app to be deployed.\n    title: Bundle ID\n- bundle_version: \"\"\n  opts:\n    category: App details\n    description: |-\n      Specifies the CFBundleVersion of the app package.\n\n      When *App's Apple ID in App Store Connect* (`app_id`) is provided, will read it from `Info.plist` when not provided.\n    is_required: false\n    summary: Specifies the CFBundleVersion of the app package.\n    title: Bundle version\n- bundle_short_version_string: \"\"\n  opts:\n    category: App details\n    description: |-\n      The version number of the app to be deployed.\n\n      When *App's Apple ID in App Store Connect* (`app_id`) is provided, will read it from `Info.plist` when not provided.\n    is_required: false\n    summary: Specifies the CFBundleShortVersionString of the app package.\n    title: CFBundleShortVersionString\n- api_key_path: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    category: App Store Connect connection override\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: Retry times when failed, set to `0` for infinite retry\n    title: Retry times\n  retries: \"10\"\n- altool_options: \"\"\n  opts:\n    category: Debugging\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example:\n      - `--team-id <<wwdr_team_id>>` (Xcode 26 and above)\n      - `--asc-provider\" <<provider_id>>` (Xcode 16)\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/2.1.0/step.yml",
    "content": "title: Deploy to App Store Connect - Application Loader (formerly iTunes Connect)\nsummary: Uploads binaries (.ipa / .pkg files) to [App Store Connect](https://appstoreconnect.apple.com/).\ndescription: |-\n  Upload your binaries to [App Store Connect](https://appstoreconnect.apple.com/) using Apple's Application Loader. You can upload iOS, macOS, or Apple TV apps with the Step. The Step does not upload metadata, screenshots, nor does it submit your app for review. For that, use the **Deploy to App Store Connect with Deliver** Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the **plus** sign and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to the App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to the App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously configured Bitrise Apple Developer connection: Set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: Add authentication data depending on which authentication method you wish to use, either Apple ID or API key authentication. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: Provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n\n  ### Troubleshooting\n\n  Use only one of the authentication methods, if you add both the Apple ID and the API key inputs the step will fail.\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader/issues\npublished_at: 2025-10-03T13:31:07.10919203Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader.git\n  commit: 4a7a6503c27cabdad52bac872c6f76b8e40f2228\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\n- kotlin-multiplatform\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the Apple ID authentication. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Use Inputs under \"App Store Connect connection override\" to configure athentication, as only these are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: Specify the platform of the file. When `auto` is selected the step\n      uses the `Info.plist` to set the platform.\n    title: Platform\n    value_options:\n    - auto\n    - ios\n    - macos\n    - tvos\n  platform: auto\n- app_id: \"\"\n  opts:\n    category: App details\n    description: |-\n      Specifies the Apple ID of the app.\n\n      Available on the **App Information** page of your app in App Store Connect. For example: `1023456789`.\n    is_required: false\n    summary: Specifies the Apple ID of the app.\n    title: App's Apple ID in App Store Connect\n- bundle_id: \"\"\n  opts:\n    category: App details\n    description: |-\n      The bundle identifier of the app to be deployed.\n\n      When *App's Apple ID in App Store Connect* (`app_id`) is provided, will read it from `Info.plist` when not provided.\n    is_required: false\n    summary: The bundle identifier of the app to be deployed.\n    title: Bundle ID\n- bundle_version: \"\"\n  opts:\n    category: App details\n    description: |-\n      Specifies the CFBundleVersion of the app package.\n\n      When *App's Apple ID in App Store Connect* (`app_id`) is provided, will read it from `Info.plist` when not provided.\n    is_required: false\n    summary: Specifies the CFBundleVersion of the app package.\n    title: Bundle version\n- bundle_short_version_string: \"\"\n  opts:\n    category: App details\n    description: |-\n      The version number of the app to be deployed.\n\n      When *App's Apple ID in App Store Connect* (`app_id`) is provided, will read it from `Info.plist` when not provided.\n    is_required: false\n    summary: Specifies the CFBundleShortVersionString of the app package.\n    title: CFBundleShortVersionString\n- api_key_path: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    category: App Store Connect connection override\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: Retry times when failed, set to `0` for infinite retry\n    title: Retry times\n  retries: \"10\"\n- altool_options: \"\"\n  opts:\n    category: Debugging\n    description: |-\n      Options added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character. Example:\n      - `--team-id <<wwdr_team_id>>` (Xcode 26 and above)\n      - `--asc-provider\" <<provider_id>>` (Xcode 16)\n    title: Additional options for `altool` call\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-application-loader/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.0.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2015-09-08T12:23:46.459975731+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 853535847833a2a09fed41329c65a6222196cbae\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.1.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2015-10-17T13:10:00.384914031+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: a5a44f2c3494d598655c4a1ef4911f25d6237267\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.10.0/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-10-16T17:35:52.362517846+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 69455d44aa3bf7276ead29a39629fada6eeee917\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      This input or `bundle_id` is required\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      This input or app_id is required\n    summary: \"\"\n    title: 'iTunes Connect: App Bundle ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- gemfile_path: ./Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.11.0/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it for review.\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-10-30T15:16:37.148057048+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: e05273741a50de922cee77267965fad232fa6d04\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      This input or `bundle_id` is required\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      This input or app_id is required\n    summary: \"\"\n    title: 'iTunes Connect: App Bundle ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- gemfile_path: ./Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.12.0/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it for review.\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2018-01-12T14:09:53.309701+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 77e06cf821ab6167e892526cad145223fc738b02\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      an Application specific password for the Apple ID.\n\n      **Note:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    summary: \"\"\n    title: 'iTunes Connect: Application Specific Password'\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      This input or `bundle_id` is required\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      This input or app_id is required\n    summary: \"\"\n    title: 'iTunes Connect: App Bundle ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- gemfile_path: ./Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.13.0/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it for review.\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2018-03-01T18:40:00.817229+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: b1c111b2a4e6e85d9278f00ccbc77ff167816f7c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      an Application specific password for the Apple ID.\n\n      **Note:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    summary: \"\"\n    title: 'iTunes Connect: Application Specific Password'\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      This input or `bundle_id` is required\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      This input or app_id is required\n    summary: \"\"\n    title: 'iTunes Connect: App Bundle ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- gemfile_path: ./Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.13.1/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review, \\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action.\\n\\nSetup guide and notes:\\n\\n* Register an app on iTunes Connect,\n  on the **My Apps** page. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* Requires an app signed with **App Store iOS\n  distibution Provisioning Profile**.\\n* Every build which you want to push to iTunes\n  Connect have to have a **unique build and version number** pair (*increment either\n  or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: !!timestamp 2018-03-23T13:09:55.029548029+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 32dbccc4a6d3411881926b33e2e1d9032b76865c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file, to be deployed.\n\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file, to be deployed.\n\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or `Team name` is required when using iTunes Connect account\n      linked to multiple publish team.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or `Team ID` is required when using iTunes Connect account\n      linked to multiple publish team.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: \"Path to the `Gemfile` which contains `fastlane` gem.\\n\\nIf `Gemfile`\n      not exist or does not contain fastlane gem and \\nif `fastlane version` input\n      not specified, latest fastlen version will be used.\\n\"\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: ' Additional options for `deliver` call'\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: \"`deliver` uses the iTunes Transporter to upload metadata and binaries.\n      \\ \\nIn case you are behind a firewall, you can specify a different transporter\n      protocol using this input.\\n\\nRead more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\"\n    title: Transporter delivery method\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.13.2/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review, \\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action.\\n\\nSetup guide and notes:\\n\\n* Register an app on iTunes Connect,\n  on the **My Apps** page. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* Requires an app signed with **App Store iOS\n  distibution Provisioning Profile**.\\n* Every build which you want to push to iTunes\n  Connect have to have a **unique build and version number** pair (*increment either\n  or both before a new deploy to iTunes Connect*).\"\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: !!timestamp 2018-04-06T11:28:56.937484013+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: abdeaa3fc57cb35583333739c0085ef5d520508f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file, to be deployed.\n\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file, to be deployed.\n\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or `Team name` is required when using iTunes Connect account\n      linked to multiple publish team.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or `Team ID` is required when using iTunes Connect account\n      linked to multiple publish team.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: \"Path to the `Gemfile` which contains `fastlane` gem.\\n\\nIf `Gemfile`\n      not exist or does not contain fastlane gem and \\nif `fastlane version` input\n      not specified, latest fastlen version will be used.\\n\"\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: ' Additional options for `deliver` call'\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: \"`deliver` uses the iTunes Transporter to upload metadata and binaries.\n      \\ \\nIn case you are behind a firewall, you can specify a different transporter\n      protocol using this input.\\n\\nRead more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\"\n    title: Transporter delivery method\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.14.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2018-06-07T17:36:53.511461425+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 0169eb350d7fd221d36fd86ffd986f3fc042d4d6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file, to be deployed.\n\n      **NOTE:** This input or `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file, to be deployed.\n\n      **NOTE:** This input or `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for the iTunes Connect site.\n    is_required: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or `Team name` is required when using iTunes Connect account\n      linked to multiple publish team.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or `Team ID` is required when using iTunes Connect account\n      linked to multiple publish team.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` not exist or does not contain fastlane gem and\n      if `fastlane version` input not specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.14.1/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2018-08-31T08:57:09.397557847Z\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 2c9e61e33b7b27538051ccbde59240f684c8bcbf\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled, then this step will\n      fail, even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.15.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2019-03-22T14:23:21.07924738Z\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: b975f2436eb701dfc2328aa9ae3f96c658c0206d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled, then this step will\n      fail, even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.16.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2019-07-16T10:01:09.852943409Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 83c6d1920d53f2fdd2adcb8477271708eb4ceaf3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled, then this step will\n      fail, even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.16.1/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2019-07-26T08:09:36.842278673Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: e7c7ebce9e4cb4249a23d19cb18c5b81d839e9ec\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled, then this step will\n      fail, even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.16.2/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2019-08-15T14:22:09.624603216Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 09bfb54640c40f45974b66ca49b099f855be7084\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled, then this step will\n      fail, even if the version was successfully uploaded\n      to iTunes Connect and only the review submission failed.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.16.3/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2019-10-11T08:29:32.4629991Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: c106316966d10479cab68b9d37b7bd9e54d8de6e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** with this option enabled, the step will only\n      be successful, if the submission is accepted by iTunes Connect.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.17.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2019-11-08T15:42:18.364894144Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: bdd1118ebe67c86fafc4796bb3c0c4a2fd37e30f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** with this option enabled, the step will only\n      be successful, if the submission is accepted by iTunes Connect.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.18.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action.\n\n  Setup guide and notes:\n\n  * Register an app on the **My Apps** page of iTunes Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an app signed with **App Store iOS distibution Provisioning Profile**.\n  * Every build that you want to push to iTunes Connect must have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*).\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2020-06-30T12:47:16.457540759Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: fd288ae43e834cf35a9c5eabba6b12eec5450163\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An Application specific password for the Apple ID.\n\n      **NOTE:** Application specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      surpass Two Factor Authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application Specific Password\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      **NOTE:** This field or the `Team name` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      **NOTE:** This field or the `Team ID` is required when using iTunes Connect account\n      linked to multiple publish teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Bundle ID` is required.\n\n      Open the **App's page on iTunes Connect**, click on **App Information**,\n      scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric value, for example, 846814360).\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n\n      If this option is disabled, then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** with this option enabled, the step will only\n      be successful, if the submission is accepted by iTunes Connect.\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update app version for submission.\n    is_required: true\n    title: Skip App Version Update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains `fastlane` gem.\n\n      If `Gemfile` doesn't exist or doesn't contain fastlane gem and\n      if `fastlane version` input isn't specified, latest fastlen version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a specific version of the **fastlane** gem to be installed.\n\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including prerelease (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list those separated by space character.\n\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      In case you are behind a firewall, you can specify a different transporter protocol using this input.\n\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.18.1/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of iTunes Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to iTunes Connect must have a unique build and\n  version number pair. Increment either or both before a new deploy to iTunes Connect.\\n\\nTo\n  deploy your app with the Step: \\n1. Make sure that either the **IPA path** or the\n  **PKG path** input has a valid value. The default value is perfect for most cases:\n  it points to the output generated by the **Xcode Archive** Step.\\n1. In the **Platform**\n  input, set the platform of your app. If, for example, you have an iOS app, set it\n  to `ios`. The Step will fail if this input isn't set correctly.\\n1. Add your Apple\n  ID information for authentication. The information must be added as Secrets to the\n  following inputs:\\n   - **Apple ID**.\\n   - **Password**.\\n   - Optionally, **Application\n  specific password**. Use this to bypass two-factor authentication on iTunesConnect.\n  \\n1. To identify the app, set either the **App Apple ID** or the **App Bundle ID**.\n  Note that while neither is marked as **Required**, one of the two MUST have a valid\n  value. \\n1. If you want to immediately submit your app for an iTunesConnect review,\n  set the **Submit for Review?** input to `yes`. Please note that if you do submit\n  the app for review, the Step will be successful only if the submission is accepted\n  by iTunesConnect.\\n\\n### Troubleshooting\\n\\nMake sure your Apple ID credentials\n  are correct. Be aware that if you use two-factor authentication, you need to submit\n  an application-specific password.\\n\\nAlways make sure that **Platform** input is\n  set to the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step\n  - or any other Step that builds your binary - did not generate an IPA or PKG with\n  a `app-store` export method. \\n\\n### Useful links \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-01-12T08:58:44.465413954Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 79cd01c37c03948129f1324a5e20a6064700c680\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: true\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: true\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application-specific password\n- opts:\n    description: |-\n      The app's *Team ID* on iTunes Connect.\n      **NOTE:** This field or the `Team name` is required when using an iTunes Connect account\n      that is linked to multiple publishing teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on iTunes Connect.\n      **NOTE:** This field or the `Team ID` is required when using an iTunes Connect account\n      that is linked to multiple publishing teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on iTunes Connect.\n      **NOTE:** This input or the `App Bundle ID` is required.\n      Open the **app's page on iTunes Connect**, click on **App Information**,\n      scroll down to the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on iTunes Connect.\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect. Note that in this case the Step will only be successful if the submission is accepted by iTunesConnect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.19.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [iTunes Connect](https://itunesconnect.apple.com/)\n  and submit your app for App Store review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of iTunes Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to iTunes Connect must have a unique build and\n  version number pair. Increment either or both before a new deploy to iTunes Connect.\\n\\nTo\n  deploy your app with the Step: \\n1. Make sure that either the **IPA path** or the\n  **PKG path** input has a valid value. The default value is perfect for most cases:\n  it points to the output generated by the **Xcode Archive** Step.\\n1. Set up your\n  connection depending on which authentication method you wish to use: with Apple\n  ID or with the App Store Connet API key. Use only one of the authentication methods.\n  \\n  - For the Apple ID: Fill out the **Apple ID**, **Password**. Optionally, add\n  the **Application specific password** if you wish to bypass two-factor authentication\n  on iTunesConnect.\\n  - For the App Store Connect API: Provide your **API Key URL**\n  (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **Issuer ID** inputs. Please note that connecting with the App Store Connect\n  API works with XCode 11.0 and above releases.  \\n1. To identify the app, set either\n  the **App Apple ID** or the **App Bundle ID**. Note that while neither is marked\n  as **Required**, one of the two MUST have a valid value. \\n1. If you want to immediately\n  submit your app for an iTunesConnect review, set the **Submit for Review?** input\n  to `yes`. Please note that if you do submit the app for review, the Step will be\n  successful only if the submission is accepted by iTunesConnect.\\n\\n### Troubleshooting\\n\\nMake\n  sure your Apple ID credentials are correct. Be aware that if you use two-factor\n  authentication, you need to submit an application-specific password.\\n\\nAlways make\n  sure that **Platform** input is set to the correct value.\\n\\nThe Step can also fail\n  if the **Xcode Archive** Step - or any other Step that builds your binary - did\n  not generate an IPA or PKG with a `app-store` export method. \\n\\n### Useful links\n  \\n\\n- [Deploying an app to iTunesConnect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-01-20T16:21:26.309772207Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 8bce4f24519585b294b1a74b9842cd52dfcef717\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the `PKG path` is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the `IPA path` is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- itunescon_user: \"\"\n  opts:\n    description: Login Apple ID for iTunes Connect.\n    is_required: false\n    is_sensitive: true\n    title: Apple ID\n- opts:\n    description: Password for the specified Apple ID.\n    is_required: false\n    is_sensitive: true\n    title: Password\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_required: false\n    is_sensitive: true\n    title: Application-specific password\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the environment variable for the file here.\n      For example: `$BITRISEIO_MYKEY_URL`\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: |-\n      Issuer ID. Required if api_key_path is specified.\n      **NOTE:** Only available from XCode 11.0 and above.\n    title: Issuer ID\n- opts:\n    description: |-\n      The app's *Team ID* on iTunes Connect.\n      **NOTE:** This field or the `Team name` is required when using an iTunes Connect account\n      that is linked to multiple publishing teams.\n    title: Team ID\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on iTunes Connect.\n      **NOTE:** This field or the `Team ID` is required when using an iTunes Connect account\n      that is linked to multiple publishing teams.\n    title: Team name\n  team_name: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on iTunes Connect.\n      **NOTE:** This input or the `App Bundle ID` is required.\n      Open the **app's page on iTunes Connect**, click on **App Information**,\n      scroll down to the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    title: App Apple ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on iTunes Connect.\n      **NOTE:** This input or the `App Apple ID` is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect. Note that in this case the Step will only be successful if the submission is accepted by iTunesConnect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.2.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2015-10-29T12:36:59.0255606+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 2910b235ab7ee1fae391eeea0b9c7cb4d7c3dd54\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.2.1/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2015-12-11T18:11:52.39703981+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 16241dca91a87c216d27bffcb3d49dbd305b3b34\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.20.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer Connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (default), `api_key` or `apple_id`.\\n\n  \\   - Provide manual step inputs, either with Apple ID or with the App Store Connet\n  API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of\n  the authentication methods. \\n        * For the Apple ID: Fill out the **Apple ID:\n  Email**, **Apple ID: Password**. Add the **Apple ID: Application specific password**\n  if you wish to bypass two-factor authentication.\\n        * For the App Store Connect\n  API: Provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8\n  or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n  Please note that connecting with the App Store Connect API works with XCode 11.0\n  and above releases.  \\n1. To identify the app, set either the **App Store Connect\n  App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**,\n  one of the two MUST have a valid value. \\n1. If you want to immediately submit your\n  app for an App Store review, set the **Submit for Review?** input to `yes`. Please\n  note that if you do submit the app for review, the Step will be successful only\n  if the submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake\n  sure your Apple ID credentials are correct. Be aware that if you use two-factor\n  authentication, you need to submit an application-specific password.\\n\\nAlways make\n  sure that **Platform** input is set to the correct value.\\n\\nThe Step can also fail\n  if the **Xcode Archive** Step - or any other Step that builds your binary - did\n  not generate an IPA or PKG with a `app-store` export method. \\n\\n### Useful links\n  \\n\\n- [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-02-02T16:05:29.2418338Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 7c20293c7cf0e967ad6274bfdc0f55643acc5218\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the environment variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Required if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.20.1/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (this is the default setting), `api_key`\n  or `apple_id`.\\n    - Provide manual Step inputs: either with Apple ID or with the\n  App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods. \\n        * For API key: provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: *Apple IDs with\n  2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password**\n  inputs.\\n1. To identify the app, set either the **App Store Connect App ID** or\n  the **App Bundle ID**. Note that while neither is marked as **Required**, one of\n  the two MUST have a valid value. \\n1. If you want to immediately submit your app\n  for an App Store review, set the **Submit for Review?** input to `yes`. Please note\n  that if you do submit the app for review, the Step will be successful only if the\n  submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake sure\n  your Apple ID credentials are correct. Be aware that if you use two-factor authentication,\n  you need to submit an application-specific password.\\n\\nAlways make sure that **Platform**\n  input is set to the correct value.\\n\\nThe Step can also fail if the **Xcode Archive**\n  Step - or any other Step that builds your binary - did not generate an IPA or PKG\n  with a `app-store` export method. \\n\\n### Useful links \\n\\n- [Deploying an app to\n  App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-02-04T11:47:52.091401606Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: c91fdc7c90cda77744ed2133a6c895d1ca3ef2ab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Required if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.20.2/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (this is the default setting), `api_key`\n  or `apple_id`.\\n    - Provide manual Step inputs: either with Apple ID or with the\n  App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods. \\n        * For API key: provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: *Apple IDs with\n  2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password**\n  inputs.\\n1. To identify the app, set either the **App Store Connect App ID** or\n  the **App Bundle ID**. Note that while neither is marked as **Required**, one of\n  the two MUST have a valid value. \\n1. If you want to immediately submit your app\n  for an App Store review, set the **Submit for Review?** input to `yes`. Please note\n  that if you do submit the app for review, the Step will be successful only if the\n  submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake sure\n  your Apple ID credentials are correct. Be aware that if you use two-factor authentication,\n  you need to submit an application-specific password.\\n\\nAlways make sure that **Platform**\n  input is set to the correct value.\\n\\nThe Step can also fail if the **Xcode Archive**\n  Step - or any other Step that builds your binary - did not generate an IPA or PKG\n  with a `app-store` export method. \\n\\n### Useful links \\n\\n- [Deploying an app to\n  App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-02-09T13:50:36.346921343Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 4d779ddbe0730bb91a0a102f37d595d21cfe47e1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Required if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.0/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (this is the default setting), `api_key`\n  or `apple_id`.\\n    - Provide manual Step inputs: either with Apple ID or with the\n  App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods. \\n        * For API key: provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: *Apple IDs with\n  2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password**\n  inputs.\\n1. To identify the app, set either the **App Store Connect App ID** or\n  the **App Bundle ID**. Note that while neither is marked as **Required**, one of\n  the two MUST have a valid value. \\n1. If you want to immediately submit your app\n  for an App Store review, set the **Submit for Review?** input to `yes`. Please note\n  that if you do submit the app for review, the Step will be successful only if the\n  submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake sure\n  your Apple ID credentials are correct. Be aware that if you use two-factor authentication,\n  you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-02-26T09:11:53.12125867Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 4a4d9384c6333b148b95d048b12f513e42dcd170\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: -t DAV\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.1/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (this is the default setting), `api_key`\n  or `apple_id`.\\n    - Provide manual Step inputs: either with Apple ID or with the\n  App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods. \\n        * For API key: provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: *Apple IDs with\n  2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password**\n  inputs.\\n1. To identify the app, set either the **App Store Connect App ID** or\n  the **App Bundle ID**. Note that while neither is marked as **Required**, one of\n  the two MUST have a valid value. \\n1. If you want to immediately submit your app\n  for an App Store review, set the **Submit for Review?** input to `yes`. Please note\n  that if you do submit the app for review, the Step will be successful only if the\n  submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake sure\n  your Apple ID credentials are correct. Be aware that if you use two-factor authentication,\n  you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-04-19T17:46:34.169320405Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 3e711602bdb23b236f6cb2ded9b3f7b59ecd396b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.2/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (this is the default setting), `api_key`\n  or `apple_id`.\\n    - Provide manual Step inputs: either with Apple ID or with the\n  App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods. \\n        * For API key: provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: *Apple IDs with\n  2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password**\n  inputs.\\n1. To identify the app, set either the **App Store Connect App ID** or\n  the **App Bundle ID**. Note that while neither is marked as **Required**, one of\n  the two MUST have a valid value. \\n1. If you want to immediately submit your app\n  for an App Store review, set the **Submit for Review?** input to `yes`. Please note\n  that if you do submit the app for review, the Step will be successful only if the\n  submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake sure\n  your Apple ID credentials are correct. Be aware that if you use two-factor authentication,\n  you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-05-10T12:32:10.703342987Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 680afa230be2819138eb4d307eea31026c0a109f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.3/step.yml",
    "content": "title: Deploy to iTunes Connect\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: \"Upload screenshots, metadata and binaries to [App Store Connect (iTunes\n  Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store\n  review,\\nusing the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/)\n  fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\\n\\nThis\n  Step, however, does NOT build your binary: to create an IPA or PKG file, you need\n  the right version of the **Xcode Archive** Step, or any other Step that is capable\n  of building a binary file.  \\n\\n### Configuring the Step \\n\\nBefore you start using\n  this Step, you need to do a couple of things:\\n\\n* Register an app on the **My Apps**\n  page of App Store Connect. Click on the *plus sign* and select the **New App** option.\n  This requires an **admin** account.\\n* This Step requires an app signed with App\n  Store Distibution provisioning profile. Make sure that you use the correct code\n  signing files and the correct export method with the Step that builds your binary.\\n*\n  Every build that you want to push to App Store Connect must have a unique build\n  and version number pair. Increment either or both before a new deploy to App Store\n  Connect.\\n\\nTo deploy your app with the Step: \\n1. Make sure that either the **IPA\n  path** or the **PKG path** input has a valid value. The default value is perfect\n  for most cases: it points to the output generated by the **Xcode Archive** Step.\\n1.\n  Set up your connection depending on which authentication method you wish to use:\\n\n  \\   - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise\n  Apple Developer Connection** to `automatic` (this is the default setting), `api_key`\n  or `apple_id`.\\n    - Provide manual Step inputs: either with Apple ID or with the\n  App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`.\n  Use only one of the authentication methods. \\n        * For API key: provide your\n  **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8)\n  and the **API Key: Issuer ID** inputs.\\n        * For Apple ID: *Apple IDs with\n  2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password**\n  inputs.\\n1. To identify the app, set either the **App Store Connect App ID** or\n  the **App Bundle ID**. Note that while neither is marked as **Required**, one of\n  the two MUST have a valid value. \\n1. If you want to immediately submit your app\n  for an App Store review, set the **Submit for Review?** input to `yes`. Please note\n  that if you do submit the app for review, the Step will be successful only if the\n  submission is accepted by App Store Connect.\\n\\n### Troubleshooting\\n\\nMake sure\n  your Apple ID credentials are correct. Be aware that if you use two-factor authentication,\n  you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password)\n  a connection with Apple ID.\\n\\nAlways make sure that **Platform** input is set to\n  the correct value.\\n\\nThe Step can also fail if the **Xcode Archive** Step - or\n  any other Step that builds your binary - did not generate an IPA or PKG with a `app-store`\n  export method. \\n\\n### Useful links \\n\\n- [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\\n-\n  [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\\n\\n###\n  Related Steps \\n\\n- [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\\n-\n  [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\"\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-08-06T15:56:01.110187354Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 392d56e90226789f52ef8d229262110cbefa7e99\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.4/step.yml",
    "content": "title: Deploy to App Store Connect with Deliver (formerly iTunes Connect)\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: either with Apple ID or with the App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: *Apple IDs with 2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password** inputs.\n  1. To identify the app, set either the **App Store Connect App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**, one of the two MUST have a valid value.\n  1. If you want to immediately submit your app for an App Store review, set the **Submit for Review?** input to `yes`. Please note that if you do submit the app for review, the Step will be successful only if the submission is accepted by App Store Connect.\n\n  ### Troubleshooting\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2021-12-03T11:19:44.375811546Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 87d333af3761fce7c02c2237f252b43f0070c9c0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.5/step.yml",
    "content": "title: Deploy to App Store Connect with Deliver (formerly iTunes Connect)\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: either with Apple ID or with the App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: *Apple IDs with 2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password** inputs.\n  1. To identify the app, set either the **App Store Connect App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**, one of the two MUST have a valid value.\n  1. If you want to immediately submit your app for an App Store review, set the **Submit for Review?** input to `yes`. Please note that if you do submit the app for review, the Step will be successful only if the submission is accepted by App Store Connect.\n\n  ### Troubleshooting\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2022-10-24T12:22:56.692842866Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: f7a6d87a10e5e529be99dec9830e2fc2cff85901\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.21.6/step.yml",
    "content": "title: Deploy to App Store Connect with Deliver (formerly iTunes Connect)\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: either with Apple ID or with the App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: *Apple IDs with 2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password** inputs.\n  1. To identify the app, set either the **App Store Connect App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**, one of the two MUST have a valid value.\n  1. If you want to immediately submit your app for an App Store review, set the **Submit for Review?** input to `yes`. Please note that if you do submit the app for review, the Step will be successful only if the submission is accepted by App Store Connect.\n\n  ### Troubleshooting\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2022-10-25T08:03:38.257125259Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: ca90492b93d0872686b3f066ababf03a6323c69f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.22.0/step.yml",
    "content": "title: Deploy to App Store Connect with Deliver (formerly iTunes Connect)\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: either with Apple ID or with the App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: *Apple IDs with 2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password** inputs.\n  1. To identify the app, set either the **App Store Connect App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**, one of the two MUST have a valid value.\n  1. If you want to immediately submit your app for an App Store review, set the **Submit for Review?** input to `yes`. Please note that if you do submit the app for review, the Step will be successful only if the submission is accepted by App Store Connect.\n\n  ### Troubleshooting\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2023-08-30T07:12:45.776826825Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: 26ad08a7bfaa28d95f6c71388560c73a58d53b80\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.22.1/step.yml",
    "content": "title: Deploy to App Store Connect with Deliver (formerly iTunes Connect)\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: either with Apple ID or with the App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: *Apple IDs with 2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password** inputs.\n  1. To identify the app, set either the **App Store Connect App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**, one of the two MUST have a valid value.\n  1. If you want to immediately submit your app for an App Store review, set the **Submit for Review?** input to `yes`. Please note that if you do submit the app for review, the Step will be successful only if the submission is accepted by App Store Connect.\n\n  ### Troubleshooting\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2025-11-12T13:12:12.776218793Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: ab706d9732e3e7978acf9ea56c5178ec99e8a125\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- itms_upload_parameters: \"\"\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.23.0/step.yml",
    "content": "title: Deploy to App Store Connect with Deliver (formerly iTunes Connect)\nsummary: Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/)\n  and submit your app for App Store review.\ndescription: |-\n  Upload screenshots, metadata and binaries to [App Store Connect (iTunes Connect)](https://appstoreconnect.apple.com/) and submit your app for App Store review,\n  using the fantastic [deliver](https://docs.fastlane.tools/actions/deliver/) fastlane action. You can upload iOS, macOS, or Apple TV apps with the Step.\n\n  This Step, however, does NOT build your binary: to create an IPA or PKG file, you need the right version of the **Xcode Archive** Step, or any other Step that is capable of building a binary file.\n\n  ### Configuring the Step\n\n  Before you start using this Step, you need to do a couple of things:\n\n  * Register an app on the **My Apps** page of App Store Connect. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * This Step requires an app signed with App Store Distibution provisioning profile. Make sure that you use the correct code signing files and the correct export method with the Step that builds your binary.\n  * Every build that you want to push to App Store Connect must have a unique build and version number pair. Increment either or both before a new deploy to App Store Connect.\n\n  To deploy your app with the Step:\n  1. Make sure that either the **IPA path** or the **PKG path** input has a valid value. The default value is perfect for most cases: it points to the output generated by the **Xcode Archive** Step.\n  1. Set up your connection depending on which authentication method you wish to use:\n      - Use a previously set up Bitrise Apple Developer connection, set the **Bitrise Apple Developer Connection** to `automatic` (this is the default setting), `api_key` or `apple_id`.\n      - Provide manual Step inputs: either with Apple ID or with the App Store Connet API key. Set the **Bitrise Apple Developer Connection** to `off`. Use only one of the authentication methods.\n          * For API key: provide your **API Key: URL** (for example, https://URL/TO/AuthKey_something.p8 or file:///PATH/TO/AuthKey_something.p8) and the **API Key: Issuer ID** inputs.\n          * For Apple ID: *Apple IDs with 2FA are not supported.* Fill out the **Apple ID: Email** and the **Apple ID: Password** inputs.\n  1. To identify the app, set either the **App Store Connect App ID** or the **App Bundle ID**. Note that while neither is marked as **Required**, one of the two MUST have a valid value.\n  1. If you want to immediately submit your app for an App Store review, set the **Submit for Review?** input to `yes`. Please note that if you do submit the app for review, the Step will be successful only if the submission is accepted by App Store Connect.\n\n  ### Troubleshooting\n\n  Make sure your Apple ID credentials are correct. Be aware that if you use two-factor authentication, you need to [set up](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#setting-up-connection-with-the-apple-id-and-password) a connection with Apple ID.\n\n  Always make sure that **Platform** input is set to the correct value.\n\n  The Step can also fail if the **Xcode Archive** Step - or any other Step that builds your binary - did not generate an IPA or PKG with a `app-store` export method.\n\n  ### Useful links\n\n  - [Deploying an app to App Store Connect](https://devcenter.bitrise.io/deploy/ios-deploy/deploying-an-ios-app-to-itunes-connect/)\n  - [iOS deployment](https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/)\n\n  ### Related Steps\n\n  - [Deploy to Google Play](https://www.bitrise.io/integrations/steps/google-play-deploy)\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2026-03-20T11:38:41.66748865Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver.git\n  commit: c4452f2961801c95091349bc0e57872bf3ab2ca2\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/deploy-to-itunesconnect-deliver/2.23.0/bin/deploy-to-itunesconnect-deliver-darwin-amd64\n    hash: sha256-bc84e732d503b2cab1e8ee9766407728a18c1751c66c563982d6d9c615e7ddd3\n  darwin-arm64:\n    storage_uri: steps/deploy-to-itunesconnect-deliver/2.23.0/bin/deploy-to-itunesconnect-deliver-darwin-arm64\n    hash: sha256-14fb2480b80d5b1a77df25740d326ed08d4b21a7ee888c7f9607957b12a08f2d\n  linux-amd64:\n    storage_uri: steps/deploy-to-itunesconnect-deliver/2.23.0/bin/deploy-to-itunesconnect-deliver-linux-amd64\n    hash: sha256-c0a00873c03a7beb11fadfd5cc4d15db89d161aa1646efdb54daa9d10220b42f\n  linux-arm64:\n    storage_uri: steps/deploy-to-itunesconnect-deliver/2.23.0/bin/deploy-to-itunesconnect-deliver-linux-arm64\n    hash: sha256-af677a83004926573a099f239f2891b27a54d82d3aac60007d87479a186555b4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the legacy method of session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication. If no app-specific password has been added to the used connection, the **Apple ID: App-specific password** Step input will be used. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- itunescon_user: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      The app's *Team ID* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team name** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n\n      For example: `2040826`\n    title: 'Apple ID: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The app's *Team Name* on App Store Connect.\n      **NOTE:** This field or the **Apple ID: Team ID** is required when authenticating using Apple ID and the account\n      is linked to multiple publishing teams.\n    title: 'Apple ID: Team name'\n  team_name: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |-\n      Path to your IPA file to be deployed.\n      **NOTE:** This input or the **PKG path** is required.\n    title: IPA path\n- opts:\n    description: |-\n      Path to your PKG file to be deployed.\n      **NOTE:** This input or the **IPA path** is required.\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- opts:\n    description: The platform of the app.\n    is_required: true\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n- app_id: \"\"\n  opts:\n    description: |-\n      The app's *Apple ID* on App Store Connect.\n      **NOTE:** This input or the **App Bundle ID** is required.\n      Open the **app's page on App Store Connect**, click on **App Information**,\n      from the **General Information** section,\n      copy the **Apple ID**'s value from here. It's a numeric value, for example, 846814360.\n    summary: App Store Connect App ID (Apple ID)\n    title: App Store Connect App ID\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The app's *Bundle ID* on App Store Connect.\n      **NOTE:** This input or the **App Store Connect App ID** is required.\n    title: App Bundle ID\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      submit the app for review for this specific version?\n      If this option is set to `no`, the Step won't wait\n      for the new version to be processed on App Store Connect\n      and won't submit it for review automatically.\n      If this input is set to `yes`, the Step will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to App Store Connect. Note that in this case the Step will only be successful if the submission is accepted by App Store Connect!\n    is_required: true\n    title: Submit for Review?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_review: \"no\"\n- opts:\n    description: Don't upload the metadata. This will still upload screenshots.\n    is_required: true\n    title: Skip metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: Don't upload the screenshots.\n    is_required: true\n    title: Skip screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: Don't update the app version for submission.\n    is_required: true\n    title: Skip app Version update?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_app_version_update: \"no\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the `Gemfile` which contains the `fastlane` gem.\n      If a `Gemfile` doesn't exist or doesn't contain the `fastlane` gem and\n      if the **fastlane version** input isn't specified, the latest fastlane version will be used.\n    title: Gemfile path\n- fastlane_version: latest-stable\n  opts:\n    category: Debug\n    description: |-\n      This option lets you specify a version of the **fastlane** gem to be installed.\n      - `latest-stable` installs the latest stable version.\n      - `latest` installs the latest version of fastlane including pre-release (release candidate) versions.\n    title: fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `deliver` call.\n      If you want to add more options, list those separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    title: Additional options for `deliver` call\n- altool_options: null\n  opts:\n    category: Debug\n    description: |-\n      `deliver` uses `altool` to upload IPAs.\n      Options are added to the end of the `altool` call.\n      You can use multiple options, separated by a space\n      character.\n      Examples:\n      - `--use-old-altool`\n      - `--bundle_id <BUNDLE_ID>`\n    title: Additional options for `altool` command\n- itms_upload_parameters: \"\"\n  opts:\n    category: Deprecated\n    description: |-\n      `deliver` uses the iTunes Transporter to upload metadata and binaries.\n      If you are behind a firewall, you can specify a different transporter protocol using this input.\n      Read more on Apple [Transporter User Guide](https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126).\n    title: Transporter delivery method\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.3.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-01-13T16:15:00.401393468+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 270e924c3b9dffc483318c4f8421ba7410fab5af\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.4.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-03-10T13:24:50.744765834+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: ad2a52e351f81ece7f42e8086a6b8d47304edf40\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: \"The App's *Team Name* on iTunes Connect.\\n\\nThis field are required\n      when using iTunes Connect account \\nlinked to multiple publish team.\"\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.4.1/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-04-13T12:03:28.671533666+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 1b65f350176e3d5c9dc11057b39b16c6ad139dca\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field are required when using iTunes Connect account\n      linked to multiple publish team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.5.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/KrauseFx/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-05-03T11:53:44.745224876+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: c63d2ef589a7697df5157de69b4d2f350ad6675b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field are required when using iTunes Connect account\n      linked to multiple publish team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.5.1/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-05-18T18:19:19.460831292+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 2db8ba5e6b35a3b18d9eade4d910749a93099095\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field are required when using iTunes Connect account\n      linked to multiple publish team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.6.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-05-25T15:01:42.710643985+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 387f067a52dfc8e0d2a829f076d313fa5a51d75c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.6.1/step.yml",
    "content": "title: Deploy to iTunes Connect (with Deliver)\nsummary: Upload the archive to iTunes Connect and you can also submit it to TestFlight\n  Beta Testing\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-08-08T09:34:22.266724391+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 5b14303278577f69fa4385d643dbfb0b2ee8a8cb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.6.2/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-09-21T16:53:46.456798614+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 604a2b6c005eee99f35ae23186e26dc71d93967b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight Beta Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight Beta Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight Beta Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight Beta Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight Beta Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.6.3/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-11-24T12:15:56.691184954+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 611b42b56f4e5a6e7246aa8a32bbe5f9c59fc138\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    is_required: false\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.7.0/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-12-06T14:06:02.116883827+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 40483dde90c7d65b9ace8ed7a0b4d5c62f21751a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata -skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.7.1/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-12-12T17:03:33.771244644+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 029c363f8371193fc0d0a8c733861f009d8ee87f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata -skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.7.2/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-12-16T13:37:19.414140708+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: a79d39776735e9459d7785311bb8fc37561f7355\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata -skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.7.3/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-12-19T16:42:26.446039506+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 200fff25f724e861b1e806b0a99c0cb105d175e6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata -skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.8.0/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2016-12-28T23:55:31.285542698+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 630ec47567cd7a9730b52ebd4836d334dcb4ec9c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata -skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.8.1/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-01-16T13:23:47.632108472+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 5525278edcb581289558080a0450713060ba5de6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.8.2/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-01-25T15:26:39.51047109+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 2e68b80b1e536fb822267f900384ddf7eca61ea6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.9.2/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-04-25T16:24:52.964497471+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: fc0aaf08dcb23d6549420a86abc766a0741b8182\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.9.4/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-07-05T17:26:07.761575005+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 89c296881c4c0bea0c90979b6b385c91faf79158\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/2.9.5/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Deliver)\nsummary: Upload the archive to iTunes Connect / TestFlight and you can also submit\n  it to TestFlight Beta Testing\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Deliver](https://github.com/fastlane/fastlane/tree/master/deliver)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues\npublished_at: 2017-09-29T13:28:26.803283045+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver.git\n  commit: 032a449d28ee39dd7d396386d97973d8c6e8257a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: IPA path\n- opts:\n    description: Path of the PKG file, to be deployed to iTunes Connect\n    summary: \"\"\n    title: PKG path\n  pkg_path: $BITRISE_PKG_PATH\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      This input or `bundle_id` is required\n\n      Open the **App's page on iTunes Connect**,\n      click on **App Information**, scroll down to the *General Information* section,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n- bundle_id: \"\"\n  opts:\n    description: |-\n      The App's *Bundle ID* on iTunes Connect.\n\n      This input or app_id is required\n    summary: \"\"\n    title: 'iTunes Connect: App Bundle ID'\n- opts:\n    description: |\n      Wait for the submission to be processed and then\n      enable **TestFlight External Testing** for this specific version?\n\n      If this option is disabled then this step won't wait\n      for the new version to be processed on iTunes Connect\n      and won't enable it for *TestFlight External Testing* automatically.\n\n      *Enabling this option will wait for the submission to be\n      processed which might take a couple of minutes after the\n      new version is deployed to iTunes Connect*.\n\n      **NOTE:** if this option is enabled then this step will\n      fail if it can't enable TestFlight External Testing for the\n      version, even if the version was successfully uploaded\n      to iTunes Connect and only the TestFlight External Testing\n      submission failed.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Submit for TestFlight External Testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  submit_for_beta: \"no\"\n- opts:\n    description: |\n      Flag to skip uploading the appstore metadata.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Metadata?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_metadata: \"yes\"\n- opts:\n    description: |\n      Flag to skip uploading changes to appstore screenshots.\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Skip Screenshots?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  skip_screenshots: \"yes\"\n- opts:\n    description: |-\n      The App's *Team ID* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_name` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team ID'\n  team_id: \"\"\n- opts:\n    description: |-\n      The App's *Team Name* on iTunes Connect.\n\n      This field is required when using iTunes Connect account\n      linked to multiple publish team.\n\n      Use this input or `team_id` to specify the team.\n    summary: \"\"\n    title: 'iTunes Connect: Team name'\n  team_name: \"\"\n- options: null\n  opts:\n    description: |-\n      Options added to the end of the `deliver` call.\n\n      If you want to add more options, list that separated by space character.\n      Example: `--skip_metadata --skip_screenshots`\n    summary: \"\"\n    title: ' Additional options for `deliver` call'\n- opts:\n    description: |-\n      Should the step use the latest version of `deliver` gem,\n      or the preinstalled one?\n    is_required: true\n    summary: \"\"\n    title: Update deliver gem\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_deliver: \"yes\"\n- opts:\n    description: The platform will be delivered to iTunes Connect.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - ios\n    - osx\n    - appletvos\n  platform: ios\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-deliver/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-shenzhen/2.0.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Shenzhen)\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Shenzhen](https://github.com/nomad/shenzhen)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nsummary: Upload the archive to iTunes Connect with a simple Step\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen/issues\npublished_at: 2015-09-08T12:12:30.332600755+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen.git\n  commit: a87ddc4e7372b937a35db09f8112000b3334db40\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-shenzhen/2.1.0/step.yml",
    "content": "title: Deploy to iTunes Connect (with Shenzhen)\nsummary: Deploy to iTunes Connect (with Shenzhen)\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Shenzhen](https://github.com/nomad/shenzhen)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen/issues\npublished_at: 2015-10-29T11:21:34.248360251+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen.git\n  commit: c265da7a93673c3f5b82574e357be9e2b65ea7e8\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-shenzhen/2.1.1/step.yml",
    "content": "title: Deploy to iTunes Connect (with Shenzhen)\nsummary: Deploy to iTunes Connect (with Shenzhen)\ndescription: |-\n  Deploy to iTunes Connect, using the\n  fantastic [Shenzhen](https://github.com/nomad/shenzhen)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen/issues\npublished_at: 2015-12-11T18:16:43.309379487+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen.git\n  commit: 65da3dc6d0c85de003f1e277faf890b1aa38d049\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-shenzhen/2.1.2/step.yml",
    "content": "title: Deploy to iTunes Connect / TestFlight (with Shenzhen)\nsummary: Deploy to iTunes Connect / TestFlight (with Shenzhen)\ndescription: |-\n  Deploy to iTunes Connect / TestFlight, using the\n  fantastic [Shenzhen](https://github.com/nomad/shenzhen)\n  Ruby gem.\n\n  **If this is the very first build** of the app\n  you try to deploy to iTunes Connect / TestFlight then you might want to upload the first\n  build manually to make sure it fulfills the initial iTunes Connect / TestFlight submission\n  verification process.\n\n  **Be advised** that this\n  step uses a well maintained, open source tool which\n  uses *undocumented and unsupported APIs* (because the current\n  iTunes Connect / TestFlight platform does not have a documented and supported API)\n  to perform the deployment.\n  This means that when the API changes\n  **this step might fail until the tool is updated**.\n\n  ## Setup guide and notes\n\n  * Register an app on iTunes Connect / TestFlight, on the **My Apps** page. Click on the *plus sign* and select the **New iOS App** option. This requires an **admin** account.\n  * Requires an **App Store iOS distibution Provisioning Profile**\n  * Every build which you want to push to iTunes Connect / TestFlight have to have a **unique build and version number** pair (*increment either or both before a new deploy to iTunes Connect*)\nwebsite: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsource_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen\nsupport_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen/issues\npublished_at: 2016-09-21T16:57:47.174402215+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-shenzhen.git\n  commit: 8b1c80bae66a30090fe54fdb31405076eba7604e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path of the IPA file, to be deployed to iTunes Connect\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- itunescon_user: \"\"\n  opts:\n    description: |-\n      Login Apple ID (email) for the iTunes Connect site.\n\n      *Make sure that this email is verified,\n      your Apple ID cannot be used until you verify it\n      on Apple's website!*\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: User Apple ID (email)'\n- opts:\n    description: |-\n      Password for the specified User Apple ID.\n\n      **Note:** if your password\n      contains special characters\n      and you experience problems, please\n      consider changing your password\n      to something with only\n      alphanumeric characters.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: Password'\n  password: \"\"\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *Apple ID* on iTunes Connect.\n\n      Open the **App's page on iTunes Connect**,\n      click on **More**, click on *About this app*,\n      copy the *Apple ID*'s value from here (numeric, like 846814360)\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: 'iTunes Connect: App Apple ID'\n"
  },
  {
    "path": "steps/deploy-to-itunesconnect-shenzhen/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, use [Deploy to App Store Connect - Application Loader](https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-application-loader) step instead.\nmaintainer: bitrise\nremoval_date: \"2018-09-20\"\n"
  },
  {
    "path": "steps/deploy-to-updraft/0.0.1/step.yml",
    "content": "title: Deploy to Updraft\nsummary: |\n  Distribute your app's builds to your team and testers\ndescription: |\n  This step will help you to upload your app's builds to Updraft. For more information please reach [Updraft](https://getupdraft.com) site.\nwebsite: https://github.com/appswithlove/bitrise-step-deploy-to-updraft\nsource_code_url: https://github.com/appswithlove/bitrise-step-deploy-to-updraft\nsupport_url: https://github.com/appswithlove/bitrise-step-deploy-to-updraft/issues\npublished_at: 2024-08-27T15:48:04.087667+04:00\nsource:\n  git: https://github.com/appswithlove/bitrise-step-deploy-to-updraft.git\n  commit: 8cfaf8f93f32beaf5de690fb1124650cc33968c1\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API Key you will find in your Profile.\n    title: Updraft API_KEY\n- app_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The App Key you will find on the application overview. The App key differs\n      for each environment.\n    title: Updraft APP_KEY\n- app_path: \"\"\n  opts:\n    description: |\n      Path to app's binary file (IPA/APK/AAB) to upload.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: Path to app's binary file (IPA/APK/AAB) to upload\n    title: App file path\n- opts:\n    description: |\n      Message to show on build download page\n    is_required: false\n    summary: Release notes\n    title: Release notes\n  release_notes: \"\"\noutputs:\n- UPDRAFT_DEPLOY_STEP_OUTPUT: null\n  opts:\n    description: \"JSON reponse of Updraft backend \\n\"\n    summary: Deploy Updraft step output json\n    title: Deploy Updraft step output\n"
  },
  {
    "path": "steps/deploy-to-updraft/0.0.2/step.yml",
    "content": "title: Deploy to Updraft\nsummary: |\n  Distribute your app's builds (ipa/apk/aab) to your team and testers\ndescription: \"This step will help you to upload your app versions to [Updraft](https://getupdraft.com)\n  for further app distribution. \\nUpdraft is a comprehensive platform for app distribution\n  and beta testing, especially for iOS and Android applications. It supports developers\n  in managing app deployments, handling app beta releases, and facilitating feedback\n  collection from testers. \\n\\nKey features include:\\n- App Management: Users can\n  manage all app settings from a centralized dashboard, including adding applications\n  to a project, adding deployment environment, upload app versions, manage settings\\n-\n  App Distribution: The platform allows easy distribution of apps through various\n  channels like email notifications, QR code installations, or public link installation.\n  Testers and Groups can be added to each app release. It also supports auto-updates\n  via an in-app notification system if the Updraft SDK is integrated.\\n- Build Management:\n  Updraft simplifies the process of uploading, resigning, and managing different iOS\n  and Android app versions, helping ensure that the right versions reach the right\n  testers and members.\\n- Resigning: Updraft allows you to resign iOS apps with new\n  distribution certificates and provisioning profiles. For Android you can add your\n  keystore and resign your uploaded .aab files with your keystore to ensure your play\n  store release will get accepeted.\\n- Integration Support: The platform integrates\n  with multiple CI/CD tools and third-party services like Slack, Microsoft Teams,\n  Gitlab, Teamcity and Jenkins, making it easier to incorporate into existing workflows.\n  Updraft also has available Plugins for Fastlane and Gradle.\\n\\nThese features make\n  GetUpdraft a robust solution for teams looking to streamline their internal app\n  testing and app distribution processes.\\n\\nUseful links:\\n- [Updraft](https://getupdraft.com)\\n-\n  [Updraft Documentation](https://docs.getupdraft.com)\\n\"\nwebsite: https://github.com/appswithlove/bitrise-step-deploy-to-updraft\nsource_code_url: https://github.com/appswithlove/bitrise-step-deploy-to-updraft\nsupport_url: https://github.com/appswithlove/bitrise-step-deploy-to-updraft/issues\npublished_at: 2024-09-03T13:33:50.831795+04:00\nsource:\n  git: https://github.com/appswithlove/bitrise-step-deploy-to-updraft.git\n  commit: b017aacf8ea97b9e2ecae61669f23e95630a2b2f\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API Key you will find in your Profile.\n    title: Updraft API_KEY\n- app_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The App Key you will find on the application overview. The App key differs\n      for each environment.\n    title: Updraft APP_KEY\n- app_path: \"\"\n  opts:\n    description: |\n      Path to app's binary file (IPA/APK/AAB) to upload.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: Path to app's binary file (IPA/APK/AAB) to upload\n    title: App file path\n- opts:\n    description: |\n      Message to show on build download page\n    is_required: false\n    summary: Release notes\n    title: Release notes\n  release_notes: \"\"\noutputs:\n- UPDRAFT_DEPLOY_STEP_OUTPUT: null\n  opts:\n    description: \"JSON reponse of Updraft backend \\n\"\n    summary: Deploy Updraft step output json\n    title: Deploy Updraft step output\n"
  },
  {
    "path": "steps/deploy-to-updraft/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/1.0.0/step.yml",
    "content": "title: DeployGate Upload\nsummary: |\n  Distribute your in-development iOS/Android apps to your developers or testers\ndescription: |\n  This is a step to upload your iOS/Android application to DeployGate. DeployGate enable to share in-development apps with others instantly. For more details, please read references in [DeployGate.com](https://deploygate.com/?locale=en)\nwebsite: https://github.com/DeployGate/upload-app-bitrise-step\nsource_code_url: https://github.com/DeployGate/upload-app-bitrise-step\nsupport_url: https://github.com/DeployGate/upload-app-bitrise-step/issues\npublished_at: 2018-08-23T16:11:24.697097562+09:00\nsource:\n  git: https://github.com/DeployGate/upload-app-bitrise-step.git\n  commit: fc26112e595aa5c062028d2abf982437a67124fc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  apt_get:\n  - name: git\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: The authorization token to be used when uploading app\n    is_required: true\n    summary: User's API Key or Organization's API Key\n    title: 'DeployGate: API Key'\n- opts:\n    description: |\n      The owner name of this application\n    is_required: true\n    summary: User name or Organization name\n    title: 'DeployGate: Owner Name'\n  owner_name: \"\"\n- app_path: \"\"\n  opts:\n    description: |\n      App's binary file (IPA/APK) to be uploaded.\n      $BITRISE_APK_PATH, $BITRISE_IPA_PATH, and so on.\n    is_required: true\n    summary: App's binary file (IPA/APK) to be uploaded\n    title: App file path\n- opts:\n    description: |\n      For newly uploaded apps only, specify the app's name and icon privacy settings to either private or public.\n      This is just only for visibility on your apps list in profile page, not for allowing download or install by anonymous.\n      Download or install apps is allowd only your app's member or invitee who knows your generated public link.\n      By default, Personal Free Plans are set to public, and all other plans are set to private.\n      This setting does not apply for updates, and any changes made will be ignored.\n    is_required: true\n    summary: The viisibility of this app in your profile page\n    title: 'DeployGate: App Visibility'\n    value_options:\n    - public\n    - private\n  visibility: private\n- message: \"\"\n  opts:\n    description: A short message to explain this version\n    is_required: false\n    summary: A short message to explain this version\n    title: 'DeployGate: Short Message'\n- distribution_key: \"\"\n  opts:\n    description: |\n      By specifying the distribution page's hash, that distribution page will be updated simultaneously.\n      The \"xxxx\" portion of the distributed page's URL like https://deploygate.com/distributions/xxxx\n    is_required: false\n    summary: The distribution key to be updated\n    title: 'DeployGate: Distribution Key'\n- distribution_name: \"\"\n  opts:\n    description: \"Specify the name of the updated distribution page. \\nIf none exists,\n      a new distribution page will be created. \\nPossible uses include creating distribution\n      pages for each Git branch name.\\n\"\n    is_required: false\n    summary: The distribution name to be created or be updated\n    title: 'DeployGate: Distribution Name'\n- opts:\n    description: Message displayed during distribution page app updates\n    is_required: false\n    summary: Message displayed during distribution page app updates\n    title: 'DeployGate: Release Note'\n  release_note: \"\"\n- disable_notify: \"false\"\n  opts:\n    description: (iOS only) A setting of true disables Push notification emails.\n    is_required: false\n    summary: (iOS only) A setting of true disables Push notification emails.\n    title: 'DeployGate: Disable Notify'\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON: null\n  opts:\n    description: The raw json which Upload API has returned\n    summary: The raw json which Upload API has returned\n    title: 'DeployGate: API result json'\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/1.0.1/step.yml",
    "content": "title: DeployGate Upload\nsummary: |\n  Distribute your in-development iOS/Android apps to your developers or testers\ndescription: |\n  This is a step to upload your iOS/Android application to DeployGate. DeployGate enable to share in-development apps with others instantly. For more details, please read references in [DeployGate.com](https://deploygate.com/?locale=en)\nwebsite: https://github.com/DeployGate/upload-app-bitrise-step\nsource_code_url: https://github.com/DeployGate/upload-app-bitrise-step\nsupport_url: https://github.com/DeployGate/upload-app-bitrise-step/issues\npublished_at: 2018-09-27T15:34:25.938975453+09:00\nsource:\n  git: https://github.com/DeployGate/upload-app-bitrise-step.git\n  commit: 35e778d9cf915dd42e30ad6ca3b8cf97336b71e6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: The authorization token to be used when uploading app\n    is_required: true\n    is_sensitive: true\n    summary: User's API Key or Organization's API Key\n    title: 'DeployGate: API Key'\n- opts:\n    description: |\n      The owner name of this application\n    is_required: true\n    summary: User name or Organization name\n    title: 'DeployGate: Owner Name'\n  owner_name: \"\"\n- app_path: \"\"\n  opts:\n    description: |\n      App's binary file (IPA/APK) to be uploaded.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: App's binary file (IPA/APK) to be uploaded\n    title: App file path\n- opts:\n    description: |\n      For newly uploaded apps only, specify the app's name and icon privacy settings to either private or public.\n      This is just only for visibility on your apps list in profile page, not for allowing download or install by anonymous.\n      Download or install apps is allowd only your app's member or invitee who knows your generated public link.\n      By default, Personal Free Plans are set to public, and all other plans are set to private.\n      This setting does not apply for updates, and any changes made will be ignored.\n    is_required: true\n    summary: The visibility of this app in your profile page\n    title: 'DeployGate: App Visibility'\n    value_options:\n    - public\n    - private\n  visibility: private\n- message: \"\"\n  opts:\n    description: A short message to explain this version\n    is_required: false\n    summary: A short message to explain this version\n    title: 'DeployGate: Short Message'\n- distribution_key: \"\"\n  opts:\n    description: |\n      By specifying the distribution page's hash, that distribution page will be updated simultaneously.\n      The \"xxxx\" portion of the distributed page's URL like https://deploygate.com/distributions/xxxx\n    is_required: false\n    summary: The distribution key to be updated\n    title: 'DeployGate: Distribution Key'\n- distribution_name: \"\"\n  opts:\n    description: \"Specify the name of the updated distribution page. \\nIf none exists,\n      a new distribution page will be created. \\nPossible uses include creating distribution\n      pages for each Git branch name.\\n\"\n    is_required: false\n    summary: The distribution name to be created or be updated\n    title: 'DeployGate: Distribution Name'\n- opts:\n    description: Message displayed during distribution page app updates\n    is_required: false\n    summary: Message displayed during distribution page app updates\n    title: 'DeployGate: Release Note'\n  release_note: \"\"\n- disable_notify: \"false\"\n  opts:\n    description: (iOS only) A setting of true disables Push notification emails.\n    is_required: false\n    summary: (iOS only) A setting of true disables Push notification emails.\n    title: 'DeployGate: Disable Notify'\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON: null\n  opts:\n    description: The raw json which Upload API has returned\n    summary: The raw json which Upload API has returned\n    title: 'DeployGate: API result json'\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/1.1.0/step.yml",
    "content": "title: DeployGate Upload\nsummary: |\n  Distribute your in-development iOS/Android apps to your developers or testers\ndescription: |\n  This is a step to upload your iOS/Android application to DeployGate. DeployGate enable to share in-development apps with others instantly. For more details, please read references in [DeployGate.com](https://deploygate.com/?locale=en)\nwebsite: https://github.com/DeployGate/upload-app-bitrise-step\nsource_code_url: https://github.com/DeployGate/upload-app-bitrise-step\nsupport_url: https://github.com/DeployGate/upload-app-bitrise-step/issues\npublished_at: 2020-02-06T17:33:38.908743+09:00\nsource:\n  git: https://github.com/DeployGate/upload-app-bitrise-step.git\n  commit: 3339182d2c244b37ef42e66ca1a349b7d5112de0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: The authorization token to be used when uploading app\n    is_required: true\n    is_sensitive: true\n    summary: User's API Key or Organization's API Key\n    title: 'DeployGate: API Key'\n- opts:\n    description: |\n      The owner name of this application\n    is_required: true\n    summary: User name or Organization name\n    title: 'DeployGate: Owner Name'\n  owner_name: \"\"\n- app_path: \"\"\n  opts:\n    description: |\n      App's binary file (IPA/APK/AAB) to be uploaded.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: App's binary file (IPA/APK/AAB) to be uploaded\n    title: App file path\n- opts:\n    description: |\n      For newly uploaded apps only, specify the app's name and icon privacy settings to either private or public.\n      This is just only for visibility on your apps list in profile page, not for allowing download or install by anonymous.\n      Download or install apps is allowd only your app's member or invitee who knows your generated public link.\n      By default, Personal Free Plans are set to public, and all other plans are set to private.\n      This setting does not apply for updates, and any changes made will be ignored.\n    is_required: true\n    summary: The visibility of this app in your profile page\n    title: 'DeployGate: App Visibility'\n    value_options:\n    - public\n    - private\n  visibility: private\n- message: \"\"\n  opts:\n    description: A short message to explain this version\n    is_required: false\n    summary: A short message to explain this version\n    title: 'DeployGate: Short Message'\n- distribution_key: \"\"\n  opts:\n    description: |\n      By specifying the distribution page's hash, that distribution page will be updated simultaneously.\n      The \"xxxx\" portion of the distributed page's URL like https://deploygate.com/distributions/xxxx\n    is_required: false\n    summary: The distribution key to be updated\n    title: 'DeployGate: Distribution Key'\n- distribution_name: \"\"\n  opts:\n    description: \"Specify the name of the updated distribution page. \\nIf none exists,\n      a new distribution page will be created. \\nPossible uses include creating distribution\n      pages for each Git branch name.\\n\"\n    is_required: false\n    summary: The distribution name to be created or be updated\n    title: 'DeployGate: Distribution Name'\n- opts:\n    description: Message displayed during distribution page app updates\n    is_required: false\n    summary: Message displayed during distribution page app updates\n    title: 'DeployGate: Release Note'\n  release_note: \"\"\n- disable_notify: \"false\"\n  opts:\n    description: (iOS only) A setting of true disables Push notification emails.\n    is_required: false\n    summary: (iOS only) A setting of true disables Push notification emails.\n    title: 'DeployGate: Disable Notify'\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON: null\n  opts:\n    description: The raw json which Upload API has returned\n    summary: The raw json which Upload API has returned\n    title: 'DeployGate: API result json'\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/1.1.1/step.yml",
    "content": "title: DeployGate Upload\nsummary: |\n  Distribute your in-development iOS/Android apps to your developers or testers\ndescription: |\n  This is a step to upload your iOS/Android application to DeployGate. DeployGate enable to share in-development apps with others instantly. For more details, please read references in [DeployGate.com](https://deploygate.com/?locale=en)\nwebsite: https://github.com/DeployGate/upload-app-bitrise-step\nsource_code_url: https://github.com/DeployGate/upload-app-bitrise-step\nsupport_url: https://github.com/DeployGate/upload-app-bitrise-step/issues\npublished_at: 2020-07-31T14:05:17.599974+09:00\nsource:\n  git: https://github.com/DeployGate/upload-app-bitrise-step.git\n  commit: 5a8775d1882942f7fe67ec5d694389c3ed4f85ec\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: The authorization token to be used when uploading app\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User's API Key or Organization's API Key\n    title: 'DeployGate: API Key'\n- opts:\n    description: |\n      The owner name of this application\n    is_required: true\n    summary: User name or Organization name\n    title: 'DeployGate: Owner Name'\n  owner_name: \"\"\n- app_path: \"\"\n  opts:\n    description: |\n      App's binary file (IPA/APK/AAB) to be uploaded.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: App's binary file (IPA/APK/AAB) to be uploaded\n    title: App file path\n- opts:\n    description: |\n      For newly uploaded apps only, specify the app's name and icon privacy settings to either private or public.\n      This is just only for visibility on your apps list in profile page, not for allowing download or install by anonymous.\n      Download or install apps is allowd only your app's member or invitee who knows your generated public link.\n      By default, Personal Free Plans are set to public, and all other plans are set to private.\n      This setting does not apply for updates, and any changes made will be ignored.\n    is_required: true\n    summary: The visibility of this app in your profile page\n    title: 'DeployGate: App Visibility'\n    value_options:\n    - public\n    - private\n  visibility: private\n- message: \"\"\n  opts:\n    description: A short message to explain this version\n    is_required: false\n    summary: A short message to explain this version\n    title: 'DeployGate: Short Message'\n- distribution_key: \"\"\n  opts:\n    description: |\n      By specifying the distribution page's hash, that distribution page will be updated simultaneously.\n      The \"xxxx\" portion of the distributed page's URL like https://deploygate.com/distributions/xxxx\n    is_required: false\n    summary: The distribution key to be updated\n    title: 'DeployGate: Distribution Key'\n- distribution_name: \"\"\n  opts:\n    description: \"Specify the name of the updated distribution page. \\nIf none exists,\n      a new distribution page will be created. \\nPossible uses include creating distribution\n      pages for each Git branch name.\\n\"\n    is_required: false\n    summary: The distribution name to be created or be updated\n    title: 'DeployGate: Distribution Name'\n- opts:\n    description: Message displayed during distribution page app updates\n    is_required: false\n    summary: Message displayed during distribution page app updates\n    title: 'DeployGate: Release Note'\n  release_note: \"\"\n- disable_notify: \"false\"\n  opts:\n    description: (iOS only) A setting of true disables Push notification emails.\n    is_required: false\n    summary: (iOS only) A setting of true disables Push notification emails.\n    title: 'DeployGate: Disable Notify'\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON: null\n  opts:\n    description: The raw json which Upload API has returned\n    summary: The raw json which Upload API has returned\n    title: 'DeployGate: API result json'\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/1.1.2/step.yml",
    "content": "title: DeployGate Upload\nsummary: |\n  Distribute your in-development iOS/Android apps to your developers or testers\ndescription: |\n  This is a step to upload your iOS/Android application to DeployGate. DeployGate enable to share in-development apps with others instantly. For more details, please read references in [DeployGate.com](https://deploygate.com/?locale=en)\nwebsite: https://github.com/DeployGate/upload-app-bitrise-step\nsource_code_url: https://github.com/DeployGate/upload-app-bitrise-step\nsupport_url: https://github.com/DeployGate/upload-app-bitrise-step/issues\npublished_at: 2022-05-13T11:45:03.558427+09:00\nsource:\n  git: https://github.com/DeployGate/upload-app-bitrise-step.git\n  commit: 45373ddadac3e3d019f24011fcb2d375a747f457\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: The authorization token to be used when uploading app\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User's API Key or Organization's API Key\n    title: 'DeployGate: API Key'\n- opts:\n    description: |\n      The owner name of this application\n    is_required: true\n    summary: User name or Organization name\n    title: 'DeployGate: Owner Name'\n  owner_name: \"\"\n- app_path: \"\"\n  opts:\n    description: |\n      App's binary file (IPA/APK/AAB) to be uploaded.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: App's binary file (IPA/APK/AAB) to be uploaded\n    title: App file path\n- message: \"\"\n  opts:\n    description: A short message to explain this version\n    is_required: false\n    summary: A short message to explain this version\n    title: 'DeployGate: Short Message'\n- distribution_key: \"\"\n  opts:\n    description: |\n      By specifying the distribution page's hash, that distribution page will be updated simultaneously.\n      The \"xxxx\" portion of the distributed page's URL like https://deploygate.com/distributions/xxxx\n    is_required: false\n    summary: The distribution key to be updated\n    title: 'DeployGate: Distribution Key'\n- distribution_name: \"\"\n  opts:\n    description: \"Specify the name of the updated distribution page. \\nIf none exists,\n      a new distribution page will be created. \\nPossible uses include creating distribution\n      pages for each Git branch name.\\n\"\n    is_required: false\n    summary: The distribution name to be created or be updated\n    title: 'DeployGate: Distribution Name'\n- opts:\n    description: Message displayed during distribution page app updates\n    is_required: false\n    summary: Message displayed during distribution page app updates\n    title: 'DeployGate: Release Note'\n  release_note: \"\"\n- disable_notify: \"false\"\n  opts:\n    description: (iOS only) A setting of true disables Push notification emails.\n    is_required: false\n    summary: (iOS only) A setting of true disables Push notification emails.\n    title: 'DeployGate: Disable Notify'\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON: null\n  opts:\n    description: The raw json which Upload API has returned\n    summary: The raw json which Upload API has returned. Available iff the request\n      has been sent to DeployGate server.\n    title: 'DeployGate: API result json'\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/1.1.3/step.yml",
    "content": "title: DeployGate Upload\nsummary: |\n  Distribute your in-development iOS/Android apps to your developers or testers\ndescription: |\n  This is a step to upload your iOS/Android application to DeployGate. DeployGate enable to share in-development apps with others instantly. For more details, please read references in [DeployGate.com](https://deploygate.com/?locale=en)\nwebsite: https://github.com/DeployGate/upload-app-bitrise-step\nsource_code_url: https://github.com/DeployGate/upload-app-bitrise-step\nsupport_url: https://github.com/DeployGate/upload-app-bitrise-step/issues\npublished_at: 2022-07-01T16:08:03.005062+09:00\nsource:\n  git: https://github.com/DeployGate/upload-app-bitrise-step.git\n  commit: f32a75e4ee2fafde45742d0cc8631826d2bae477\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: The authorization token to be used when uploading app\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User's API Key or Organization's API Key\n    title: 'DeployGate: API Key'\n- opts:\n    description: |\n      The owner name of this application\n    is_required: true\n    summary: User name or Organization name\n    title: 'DeployGate: Owner Name'\n  owner_name: \"\"\n- app_path: \"\"\n  opts:\n    description: |\n      App's binary file (IPA/APK/AAB) to be uploaded.\n      $BITRISE\\_APK\\_PATH, $BITRISE\\_IPA\\_PATH, and so on.\n    is_required: true\n    summary: App's binary file (IPA/APK/AAB) to be uploaded\n    title: App file path\n- message: \"\"\n  opts:\n    description: A short message to explain this version\n    is_required: false\n    summary: A short message to explain this version\n    title: 'DeployGate: Short Message'\n- distribution_key: \"\"\n  opts:\n    description: |\n      By specifying the distribution page's hash, that distribution page will be updated simultaneously.\n      The \"xxxx\" portion of the distributed page's URL like https://deploygate.com/distributions/xxxx\n    is_required: false\n    summary: The distribution key to be updated\n    title: 'DeployGate: Distribution Key'\n- distribution_name: \"\"\n  opts:\n    description: \"Specify the name of the updated distribution page. \\nIf none exists,\n      a new distribution page will be created. \\nPossible uses include creating distribution\n      pages for each Git branch name.\\n\"\n    is_required: false\n    summary: The distribution name to be created or be updated\n    title: 'DeployGate: Distribution Name'\n- opts:\n    description: Message displayed during distribution page app updates\n    is_required: false\n    summary: Message displayed during distribution page app updates\n    title: 'DeployGate: Release Note'\n  release_note: \"\"\n- disable_notify: \"false\"\n  opts:\n    description: (iOS only) A setting of true disables Push notification emails.\n    is_required: false\n    summary: (iOS only) A setting of true disables Push notification emails.\n    title: 'DeployGate: Disable Notify'\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON: null\n  opts:\n    description: The raw json which Upload API has returned\n    summary: The raw json which Upload API has returned. Available iff the request\n      has been sent to DeployGate server.\n    title: 'DeployGate: API result json'\n"
  },
  {
    "path": "steps/deploygate--upload-app-bitrise-step/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/detekt/1.0.0/step.yml",
    "content": "title: detekt\nsummary: |\n  Runs detekt static code analysis for Kotlin\ndescription: |\n  Runs detekt, a static code analysis tool for the Kotlin programming language.\nwebsite: https://github.com/misaelmt/bitrise-step-detekt\nsource_code_url: https://github.com/misaelmt/bitrise-step-detekt\nsupport_url: https://github.com/misaelmt/bitrise-step-detekt/issues\npublished_at: 2018-03-07T17:47:02.984966415-05:00\nsource:\n  git: https://github.com/misaelmt/bitrise-step-detekt.git\n  commit: 17608029bb094e5226e830a4ab40deaf8b1973aa\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Input path to analyze, can either be a directory or a single Kotlin\n      file\n    is_required: true\n    summary: Path to analyze (path/to/project)\n    title: Path to analyze\n  path_to_analyze: .\n"
  },
  {
    "path": "steps/detekt/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/0.0.10/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2025-04-08T16:43:49.443528+01:00\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: 532d225935181acb489533e6cfc8f0f748c14950\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test seperated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- additional_app_binary_ids: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app binary IDs\n    title: Additional App Binary IDs\n- additional_app_files: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app file paths\n    title: Additional App Files\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Device orientation in degrees\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use x86 architecture for Android emulation\n    title: x86 Architecture\n    value_options:\n    - \"true\"\n    - \"false\"\n  x86_arch: \"false\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Skip Chrome browser onboarding screens when running tests'\n    title: Skip Chrome Onboarding\n    value_options:\n    - \"true\"\n    - \"false\"\n  skip_chrome_onboarding: \"false\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: '[experimental] The type of runner to use - note: anything other than\n      default will incur premium pricing tiers'\n    title: Runner Type\n  runner_type: \"\"\n- opts:\n    default_value: junit\n    is_expand: true\n    is_required: false\n    summary: Generate a report in the specified format\n    title: Report Format\n    value_options:\n    - junit\n    - html\n  report: junit\n- ignore_sha_check: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Ignore the SHA hash check and upload the binary regardless of whether\n      it already exists (not recommended)\n    title: Ignore SHA Check\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom API URL for devicecloud.dev (optional)\n    title: API URL\noutputs:\n- DEVICE_CLOUD_CONSOLE_URL: null\n  opts:\n    summary: URL to view the test results in the Device Cloud console\n    title: Device Cloud Console URL\n- DEVICE_CLOUD_FLOW_RESULTS: null\n  opts:\n    summary: JSON array containing results for each flow, including name, status,\n      and any errors\n    title: Flow Results\n- DEVICE_CLOUD_UPLOAD_STATUS: null\n  opts:\n    summary: Status of the test run (PENDING, RUNNING, PASSED, FAILED, CANCELLED)\n    title: Test Run Status\n- DEVICE_CLOUD_APP_BINARY_ID: null\n  opts:\n    summary: ID of the uploaded app binary in Device Cloud\n    title: App Binary ID\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/0.0.11/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2025-05-07T19:30:16.200477+01:00\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: 638ca2512751f8844b8515de073519c093aeb008\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test seperated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- additional_app_binary_ids: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app binary IDs\n    title: Additional App Binary IDs\n- additional_app_files: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app file paths\n    title: Additional App Files\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Device orientation in degrees\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use x86 architecture for Android emulation\n    title: x86 Architecture\n    value_options:\n    - \"true\"\n    - \"false\"\n  x86_arch: \"false\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Skip Chrome browser onboarding screens when running tests'\n    title: Skip Chrome Onboarding\n    value_options:\n    - \"true\"\n    - \"false\"\n  skip_chrome_onboarding: \"false\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: '[experimental] The type of runner to use - note: anything other than\n      default will incur premium pricing tiers'\n    title: Runner Type\n  runner_type: \"\"\n- opts:\n    default_value: junit\n    is_expand: true\n    is_required: false\n    summary: Generate a report in the specified format\n    title: Report Format\n    value_options:\n    - junit\n    - html\n  report: junit\n- ignore_sha_check: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Ignore the SHA hash check and upload the binary regardless of whether\n      it already exists (not recommended)\n    title: Ignore SHA Check\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom API URL for devicecloud.dev (optional)\n    title: API URL\n- debug: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Enable detailed debug logging for troubleshooting issues\n    title: Debug Mode\n    value_options:\n    - \"true\"\n    - \"false\"\n- json: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: 'Output results in JSON format - note: will always provide exit code\n      0'\n    title: JSON Output\n    value_options:\n    - \"true\"\n    - \"false\"\n- json_file: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Write JSON output to a file with name <run_name>_dcd.json or <upload_id>_dcd.json\n      if no name is provided\n    title: JSON File Output\n    value_options:\n    - \"true\"\n    - \"false\"\n- config: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to custom config.yaml file. If not provided, defaults to config.yaml\n      in root flows folders.\n    title: Config File\n- artifacts_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded artifacts (default: ./artifacts.zip)'\n    title: Artifacts Path\noutputs:\n- DEVICE_CLOUD_CONSOLE_URL: null\n  opts:\n    summary: URL to view the test results in the Device Cloud console\n    title: Device Cloud Console URL\n- DEVICE_CLOUD_FLOW_RESULTS: null\n  opts:\n    summary: JSON array containing results for each flow, including name, status,\n      and any errors\n    title: Flow Results\n- DEVICE_CLOUD_UPLOAD_STATUS: null\n  opts:\n    summary: Status of the test run (PENDING, RUNNING, PASSED, FAILED, CANCELLED)\n    title: Test Run Status\n- DEVICE_CLOUD_APP_BINARY_ID: null\n  opts:\n    summary: ID of the uploaded app binary in Device Cloud\n    title: App Binary ID\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/0.0.6/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2024-11-27T12:05:53.298331Z\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: 4a4730bf487ba238818832004f075a1b7663ffc1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test seperated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- additional_app_binary_ids: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app binary IDs\n    title: Additional App Binary IDs\n- additional_app_files: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app file paths\n    title: Additional App Files\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Device orientation in degrees\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/0.0.7/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2025-01-22T09:46:20.981118Z\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: b1d2882d24bff6ad2e3e2af2dd13fb4c408a5d58\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test seperated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- additional_app_binary_ids: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app binary IDs\n    title: Additional App Binary IDs\n- additional_app_files: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app file paths\n    title: Additional App Files\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Device orientation in degrees\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use x86 architecture for Android emulation\n    title: x86 Architecture\n    value_options:\n    - \"true\"\n    - \"false\"\n  x86_arch: \"false\"\n- opts:\n    default_value: junit\n    is_expand: true\n    is_required: false\n    summary: Generate a report in the specified format\n    title: Report Format\n    value_options:\n    - junit\n    - html\n  report: junit\n- ignore_sha_check: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Ignore the SHA hash check and upload the binary regardless of whether\n      it already exists (not recommended)\n    title: Ignore SHA Check\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom API URL for devicecloud.dev (optional)\n    title: API URL\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/0.0.8/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2025-02-06T14:50:43.328482Z\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: c6bcd2e13df903dd965d964a6129f1c34addfff0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test seperated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- additional_app_binary_ids: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app binary IDs\n    title: Additional App Binary IDs\n- additional_app_files: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of additional app file paths\n    title: Additional App Files\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Device orientation in degrees\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use x86 architecture for Android emulation\n    title: x86 Architecture\n    value_options:\n    - \"true\"\n    - \"false\"\n  x86_arch: \"false\"\n- opts:\n    default_value: junit\n    is_expand: true\n    is_required: false\n    summary: Generate a report in the specified format\n    title: Report Format\n    value_options:\n    - junit\n    - html\n  report: junit\n- ignore_sha_check: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Ignore the SHA hash check and upload the binary regardless of whether\n      it already exists (not recommended)\n    title: Ignore SHA Check\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom API URL for devicecloud.dev (optional)\n    title: API URL\noutputs:\n- DEVICE_CLOUD_CONSOLE_URL: null\n  opts:\n    summary: URL to view the test results in the Device Cloud console\n    title: Device Cloud Console URL\n- DEVICE_CLOUD_FLOW_RESULTS: null\n  opts:\n    summary: JSON array containing results for each flow, including name, status,\n      and any errors\n    title: Flow Results\n- DEVICE_CLOUD_UPLOAD_STATUS: null\n  opts:\n    summary: Status of the test run (PENDING, RUNNING, PASSED, FAILED, CANCELLED)\n    title: Test Run Status\n- DEVICE_CLOUD_APP_BINARY_ID: null\n  opts:\n    summary: ID of the uploaded app binary in Device Cloud\n    title: App Binary ID\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/1.0.0/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2026-01-06T09:46:43.325525Z\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: 81841bfb66a67e82236a22684342216a17f3dd7b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test separated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- metadata: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Arbitrary key-value metadata to include with your test run, separated\n      by newlines (format: key=value)'\n    title: Metadata\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously (exit immediately without waiting for results)\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- dry_run: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Simulate the run without actually triggering the upload/test, useful\n      for debugging workflow issues\n    title: Dry Run\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- android_no_snapshot: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Force cold boot instead of using snapshot boot. Automatically\n      enabled for API 35+ but can be used to force cold boot on older API levels.'\n    title: Android No Snapshot\n    value_options:\n    - \"true\"\n    - \"false\"\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Device orientation (0 = portrait, 90 = landscape)'\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Display crosshairs for screen interactions during test\n      execution'\n    title: Show Crosshairs\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_crosshairs: \"false\"\n- maestro_chrome_onboarding: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Force Maestro-based Chrome onboarding - note: this will\n      slow your tests but can fix browser related crashes'\n    title: Maestro Chrome Onboarding\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: '[experimental] The type of runner to use - note: anything other than\n      default will incur premium pricing tiers'\n    title: Runner Type\n  runner_type: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Generate and download test reports in the specified format (allure, junit,\n      or html)\n    title: Report Format\n  report: \"\"\n- junit_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded JUnit report (requires report=junit,\n      default: ./report.xml)'\n    title: JUnit Report Path\n- allure_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded Allure report (requires report=allure,\n      default: ./report.html)'\n    title: Allure Report Path\n- html_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded HTML report (requires report=html, default:\n      ./report.html)'\n    title: HTML Report Path\n- ignore_sha_check: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Ignore the SHA hash check and upload the binary regardless of whether\n      it already exists (not recommended)\n    title: Ignore SHA Check\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom API URL for devicecloud.dev (optional)\n    title: API URL\n- debug: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Enable detailed debug logging for troubleshooting issues\n    title: Debug Mode\n    value_options:\n    - \"true\"\n    - \"false\"\n- json: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: 'Output results in JSON format - note: will always provide exit code\n      0'\n    title: JSON Output\n    value_options:\n    - \"true\"\n    - \"false\"\n- json_file: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Write JSON output to a file with name <run_name>_dcd.json or <upload_id>_dcd.json\n      if no name is provided\n    title: JSON File Output\n    value_options:\n    - \"true\"\n    - \"false\"\n- json_file_name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the JSON file (can also include relative path). Requires\n      json_file to be true.\n    title: JSON File Name\n- config: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to custom config.yaml file. If not provided, defaults to config.yaml\n      in root flows folders.\n    title: Config File\n- artifacts_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded artifacts (default: ./artifacts.zip)'\n    title: Artifacts Path\noutputs:\n- DEVICE_CLOUD_CONSOLE_URL: null\n  opts:\n    summary: URL to view the test results in the Device Cloud console\n    title: Device Cloud Console URL\n- DEVICE_CLOUD_FLOW_RESULTS: null\n  opts:\n    summary: JSON array containing results for each flow, including name, status,\n      and any errors\n    title: Flow Results\n- DEVICE_CLOUD_UPLOAD_STATUS: null\n  opts:\n    summary: Status of the test run (PENDING, RUNNING, PASSED, FAILED, CANCELLED)\n    title: Test Run Status\n- DEVICE_CLOUD_APP_BINARY_ID: null\n  opts:\n    summary: ID of the uploaded app binary in Device Cloud\n    title: App Binary ID\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/1.1.0/step.yml",
    "content": "title: Device Cloud for Maestro\nsummary: Uses devicecloud.dev to execute Maestro mobile tests\ndescription: Executes Maestro mobile tests on devicecloud.dev with configurable parameters\nwebsite: https://devicecloud.dev\nsource_code_url: https://github.com/devicecloud-dev/bitrise-integration\npublished_at: 2026-04-09T00:00:00.000000Z\nsource:\n  git: https://github.com/devicecloud-dev/bitrise-integration.git\n  commit: b736452765777d27f4a42471154b4c64f3aaccb0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: node\n  apt_get:\n  - name: git\n  - name: node\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: devicecloud.dev API Key from your app settings\n    title: Device Cloud API Key\n- app_file: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the build artifact to upload\n    title: App File Path\n- app_binary_id: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The app binary already uploaded to devicecloud.dev\n    title: App Binary ID\n- app_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Signed URL to an Expo iOS build (.tar.gz). The archive is downloaded and extracted automatically. Expo signed URLs expire after ~1 hour.\n    title: Expo App URL\n- android_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android device to run your flow against\n    title: Android Device\n- ios_device: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS device to run your flow against\n    title: iOS Device\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Path to the workspace folder containing Maestro flows\n    title: Workspace Folder\n  workspace: \"\"\n- env_list: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: List of environment variables to pass to the test separated by newlines\n      (e.g. MY_VAR=my_value <newline> MY_OTHER_VAR=other_value)\n    title: Environment Variables\n- metadata: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Arbitrary key-value metadata to include with your test run, separated\n      by newlines (format: key=value)'\n    title: Metadata\n- async: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Run tests asynchronously (exit immediately without waiting for results)\n    title: Async Execution\n    value_options:\n    - \"true\"\n    - \"false\"\n- dry_run: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Simulate the run without actually triggering the upload/test, useful\n      for debugging workflow issues\n    title: Dry Run\n    value_options:\n    - \"true\"\n    - \"false\"\n- android_api_level: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Android API level to use for testing\n    title: Android API Level\n- android_no_snapshot: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Force cold boot instead of using snapshot boot. Automatically\n      enabled for API 35+ but can be used to force cold boot on older API levels.'\n    title: Android No Snapshot\n    value_options:\n    - \"true\"\n    - \"false\"\n- ios_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: iOS version to use for testing\n    title: iOS Version\n- include_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to include in test execution\n    title: Include Tags\n- exclude_tags: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Comma-separated list of tags to exclude from test execution\n    title: Exclude Tags\n- exclude_flows: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Flows to exclude from test execution\n    title: Exclude Flows\n- google_play: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Whether to use Google Play services\n    title: Google Play\n    value_options:\n    - \"true\"\n    - \"false\"\n- name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the test run\n    title: Test Run Name\n- device_locale: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Locale to use on the device\n    title: Device Locale\n- download_artifacts: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Which artifacts to download (ALL or FAILED)\n    title: Download Artifacts\n- maestro_version: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Specific version of Maestro to use\n    title: Maestro Version\n- opts:\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Device orientation (0 = portrait, 90 = landscape)'\n    title: Device Orientation\n  orientation: \"\"\n- opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Display crosshairs for screen interactions during test\n      execution'\n    title: Show Crosshairs\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_crosshairs: \"false\"\n- maestro_chrome_onboarding: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: '[Android only] Force Maestro-based Chrome onboarding - note: this will\n      slow your tests but can fix browser related crashes'\n    title: Maestro Chrome Onboarding\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Number of times to retry failed tests\n    title: Retry Count\n  retry: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: '[experimental] The type of runner to use - note: anything other than\n      default will incur premium pricing tiers'\n    title: Runner Type\n  runner_type: \"\"\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Generate and download test reports in the specified format (allure, junit,\n      html, or html-detailed)\n    title: Report Format\n  report: \"\"\n- junit_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded JUnit report (requires report=junit,\n      default: ./report.xml)'\n    title: JUnit Report Path\n- allure_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded Allure report (requires report=allure,\n      default: ./report.html)'\n    title: Allure Report Path\n- html_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded HTML report (requires report=html, default:\n      ./report.html)'\n    title: HTML Report Path\n- ignore_sha_check: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Ignore the SHA hash check and upload the binary regardless of whether\n      it already exists (not recommended)\n    title: Ignore SHA Check\n    value_options:\n    - \"true\"\n    - \"false\"\n- api_url: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom API URL for devicecloud.dev (optional)\n    title: API URL\n- debug: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Enable detailed debug logging for troubleshooting issues\n    title: Debug Mode\n    value_options:\n    - \"true\"\n    - \"false\"\n- disable_animations: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Disable device animations during test execution. On Android, disables\n      system animation scales. On iOS, enables Reduce Motion. Reduces CPU load and\n      may improve test reliability.\n    title: Disable Animations\n    value_options:\n    - \"true\"\n    - \"false\"\n- quiet: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Suppress the progress table output from the DCD CLI.\n    title: Quiet Mode\n    value_options:\n    - \"true\"\n    - \"false\"\n\n- use_beta: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Use the beta version of the DCD CLI instead of the latest stable release.\n    title: Use Beta CLI\n    value_options:\n    - \"true\"\n    - \"false\"\n- json: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: 'Output results in JSON format - note: will always provide exit code\n      0'\n    title: JSON Output\n    value_options:\n    - \"true\"\n    - \"false\"\n- json_file: \"false\"\n  opts:\n    default_value: \"false\"\n    is_expand: true\n    is_required: false\n    summary: Write JSON output to a file with name <run_name>_dcd.json or <upload_id>_dcd.json\n      if no name is provided\n    title: JSON File Output\n    value_options:\n    - \"true\"\n    - \"false\"\n- json_file_name: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Custom name for the JSON file (can also include relative path). Requires\n      json_file to be true.\n    title: JSON File Name\n- config: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: Path to custom config.yaml file. If not provided, defaults to config.yaml\n      in root flows folders.\n    title: Config File\n- artifacts_path: \"\"\n  opts:\n    is_expand: true\n    is_required: false\n    summary: 'Custom file path for downloaded artifacts (default: ./artifacts.zip)'\n    title: Artifacts Path\noutputs:\n- DEVICE_CLOUD_CONSOLE_URL: null\n  opts:\n    summary: URL to view the test results in the Device Cloud console\n    title: Device Cloud Console URL\n- DEVICE_CLOUD_FLOW_RESULTS: null\n  opts:\n    summary: JSON array containing results for each flow, including name, status,\n      and any errors\n    title: Flow Results\n- DEVICE_CLOUD_UPLOAD_STATUS: null\n  opts:\n    summary: Status of the test run (PENDING, RUNNING, PASSED, FAILED, CANCELLED)\n    title: Test Run Status\n- DEVICE_CLOUD_APP_BINARY_ID: null\n  opts:\n    summary: ID of the uploaded app binary in Device Cloud\n    title: App Binary ID\n"
  },
  {
    "path": "steps/device-cloud-for-maestro/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/dexprotector/1.0.5/step.yml",
    "content": "title: DexProtector\nsummary: |\n  Protect your Android or iOS app with DexProtector.\ndescription: |-\n  Protect your Android or iOS app with DexProtector.\n  This Step allows you to integrate DexProtector into your Android or iOS app build as simply as possible using Bitrise.\n  Note: To use this Step, you need a valid DexProtector Enterprise license.\n\n  First, make sure that Bitrise has access to a repository containing all of the following:\n  - your project's source code\n  - DexProtector (dexprotector.jar)\n  - your customized DexProtector configuration file (dexprotector.xml)\n\n  You will also need the Base64 string of your DexProtector license file.\n  This string must be stored in the Secrets tab of the Bitrise Workflow Editor.\n  For this you need to:\n  1. Activate your license to create your `dexprotector.licel` file.\n  2. Generate the Base64 of this file. You can use the command `base64 [PATH TO YOUR LICENSE FILE]`.\n\n  Visit [licelus.com](https://licelus.com/products/dexprotector/docs) for more information on activating your license and customizing your configuration file.\n  For licensing or other queries, please contact us at primary@licelus.com.\n\n  Example of project structure:\n  ```\n  /\n  +-- dexprotector\n  |   +-- dexprotector.jar\n  |   +-- dexprotector.xml\n  [YOUR PROJECT FILES]\n  ```\nwebsite: https://github.com/dexprotector/bitrise-step-dexprotector\nsource_code_url: https://github.com/dexprotector/bitrise-step-dexprotector\nsupport_url: https://github.com/dexprotector/bitrise-step-dexprotector/issues\npublished_at: 2021-05-07T00:02:47.121347+08:00\nsource:\n  git: https://github.com/dexprotector/bitrise-step-dexprotector.git\n  commit: 9828ac5605286983cdf0ca1a75c0143e7fd211a8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: java\n  apt_get:\n  - name: java\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- app_file: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: 'Path to the app file to be protected. For example: `$BITRISE_APK_PATH`\n      or `$BITRISE_AAB_PATH` for Android; `$BITRISE_IPA_PATH` for iOS.'\n    title: Path to the app file to be protected\n- jar_file: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to DexProtector JAR file. This must be in the same repository as\n      your project.\n    title: Path to DexProtector JAR file\n- config_file: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to DexProtector XML configuration file. This must be in the same\n      repository as your project.\n    title: Path to DexProtector XML configuration file\n- license_base64: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: DexProtector license file encoded to Base64. To generate the Base64 string\n      of the license file, you can use the bash command `base64 [PATH TO YOUR LICENSE\n      FILE]`.\n    title: DexProtector license file Base64\n- app_platform: auto\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Specify your app’s platform. If you select the `auto` option, the application’s\n      file extension will be used to determine the platform automatically.\n    title: Your app platform\n    value_options:\n    - auto\n    - Android\n    - iOS\n- opts:\n    category: Android specific options\n    is_expand: true\n    summary: 'APK signing mode. Note: `-` means that this option will not be passed\n      to DexProtector as a command line argument. Therefore, if you select `-`, the\n      signing mode must be specified separately in the configuration file.'\n    title: APK signing mode\n    value_options:\n    - '-'\n    - debug\n    - release\n    - google\n    - amazon\n    - none\n  sign_mode: '-'\n- certificate: null\n  opts:\n    category: Android specific options\n    is_expand: true\n    summary: Certificate location. Specifies the path to the signing certificate file.\n      This is necessary if you intend to re-sign the app after it has been DexProtected;\n      this option is therefore only for when the sign mode == `none`. This option\n      can also be specified via the configuration file.\n    title: Certificate location\n- opts:\n    category: Android specific options\n    is_expand: true\n    is_sensitive: true\n    summary: |\n      For `google` or `amazon` sign mode only.\n      Specifies the target certificate's SHA256 certificate fingerprint.\n      The value of this fingerprint can be found:\n      Amazon: Amazon Developer Console, then go to settings of your application: Application -> Binary Files -> Appstore Certificate Hashes -> SHA-256 -> Hexadecimal.\n      Google: Google Play Console, then go to settings of your application: App Signing -> App signing certificate -> SHA-256 certificate fingerprint\n    title: SHA256 certificate fingerprint of the target certificate\n  sha256_certificate_fingerprint: null\n- keystore: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    category: Android specific options\n    is_expand: true\n    summary: Path to keystore. For `release` sign mode only. Specifies the path to\n      the keystore containing the relevant signing key. This option can also be specified\n      in the configuration file.\n    title: Path to keystore\n- opts:\n    category: Android specific options\n    is_expand: true\n    is_sensitive: true\n    summary: Password for keystore integrity. For `release` sign mode only. Specifies\n      the password to the keystore containing the relevant signing key. This option\n      can also be specified in the configuration file.\n    title: Password for keystore integrity\n  storepass: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n- keyalias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    category: Android specific options\n    is_expand: true\n    summary: Key alias. For `release` sign mode only. Specifies the alias string for\n      the relevant signing key in your keystore. This option can also be specified\n      in the configuration file.\n    title: Key alias\n- keypass: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n  opts:\n    category: Android specific options\n    is_expand: true\n    is_sensitive: true\n    summary: Password for the private key (if different). For `release` sign mode\n      only. Specifies the password for the signing key. This option can also be specified\n      in the configuration file.\n    title: Password for the private key (if different)\n- opts:\n    category: Android specific options\n    is_expand: true\n    summary: ProGuard mapping file path. Specifies the path to ProGuard's ‘mappings.txt’\n      file. If you use ProGuard for name obfuscation, it is necessary to provide the\n      path to ProGuard's map file so that DexProtector can locate classes for encryption.\n      This option can also be specified in the configuration file.\n    title: ProGuard mapping file path\n  proguard_map_file: $BITRISE_MAPPING_PATH\n- opts:\n    category: Debug\n    title: Print the verbose protection build log to stdout. This option can also\n      be specified in the configuration file.\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- DEXPROTECTOR_PROTECTED_APP_FILE: null\n  opts:\n    title: Path to the protected app file\n- DEXPROTECTOR_LOG_FILE: null\n  opts:\n    summary: Protection build log in .txt file format.\n    title: Path to the protection build log file\n"
  },
  {
    "path": "steps/dexprotector/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/diawi-upload/0.0.2/step.yml",
    "content": "title: Diawi Upload\nsummary: |\n  Upload an ipa/apk/zip to Diawi\ndescription: |\n  Upload an ipa/apk/zip to Diawi\nwebsite: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsource_code_url: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsupport_url: https://github.com/deanWombourne/bitrise-step-diawi-upload/issues\npublished_at: 2017-11-18T20:21:03.190009Z\nsource:\n  git: https://github.com/deanWombourne/bitrise-step-diawi-upload.git\n  commit: dfede936d94c44081b6360d999b806fbb69e4a18\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: npm\n  apt_get:\n  - name: npm\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: $DIAWI_TOKEN\n  opts:\n    description: |\n      The API token for Diawi.\n\n      It's free to sign up and get one, just go here: https://dashboard.diawi.com/signup.\n      You create an api token in the profile tab.\n    is_expand: true\n    is_required: true\n    summary: Diawi API token\n    title: API token\n- filename: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      The path to the file to upload - defaults to an IPA created by a bitrise archive step\n    is_expand: true\n    is_required: true\n    summary: The path to the file to upload\n    title: ipa/akp/zip file path\noutputs:\n- DIAWI_UPLOAD_URL: null\n  opts:\n    description: |\n      The URL of the uploaded file\n    summary: The URL of the uploaded file\n    title: The URL of the uploaded file\n"
  },
  {
    "path": "steps/diawi-upload/0.0.3/step.yml",
    "content": "title: Diawi Upload\nsummary: |\n  Upload an ipa/apk/zip to Diawi\ndescription: |\n  Upload an ipa/apk/zip to Diawi\nwebsite: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsource_code_url: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsupport_url: https://github.com/deanWombourne/bitrise-step-diawi-upload/issues\npublished_at: 2017-11-20T12:43:30.563291Z\nsource:\n  git: https://github.com/deanWombourne/bitrise-step-diawi-upload.git\n  commit: 8482aa583f86d66f0af5eb177807a1964e3d71b3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: npm\n  apt_get:\n  - name: npm\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: $DIAWI_TOKEN\n  opts:\n    description: |\n      The API token for Diawi.\n\n      It's free to sign up and get one, just go here: https://dashboard.diawi.com/signup.\n      You create an api token in the profile tab.\n    is_expand: true\n    is_required: true\n    summary: Diawi API token\n    title: API token\n- filename: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      The path to the file to upload - defaults to an IPA created by a bitrise archive step\n    is_expand: true\n    is_required: true\n    summary: The path to the file to upload\n    title: ipa/akp/zip file path\noutputs:\n- DIAWI_UPLOAD_URL: null\n  opts:\n    description: |\n      The URL of the uploaded file\n    summary: The URL of the uploaded file\n    title: The URL of the uploaded file\n"
  },
  {
    "path": "steps/diawi-upload/0.0.4/step.yml",
    "content": "title: Diawi Upload\nsummary: |\n  Upload an ipa/apk/zip to Diawi\ndescription: |\n  Upload an ipa/apk/zip to Diawi\nwebsite: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsource_code_url: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsupport_url: https://github.com/deanWombourne/bitrise-step-diawi-upload/issues\npublished_at: 2017-11-30T14:38:45.104142Z\nsource:\n  git: https://github.com/deanWombourne/bitrise-step-diawi-upload.git\n  commit: 5814a065056257a2af37ae12cdade6ff051690f9\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: npm\n  apt_get:\n  - name: npm\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: $DIAWI_TOKEN\n  opts:\n    description: |\n      The API token for Diawi.\n\n      It's free to sign up and get one, just go here: https://dashboard.diawi.com/signup.\n      You create an api token in the profile tab.\n    is_expand: true\n    is_required: true\n    summary: Diawi API token\n    title: API token\n- filename: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      The path to the file to upload - defaults to an IPA created by a bitrise archive step\n    is_expand: true\n    is_required: true\n    summary: The path to the file to upload\n    title: ipa/akp/zip file path\noutputs:\n- DIAWI_UPLOAD_URL: null\n  opts:\n    description: |\n      The URL of the uploaded file\n    summary: The URL of the uploaded file\n    title: The URL of the uploaded file\n"
  },
  {
    "path": "steps/diawi-upload/0.0.7/step.yml",
    "content": "title: Diawi Upload\nsummary: |\n  Upload an ipa/apk/zip to Diawi\ndescription: |\n  Upload an ipa/apk/zip to Diawi\nwebsite: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsource_code_url: https://github.com/deanWombourne/bitrise-step-diawi-upload\nsupport_url: https://github.com/deanWombourne/bitrise-step-diawi-upload/issues\npublished_at: 2020-02-18T22:15:10.236712Z\nsource:\n  git: https://github.com/deanWombourne/bitrise-step-diawi-upload.git\n  commit: 3a5d94964a12c19c64dda02e4562eafe0a043ecc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: npm\n  apt_get:\n  - name: npm\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: null\n  opts:\n    description: |\n      The API token for Diawi.\n\n      It's free to sign up and get one, just go here: https://dashboard.diawi.com/signup.\n      You create an api token in the profile tab.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Diawi API token\n    title: API token\n- filename: null\n  opts:\n    description: |\n      The path to the file to upload - defaults to an IPA created by a bitrise archive step\n    is_expand: true\n    is_required: true\n    summary: The path to the file to upload\n    title: ipa/akp/zip file path\n- opts:\n    description: Users will have to provide this to download the app from Diawi. No\n      value in here will allow anyone to download the app.\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: Users will have to provide this to download the app from Diawi. No value\n      in here will allow anyone to download the app.\n    title: Password\n  password: null\noutputs:\n- DIAWI_UPLOAD_URL: null\n  opts:\n    description: |\n      The URL of the uploaded file\n    summary: The URL of the uploaded file\n    title: The URL of the uploaded file\n"
  },
  {
    "path": "steps/diawi-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/disable-iphonesimulator-connect-hardware-keyboard/0.1.0/step.yml",
    "content": "title: Disable iphonesimulator ConnectHardwareKeyboard preference\nsummary: |\n  This Step disables ConnectHardwareKeyboard preference for all iphonesimulator devices.\nwebsite: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard\nsource_code_url: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard\nsupport_url: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard/issues\npublished_at: 2024-11-08T15:25:10.647718+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard.git\n  commit: ef0f68a586922edd52267017981fe4a5c34fd408\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard\ninputs:\n- iphonesimulator_preferences_pth: ~/Library/Preferences/com.apple.iphonesimulator.plist\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The path of the iphonesimulator preferences file.\n    title: iphonesimulator preferences path\n- opts:\n    is_required: true\n    summary: Print verbose information.\n    title: Verbose\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/disable-iphonesimulator-connect-hardware-keyboard/0.1.1/step.yml",
    "content": "title: Disable iphonesimulator ConnectHardwareKeyboard preference\nsummary: |\n  This Step disables ConnectHardwareKeyboard preference for all iphonesimulator devices.\nwebsite: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard\nsource_code_url: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard\nsupport_url: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard/issues\npublished_at: 2025-11-12T08:37:20.809518914Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard.git\n  commit: b46fc61f80fc084161dc1f8f02dc9362f05c1c28\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-disable-iphonesimulator-connect-hardware-keyboard\ninputs:\n- iphonesimulator_preferences_pth: ~/Library/Preferences/com.apple.iphonesimulator.plist\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The path of the iphonesimulator preferences file.\n    title: iphonesimulator preferences path\n- opts:\n    is_required: true\n    summary: Print verbose information.\n    title: Verbose\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/disable-iphonesimulator-connect-hardware-keyboard/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/discord-message/0.0.1/step.yml",
    "content": "title: Send a Discord message\nsummary: |\n  Send a [Discord](https://discordapp.com) message with the build status\ndescription: |\n  Send a [Discord](https://discordapp.com) message to a text channel with the build status using Discord Webhooks\n\n  To find your text channel **webhook** visit: [https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token](https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token)\nwebsite: https://gitlab.com/lighthouseit/packages/bitrise-discord-message\nsource_code_url: https://gitlab.com/lighthouseit/packages/bitrise-discord-message\nsupport_url: https://gitlab.com/lighthouseit/packages/bitrise-discord-message/issues\npublished_at: 2019-10-11T12:06:49.077703198-03:00\nsource:\n  git: https://gitlab.com/lighthouseit/packages/bitrise-discord-message.git\n  commit: b58f0a1a85b9d13b1f280fd4e27f5155fbe1cfeb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |\n      **Webhook\\_url with webhook token is required.**\n\n      To obtain the channel **Webhook** visit: https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token\n    is_required: true\n    is_sensitive: true\n    title: Discord channel Webhook URL\n  webhook_url: null\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, running, success, failed or aborted.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      and `failed` status if the build previously failed.\n    title: Set Specific Status\n    value_options:\n    - auto\n    - running\n    - success\n    - failed\n    - aborted\n  preset_status: auto\n- is_debug_mode: \"no\"\n  opts:\n    description: Step prints additional debug information if this option is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/discord-message/0.0.2/step.yml",
    "content": "title: Send a Discord message\nsummary: |\n  Send a [Discord](https://discordapp.com) message with the build status\ndescription: |\n  Send a [Discord](https://discordapp.com) message to a text channel with the build status using Discord Webhooks\n\n  To find your text channel **webhook** visit: [https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token](https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token)\nwebsite: https://gitlab.com/lighthouseit/packages/bitrise-discord-message\nsource_code_url: https://gitlab.com/lighthouseit/packages/bitrise-discord-message\nsupport_url: https://gitlab.com/lighthouseit/packages/bitrise-discord-message/issues\npublished_at: 2019-10-16T09:47:25.406531335-03:00\nsource:\n  git: https://gitlab.com/lighthouseit/packages/bitrise-discord-message.git\n  commit: 94ef4e833bf0bfd8209ff892f3bf49e89443c1a4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |\n      **Webhook\\_url with webhook token is required.**\n\n      To obtain the channel **Webhook** visit: https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token\n    is_required: true\n    is_sensitive: true\n    title: Discord Webhook URL\n  webhook_url: null\n- mention_role: '@everyone'\n  opts:\n    description: The Discord role to be mentioned if a build failure\n    is_required: false\n    title: Mention Role\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, running, success, failed or aborted.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      and `failed` status if the build previously failed.\n    title: Set Specific Status\n    value_options:\n    - auto\n    - running\n    - success\n    - failed\n    - aborted\n  preset_status: auto\n- is_debug_mode: \"no\"\n  opts:\n    description: Step prints additional debug information if this option is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/discord-message/0.0.3/step.yml",
    "content": "title: Send a Discord message\nsummary: |\n  Send a [Discord](https://discordapp.com) message with the build status\ndescription: |\n  Send a [Discord](https://discordapp.com) message to a text channel with the build status using Discord Webhooks\n\n  To find your text channel **webhook** visit: [https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token](https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token)\nwebsite: https://gitlab.com/lighthouseit/packages/bitrise-discord-message\nsource_code_url: https://gitlab.com/lighthouseit/packages/bitrise-discord-message\nsupport_url: https://gitlab.com/lighthouseit/packages/bitrise-discord-message/issues\npublished_at: 2019-11-05T22:45:33.984959669-03:00\nsource:\n  git: https://gitlab.com/lighthouseit/packages/bitrise-discord-message.git\n  commit: 743bdba23c4a5e4ad6a6417e15a02c8fe7c5c5a3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |\n      **Webhook\\_url with webhook token is required.**\n\n      To obtain the channel **Webhook** visit: https://github.com/Akizo96/de.isekaidev.discord.wbbBridge/wiki/How-to-get-Webhook-ID-&-Token\n    is_required: true\n    is_sensitive: true\n    title: Discord Webhook URL\n  webhook_url: null\n- mention_role: '@everyone'\n  opts:\n    description: The Discord role to be mentioned if a build failure\n    is_required: false\n    title: Mention Role\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, running, success, failed or aborted.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      and `failed` status if the build previously failed.\n    title: Set Specific Status\n    value_options:\n    - auto\n    - running\n    - success\n    - failed\n    - aborted\n  preset_status: auto\n- is_debug_mode: \"no\"\n  opts:\n    description: Step prints additional debug information if this option is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/discord-message/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/docker-build-push/1.0.0/step.yml",
    "content": "title: Docker Build & Push\nsummary: |\n  Building and pushing docker images with built-in cache support\ndescription: |\n  Enables you to build and optionally push docker images with built-in Bitrise key-value cache support.\n  It is possible to customize the docker build command to utilize other cache mechanisms, such as registry-cache.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-docker-build-push\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-docker-build-push\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-docker-build-push/issues\npublished_at: 2024-01-31T15:32:12.531287+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-docker-build-push.git\n  commit: 36d5e2e40f42ec926ab4982669c3830fa26e8836\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-docker-build-push\ninputs:\n- opts:\n    description: |-\n      List of tags (full image names) to be applied to the built image\n\n      Add one tag per line. Example: `myregistry.com/myimage:latest`\n    is_required: true\n    summary: List of tags (full image names) to be applied to the built image\n    title: Image tags\n  tags: null\n- context: .\n  opts:\n    description: |-\n      Path to the build context to be used for the docker build\n\n      The path is relative to the working directory.\n    is_required: true\n    summary: Path to the build context to be used for the docker build\n    title: Build context path\n- file: ./Dockerfile\n  opts:\n    description: |-\n      Path to the Dockerfile to be built\n\n      The path is relative to the working directory.\n    is_required: true\n    summary: Path to the Dockerfile to be built\n    title: Dockerfile path\n- opts:\n    description: When set to 'true', the docker image will be pushed.\n    is_required: true\n    summary: When set to 'true', the docker image will be pushed\n    title: Push docker image\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"false\"\n- opts:\n    description: |-\n      When set to 'true', the docker image will automatically be cached using Bitrise key-value cache.\n\n      The following cache keys will be used:\n      - docker-imagename-{{ .OS }}-{{ .Arch }}-{{ .Branch }}-{{ .CommitHash }}\n      - docker-imagename-{{ .OS }}-{{ .Arch }}-{{ .Branch }}\n      - docker-imagename-{{ .OS }}-{{ .Arch }}\n\n      Warning: Do not specify the cache-to and cache-from parameters when using this option.\n    is_required: true\n    summary: When set to 'true', image will be cached automatically with Bitrise key-value\n      cache\n    title: Use Bitrise key-value cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_bitrise_cache: \"false\"\n- build_arg: null\n  opts:\n    description: |-\n      List of build arguments to be passed to the docker build\n\n      Add one build argument per line. Example: `MY_BUILD_ARG=myvalue`\n    is_required: false\n    summary: List of [build arguments](https://docs.docker.com/build/guide/build-args/)\n      to be passed to the docker build\n    title: Build arguments\n- cache_from: null\n  opts:\n    description: |-\n      List of arguments to be passed to the docker build for cache-from\n\n      Add one cache-from argument per line. Example: `type=registry,ref=myregistry.dev/myrepository/my-image:latest`\n    is_required: false\n    summary: List of arguments to be passed to the docker build for cache-from\n    title: Cache from arguments\n- cache_to: null\n  opts:\n    description: |-\n      List of arguments to be passed to the docker build for cache-to\n\n      Add one cache-to argument per line. Example: `type=registry,ref=myregistry.dev/myrepository/my-image:latest,mode=max,compression=zstd`\n    is_required: false\n    summary: List of arguments to be passed to the docker build for cache-to\n    title: Cache to arguments\n- extra_options: null\n  opts:\n    description: |-\n      List of extra options to be passed to the docker build\n\n      Extra options must be in the format of `--option value` or `--option=value`.\n\n      Warning:\n        When using values with quotes in them (for example when they contain spaces) do not use the equal sign.\n        Separate it with spaces instead. Example: `--option \"value with spaces\"`\n\n      Add one extra option per line.\n    is_required: false\n    summary: List of extra options to be passed to the docker build\n    title: Extra options\n- buildx_host_network: \"false\"\n  opts:\n    is_required: true\n    summary: Enables to use the host network with the buildkit build container\n    title: Enables to use the host network with the buildkit build container\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/docker-build-push/1.0.1/step.yml",
    "content": "title: Docker Build & Push\nsummary: |\n  Building and pushing docker images with built-in cache support\ndescription: |\n  Enables you to build and optionally push docker images with built-in Bitrise key-value cache support.\n  It is possible to customize the docker build command to utilize other cache mechanisms, such as registry-cache.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-docker-build-push\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-docker-build-push\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-docker-build-push/issues\npublished_at: 2024-01-31T15:58:01.08045114Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-docker-build-push.git\n  commit: 74e34334e7006cdc12b142318d6a733bf1c130e2\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-docker-build-push\ninputs:\n- opts:\n    description: |-\n      List of tags (full image names) to be applied to the built image\n\n      Add one tag per line. Example: `myregistry.com/myimage:latest`\n    is_required: true\n    summary: List of tags (full image names) to be applied to the built image\n    title: Image tags\n  tags: null\n- context: .\n  opts:\n    description: |-\n      Path to the build context to be used for the docker build\n\n      The path is relative to the working directory.\n    is_required: true\n    summary: Path to the build context to be used for the docker build\n    title: Build context path\n- file: ./Dockerfile\n  opts:\n    description: |-\n      Path to the Dockerfile to be built\n\n      The path is relative to the working directory.\n    is_required: true\n    summary: Path to the Dockerfile to be built\n    title: Dockerfile path\n- opts:\n    description: When set to 'true', the docker image will be pushed.\n    is_required: true\n    summary: When set to 'true', the docker image will be pushed\n    title: Push docker image\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"false\"\n- opts:\n    description: |-\n      When set to 'true', the docker image will automatically be cached using Bitrise key-value cache.\n\n      The following cache keys will be used:\n      - docker-imagename-{{ .OS }}-{{ .Arch }}-{{ .Branch }}-{{ .CommitHash }}\n      - docker-imagename-{{ .OS }}-{{ .Arch }}-{{ .Branch }}\n      - docker-imagename-{{ .OS }}-{{ .Arch }}\n\n      Warning: Do not specify the cache-to and cache-from parameters when using this option.\n    is_required: true\n    summary: When set to 'true', image will be cached automatically with Bitrise key-value\n      cache\n    title: Use Bitrise key-value cache\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_bitrise_cache: \"false\"\n- build_arg: null\n  opts:\n    description: |-\n      List of build arguments to be passed to the docker build\n\n      Add one build argument per line. Example: `MY_BUILD_ARG=myvalue`\n    is_required: false\n    summary: List of [build arguments](https://docs.docker.com/build/guide/build-args/)\n      to be passed to the docker build\n    title: Build arguments\n- cache_from: null\n  opts:\n    description: |-\n      List of arguments to be passed to the docker build for cache-from\n\n      Add one cache-from argument per line. Example: `type=registry,ref=myregistry.dev/myrepository/my-image:latest`\n    is_required: false\n    summary: List of arguments to be passed to the docker build for cache-from\n    title: Cache from arguments\n- cache_to: null\n  opts:\n    description: |-\n      List of arguments to be passed to the docker build for cache-to\n\n      Add one cache-to argument per line. Example: `type=registry,ref=myregistry.dev/myrepository/my-image:latest,mode=max,compression=zstd`\n    is_required: false\n    summary: List of arguments to be passed to the docker build for cache-to\n    title: Cache to arguments\n- extra_options: null\n  opts:\n    description: |-\n      List of extra options to be passed to the docker build\n\n      Extra options must be in the format of `--option value` or `--option=value`.\n\n      Warning:\n        When using values with quotes in them (for example when they contain spaces) do not use the equal sign.\n        Separate it with spaces instead. Example: `--option \"value with spaces\"`\n\n      Add one extra option per line.\n    is_required: false\n    summary: List of extra options to be passed to the docker build\n    title: Extra options\n- buildx_host_network: \"false\"\n  opts:\n    is_required: true\n    summary: Enables to use the host network with the buildkit build container\n    title: Enables to use the host network with the buildkit build container\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/docker-build-push/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/dropbox/1.0.3/step.yml",
    "content": "title: Send file to dropbox\nsummary: |\n  Upload one or more files to [dropbox](https://www.dropbox.com)\ndescription: |\n  This step is used to send files to dropbox.\n\n  * This step is able to upload only one file\n  * If a remote file exist with the same name, the file is not deleted\n  * If you specify a directory, the directory is created\nwebsite: https://github.com/kawaiseb/bitrise-step-dropbox\nsource_code_url: https://github.com/kawaiseb/bitrise-step-dropbox\nsupport_url: https://github.com/kawaiseb/bitrise-step-dropbox/issues\npublished_at: 2018-03-20T17:44:28.703977+01:00\nsource:\n  git: https://github.com/kawaiseb/bitrise-step-dropbox.git\n  commit: bf984c305021e43b3bbecbe8b96ae2ba19ef2be4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- dropbox_secret: null\n  opts:\n    description: |\n      You have to generate a secret access token in [the developer website](https://www.dropbox.com/developers).\n      Create an application and go in the setting's application.\n    is_required: true\n    title: The secret access token (OAuth2)\n- dropbox_local_path: null\n  opts:\n    description: |\n      The name of the local file you wish to upload on dropbox.\n\n      * Only one file !\n      * If a remote file exist with the same name, the file is not deleted\n\n\n      **example :** \"/tmp/myapp.ipa\" or \"/tmp/myapp.apk\"\n    is_required: true\n    title: Local File\n- dropbox_remote_path: null\n  opts:\n    description: |\n      The directory to upload file in dropbox\n\n      * If you specify a directory that does not exist this one is created\n\n      **example :** \"/delivery/ios\" or \"/delivery/android\"\n    is_required: true\n    title: Dropbox remote target\n- dropbox_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode ?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/dropbox/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/dsym-upload-to-crashlytics--no-cocoapods/0.0.1/step.yml",
    "content": "title: Firebase dSym Upload (SPM installation)\nsummary: |\n  Upload of dSym to Firebase Crashlytics with SPM installation\ndescription: |\n  This step will help you to upload dSym of your build to Firebase Crashlytics with SPM installation.\nwebsite: https://github.com/hughmaurer/bitrise-step-dsym-upload-to-crashlytics--no-cocoapods\nsource_code_url: https://github.com/hughmaurer/bitrise-step-dsym-upload-to-crashlytics--no-cocoapods\nsupport_url: https://github.com/hughmaurer/bitrise-step-dsym-upload-to-crashlytics--no-cocoapods/issues\npublished_at: 2023-12-20T12:22:50.911776+01:00\nsource:\n  git: https://github.com/hughmaurer/bitrise-step-dsym-upload-to-crashlytics--no-cocoapods.git\n  commit: 5613b9ade23a2f1472fe11eaa9e59da904d537d2\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- google_plist_path: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_required: true\n    title: Location of your GoogleService info plist\n- dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n"
  },
  {
    "path": "steps/dsym-upload-to-crashlytics--no-cocoapods/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/email-with-mailgun/2.0.0/step.yml",
    "content": "title: Send Email with Mailgun\nsummary: Send an email using your Mailgun account.\ndescription: |-\n  Send email with Mailgun ( [https://mailgun.com](https://mailgun.com) ).\n\n  With the free Mailgun account you can send 10,000 emails/month, 300 emails/day.\nwebsite: https://github.com/bitrise-io/steps-email-with-mailgun\nsource_code_url: https://github.com/bitrise-io/steps-email-with-mailgun\nsupport_url: https://github.com/bitrise-io/steps-email-with-mailgun/issues\npublished_at: 2015-09-08T20:55:10.881817411+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-email-with-mailgun.git\n  commit: 10dd6e4e94422688dacf50190d5bde736369fbe5\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- email\n- messaging\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Mailgun API Key\n- domain: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Mailgun Domain\n- opts:\n    description: |\n      Comma separated email address list.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Send To emails\n  send_to: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Email Subject\n  subject: \"\"\n- message: Build finished on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Email Message\n"
  },
  {
    "path": "steps/email-with-mailgun/2.1.0/step.yml",
    "content": "title: Send Email with Mailgun\nsummary: Send an email using your Mailgun account.\ndescription: |-\n  Send email with Mailgun ( [https://mailgun.com](https://mailgun.com) ).\n\n  How to get step inputs from mailgun?\n\n  - [Sign up](https://mailgun.com/signup) or [Log in](https://mailgun.com/cp) to mailgun.\n  - Go to [Domains](https://mailgun.com/app/domains) and select a domain which one you want to use or create a new one.\n  - On the selected domain's page you can grab the:\n    - `MAILGUN_DOMAIN`'s environment value (sandobox...mailgun.org)\n    - `MAILGUN_API_KEY`'s environment value (key-...)\n\n  With the free Mailgun account you can send 10,000 emails/month, 300 emails/day.\nwebsite: https://github.com/bitrise-io/steps-email-with-mailgun\nsource_code_url: https://github.com/bitrise-io/steps-email-with-mailgun\nsupport_url: https://github.com/bitrise-io/steps-email-with-mailgun/issues\npublished_at: 2016-04-12T11:33:32.560444312+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-email-with-mailgun.git\n  commit: 835a7551223b971be057ec1eb3805af3691a0785\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $MAILGUN_API_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Mailgun API Key\n- domain: $MAILGUN_DOMAIN\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Mailgun Domain\n- from_email: Bitrise Mailgun Step <postmaster@$domain>\n  opts:\n    description: |\n      Email address for From header\n    is_required: true\n    summary: \"\"\n    title: Email address for From header\n- opts:\n    description: |\n      Comma separated email address list.\n    is_required: true\n    summary: \"\"\n    title: Send To emails\n  send_to: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Email Subject\n  subject: Build finished\n- message: Build succed on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message\n- error_message: Build failed on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message on build failed\n- message_format: html\n  opts:\n    description: |\n      Message format.\n    is_required: true\n    summary: \"\"\n    title: Message format\n    value_options:\n    - html\n    - text\n- attachments: null\n  opts:\n    description: |\n      You can post multiple attachments separated with comma.\n      example: image1.jpg,image2.jpg,image3.jpg\n    summary: \"\"\n    title: File attachments\n"
  },
  {
    "path": "steps/email-with-mailgun/2.1.1/step.yml",
    "content": "title: Send Email with Mailgun\nsummary: Send an email using your Mailgun account.\ndescription: |-\n  Send email with Mailgun ( [https://mailgun.com](https://mailgun.com) ).\n\n  How to get step inputs from mailgun?\n\n  - [Sign up](https://mailgun.com/signup) or [Log in](https://mailgun.com/cp) to mailgun.\n  - Go to [Domains](https://mailgun.com/app/domains) and select a domain which one you want to use or create a new one.\n  - On the selected domain's page you can grab the:\n    - `MAILGUN_DOMAIN`'s environment value (sandobox...mailgun.org)\n    - `MAILGUN_API_KEY`'s environment value (key-...)\n\n  With the free Mailgun account you can send 10,000 emails/month, 300 emails/day.\n\n  If you don't get the email check your spam folder and your mailgun log on `Logs` tab after you logged in.\nwebsite: https://github.com/bitrise-io/steps-email-with-mailgun\nsource_code_url: https://github.com/bitrise-io/steps-email-with-mailgun\nsupport_url: https://github.com/bitrise-io/steps-email-with-mailgun/issues\npublished_at: 2018-01-08T15:28:32.275701091+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-email-with-mailgun.git\n  commit: 75b2f4e543c30bb9b56898d48b8f12b9ea682633\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-email-with-mailgun\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $MAILGUN_API_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Mailgun API Key\n- domain: $MAILGUN_DOMAIN\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Mailgun Domain\n- from_email: Bitrise Mailgun Step <postmaster@$domain>\n  opts:\n    description: |\n      Email address for From header\n    is_required: true\n    summary: \"\"\n    title: Email address for From header\n- opts:\n    description: |\n      Comma separated email address list.\n    is_required: true\n    summary: \"\"\n    title: Send To emails\n  send_to: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Email Subject\n  subject: Build finished\n- message: Build succed on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message\n- error_message: Build failed on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message on build failed\n- message_format: html\n  opts:\n    description: |\n      Message format.\n    is_required: true\n    summary: \"\"\n    title: Message format\n    value_options:\n    - html\n    - text\n- attachments: null\n  opts:\n    description: |\n      You can post multiple attachments separated with comma.\n      example: image1.jpg,image2.jpg,image3.jpg\n    summary: \"\"\n    title: File attachments\n"
  },
  {
    "path": "steps/email-with-mailgun/2.1.2/step.yml",
    "content": "title: Send Email with Mailgun\nsummary: Send an email using your Mailgun account.\ndescription: |-\n  Send email with Mailgun ( [https://mailgun.com](https://mailgun.com) ).\n\n  How to get step inputs from mailgun?\n\n  - [Sign up](https://mailgun.com/signup) or [Log in](https://mailgun.com/cp) to mailgun.\n  - Go to [Domains](https://mailgun.com/app/domains) and select a domain which one you want to use or create a new one.\n  - On the selected domain's page you can grab the:\n    - `MAILGUN_DOMAIN`'s environment value (sandobox...mailgun.org)\n    - `MAILGUN_API_KEY`'s environment value (key-...)\n\n  With the free Mailgun account you can send 10,000 emails/month, 300 emails/day.\n\n  If you don't get the email check your spam folder and your mailgun log on `Logs` tab after you logged in.\nwebsite: https://github.com/bitrise-io/steps-email-with-mailgun\nsource_code_url: https://github.com/bitrise-io/steps-email-with-mailgun\nsupport_url: https://github.com/bitrise-io/steps-email-with-mailgun/issues\npublished_at: !!timestamp 2018-04-10T15:57:27.515096218+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-email-with-mailgun.git\n  commit: a3bb81e1fbba81cf4fb9c0e99e3ac5199cf655ab\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-email-with-mailgun\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $MAILGUN_API_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Mailgun API Key\n- domain: $MAILGUN_DOMAIN\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Mailgun Domain\n- from_email: Bitrise Mailgun Step <postmaster@$domain>\n  opts:\n    description: |\n      Email address for From header\n    is_required: true\n    summary: \"\"\n    title: Email address for From header\n- opts:\n    description: |\n      Comma separated email address list.\n    is_required: true\n    summary: \"\"\n    title: Send To emails\n  send_to: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Email Subject\n  subject: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER finished\n- message: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER succeeded on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message\n- error_message: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER failed on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message on build failed\n- message_format: html\n  opts:\n    description: |\n      Message format.\n    is_required: true\n    summary: \"\"\n    title: Message format\n    value_options:\n    - html\n    - text\n- attachments: null\n  opts:\n    description: |\n      You can post multiple attachments separated with comma.\n      example: image1.jpg,image2.jpg,image3.jpg\n    summary: \"\"\n    title: File attachments\n"
  },
  {
    "path": "steps/email-with-mailgun/2.1.4/step.yml",
    "content": "title: Send Email with Mailgun\nsummary: Send emails using your Mailgun account.\ndescription: |-\n  Send emails with [Mailgun](https://mailgun.com).\n\n  How to get step inputs from Mailgun?\n\n  - [Sign up](https://mailgun.com/signup) or [Log in](https://mailgun.com/cp) to Mailgun.\n  - Go to [Domains](https://mailgun.com/app/domains) and select a domain you want to use or create a new domain.\n  - On the selected domain's page you can grab the:\n    - `MAILGUN_DOMAIN`'s environment value (sandbox...mailgun.org)\n    - `MAILGUN_API_KEY`'s environment value (key-...)\n\n  With the free Mailgun account you can send 10,000 emails/month, 300 emails/day.\n\n  If you don't get the email, check your spam folder and your Mailgun log on `Logs` tab after you logged in.\nwebsite: https://github.com/bitrise-io/steps-email-with-mailgun\nsource_code_url: https://github.com/bitrise-io/steps-email-with-mailgun\nsupport_url: https://github.com/bitrise-io/steps-email-with-mailgun/issues\npublished_at: 2018-08-31T08:17:31.528266763Z\nsource:\n  git: https://github.com/bitrise-io/steps-email-with-mailgun.git\n  commit: f64779287399f42b6f005e8d86106c5985283e17\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-email-with-mailgun\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $MAILGUN_API_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Mailgun API Key\n- domain: $MAILGUN_DOMAIN\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Mailgun Domain\n- from_email: Bitrise Mailgun Step <postmaster@$domain>\n  opts:\n    description: |\n      Email address for From header\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Email address for From header\n- opts:\n    description: |\n      Comma separated email address list.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Send To emails\n  send_to: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Email Subject\n  subject: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER finished\n- message: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER succeeded on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message\n- error_message: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER failed on Bitrise.io\n  opts:\n    description: |\n      The message can be HTML or plain text.\n    is_required: true\n    summary: \"\"\n    title: Email Message on build failed\n- message_format: html\n  opts:\n    description: |\n      Message format.\n    is_required: true\n    summary: \"\"\n    title: Message format\n    value_options:\n    - html\n    - text\n- attachments: null\n  opts:\n    description: |\n      You can post multiple attachments separated with commas.\n      example: image1.jpg,image2.jpg,image3.jpg\n    summary: \"\"\n    title: File attachments\n"
  },
  {
    "path": "steps/email-with-mailgun/2.2.0/step.yml",
    "content": "title: Send Email with Mailgun\nsummary: Send emails using your Mailgun account.\ndescription: |-\n  Send emails with [Mailgun](https://mailgun.com).\n\n  How to get step inputs from Mailgun?\n\n  - [Sign up](https://mailgun.com/signup) or [Log in](https://mailgun.com/cp) to Mailgun.\n  - Go to [Domains](https://mailgun.com/app/domains) and select a domain you want to use or create a new domain.\n  - On the selected domain's page you can grab the:\n    - `MAILGUN_DOMAIN`'s environment value (sandbox...mailgun.org)\n    - `MAILGUN_API_KEY`'s environment value (key-...)\n\n  With the free Mailgun account you can send 10,000 emails/month, 300 emails/day.\n\n  If you don't get the email, check your spam folder and your Mailgun log on `Logs` tab after you logged in.\nwebsite: https://github.com/bitrise-io/steps-email-with-mailgun\nsource_code_url: https://github.com/bitrise-io/steps-email-with-mailgun\nsupport_url: https://github.com/bitrise-io/steps-email-with-mailgun/issues\npublished_at: 2021-09-23T12:27:38.411156438Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-email-with-mailgun.git\n  commit: 0c792d2f75a2ca6acc520abc177c6406dbe107cc\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-email-with-mailgun\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $MAILGUN_API_KEY\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Mailgun API Key\n- api_endpoint: api.mailgun.net\n  opts:\n    description: |-\n      The API endpoint to be used with Mailgun: US or EU.\n\n      The default value is the US endpoint (api.mailgun.net).\n    is_required: true\n    title: Mailgun API Endpoint\n    value_options:\n    - api.mailgun.net\n    - api.eu.mailgun.net\n- domain: $MAILGUN_DOMAIN\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Mailgun Domain\n- from_email: Bitrise Mailgun Step <postmaster@$domain>\n  opts:\n    description: Email address for From header\n    is_required: true\n    is_sensitive: true\n    title: Email address for From header\n- opts:\n    description: Comma separated email address list.\n    is_required: true\n    is_sensitive: true\n    title: Send To emails\n  send_to: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    title: Email Subject\n  subject: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER finished\n- message: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER succeeded on Bitrise.io\n  opts:\n    description: The message can be HTML or plain text.\n    is_required: true\n    title: Email Message\n- error_message: $BITRISE_APP_TITLE Build $BITRISE_BUILD_NUMBER failed on Bitrise.io\n  opts:\n    description: The message can be HTML or plain text.\n    is_required: true\n    title: Email Message on build failed\n- message_format: html\n  opts:\n    description: Message format.\n    is_required: true\n    title: Message format\n    value_options:\n    - html\n    - text\n- attachments: null\n  opts:\n    description: |-\n      You can post multiple attachments separated with commas.\n      example: image1.jpg,image2.jpg,image3.jpg\n    title: File attachments\n"
  },
  {
    "path": "steps/email-with-mailgun/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/embrace-symbol-upload/1.0.0/step.yml",
    "content": "title: Embrace iOS Symbol Upload\nsummary: |\n  Upload iOS debug symbols to Embrace through Bitrise CI integration\ndescription: |\n  Upload iOS debug symbols to Embrace through Bitrise CI. This will make your integration with Embrace more efficient. Environment Variables are supported via the upload tool.\n\n  Env Vars:\n  ---------\n  EMBRACE_APP: Your Embrace app idenifier\n  EMBRACE_API_TOKEN: Your Embrace upload API token\nwebsite: https://github.com/embrace-io/bitrise-symbol-upload\nsource_code_url: https://github.com/embrace-io/bitrise-symbol-upload\nsupport_url: https://github.com/embrace-io/bitrise-symbol-upload\npublished_at: 2023-10-05T14:49:30.418918-04:00\nsource:\n  git: https://github.com/embrace-io/bitrise-symbol-upload.git\n  commit: f24fc1c9e96311333c2deab2ae69f3ad4b13409b\nproject_type_tags:\n- ios\ntype_tags:\n- artifact-info\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- embrace_app: $EMBRACE_APP\n  opts:\n    is_required: true\n    title: Embrace App ID\n- embrace_api_token: $EMBRACE_API_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Embrace API Token\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    is_required: true\n    title: DSYM Path\n"
  },
  {
    "path": "steps/embrace-symbol-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/ensure-clean-git/0.9.0/step.yml",
    "content": "title: Ensure clean git\ndescription: |-\n  Fails if there's any uncommitted change in the git repository.\n\n  Calls `git status` and fails if it reports any changed/uncommitted file.\nsummary: |-\n  Make sure your repo is clean as a whistle, no uncommitted changes,\n  nothing to hide.\nwebsite: https://github.com/bitrise-io/steps-ensure-clean-git\nsource_code_url: https://github.com/bitrise-io/steps-ensure-clean-git\nsupport_url: https://github.com/bitrise-io/steps-ensure-clean-git/issues\npublished_at: 2015-08-15T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ensure-clean-git.git\n  commit: a3fa0a5aeebc22046bf4d1ce4080e86a7451de82\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\n"
  },
  {
    "path": "steps/ensure-clean-git/0.9.1/step.yml",
    "content": "title: Ensure clean git\nsummary: |-\n  Make sure your repo is clean as a whistle, no uncommitted changes,\n  nothing to hide.\ndescription: |-\n  Fails if there's any uncommitted change in the git repository.\n\n  Calls `git status` and fails if it reports any changed/uncommitted file.\nwebsite: https://github.com/bitrise-io/steps-ensure-clean-git\nsource_code_url: https://github.com/bitrise-io/steps-ensure-clean-git\nsupport_url: https://github.com/bitrise-io/steps-ensure-clean-git/issues\npublished_at: 2015-10-19T12:38:49.223321288+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ensure-clean-git.git\n  commit: e869d49a9092cc556b0281b6ca4e3e9bd410006a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- dir_to_check: null\n  opts:\n    description: The path that will be scanned for any uncommitted files. By default\n      it is the current directory.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: The directory to check if contains any uncommitted changes\n"
  },
  {
    "path": "steps/ensure-clean-git/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/errcheck/0.9.0/step.yml",
    "content": "title: Errcheck\nsummary: Checks for unchecked errors in go program\ndescription: |-\n  Runs errcheck command on the given packages one-by-one:\n\n  `errcheck -asserts=true -blank=true -verbose <package>`\nwebsite: https://github.com/bitrise-steplib/steps-errcheck\nsource_code_url: https://github.com/bitrise-steplib/steps-errcheck\nsupport_url: https://github.com/bitrise-steplib/steps-errcheck/issues\npublished_at: 2018-04-11T15:22:11.797398474+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-errcheck.git\n  commit: 0abbc51a89fb479e07f76b81092fb0bccaa6261b\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-errcheck\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages, to run the errcheck command against.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    summary: errcheck target packages\n    title: errcheck target packages\n  packages: $BITRISE_GO_PACKAGES\n"
  },
  {
    "path": "steps/errcheck/0.9.1/step.yml",
    "content": "title: Errcheck\nsummary: Checks for unchecked errors in go program\ndescription: |-\n  Runs errcheck command on the given packages one-by-one:\n\n  `errcheck -asserts=true -blank=true -verbose <package>`\nwebsite: https://github.com/bitrise-steplib/steps-errcheck\nsource_code_url: https://github.com/bitrise-steplib/steps-errcheck\nsupport_url: https://github.com/bitrise-steplib/steps-errcheck/issues\npublished_at: 2020-12-16T16:28:01.382958573Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-errcheck.git\n  commit: 9846afc8e53c9c453105af50f386931b35fc325a\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-errcheck\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages, to run the errcheck command against.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    summary: errcheck target packages\n    title: errcheck target packages\n  packages: $BITRISE_GO_PACKAGES\n"
  },
  {
    "path": "steps/errcheck/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/expo-detach/0.10.1/step.yml",
    "content": "title: '[Beta] Expo Eject'\nsummary: Creates Xcode and Android Studio projects for your app.\ndescription: |-\n  Using the The Expo Development CLI to create Xcode and Android Studio projects for your app.\n  **EXPO DEVELOPMENT CLI** https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2019-12-10T12:31:26.188028815Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: 1029abb4799c42c5de86cd3366da6d3681326b4b\nproject_type_tags:\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ninputs:\n- opts:\n    description: The root directory of the React Native project (the directory of\n      the project package.js file).\n    summary: The root directory of the React Native project\n    title: Working directory\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: \"Specify the Expo CLI version to install.  \\nThe Expo CLI ejects\n      your project and creates Xcode and Android Studio projects for your app.\\n\\n[https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\\n\\nA\n      couple of examples:\\n\\n* \\\"3.0.0\\\"\\n* latest\"\n    is_required: \"true\"\n    summary: Specify the Expo CLI version to install.\n    title: Expo CLI version\n- opts:\n    description: \"Your account's username for `https://expo.io/` .\\n\\nIn case of React\n      Native project __using Expo Kit__ library (any .js file imports expo),  \\nthe\n      `user_name` and `password` inputs are __required__.\\n\\nIf you provide these\n      inputs the step will run: `expo eject --eject-method expoKit`,  \\notherwise:\n      `expo eject --eject-method bare`.\\n\\n**NOTE:** You need to use your username\n      and not your e-mail address.\"\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: \"Your password for `https://expo.io/` .\\n\\nIn case of React Native\n      project __using Expo Kit__ library (any .js file imports expo),  \\nthe `user_name`\n      and `password` inputs are __required__.\\n\\nIf you provide these inputs the step\n      will run: `expo eject --eject-method expoKit`,  \\notherwise: `expo eject --eject-method\n      bare`.\"\n    is_sensitive: true\n    summary: Password for your Expo account.\n    title: Password for your Expo account\n  password: \"\"\n- opts:\n    description: \"Should the step run `expo publish` after eject?\\n\\nIn case of React\n      Native project using Expo Kit library (any .js file imports expo),  \\n`expo\n      publis` command generates the:\\n\\n- ./android/app/src/main/assets/shell-app-manifest.json\\n-\n      ./android/app/src/main/assets/shell-app.bundle\\n- ./ios/bitriseexpokit/Supporting/shell-app-manifest.json\\n-\n      ./ios/bitriseexpokit/Supporting/shell-app.bundle\\n\\nfiles, which are required\n      for the native builds.\"\n    summary: Should the step run `expo publish` after eject?\n    title: Run expo publish after eject?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  run_publish: \"no\"\n- opts:\n    description: React Native version to set in package.json after the eject process.\n    summary: React Native version to set in package.json after the eject process.\n    title: React Native version to set in package.json\n  override_react_native_version: null\n"
  },
  {
    "path": "steps/expo-detach/0.10.2/step.yml",
    "content": "title: '[Beta] Expo Eject'\nsummary: Creates Xcode and Android Studio projects for your app.\ndescription: |2-\n\n  Expo is a toolchain that allows you to quickly get a React Native app up and running without having to use native code in Xcode or Android Studio. The Expo Eject Step is necessary to eject your app to install any missing native dependencies. Installing the native dependencies is done by our dedicated Steps, such as **Install missing Android SDK components** and **Run CocoaPods install**.\n\n  ### Configuring the Step\n\n  1. Add the Step to your Workflow after the Step or Steps that install your app's Javascript dependencies (such as **Run npm command** or **Run yarn command**).\n\n  1. Set the **Working directory input field** to the value of your project directory. By default, you do not have to change this.\n\n  1. Specify the Expo CLI version.\n\n     The default value is `latest` but you can specify an exact version, such as 3.0.0.\n\n  1. If your app uses an Expo SDK, you must provide the username and password for your Expo account! Without it, the Expo SDK imports will stop working.\n\n  ### Troubleshooting\n\n  If the Expo CLI used the default `--eject-method` and your SDK imports stop working, check your Expo username and password.\n\n  Make sure that the Expo CLI version you use is compatible with your app.\n\n  ### Useful links\n\n  - [Expo Development CLI](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\n  - [Getting started with Expo apps](https://devcenter.bitrise.io/getting-started/getting-started-with-expo-apps/)\n\n  ### Related Steps\n\n  - [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2020-11-19T17:30:22.187155575Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: 9041582b6020bf1a8acd7c134d6cd3b5ca481651\nproject_type_tags:\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ninputs:\n- opts:\n    description: The root directory of the React Native project (the directory of\n      the project package.js file).\n    summary: The root directory of the React Native project\n    title: Working directory\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: \"Specify the Expo CLI version to install.  \\nThe Expo CLI ejects\n      your project and creates Xcode and Android Studio projects for your app.\\n\\n[https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\\n\\nA\n      couple of examples:\\n\\n* \\\"3.0.0\\\"\\n* latest\"\n    is_required: \"true\"\n    summary: Specify the Expo CLI version to install.\n    title: Expo CLI version\n- opts:\n    description: \"Your account's username for `https://expo.io/` .\\n\\nIn case of React\n      Native project __using Expo Kit__ library (any .js file imports expo),  \\nthe\n      `user_name` and `password` inputs are __required__.\\n\\nIf you provide these\n      inputs the step will run: `expo eject --eject-method expoKit`,  \\notherwise:\n      `expo eject --eject-method bare`.\\n\\n**NOTE:** You need to use your username\n      and not your e-mail address.\"\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: \"Your password for `https://expo.io/` .\\n\\nIn case of React Native\n      project __using Expo Kit__ library (any .js file imports expo),  \\nthe `user_name`\n      and `password` inputs are __required__.\\n\\nIf you provide these inputs the step\n      will run: `expo eject --eject-method expoKit`,  \\notherwise: `expo eject --eject-method\n      bare`.\"\n    is_sensitive: true\n    summary: Password for your Expo account.\n    title: Password for your Expo account\n  password: \"\"\n- opts:\n    description: \"Should the step run `expo publish` after eject?\\n\\nIn case of React\n      Native project using Expo Kit library (any .js file imports expo),  \\n`expo\n      publis` command generates the:\\n\\n- ./android/app/src/main/assets/shell-app-manifest.json\\n-\n      ./android/app/src/main/assets/shell-app.bundle\\n- ./ios/bitriseexpokit/Supporting/shell-app-manifest.json\\n-\n      ./ios/bitriseexpokit/Supporting/shell-app.bundle\\n\\nfiles, which are required\n      for the native builds.\"\n    summary: Should the step run `expo publish` after eject?\n    title: Run expo publish after eject?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  run_publish: \"no\"\n- opts:\n    description: React Native version to set in package.json after the eject process.\n    summary: React Native version to set in package.json after the eject process.\n    title: React Native version to set in package.json\n  override_react_native_version: null\n"
  },
  {
    "path": "steps/expo-detach/0.9.0/step.yml",
    "content": "title: '[Beta] Expo Detach'\nsummary: Creates Xcode and Android Studio projects for your app. Use this if you need\n  to add custom native functionality.\ndescription: |-\n  Using the The Expo Development CLI to create Xcode and Android Studio projects for your app.\n  **EXPO DEVELOPMENT CLI** https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2018-09-24T09:44:24.280753691Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: a8d1eb1f7b0e327c72b45b4410628a0dd4b8a109\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- opts:\n    description: The path of your project directory\n    is_required: true\n    summary: Project path\n    title: Project path\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: |-\n      Specify the Expo CLI verion to install.\n      The Expo CLI detach your project and creates Xcode and Android Studio projects for your app.\n\n\n      [https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\n\n\n      A couple of examples:\n\n\n      * \"2.0.0\"\n      * latest\n    is_required: \"true\"\n    summary: Specify the Expo CLI verion to install.\n    title: Expo CLI version\n- opts:\n    description: |-\n      Your account's username for `https://expo.io/` .\n\n\n      **NOTE** You need to use your username and not your e-mail adress.\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: Your password for `https://expo.io/` .\n    is_sensitive: true\n    summary: Password for your Expo account\n    title: Password for your Expo account\n  password: \"\"\n"
  },
  {
    "path": "steps/expo-detach/0.9.2/step.yml",
    "content": "title: '[Beta] Expo Eject'\nsummary: Creates Xcode and Android Studio projects for your app.\ndescription: |-\n  Using the The Expo Development CLI to create Xcode and Android Studio projects for your app.\n  **EXPO DEVELOPMENT CLI** https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2018-09-28T14:19:18.992377701Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: b3ca09b95db8cbf3ed72a2235994ec4721854401\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- opts:\n    description: The path of your project directory\n    is_required: true\n    summary: Project path\n    title: Project path\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: |-\n      Specify the Expo CLI version to install.\n      The Expo CLI ejects your project and creates Xcode and Android Studio projects for your app.\n\n\n      [https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\n\n\n      A couple of examples:\n\n\n      * \"2.0.0\"\n      * latest\n    is_required: \"true\"\n    summary: Specify the Expo CLI version to install.\n    title: Expo CLI version\n- opts:\n    description: |-\n      Your account's username for `https://expo.io/` .\n\n\n      **NOTE** You need to use your username and not your e-mail address.\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: Your password for `https://expo.io/` .\n    is_sensitive: true\n    summary: Password for your Expo account.\n    title: Password for your Expo account\n  password: \"\"\n"
  },
  {
    "path": "steps/expo-detach/0.9.3/step.yml",
    "content": "title: '[Beta] Expo Eject'\nsummary: Creates Xcode and Android Studio projects for your app.\ndescription: |-\n  Using the The Expo Development CLI to create Xcode and Android Studio projects for your app.\n  **EXPO DEVELOPMENT CLI** https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2018-10-31T15:25:40.855613639Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: daaa787cd47ddd68b190d45d4e097b84b6eca7cc\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- opts:\n    description: The root directory of the React Native project (the directory of\n      the project package.js file).\n    summary: The root directory of the React Native project\n    title: Working directory\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: \"Specify the Expo CLI version to install.  \\nThe Expo CLI ejects\n      your project and creates Xcode and Android Studio projects for your app.\\n\\n[https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\\n\\nA\n      couple of examples:\\n\\n* \\\"2.0.0\\\"\\n* latest\"\n    is_required: \"true\"\n    summary: Specify the Expo CLI version to install.\n    title: Expo CLI version\n- opts:\n    description: \"Your account's username for `https://expo.io/` .\\n\\nIn case of React\n      Native project __using Expo Kit__ library (any .js file imports expo),  \\nthe\n      `user_name` and `password` inputs are __required__.\\n\\nIf you provide these\n      inputs the step will run: `expo eject --eject-method expoKit`,  \\notherwise:\n      `expo eject --eject-method plain`.\\n\\n**NOTE:** You need to use your username\n      and not your e-mail address.\"\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: \"Your password for `https://expo.io/` .\\n\\nIn case of React Native\n      project __using Expo Kit__ library (any .js file imports expo),  \\nthe `user_name`\n      and `password` inputs are __required__.\\n\\nIf you provide these inputs the step\n      will run: `expo eject --eject-method expoKit`,  \\notherwise: `expo eject --eject-method\n      plain`.\"\n    is_sensitive: true\n    summary: Password for your Expo account.\n    title: Password for your Expo account\n  password: \"\"\n- opts:\n    description: \"Should the step run `expo publish` after eject?\\n\\nIn case of React\n      Native project using Expo Kit library (any .js file imports expo),  \\n`expo\n      publis` command generates the:\\n\\n- ./android/app/src/main/assets/shell-app-manifest.json\\n-\n      ./android/app/src/main/assets/shell-app.bundle\\n- ./ios/bitriseexpokit/Supporting/shell-app-manifest.json\\n-\n      ./ios/bitriseexpokit/Supporting/shell-app.bundle\\n\\nfiles, which are required\n      for the native builds.\"\n    summary: Should the step run `expo publish` after eject?\n    title: Run expo publish after eject?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  run_publish: \"no\"\n- opts:\n    description: React Native version to set in package.json after the eject process.\n    summary: React Native version to set in package.json after the eject process.\n    title: React Native version to set in package.json\n  override_react_native_version: null\n"
  },
  {
    "path": "steps/expo-detach/1.0.0/step.yml",
    "content": "title: Expo Eject\nsummary: Creates Xcode and Android Studio projects for your app.\ndescription: |2-\n\n  Expo is a toolchain that allows you to quickly get a React Native app up and running without having to use native code in Xcode or Android Studio. The Expo Eject Step is necessary to eject your app to install any missing native dependencies. Installing the native dependencies is done by our dedicated Steps, such as **Install missing Android SDK components** and **Run CocoaPods install**.\n\n  ### Configuring the Step\n\n  1. Add the Step to your Workflow after the Step or Steps that install your app's Javascript dependencies (such as **Run npm command** or **Run yarn command**).\n\n  1. Set the **Working directory input field** to the value of your project directory. By default, you do not have to change this.\n\n  1. Specify the Expo CLI version.\n\n     The default value is `latest` but you can specify an exact version, such as 3.0.0.\n\n  ### Troubleshooting\n\n  Make sure that the Expo CLI version you use is compatible with your app.\n\n  ### Useful links\n\n  - [Expo Development CLI](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\n  - [Getting started with Expo apps](https://devcenter.bitrise.io/getting-started/getting-started-with-expo-apps/)\n\n  ### Related Steps\n\n  - [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2020-12-04T15:38:27.526457428Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: f92d72cc9724b6c9de842e0403ef3e1ed57948bb\nproject_type_tags:\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ninputs:\n- opts:\n    description: The root directory of the React Native project (the directory of\n      the project package.js file).\n    summary: The root directory of the React Native project\n    title: Working directory\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: \"Specify the Expo CLI version to install.  \\nThe Expo CLI ejects\n      your project and creates Xcode and Android Studio projects for your app.\\n\\n[https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\\n\\nA\n      couple of examples:\\n\\n* \\\"3.0.0\\\"\\n* latest\"\n    is_required: \"true\"\n    summary: Specify the Expo CLI version to install.\n    title: Expo CLI version\n- opts:\n    description: |-\n      Your account's username for `https://expo.io/` .\n\n      Required if `run_publish` is set to \"yes\".\n      **NOTE:** You need to use your username and not your e-mail address.\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: |-\n      Your password for `https://expo.io/` .\n\n      Required if `run_publish` is set to \"yes\".\n    is_sensitive: true\n    summary: Password for your Expo account.\n    title: Password for your Expo account\n  password: \"\"\n- opts:\n    description: |-\n      Should the step run `expo publish` after eject?\n\n      If set to \"yes\" both, `user_name` and `password` are required to be provided.\n    summary: Should the step run `expo publish` after eject?\n    title: Run expo publish after eject?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  run_publish: \"no\"\n- opts:\n    description: React Native version to set in package.json after the eject process.\n    summary: React Native version to set in package.json after the eject process.\n    title: React Native version to set in package.json\n  override_react_native_version: null\n"
  },
  {
    "path": "steps/expo-detach/1.1.0/step.yml",
    "content": "title: Expo Eject\nsummary: Creates Xcode and Android Studio projects for your app.\ndescription: |2-\n\n  Expo is a toolchain that allows you to quickly get a React Native app up and running without having to use native code in Xcode or Android Studio. The Expo Eject Step is necessary to eject your app to install any missing native dependencies. Installing the native dependencies is done by our dedicated Steps, such as **Install missing Android SDK components** and **Run CocoaPods install**.\n\n  ### Configuring the Step\n\n  1. Add the Step to your Workflow after the Step or Steps that install your app's Javascript dependencies (such as **Run npm command** or **Run yarn command**).\n\n  1. Set the **Working directory input field** to the value of your project directory. By default, you do not have to change this.\n\n  1. Provide your Expo username and password if you are using an Expo module that requires logging in before ejecting your app. Please refer to the [Expo documentation](https://docs.expo.io/) for more information.\n\n  1. Specify the Expo CLI version.\n\n     The default value is `latest` but you can specify an exact version, such as 3.0.0.\n\n  ### Troubleshooting\n\n  Make sure that the Expo CLI version you use is compatible with your app.\n\n  ### Useful links\n\n  - [Expo Development CLI](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\n  - [Getting started with Expo apps](https://devcenter.bitrise.io/getting-started/getting-started-with-expo-apps/)\n\n  ### Related Steps\n\n  - [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\n  - [Install missing Android SDK components](https://www.bitrise.io/integrations/steps/install-missing-android-tools)\n  - [Run CocoaPods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\nwebsite: https://github.com/bitrise-steplib/steps-expo-detach\nsource_code_url: https://github.com/bitrise-steplib/steps-expo-detach\nsupport_url: https://github.com/bitrise-steplib/steps-expo-detach/issues\npublished_at: 2021-03-16T08:34:07.747189121Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-expo-detach.git\n  commit: 518310a0ab57286f0de2a894dc59e288f2f6e0f4\nproject_type_tags:\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-expo-detach\ninputs:\n- opts:\n    description: The root directory of the React Native project (the directory of\n      the project package.js file).\n    summary: The root directory of the React Native project\n    title: Working directory\n  project_path: $BITRISE_SOURCE_DIR\n- expo_cli_verson: latest\n  opts:\n    description: \"Specify the Expo CLI version to install.  \\nThe Expo CLI ejects\n      your project and creates Xcode and Android Studio projects for your app.\\n\\n[https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli](https://docs.expo.io/versions/latest/introduction/installation#local-development-tool-expo-cli)\\n\\nA\n      couple of examples:\\n\\n* \\\"3.0.0\\\"\\n* latest\"\n    is_required: \"true\"\n    summary: Specify the Expo CLI version to install.\n    title: Expo CLI version\n- opts:\n    description: |-\n      Your account's username for `https://expo.io/` . If provided, `expo login` will be run before eject.\n\n      Required if `run_publish` is set to \"yes\".\n      **NOTE:** You need to use your username and not your e-mail address.\n    summary: Username for Expo\n    title: Username for Expo\n  user_name: \"\"\n- opts:\n    description: |-\n      Your password for `https://expo.io/` . If provided, `expo login` will be run before eject.\n\n      Required if `run_publish` is set to \"yes\".\n    is_sensitive: true\n    summary: Password for your Expo account.\n    title: Password for your Expo account\n  password: \"\"\n- opts:\n    description: |-\n      Should the step run `expo publish` after eject?\n\n      If set to \"yes\" both, `user_name` and `password` are required to be provided.\n    summary: Should the step run `expo publish` after eject?\n    title: Run expo publish after eject?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  run_publish: \"no\"\n- opts:\n    description: React Native version to set in package.json after the eject process.\n    summary: React Native version to set in package.json after the eject process.\n    title: React Native version to set in package.json\n  override_react_native_version: null\n"
  },
  {
    "path": "steps/expo-detach/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/export-ios-to-lingohub/0.0.1/step.yml",
    "content": "title: iOS To LingoHub\nsummary: |\n  Push iOS project default language to LingoHub\ndescription: |\n  Will take the default language in your iOS project and update the terms in LingoHub using the xliff file produced\nwebsite: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import\nsource_code_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import\nsupport_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import/issues\npublished_at: 2019-02-06T13:31:33.432215Z\nsource:\n  git: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import.git\n  commit: 0dd4e8f031021181b3b99a6575dc470842dcf32a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lingohub_ios_account: null\n  opts:\n    is_required: true\n    summary: Username of project owner\n    title: Account\n    value_options: []\n- lingohub_ios_project_name: null\n  opts:\n    description: |\n      project url, e.g. “Sample Project” -> “sample-project”\n    is_required: true\n    summary: Name of Project\n    title: Project\n    value_options: []\n- lingohub_ios_token: null\n  opts:\n    description: |\n      Can obtain from here https://translate.lingohub.com/user/edit\n    is_required: true\n    is_sensitive: true\n    summary: Auth Token to authenticate\n    title: Auth Token\n    value_options: []\n- lingohub_ios_upload_language: null\n  opts:\n    is_required: true\n    summary: This should be your default development language\n    title: Upload Language\n    value_options: []\n- lingohub_ios_project_path: null\n  opts:\n    is_required: true\n    summary: Path to .xcodeproj\n    title: Project Path\n    value_options: []\n"
  },
  {
    "path": "steps/export-ios-to-lingohub/0.0.2/step.yml",
    "content": "title: iOS To LingoHub\nsummary: |\n  Push iOS project default language to LingoHub\ndescription: |\n  Will take the default language in your iOS project and update the terms in LingoHub using the xliff file produced\nwebsite: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import\nsource_code_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import\nsupport_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import/issues\npublished_at: 2019-02-13T12:24:49.47339Z\nsource:\n  git: https://github.com/muzmatch/apps-ios-bitrise-lingohub-import.git\n  commit: 06040711143224836e329c55a7719e825aeb5489\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lingohub_ios_account: null\n  opts:\n    is_required: true\n    summary: Username of project owner\n    title: Account\n    value_options: []\n- lingohub_ios_project_name: null\n  opts:\n    description: |\n      project url, e.g. “Sample Project” -> “sample-project”\n    is_required: true\n    summary: Name of Project\n    title: Project\n    value_options: []\n- lingohub_ios_token: null\n  opts:\n    description: |\n      Can obtain from here https://translate.lingohub.com/user/edit\n    is_required: true\n    is_sensitive: true\n    summary: Auth Token to authenticate\n    title: Auth Token\n    value_options: []\n- lingohub_ios_upload_language: null\n  opts:\n    is_required: true\n    summary: This should be your default development language\n    title: Upload Language\n    value_options: []\n- lingohub_ios_project_path: null\n  opts:\n    is_required: true\n    summary: Path to .xcodeproj\n    title: Project Path\n    value_options: []\n"
  },
  {
    "path": "steps/export-ios-to-lingohub/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/export-lingohub-to-ios/0.0.1/step.yml",
    "content": "title: LingoHub to iOS\nsummary: |\n  Pull languages from LingoHub and import them into XCode Project\ndescription: |\n  Will take all the languages available in LingoHub and import them into your .xcodeproj using xliff format\nwebsite: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export\nsource_code_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export\nsupport_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export/issues\npublished_at: 2019-02-12T10:29:54.731213Z\nsource:\n  git: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export.git\n  commit: c9a0bdfbfe3cd089169a7381ce0368903b19259b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lingohub_to_ios_account: null\n  opts:\n    is_required: true\n    summary: Username of project owner\n    title: Account\n    value_options: []\n- lingohub_to_ios_project_name: null\n  opts:\n    description: |\n      project url, e.g. “Sample Project” -> “sample-project”\n    is_required: true\n    summary: Name of Project\n    title: Project\n    value_options: []\n- lingohub_to_ios_token: null\n  opts:\n    description: |\n      Can obtain from here https://translate.lingohub.com/user/edit\n    is_required: true\n    is_sensitive: true\n    summary: Auth Token to authenticate\n    title: Auth Token\n    value_options: []\n- lingohub_to_ios_project_path: null\n  opts:\n    is_required: true\n    summary: Path to .xcodeproj\n    title: Project Path\n    value_options: []\n"
  },
  {
    "path": "steps/export-lingohub-to-ios/0.0.2/step.yml",
    "content": "title: LingoHub to iOS\nsummary: |\n  Pull languages from LingoHub and import them into XCode Project\ndescription: |\n  Will take all the languages available in LingoHub and import them into your .xcodeproj using xliff format\nwebsite: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export\nsource_code_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export\nsupport_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export/issues\npublished_at: 2019-02-13T12:33:23.661143Z\nsource:\n  git: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export.git\n  commit: b6d1569ca3623cba7e43052ad3c394e83b22d30c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lingohub_to_ios_account: null\n  opts:\n    is_required: true\n    summary: Username of project owner\n    title: Account\n    value_options: []\n- lingohub_to_ios_project_name: null\n  opts:\n    description: |\n      project url, e.g. “Sample Project” -> “sample-project”\n    is_required: true\n    summary: Name of Project\n    title: Project\n    value_options: []\n- lingohub_to_ios_token: null\n  opts:\n    description: |\n      Can obtain from here https://translate.lingohub.com/user/edit\n    is_required: true\n    is_sensitive: true\n    summary: Auth Token to authenticate\n    title: Auth Token\n    value_options: []\n- lingohub_to_ios_project_path: null\n  opts:\n    is_required: true\n    summary: Path to .xcodeproj\n    title: Project Path\n    value_options: []\n"
  },
  {
    "path": "steps/export-lingohub-to-ios/0.0.3/step.yml",
    "content": "title: LingoHub to iOS\nsummary: |\n  Pull languages from LingoHub and import them into XCode Project\ndescription: |\n  Will take all the languages available in LingoHub and import them into your .xcodeproj using xliff format\nwebsite: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export\nsource_code_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export\nsupport_url: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export/issues\npublished_at: 2019-02-21T11:50:44.789643Z\nsource:\n  git: https://github.com/muzmatch/apps-ios-bitrise-lingohub-export.git\n  commit: 3eb31039dee7782f65f14f7db03181ecd771b992\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lingohub_to_ios_account: null\n  opts:\n    is_required: true\n    summary: Username of project owner\n    title: Account\n    value_options: []\n- lingohub_to_ios_project_name: null\n  opts:\n    description: |\n      project url, e.g. “Sample Project” -> “sample-project”\n    is_required: true\n    summary: Name of Project\n    title: Project\n    value_options: []\n- lingohub_to_ios_token: null\n  opts:\n    description: |\n      Can obtain from here https://translate.lingohub.com/user/edit\n    is_required: true\n    is_sensitive: true\n    summary: Auth Token to authenticate\n    title: Auth Token\n    value_options: []\n- lingohub_to_ios_project_path: null\n  opts:\n    is_required: true\n    summary: Path to .xcodeproj\n    title: Project Path\n    value_options: []\n- lingohub_to_ios_upload_language: null\n  opts:\n    is_required: true\n    summary: Default language of xcodeproj, e.g. en\n    title: Upload language\n    value_options: []\n"
  },
  {
    "path": "steps/export-lingohub-to-ios/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/export-xcarchive/0.9.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2016-10-18T14:36:25.662778162+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 11298d24d810ed9a95f9fe929a839b574ced5ac7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"Describes how Xcode should export the archive.   \\n\\nIf you select\n      `auto-detect` step will figure out proper export method  \\nbased on provisioning\n      profile embedded into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty the step will use the embedded provisining\n      profile.\n    title: Specify Provisioning Profile name to use by export\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS or tvOS .dSYM file's path\n"
  },
  {
    "path": "steps/export-xcarchive/0.9.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2016-11-23T17:14:35.055329275+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: a292c2ba011e3168cf07d6f9f029949468dad420\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"Describes how Xcode should export the archive.   \\n\\nIf you select\n      `auto-detect` step will figure out proper export method  \\nbased on provisioning\n      profile embedded into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: |-\n      This input will be used if `use_legacy_export` is set to `\"yes\"`.\n\n      If this input is empty the step will use the embedded provisining profile.\n    title: Specify Provisioning Profile name to use by export\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/0.9.2/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2016-12-19T17:13:03.776916424+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 33ba72f197976dcc5fe19c42d029de5d9d4535aa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"Describes how Xcode should export the archive.   \\n\\nIf you select\n      `auto-detect` step will figure out proper export method  \\nbased on provisioning\n      profile embedded into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: |-\n      This input will be used if `use_legacy_export` is set to `\"yes\"`.\n\n      If this input is empty the step will use the embedded provisining profile.\n    title: Specify Provisioning Profile name to use by export\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/1.0.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2017-11-24T12:46:59.588323192+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 665f0194a75ad6b22870b1a54524caa0e3b5dc64\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: |-\n      This input will be used if `use_legacy_export` is set to `\"yes\"`.\n\n      If this input is empty the step will use the embedded provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/1.0.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2017-12-21T11:31:16.916807+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 2a77d57319afb8f66d21ee29b38b37a53fe01967\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: |-\n      This input will be used if `use_legacy_export` is set to `\"yes\"`.\n\n      If this input is empty the step will use the embedded provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/1.0.2/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2019-10-11T08:49:40.546960322Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 5425be33bc7c8b7db3bd72d7d04c7bfabaa7884a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: |-\n      This input will be used if `use_legacy_export` is set to `\"yes\"`.\n\n      If this input is empty the step will use the embedded provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/1.0.3/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2019-11-12T14:22:29.783910219Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: e99c520f113cc3f27355507547ea03acefc2435c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy ipa export method.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: |-\n      This input will be used if `use_legacy_export` is set to `\"yes\"`.\n\n      If this input is empty the step will use the embedded provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/2.0.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2020-01-09T09:46:12.893326829Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: bd60f2b5635e7079b7528ca69a3b52abf5188737\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: |-\n      If this input is set to `yes`, step will use legacy ipa export method.\n\n      The embedded provisining profile will be used.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/2.1.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2020-10-08T13:52:54.091072647Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 5b89c265864b138e3af703deab4fe18f6ec03b89\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: \"Describes which product to export.   \\nPossible options are App\n      or App Clip.\"\n    is_required: true\n    summary: \"\"\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: |-\n      If this input is set to `yes`, step will use legacy ipa export method.\n\n      The embedded provisining profile will be used.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/2.2.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2020-12-09T14:55:32.938447101Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: bbc2eccb419e98b72f921173eee23ac75a7a85ab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect` step\n      will figure out proper export method  \\nbased on provisioning profile embedded\n      into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: \"Describes which product to export.   \\nPossible options are App\n      or App Clip.\"\n    is_required: true\n    summary: \"\"\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: |-\n      If this input is set to `yes`, step will use legacy ipa export method.\n\n      The embedded provisining profile will be used.\n    is_required: true\n    title: Use legacy ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/3.0.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS Xcode archive\ndescription: |-\n  Export iOS and tvOS Xcode archive.\n\n  Exports .ipa from iOS and tvOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2020-12-10T08:28:43.637754883Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: d57006554c32507971a8676af3df5b0753f08644\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: Path to the iOS or tvOS archive (.xcarchive) which should be exported.\n    is_required: true\n    summary: iOS or tvOS archive path\n    title: iOS or tvOS archive path\n- export_method: auto-detect\n  opts:\n    description: \"`auto-detect` option is **DEPRECATED** - use direct export methods!\\n\\nDescribes\n      how Xcode should export the archive.   \\n\\nIf you select `auto-detect`, the\n      step will figure out the proper export method  \\nbased on the provisioning profile\n      embedded into the generated xcode archive.\"\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: \"Describes which product to export.   \\nPossible options are App\n      or App Clip.\"\n    is_required: true\n    summary: \"\"\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/4.0.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: Exports an IPA from an existing iOS and tvOS `.xcarchive` file.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2021-10-04T10:10:51.908667131Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 933de40a9d3886ab0514702c57ac2938b0442d29\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS or tvOS .ipa file's path.\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive/4.1.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2021-12-07T11:03:51.192641623Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 25b4a31beca0c12301a81a6329dd9eb72cb60251\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2021-12-08T10:27:41.096706436Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: a7c42739dd012d2823935e8545044c81bd37df13\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2021-12-13T13:39:26.550974792Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 127be8c00b6ba3202d599026b8dd1e9279175850\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.2/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2021-12-17T16:10:46.960446626Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 9d73808a8dba4e4bf5a2ef45d43c6ad1f8427e06\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.3/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-01-06T17:52:10.389203342Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 97b5b364c87021a39ccb9ec92b09f9927891b6b8\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.4/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-01-21T09:20:22.257982101Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 88024332fe87449be724e334b2676475f58f1dbb\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.5/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-01-28T13:30:17.767640162Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 8342dbf5bbdc2b89dd6c3257e297716fc8151afd\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.6/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-02-23T21:19:19.621198073Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 532a5cbe6b090f5bf83770558cdde0b121c844ee\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.7/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-03-21T10:21:58.453167584Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: f2eec7e3f9d9e2f10dfdd6902f894a77d6ab784b\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.2.8/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-04-14T15:25:33.521817524Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 365f8740ae6d073ead2b6371d4028ac4a54f6318\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.3.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2022-08-12T08:29:14.477355047Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 85912c3ed82c5595b29b231a29d8a6ed25bb0776\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.3.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2023-03-01T10:14:10.077557721Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: f8dc2af1f1b4a4a962fb09bc18e25af0e253221e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.4.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2023-06-16T12:26:28.083593245Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 5c637d6a6c34c6c23444ea6bc3223db768ee74f4\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.5.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2023-08-30T06:13:54.020866906Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 56113d9e614fceb288c514c4be41a246363573c3\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.5.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2024-04-16T14:29:48.780774145Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 52cb93a1cab6426622c85f1f2c6f26f538baec17\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.5.2/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2024-08-05T07:29:04.797719867Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: b4a537d113a13275e006f8b7af4dde88dd7e818d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.5.3/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2024-10-21T19:44:43.303116017Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: c31496d986a0ed04a619d6cb8e04f15e8694ec9d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.6.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2024-11-21T12:51:35.189073467Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 1df1e70527a2b7ee73f637b8589bda0c0840d20f\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.6.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-01-14T13:06:52.479158394Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: b2bbee9d1a07d139e0644dd8ba35db22b5613dd7\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.6.2/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-03-21T15:53:46.188988537Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 80f530e3bdfffe79d7b4a8d84fbf7c693db5b199\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.6.3/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-04-09T09:23:19.672272612Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 97fd326411c32f7959a3f4b7177a2251b7898101\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.7.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-04-14T13:33:13.79548431Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 05b4884638232ff700e1158ac03b1478bd7e751c\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    is_required: true\n    summary: Describes which product to export.\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.8.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-04-23T12:05:16.199765155Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 236ec2f3d56b2cc1e3f8effd08f8a27e9086447a\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    description: |-\n      Describes which product to export. (Not needed for app-store distribution.)\n\n      For app-store distribution both the main App and the App Clip are included in the IPA, regardless of this setting.\n    is_required: true\n    summary: Describes which product to export. (Not needed for app-store distribution.)\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.8.1/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-05-16T12:07:22.911050523Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 0b8870449ef1e33c93de937cc8acf181cfb5f3fe\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    description: |-\n      Describes which product to export. (Not needed for app-store distribution.)\n\n      For app-store distribution both the main App and the App Clip are included in the IPA, regardless of this setting.\n    is_required: true\n    summary: Describes which product to export. (Not needed for app-store distribution.)\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.8.2/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-06-18T13:55:04.025411312Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: 195a0c22fc27ea86a4a9aac9ef0de855be858a96\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    description: |-\n      Describes which product to export. (Not needed for app-store distribution.)\n\n      For app-store distribution both the main App and the App Clip are included in the IPA, regardless of this setting.\n    is_required: true\n    summary: Describes which product to export. (Not needed for app-store distribution.)\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.8.3/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-08-26T11:31:33.953358164Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: ad067886f2fd7f29a5423882857796600c97d13f\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    description: |-\n      Describes which product to export. (Not needed for app-store distribution.)\n\n      For app-store distribution both the main App and the App Clip are included in the IPA, regardless of this setting.\n    is_required: true\n    summary: Describes which product to export. (Not needed for app-store distribution.)\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.8.4/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2025-11-11T08:10:22.321816294Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: c280e4ed7916bcd0ec289f590d69ffe3184b4106\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    description: |-\n      Describes which product to export. (Not needed for app-store distribution.)\n\n      For app-store distribution both the main App and the App Clip are included in the IPA, regardless of this setting.\n    is_required: true\n    summary: Describes which product to export. (Not needed for app-store distribution.)\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/4.9.0/step.yml",
    "content": "title: Export iOS and tvOS Xcode archive\nsummary: Export iOS and tvOS IPA from an existing Xcode archive\ndescription: |-\n  Exports an IPA from an existing iOS and tvOS `.xcarchive` file. You can add multiple **Export iOS and tvOS Xcode archive** Steps to your Workflows to create multiple different signed .ipa files.\n  The Step also logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and downloads any provisioning profiles needed for your project based on the **Distribution method**.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Archive Path**: Specifies the archive that should be exported. The input value sets xcodebuild's `-archivePath` option.\n  2. **Select a product to distribute**: Decide if an App or an App Clip IPA should be exported.\n  3. **Distribution method**: Describes how Xcode should export the archive: development, app-store, ad-hoc, or enterprise.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive/issues\npublished_at: 2026-05-12T12:10:22.16155596Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive.git\n  commit: c09389699734d47e03b9ebf28f604d5ca15a2e08\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/export-xcarchive/4.9.0/bin/export-xcarchive-darwin-amd64\n    hash: sha256-67996f5ca5f670cd920db3d94c7b21ecd2d5e4a641d2ac2951d389b04229df14\n  darwin-arm64:\n    storage_uri: steps/export-xcarchive/4.9.0/bin/export-xcarchive-darwin-arm64\n    hash: sha256-5707f1573e36115fa6dc79f5720ba6a4030d4cebc2ba9a3f74e384da47b1bfad\n  linux-amd64:\n    storage_uri: steps/export-xcarchive/4.9.0/bin/export-xcarchive-linux-amd64\n    hash: sha256-c23b0e0bebe45f39347d09a876ef356e5c2d6c7b7eac1493ff46f5937c609fdb\n  linux-arm64:\n    storage_uri: steps/export-xcarchive/4.9.0/bin/export-xcarchive-linux-arm64\n    hash: sha256-ce42dc0f7c0893c9a7b4706e90af62e4c089bc5eb304085eb703425bddb3af35\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    description: |-\n      Specifies the archive that should be exported.\n\n      The input value sets xcodebuild's `-archivePath` option.\n    is_required: true\n    summary: Specifies the archive that should be exported.\n    title: Archive path\n- opts:\n    description: |-\n      Describes which product to export. (Not needed for app-store distribution.)\n\n      For app-store distribution both the main App and the App Clip are included in the IPA, regardless of this setting.\n    is_required: true\n    summary: Describes which product to export. (Not needed for app-store distribution.)\n    title: Select a product to distribute\n    value_options:\n    - app\n    - app-clip\n  product: app\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- manage_version_and_build_number: \"no\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Should Xcode manage the app's build number when uploading to App Store\n      Connect. This will change the version and build numbers of all content in your\n      app only if the is an invalid number (like one that was used previously or precedes\n      your current build number). The input will not work if `export options plist\n      content` input has been set. Default set to No.\n    title: Xcode manage version and build number (App Store Connect)\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: The created iOS or tvOS .ipa file's path.\n    title: iOS or tvOS IPA\n- BITRISE_DSYM_PATH: null\n  opts:\n    summary: Step will collect every dsym (app dsym and framwork dsyms) in a directory,\n      zip it and export the zipped directory path.\n    title: The created iOS or tvOS .dSYM zip file's path.\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    summary: Path to the xcdistributionlogs zip\n    title: xcdistributionlogs\n"
  },
  {
    "path": "steps/export-xcarchive/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/export-xcarchive-mac/0.9.0/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2016-10-18T14:49:43.340291944+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: 3d4867f57a8d68e6ab1a43580c7349ca7328d505\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n    - developer-id\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty xcodebuild will grab one of the matching installed\n      provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/export-xcarchive-mac/0.9.1/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2016-11-23T17:16:16.478067191+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: bd0f7ba801d16f72fc09817801479f016cb36968\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n    - developer-id\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty xcodebuild will grab one of the matching installed\n      provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/0.9.2/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2016-12-20T17:42:22.983295803+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: 0fde6a3d728b63e61eeba886dbf9236ca48d6007\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n    - developer-id\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty xcodebuild will grab one of the matching installed\n      provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.0.2/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2017-11-22T15:23:36.743181966+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: e560ec8bb2e37bd8e16a7ba1a8b0045f394914c1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty xcodebuild will grab one of the matching installed\n      provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.0.3/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2020-12-11T16:51:44.567190172Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: 161053c79a1b4abfd70d7ec8b2aa748737cd6785\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty xcodebuild will grab one of the matching installed\n      provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.0.4/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2020-12-11T17:03:35.28798118Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: 94185e0e7a08b091c051f9af7b88c84e0cb1c99c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, the step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty, xcodebuild will grab one of the matching\n      installed provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.1.0/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2021-02-17T15:10:29.788165427Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: b29039751eba2cc6d609c496ec887e8d1c2dc26a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, the step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty, xcodebuild will grab one of the matching\n      installed provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.1.1/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: |-\n  Export macOS Xcode archive.\n\n  Exports .app or .pkg from macOS .xcarchive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2022-02-04T18:05:44.823070021Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: 5a6d6a0d40d9b6278a663779a72c114c70397c5f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4` \"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, the step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty, xcodebuild will grab one of the matching\n      installed provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs zip\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.1.2/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: This step exports an app (`.app` or `.pkg` from an existing macOS `xcarchive`.\n  This is useful when one archive needs to be exported with different distribution\n  methods without rebuilding the archive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2022-03-03T12:25:18.379571801Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: bac9b4ee66b8ca4f1acda6fc566fa0fed62144cb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    category: Export configuration\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export configuration\n    description: For __non-App Store__ exports, should Xcode re-compile the app from\n      bitcode?\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, the step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty, xcodebuild will grab one of the matching\n      installed provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    description: The created macOS `.app` file's path\n    title: macOS .app path\n- BITRISE_PKG_PATH: null\n  opts:\n    description: The created macOS `.pkg` file's path\n    title: macOS .pkg path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Path to the `xcdistributionlogs` ZIP file\n    title: '`xcdistributionlogs` ZIP path'\n"
  },
  {
    "path": "steps/export-xcarchive-mac/1.2.0/step.yml",
    "content": "title: Export macOS Xcode archive\nsummary: Export macOS Xcode archive\ndescription: This step exports an app (`.app` or `.pkg` from an existing macOS `xcarchive`.\n  This is useful when one archive needs to be exported with different distribution\n  methods without rebuilding the archive.\nwebsite: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues\npublished_at: 2023-08-30T07:09:59.033815042Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-export-xcarchive-mac.git\n  commit: 67a7b4e57c5db11bcd78f76e57242c95e3972380\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH\n  opts:\n    description: Path to the macOS archive (.xcarchive) which should be exported.\n    title: macOS archive path\n- export_method: development\n  opts:\n    description: Describes how Xcode should export the archive.\n    is_required: true\n    title: Select method for export\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- opts:\n    category: Export configuration\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export configuration\n    description: For __non-App Store__ exports, should Xcode re-compile the app from\n      bitcode?\n    is_required: true\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: The Developer Portal team to use for this export\n  team_id: null\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on the embedded provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    description: If this input is set to `yes`, the step will use legacy export method.\n    is_required: true\n    title: Use legacy export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_legacy_export: \"no\"\n- legacy_export_provisioning_profile_name: null\n  opts:\n    description: If this input is empty, xcodebuild will grab one of the matching\n      installed provisining profile.\n    title: Specify Provisioning Profile name to use by export\n- legacy_export_output_format: app\n  opts:\n    description: Specify export format\n    is_required: true\n    title: Specify export format\n    value_options:\n    - app\n    - pkg\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    description: The created macOS `.app` file's path\n    title: macOS .app path\n- BITRISE_PKG_PATH: null\n  opts:\n    description: The created macOS `.pkg` file's path\n    title: macOS .pkg path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Path to the `xcdistributionlogs` ZIP file\n    title: '`xcdistributionlogs` ZIP path'\n"
  },
  {
    "path": "steps/export-xcarchive-mac/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.0.0/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2015-09-08T13:23:04.587005867+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 2cf25e46e89412a7c1527a9cb38dcfd42dd5f456\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.0.1/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2016-02-26T15:03:29.380840456+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 9faa67476c64ac096037857cc76f883d868f4152\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.1.0/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2016-05-30T14:28:46.645930146+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: d4e09748b66986b238c8aecd7a6f09e4458d79ee\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.1.1/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2016-06-01T11:53:06.796588287+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 0fddf5ad1f98c73f8c747a0dd1c7155ad492bb1a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.2.0/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2016-09-19T13:57:33.92813459+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: ba9e8b310560b896187520401a01c90cf0eb1b28\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.2.1/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2016-10-31T13:09:32.058265911+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 9c0fcdde977c2d69f3b002cf0a86cdaed74adb89\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.2.3/step.yml",
    "content": "title: Fabric / Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics / Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric / Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account\n  * After your first Fabric & Crashlytics app setup the app should be listed on [https://fabric.io](https://fabric.io)\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode and if the Fabric menu bar app is running it'll show an upload popup\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: !!timestamp 2018-03-27T11:41:08.426979764+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 585bed270d59c00337c91b80dab778293a8c1686\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to\n      and at the top you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.2.4/step.yml",
    "content": "title: Fabric/Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics/Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric/Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account.\n  * After your first Fabric & Crashlytics app setup, the app should be listed on [https://fabric.io](https://fabric.io).\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode, if the Fabric menu bar app is running, it'll show an upload popup.\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2018-08-31T11:02:15.44690318Z\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 61b936f68eb3273c86924b249e89a279a0695bf4\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation, open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_sensitive: true\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.2.5/step.yml",
    "content": "title: Fabric/Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics/Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric/Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account.\n  * After your first Fabric & Crashlytics app setup, the app should be listed on [https://fabric.io](https://fabric.io).\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode, if the Fabric menu bar app is running, it'll show an upload popup.\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2018-10-18T14:36:18.783919368Z\nsource:\n  git: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy.git\n  commit: 086b48937724eb8b616714ace8db21b65241752f\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation, open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_sensitive: true\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.3.0/step.yml",
    "content": "title: Fabric/Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics/Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric/Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account.\n  * After your first Fabric & Crashlytics app setup, the app should be listed on [https://fabric.io](https://fabric.io).\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode, if the Fabric menu bar app is running, it'll show an upload popup.\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2019-08-16T11:54:26.506428042Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fabric-crashlytics-beta-deploy.git\n  commit: 7d8e935fe4a6bbed3bdbd680c3b3e6dc58c897f8\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta.\n      Required for Crashlytics dSYM upload with projects that use or migrated from Fabric to Firebase Crashlytics.\n\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta. Not needed for dSYM upload with upload-symbols.\n\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Set this input to empty string to perform only dSYM upload (no Crashlytics\n      Beta deploy).\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    category: dSYM upload\n    description: |-\n      To turn on dSYM generation, open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- opts:\n    category: dSYM upload\n    description: |-\n      The path to GoogleService-Info.plist when using upload-symbols with Firebase Crashlytics.\n\n      Important: If you're working with an app that you previously linked from Fabric to Firebase Crashlytics, pass in your Fabric API Key to run the upload symbols script.\n    title: GoogleService-Info.plist path\n  service_info_plist_path: \"\"\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_sensitive: true\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.3.1/step.yml",
    "content": "title: Fabric/Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics/Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric/Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account.\n  * After your first Fabric & Crashlytics app setup, the app should be listed on [https://fabric.io](https://fabric.io).\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode, if the Fabric menu bar app is running, it'll show an upload popup.\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2019-10-15T09:12:09.311974597Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fabric-crashlytics-beta-deploy.git\n  commit: 42447d2d6d9521c20c2fc4f5db2fd9c2c318f10d\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta.\n      Required for Crashlytics dSYM upload with projects that use or migrated from Fabric to Firebase Crashlytics.\n\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta. Not needed for dSYM upload with upload-symbols.\n\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Set this input to empty string to perform only dSYM upload (no Crashlytics\n      Beta deploy).\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    category: dSYM upload\n    description: |-\n      To turn on dSYM generation, open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- opts:\n    category: dSYM upload\n    description: |-\n      The path to GoogleService-Info.plist when using upload-symbols with Firebase Crashlytics.\n\n      Important: If you're working with an app that you previously linked from Fabric to Firebase Crashlytics, pass in your Fabric API Key to run the upload symbols script.\n    title: GoogleService-Info.plist path\n  service_info_plist_path: \"\"\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_sensitive: true\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.3.2/step.yml",
    "content": "title: Fabric/Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics/Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric/Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account.\n  * After your first Fabric & Crashlytics app setup, the app should be listed on [https://fabric.io](https://fabric.io).\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode, if the Fabric menu bar app is running, it'll show an upload popup.\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2020-02-11T15:50:44.421758093Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fabric-crashlytics-beta-deploy.git\n  commit: a607641a7652bdd0167bea8b77addfafc2498ee5\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta.\n      Required for Crashlytics dSYM upload with projects that use or migrated from Fabric to Firebase Crashlytics.\n\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta. Not needed for dSYM upload with upload-symbols.\n\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Set this input to empty string to perform only dSYM upload (no Crashlytics\n      Beta deploy).\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    category: dSYM upload\n    description: |-\n      To turn on dSYM generation, open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- opts:\n    category: dSYM upload\n    description: |-\n      The path to GoogleService-Info.plist when using upload-symbols with Firebase Crashlytics.\n\n      Important: If you're working with an app that you previously linked from Fabric to Firebase Crashlytics, pass in your Fabric API Key to run the upload symbols script.\n    title: GoogleService-Info.plist path\n  service_info_plist_path: \"\"\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_sensitive: true\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/2.3.3/step.yml",
    "content": "title: Fabric/Crashlytics deployer\nsummary: |-\n  Use the awesome Crashlytics/Fabric beta distribution service during your\n  workflow. Add notes, send notification to the testers, groups or to any email\n  address and let the search for those nasty bugs begin!\ndescription: |-\n  Deploys to Fabric/Crashlytics beta testing service.\n\n  ## How to setup your Xcode project for [Fabric](https://get.fabric.io/) / Crashlytics beta testing?\n\n  * Register a Fabric account at [https://get.fabric.io/](https://get.fabric.io/).\n  * Add Fabric & Crashlytics to your Xcode project as described when you first sign into your Fabric account.\n  * After your first Fabric & Crashlytics app setup, the app should be listed on [https://fabric.io](https://fabric.io).\n  * You should also test that everything works correctly with a manual version upload: just Create an Archive in Xcode, if the Fabric menu bar app is running, it'll show an upload popup.\n\n  Your app is now ready to be deployed with this Step!\nwebsite: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsource_code_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy\nsupport_url: https://github.com/bitrise-io/steps-fabric-crashlytics-beta-deploy/issues\npublished_at: 2020-12-01T09:26:24.0277899Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fabric-crashlytics-beta-deploy.git\n  commit: 8cafee25f118b78de8f4deed1506384a37367f62\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta.\n      Required for Crashlytics dSYM upload with projects that use or migrated from Fabric to Firebase Crashlytics.\n\n      You can get your API Key under **Organizations**\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **API Key**.\n      Click it and the API key will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: API Key'\n- build_secret: \"\"\n  opts:\n    description: |-\n      Required for Crashlytics Beta. Not needed for dSYM upload with upload-symbols.\n\n      You can get the Build Secret key on the same\n      page as the API Key.\n\n      Select the **Organizations** option\n      at [https://fabric.io/settings](https://fabric.io/settings).\n\n      Select the organization your app belongs to.\n      At the top, you'll see a text: **Build Secret**.\n      Click it and the Build Secret will appear.\n    is_required: false\n    is_sensitive: true\n    summary: \"\"\n    title: 'Fabric: Build Secret'\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Set this input to empty string to perform only dSYM upload (no Crashlytics\n      Beta deploy).\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    category: dSYM upload\n    description: |-\n      To turn on dSYM generation, open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path\n- opts:\n    category: dSYM upload\n    description: |-\n      The path to GoogleService-Info.plist when using upload-symbols with Firebase Crashlytics.\n\n      Important: If you're working with an app that you previously linked from Fabric to Firebase Crashlytics, pass in your Fabric API Key to run the upload symbols script.\n    title: GoogleService-Info.plist path\n  service_info_plist_path: \"\"\n- email_list: \"\"\n  opts:\n    description: \"Optional list of individual addresses (comma-separated)\\uFEFF\\n\"\n    is_sensitive: true\n    summary: \"\"\n    title: 'Notify: Emails'\n- group_aliases_list: \"\"\n  opts:\n    description: Optional list of group aliases from web dashboard (comma-separated)\n    summary: \"\"\n    title: 'Notify: Group Aliases'\n- notification: \"Yes\"\n  opts:\n    description: Should send email notification to testers about the new release?\n    is_required: true\n    summary: \"\"\n    title: Notify testers?\n    value_options:\n    - \"Yes\"\n    - \"No\"\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: Release Notes\n  release_notes: Automatic build with Bitrise\n"
  },
  {
    "path": "steps/fabric-crashlytics-beta-deploy/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/fastlane/2.0.0/step.yml",
    "content": "title: Fastlane\nsummary: |-\n  You probably heard of the awesome fastlane. We are proud to welcome this\n  great tool in the integrations section. Add the step to your workflow and\n  enjoy your ride with us in the fastlane!\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2015-09-10T16:48:13.692401803+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: c4e819193bcaceef0c4356653d4bf7fa5ce93fd6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\n- fastlane\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lane: null\n  opts:\n    description: |\n      Fastlane lane to run\n      $ fastlane [lane]\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Fastlane lane\n- opts:\n    description: |\n      Work directory\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Work directory\n  work_dir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/fastlane/2.1.0/step.yml",
    "content": "title: Fastlane\nsummary: |-\n  You probably heard of the awesome fastlane. We are proud to welcome this\n  great tool in the integrations section. Add the step to your workflow and\n  enjoy your ride with us in the fastlane!\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2015-11-11T12:55:21.163194699+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: aa852e4ab93b50523ab5a05b5dbed42b492a0f06\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\n- fastlane\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lane: null\n  opts:\n    description: |\n      Fastlane lane to run\n      $ fastlane [lane]\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Fastlane lane\n- opts:\n    description: |\n      Work directory\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Work directory\n  work_dir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/fastlane/2.1.1/step.yml",
    "content": "title: Fastlane\nsummary: |-\n  You probably heard of the awesome fastlane. We are proud to welcome this\n  great tool in the integrations section. Add the step to your workflow and\n  enjoy your ride with us in the fastlane!\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2015-12-12T17:22:28.751748689+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 74bfe38ce92c265a0c9eb0498e6d612557b1336e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\n- fastlane\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- lane: null\n  opts:\n    description: |\n      Fastlane lane to run\n      $ fastlane [lane]\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Fastlane lane\n- opts:\n    description: |\n      Work directory\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Work directory\n  work_dir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/fastlane/2.1.2/step.yml",
    "content": "title: Fastlane\nsummary: |-\n  You probably heard of the awesome fastlane. We are proud to welcome this\n  great tool in the integrations section. Add the step to your workflow and\n  enjoy your ride with us in the fastlane!\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2016-02-26T15:19:44.94592212+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: ede215ca318bd897fedf97d40f8a886450df6d36\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\n- fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      Fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: Fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/fastlane/2.1.3/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2016-04-08T14:45:42.26374279+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 30d7dc143c722f9a0847541bb24533a02e1307dc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/fastlane/2.2.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2016-05-11T12:28:12.630029642+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 3a230e0328115f5947747123435c2275c2e9ff74\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-01-11T17:18:57.289565053+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 7687922f1cf3acf6e31fa48de719b6c1a21c0022\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-01-13T14:14:53.289558266+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 92916b39b5d22a521ca49dc55983ae8ddc8791ec\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.11/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-12-19T15:04:53.83775983+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: bb21ea7c310b8d3e0eb40abee4edebbf33ff3f31\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\n- fastlane\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.12/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-12-21T17:30:34.238582012+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: ae39dbb65a36320446593e1e2f104b93b62bf09c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\n- fastlane\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.13/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-03-14T15:44:07.076885674Z\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: a20006ba1a767360bd3e23a37624b9c342afab62\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.3/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-01-16T15:44:25.586712568+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 465e8ff7d77c3bf66b7ae1f7e3b32d8615830e38\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.4/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-02-02T15:19:54.610752194+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 9defec660a98a1737d66671a1a5f6f99599e5f37\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.5/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-02-09T15:22:25.843253698+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 11baf12c23330a015d7af8c4b288cd9d1fa8fa35\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.6/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-02-10T14:46:57.363579846+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 113e5b1d5b70b5bd48220c05cfde6bb9d7e2c99a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.7/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-02-20T15:00:39.422174425+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: e3bd158fc3878c09f029a4267def9f08ece21769\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- build\n- xcode\n- fastlane\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.3.9/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  `bundle install` && `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2017-03-29T13:05:13.873495041+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: b837d69032fc2bb55262b57756d82400a7395b43\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      Example:\n\n      * If Fastfile path: `./here/is/my/fastlane/Fastfile`\n      * Then Fastfile's directory: `./here/is/my/fastlane`\n      * So Working Directory should be: `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.4.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-03-22T14:51:54.175467217Z\nsource:\n  git: https://github.com/bitrise-io/steps-fastlane.git\n  commit: 53fde93499d154260376985a19fb8a4be8448312\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.5.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-06-13T14:55:29.978286775Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: a6e1b28b292e0b7ce826dcc9c032f59ef95bd124\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.5.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-07-16T07:55:23.986231795Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: f446b7b2892c834c2a786f4a4e07fb9a44ab2c08\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n"
  },
  {
    "path": "steps/fastlane/2.5.2/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-07-26T08:30:11.294404962Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 4fcb9f597d683b6ae4a06277a734cc361a65a50f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/fastlane/2.6.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-09-05T14:58:15.7688155Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 34056f1e27bc075e51f95179eab2c913ee2b909a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/2.7.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane.\ndescription: |-\n  Runs your fastlane lane.\n\n  If `Gemfile` exists in the `work_dir` directory, fastlane will be used by\n  calling `bundle install` then `bundle exec`.\n\n  Otherwise the system installed `fastlane` version will be used.\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2019-11-08T16:09:17.584054357Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 83813b44baeca49e8480b52bc20e9744ae432214\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/2.7.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-apple-dev-account/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/yarn)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/bundler)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2020-03-25T13:13:49.053027799Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 52fbec2b7acb9e686ef3f726342329ac0758583c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/2.7.2/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-apple-dev-account/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/yarn)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/bundler)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-01-12T08:52:37.050104547Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 55549c487352612acfbbae0a6eba3346eed639c2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/2.7.3/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-01-13T14:02:23.688354064Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 54a46e034a6d0f38e88fb3923edb83dfa050eea5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/2.7.4/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-01-15T08:16:00.709883615Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: ff9e53757f8eb375c19ce3ce350f8fb413eb3e7a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.0.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-02-04T17:29:25.631335433Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 185f6d5ffe5a6bd95baa53d44e101b4d6d9a7b03\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Required if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.0.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-02-09T16:56:10.012518972Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 9ca07685bc285693265820ebcc523abb530ce423\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      An application-specific password for the Apple ID.\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Required if using Apple ID\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.1.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-02-26T09:11:02.678652111Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: e2ead355a8e9f43605281d2e0ed64e44c0ace4bb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.2.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is connected to Bitrise, the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-03-02T08:54:27.083018337Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 5c913b56ff1d9937786bd3e8cbb8c6c4e7eb4a05\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.2.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-05-10T14:15:34.515949062Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 4e075c9c20cb0f37625354e506a17f1c44c65bd0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.2.2/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-05-28T12:15:22.017804277Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: aa391790f5755f45fde46317d1231fa5f90358ad\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.2.3/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-08-18T14:46:15.733436695Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: b2b7b6487cfd236f553862ab792d62f275396929\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.3.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2021-09-27T09:16:58.520105138Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: cb6dc87f8661b3d11ba2eb451f843c8e6cf538ff\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: \"If enabled the step will add the following cache items (if they\n      exist):  \\n- Pods -> Podfile.lock\\n- Carthage -> Cartfile.resolved\\n- Android\n      dependencies\"\n    is_required: true\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.4.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2022-11-21T15:39:42.739177075Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 85117c0aab9dc98a15f9990a6884374da6b70850\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.4.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2022-12-01T15:37:18.820166461Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: f3b68897006c3cb2910ecbc52be74dca3e47f9da\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.4.2/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2023-03-29T07:41:28.305217791Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: aec09a6bf8447c71a1fe2662a092a64226081465\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.4.3/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2023-04-20T14:15:02.966345651Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 8f61f0832ec3c5fbacc6f06773245a5b9fc36772\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.5.0/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2023-08-30T07:11:08.737392636Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: edd1038bdae24ef6543bf0f60b874081d90d9f65\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.5.1/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2023-10-18T11:24:48.738000955Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 3511f1105094ca4db021d8173bbf7ff1397d90fd\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/3.5.2/step.yml",
    "content": "title: fastlane\nsummary: Runs your fastlane lane on [bitrise.io](https://www.bitrise.io).\ndescription: |-\n  fastlane is an open-source app automation tool for iOS, Android and for most cross-platform frameworks, for example, React Native, Xamarin and Flutter.\n  **fastlane** Step helps you integrate your lane to your Bitrise Workflow and runs your lane based on the fastlane actions with minimal configuration.\n  If your Apple Developer Portal account is [connected to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/), the `FASTLANE_SESSION` Environment Variable will pass on the session data to fastlane.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've [connected to Apple services either by API key, Apple ID or through Fastlane Step's input fields](https://devcenter.bitrise.io/getting-started/connecting-to-services/bitrise-steps-and-their-authentication-methods/#fastlane-step).\n  1. Add the **fastlane** Step to your Workflow after the **Git Clone Repository** Step or any other dependency Step.\n  1. Based on your project's fastlane setup, you can add your project's default lane or a custom lane in the **fastlane lane** input.\n  2. If your fastlane directory is not available in your repository's root, then you can add the parent directory of fastlane directory in the **Working directory** input.\n  3. If your project doesn't contain a fastlane gem in your project's Gemfile, you can use the **Should update fastlane gem before run** input.\n  Set this input to `true` so that the Step can install the latest fastlane version to your project.\n  If a gem lockfile (Gemfile.lock or gems.locked) includes the fastlane gem in the working directory, that specific fastlane version will be installed.\n  4. Select `yes` in the **Enable verbose logging** input if you wish to run your build in debug mode and print out error additional debug logs.\n  5. Select `yes` in the **Enable collecting files to be included in the build cache** to cache pods, Carthage and Android dependencies.\n\n  ### Troubleshooting\n  If you run your lane on Bitrise and your build fails on the **fastlane** Step, the logs won't reveal too much about the error since it's most likely related to the fastlane file's configuration.\n  We recommend you swap your fastlane actions for Bitrise Steps which will bring out the problem.\n\n  ### Useful links\n  - [About fastlane](https://docs.fastlane.tools)\n  - [Connecting your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/connecting-to-services/configuring-bitrise-steps-that-require-apple-developer-account-data/)\n  - [Running fastlane on Bitrise](https://devcenter.bitrise.io/tutorials/fastlane/fastlane-index/)\n\n  ### Related Steps\n  - [Deploy to iTunes Connect/Deliver](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Fastlane Match](https://www.bitrise.io/integrations/steps/fastlane-match)\nwebsite: https://github.com/bitrise-io/steps-fastlane\nsource_code_url: https://github.com/bitrise-io/steps-fastlane\nsupport_url: https://github.com/bitrise-io/steps-fastlane/issues\npublished_at: 2023-12-13T21:58:53.549925491Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-fastlane.git\n  commit: 42c448941ca40fc364c4dacdee04269d2caed843\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-fastlane\ninputs:\n- lane: null\n  opts:\n    description: |\n      fastlane lane to run\n      $ fastlane [lane]\n    is_required: true\n    summary: The lane to execute.\n    title: fastlane lane\n- opts:\n    description: |-\n      Use this option if the fastlane directory is not in your repository's root.\n\n      Working directory should be the parent directory of your Fastfile's directory.\n\n      For example:\n\n      * If the Fastfile path is `./here/is/my/fastlane/Fastfile`\n      * Then the Fastfile's directory is `./here/is/my/fastlane`\n      * So the Working Directory should be `./here/is/my`\n    summary: The working directory to execute the fastlane command in.\n    title: Working directory\n  work_dir: $BITRISE_SOURCE_DIR\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, any enabled Bitrise Apple Developer connection is used and other authentication-related Step inputs are ignored.\n\n      There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is the session-based authentication with an Apple ID. You can choose which type of Bitrise Apple Developer connection to use or you can tell the Step to only use the Step inputs for authentication:\n      - `automatic`: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication.  Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `apple_id`: Use the Apple Developer connection based on Apple ID authentication and the **Application-specific password** Step input. Other authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, any\n      enabled Bitrise Apple Developer connection is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - apple_id\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    summary: Path to local or remote file.\n    title: 'API Key: URL'\n- api_issuer: \"\"\n  opts:\n    description: 'Issuer ID. Required if **API Key: URL** (`api_key_path`) is specified.'\n    summary: Your issuer ID from the API Keys page in App Store Connect.\n    title: 'API Key: Issuer ID'\n- apple_id: \"\"\n  opts:\n    description: Email for Apple ID login.\n    is_sensitive: true\n    summary: Email for Apple ID login.\n    title: 'Apple ID: Email'\n- opts:\n    description: Password for the specified Apple ID.\n    is_sensitive: true\n    summary: Password for the specified Apple ID.\n    title: 'Apple ID: Password'\n  password: \"\"\n- app_password: \"\"\n  opts:\n    description: |-\n      Use this input if TFA is enabled on the Apple ID but no app-specific password has been added to the used Bitrise Apple ID connection.\n\n      **NOTE:** Application-specific passwords can be created on the\n      [AppleID Website](https://appleid.apple.com). It can be used to\n      bypass two-factor authentication.\n    is_sensitive: true\n    summary: Optional if using two-factor enabled Apple ID.\n    title: 'Apple ID: Application-specific password'\n- opts:\n    description: |-\n      Should update fastlane gem before run?\n      *This option will be skipped if you have a `Gemfile` in the `work_dir` directory.*\n    summary: Will cause the fastlane gem to be updated before running the lane.\n    title: Should update fastlane gem before run?\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_fastlane: \"true\"\n- opts:\n    description: Enable/disable verbose logging.\n    is_required: true\n    summary: Enable/disable verbose logging.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- enable_cache: \"yes\"\n  opts:\n    description: |-\n      If enabled the step will add the following cache items (if they exist):\n      - Pods -> Podfile.lock\n      - Carthage -> Cartfile.resolved\n      - Android dependencies\n    is_required: true\n    summary: Enable/disable collecting files to be included in the build cache.\n    title: Enable collecting files to be included in the build cache\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/fastlane/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/fastlane-match/0.0.2/step.yml",
    "content": "title: Fastlane Match\nsummary: |\n  Download and install certificates and provisioning profiles managed with fastlane match\ndescription: |\n  Download and install certificates and provisioning profiles, using the\n  fastlane [Match](https://github.com/fastlane/fastlane/tree/master/match)\n  Ruby gem.\n\n  ## Setup guide and notes\n\n  Follow these steps to create your certificates and provisioning profiles using fastlane match. https://codesigning.guide/\nwebsite: https://github.com/platanus/bitrise-step-fastlane-match\nsource_code_url: https://github.com/platanus/bitrise-step-fastlane-match\nsupport_url: https://github.com/platanus/bitrise-step-fastlane-match/issues\npublished_at: 2017-10-20T11:43:34.36513-04:00\nsource:\n  git: https://github.com/platanus/bitrise-step-fastlane-match.git\n  commit: 83dbc4b46fc73d0c6a4ca2f859c734d7fa63d24e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/platanus/bitrise-step-fastlane-match\ndeps:\n  brew:\n  - name: git\n  - name: go\n  apt_get:\n  - name: git\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- git_url: \"\"\n  opts:\n    description: |-\n      The private git repostiry url where you have your\n      encrypted certificates and profiles\n    is_required: true\n    summary: \"\"\n    title: Match git url\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *ID* on Apple Developer Account.\n\n      This is sometimes refered as Bundle ID\n    is_required: true\n    summary: \"\"\n    title: App ID\n- decrypt_password: \"\"\n  opts:\n    description: Password for decrypting the repository content\n    is_required: true\n    summary: \"\"\n    title: Match decrypt password\n- opts:\n    description: The type of certificate and provisioning profile you want to install.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - adhoc\n    - appstore\n    - development\n    - enterprise\n  type: development\n- gemfile_path: ./Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n"
  },
  {
    "path": "steps/fastlane-match/0.1.0/step.yml",
    "content": "title: Fastlane Match\nsummary: |\n  Download and install certificates and provisioning profiles managed with fastlane match\ndescription: |\n  Download and install certificates and provisioning profiles, using the\n  fastlane [Match](https://github.com/fastlane/fastlane/tree/master/match)\n  Ruby gem.\n\n  ## Setup guide and notes\n\n  Follow these steps to create your certificates and provisioning profiles using fastlane match. https://codesigning.guide/\nwebsite: https://github.com/platanus/bitrise-step-fastlane-match\nsource_code_url: https://github.com/platanus/bitrise-step-fastlane-match\nsupport_url: https://github.com/platanus/bitrise-step-fastlane-match/issues\npublished_at: 2017-11-15T12:49:48.685544-05:00\nsource:\n  git: https://github.com/platanus/bitrise-step-fastlane-match.git\n  commit: fb3bea6cdee1512366382a026fb4099ef8c0dcb5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/platanus/bitrise-step-fastlane-match\ndeps:\n  brew:\n  - name: git\n  - name: go\n  apt_get:\n  - name: git\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- git_url: \"\"\n  opts:\n    description: |-\n      The private git repository url where you have your\n      encrypted certificates and profiles\n    is_required: true\n    summary: \"\"\n    title: Match git url\n- git_branch: \"\"\n  opts:\n    description: |-\n      The name of the git branch containing the encrypted\n      certificates and profiles. Uses master by default.\n    summary: \"\"\n    title: Match git branch\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *ID* on Apple Developer Account.\n\n      This is sometimes refered as Bundle ID\n    is_required: true\n    summary: \"\"\n    title: App ID\n- decrypt_password: \"\"\n  opts:\n    description: Password for decrypting the repository content\n    is_required: true\n    summary: \"\"\n    title: Match decrypt password\n- opts:\n    description: The type of certificate and provisioning profile you want to install.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - adhoc\n    - appstore\n    - development\n    - enterprise\n  type: development\n- gemfile_path: ./Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n"
  },
  {
    "path": "steps/fastlane-match/0.2.0/step.yml",
    "content": "title: Fastlane Match\nsummary: |\n  Download and install certificates and provisioning profiles managed with fastlane match\ndescription: |\n  Download and install certificates and provisioning profiles, using the\n  fastlane [Match](https://github.com/fastlane/fastlane/tree/master/match)\n  Ruby gem.\n\n  ## Setup guide and notes\n\n  Follow these steps to create your certificates and provisioning profiles using fastlane match. https://codesigning.guide/\nwebsite: https://github.com/platanus/bitrise-step-fastlane-match\nsource_code_url: https://github.com/platanus/bitrise-step-fastlane-match\nsupport_url: https://github.com/platanus/bitrise-step-fastlane-match/issues\npublished_at: 2018-08-10T12:03:19.742266745-04:00\nsource:\n  git: https://github.com/platanus/bitrise-step-fastlane-match.git\n  commit: 95a063ae7dd70077ca726128d5905e8037191402\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/platanus/bitrise-step-fastlane-match\ndeps:\n  brew:\n  - name: git\n  - name: go\n  apt_get:\n  - name: git\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- git_url: \"\"\n  opts:\n    description: |-\n      The private git repository url where you have your\n      encrypted certificates and profiles\n    is_required: true\n    summary: \"\"\n    title: Match git url\n- git_branch: \"\"\n  opts:\n    description: |-\n      The name of the git branch containing the encrypted\n      certificates and profiles. Uses master by default.\n    summary: \"\"\n    title: Match git branch\n- app_id: \"\"\n  opts:\n    description: |-\n      The App's *ID* on Apple Developer Account.\n\n      This is sometimes refered as Bundle ID\n    is_required: true\n    summary: \"\"\n    title: App ID\n- decrypt_password: \"\"\n  opts:\n    description: Password for decrypting the repository content\n    is_required: true\n    summary: \"\"\n    title: Match decrypt password\n- opts:\n    description: The type of certificate and provisioning profile you want to install.\n    is_required: true\n    summary: \"\"\n    title: Platform\n    value_options:\n    - adhoc\n    - appstore\n    - development\n    - enterprise\n  type: development\n- opts:\n    description: The ID of your Developer Portal team if you're in multiple teams.\n    summary: \"\"\n    title: Team ID\n  team_id: \"\"\n- gemfile_path: ./Gemfile\n  opts:\n    category: Debug\n    description: |\n      Path to the Gemfile which contains `fastlane` gem.\n\n      If Gemfile not exist or does not contain fastlane gem:\n\n      - if `fastlane_version` input not specified, latest version will be used\n    title: Gemfile path\n- fastlane_version: latest\n  opts:\n    category: Debug\n    description: This option lets you specify a specific version of the `fastlane`\n      gem to be installed.\n    summary: Install a specific version of the `fastlane` gem.\n    title: Fastlane version\n- options: null\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `match` call.\n\n      If you want to add more options, list them separated by a space character.\n\n      Example: `--team_name`\n    title: Additional options for `match` call\n"
  },
  {
    "path": "steps/fastlane-match/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/fauxpasapp/0.1.3/step.yml",
    "content": "title: Fauxpasapp Step\nsummary: Step for Fauxpasapp\ndescription: |-\n  This is a Step for [Faux Pas App](http://fauxpasapp.com).\n  This is not an officially supported plugin\nwebsite: https://github.com/mackoj/fauxpasapp-bitrise\nsource_code_url: https://github.com/mackoj/fauxpasapp-bitrise\nsupport_url: https://github.com/mackoj/fauxpasapp-bitrise/issues\npublished_at: 2016-04-11T17:45:40.879825299+02:00\nsource:\n  git: https://github.com/mackoj/fauxpasapp-bitrise.git\n  commit: b0915237035f3c2d6dead8571415ff8d01662e75\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- fauxpas_license_type: personal\n  opts:\n    is_required: true\n    summary: Set the type in the license between these personal,organization-seat,site\n      and enterprise\n    title: License type\n    value_options:\n    - personal\n    - organization-seat\n    - site\n    - enterprise\n- fauxpas_license_name: $FAUXPAS_LICENSE_NAME\n  opts:\n    is_required: true\n    summary: Set the name in the license\n    title: License name\n- fauxpas_license_key: $FAUXPAS_LICENSE_KEY\n  opts:\n    is_required: true\n    summary: Set the Key in the license\n    title: License Key\n- fauxpas_project_path: $BITRISE_PROJECT_PATH\n  opts:\n    is_required: true\n    title: Path of the xcodeproj\n- fauxpas_target: null\n  opts:\n    is_required: true\n    title: Xcode target to check\n- fauxpas_scheme: $BITRISE_SCHEME\n  opts:\n    is_required: true\n    title: If you use a workspace you need to define a shared scheme\n- fauxpas_build_config: null\n  opts:\n    is_required: true\n    title: Xcode build configuration to check\n- fauxpas_partial_custom_config: null\n  opts:\n    summary: Use whatever flag you want to launch faux pas in check mode\n    title: Faux Pas custom configuration\n- fauxpas_debug_mode: \"false\"\n  opts:\n    is_required: true\n    title: Faux Pas Debug\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- FAUXPAS_JSON_OUTPUT_FILE: null\n  opts:\n    title: Faux Pas JSON Output\n"
  },
  {
    "path": "steps/fauxpasapp/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/feature-list-for-release-notes/0.0.1/step.yml",
    "content": "title: Features and epics list for release notes\nsummary: |\n  Creates a list of features and gathered from git commits and tags using given pattern.\ndescription: |\n  Feature descriptions are derived from commit messages. List of the features is based on previous commits messages.\n\n  The regex pattern to look for features is \"<project_prefix>[0-9]{0,5}\"\n\n  Epics are derived from tags.\n\n  The regex pattern to look for epics is \"<project_prefix>[0-9]{0,5}_\"\n\n  An alternative use, would be to create links to appropriate features and epics in the backlog system using the <default_backlog_url> variable.\nwebsite: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsupport_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features/issues\npublished_at: 2018-06-29T16:11:01.075182967+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_set_jira_features.git\n  commit: a811857b7ba477be22bbc27ed91ba83734c23e7e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- backlog_default_url: null\n  opts:\n    description: |\n      Base URL for prefixing the features and epics.\n\n      e.g. \"https://example.com/\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Default URL for the backlog system\n- opts:\n    description: |\n      Project prefix to search for features and epics.\n\n      e.g. \"PROJ-\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Project prefix\n  project_prefix: null\noutputs:\n- FEATURES_FROM_COMMITS: null\n  opts:\n    description: |\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of features derived from commits\n- EPICS_FROM_TAGS: null\n  opts:\n    description: |-\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of epics with titles derived from tags\n"
  },
  {
    "path": "steps/feature-list-for-release-notes/0.0.2/step.yml",
    "content": "title: Features and epics list for release notes\nsummary: |\n  Creates a list of features and gathered from git commits and tags using given pattern.\ndescription: |\n  Feature descriptions are derived from commit messages. List of the features is based on previous commits messages.\n\n  The regex pattern to look for features is \"<project_prefix>[0-9]{0,5}\"\n\n  Epics are derived from tags.\n\n  The regex pattern to look for epics is \"<project_prefix>[0-9]{0,5}_\"\n\n  An alternative use, would be to create links to appropriate features and epics in the backlog system using the <default_backlog_url> variable.\nwebsite: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsupport_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features/issues\npublished_at: 2018-07-05T16:03:40.589734584+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_set_jira_features.git\n  commit: d7825fa3b26d5e26a04391e0afc166b7cb3d1170\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- backlog_default_url: null\n  opts:\n    description: |\n      Base URL for prefixing the features and epics.\n\n      e.g. \"https://example.com/\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Default URL for the backlog system\n- opts:\n    description: |\n      Project prefix to search for features and epics.\n\n      e.g. \"PROJ-\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Project prefix\n  project_prefix: null\noutputs:\n- FEATURES_FROM_COMMITS: null\n  opts:\n    description: |\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of features derived from commits\n- EPICS_FROM_TAGS: null\n  opts:\n    description: |-\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of epics with titles derived from tags\n"
  },
  {
    "path": "steps/feature-list-for-release-notes/0.0.3/step.yml",
    "content": "title: Features and epics list for release notes\nsummary: |\n  Creates a list of features and gathered from git commits and tags using given pattern.\ndescription: |\n  Feature descriptions are derived from commit messages. List of the features is based on previous commits messages.\n\n  The regex pattern to look for features is \"<project_prefix>[0-9]{1,5}\"\n\n  Epics are derived from tags.\n\n  The regex pattern to look for epics is \"<project_prefix>[0-9]{1,5}_\"\n\n  An alternative use, would be to create links to appropriate features and epics in the backlog system using the <default_backlog_url> variable.\nwebsite: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsupport_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features/issues\npublished_at: 2018-07-09T13:30:16.034204875+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_set_jira_features.git\n  commit: aba9398f668da5444567e4bd964e5da1c33ba3a6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- backlog_default_url: null\n  opts:\n    description: |\n      Base URL for prefixing the features and epics.\n\n      e.g. \"https://example.com/\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Default URL for the backlog system\n- opts:\n    description: |\n      Project prefix to search for features and epics.\n\n      e.g. \"PROJ-\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Project prefix\n  project_prefix: null\noutputs:\n- FEATURES_FROM_COMMITS: null\n  opts:\n    description: |\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of features derived from commits\n- EPICS_FROM_TAGS: null\n  opts:\n    description: |-\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of epics with titles derived from tags\n"
  },
  {
    "path": "steps/feature-list-for-release-notes/0.0.4/step.yml",
    "content": "title: Features and epics list for release notes\nsummary: |\n  Creates a list of features and gathered from git commits and tags using given pattern.\ndescription: |\n  Feature descriptions are derived from commit messages. List of the features is based on previous commits messages.\n\n  The regex pattern to look for features is \"<project_prefix>[0-9]{1,5}\"\n\n  Epics are derived from tags.\n\n  The regex pattern to look for epics is \"<project_prefix>[0-9]{1,5}_\"\n\n  An alternative use, would be to create links to appropriate features and epics in the backlog system using the <default_backlog_url> variable.\nwebsite: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features\nsupport_url: https://github.com/DroidsOnRoids/bitrise_set_jira_features/issues\npublished_at: 2018-09-04T10:14:38.946874683+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_set_jira_features.git\n  commit: 3acaaee1a98e6d134702d464be1fe74697c3ae7a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- backlog_default_url: null\n  opts:\n    description: |\n      Base URL for prefixing the features and epics.\n\n      e.g. \"https://example.com/\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Default URL for the backlog system\n- opts:\n    description: |\n      Project prefix to search for features and epics.\n\n      e.g. \"PROJ-\"\n\n      Can be empty.\n    is_expand: true\n    is_required: true\n    title: Project prefix\n  project_prefix: null\noutputs:\n- FEATURES_FROM_COMMITS: null\n  opts:\n    description: |\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of features derived from commits\n- EPICS_FROM_TAGS: null\n  opts:\n    description: |-\n      If the backlog_default_url is specified, each element is prefixed with the given URL\n\n      e.g. https://example.com/PROJ-1\n    title: List of epics with titles derived from tags\n"
  },
  {
    "path": "steps/feature-list-for-release-notes/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/fetch-infisical-secrets/1.0.0/step.yml",
    "content": "title: Fetch Infisical Secrets\nsummary: |\n  Allows the collection of secrets from your Infisical account.\ndescription: |\n  Allow the collection of secrets from your Infisical account and injects them into your workflow in a secure manner.\nwebsite: https://github.com/Willt123/bitrise-step-fetch-infisical-secrets\nsource_code_url: https://github.com/Willt123/bitrise-step-fetch-infisical-secrets\nsupport_url: https://github.com/Willt123/bitrise-step-fetch-infisical-secrets/issues\npublished_at: 2025-07-22T10:42:34.348659+09:30\nsource:\n  git: https://github.com/Willt123/bitrise-step-fetch-infisical-secrets.git\n  commit: 596146fd517668b19b5f065204a743b249e6d8ed\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/Willt123/bitrise-step-fetch-infisical-secrets\ninputs:\n- infisical_client: null\n  opts:\n    description: The client ID is required to identify the machine identity from Infisical\n    is_expand: true\n    is_required: true\n    summary: The client ID from infisical.\n    title: Infisical Client ID\n- infisical_client_secret: null\n  opts:\n    description: The client secret is required to authenticate the machine identity\n      from Infisical\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The client secret from infisical.\n    title: Infisical Client Secret\n- infisical_project_id: null\n  opts:\n    description: The project ID is required to access the correct project from Infisical\n    is_expand: true\n    is_required: true\n    summary: The project ID from infisical.\n    title: Infisical Project ID\n- infisical_env: null\n  opts:\n    description: The env is required to match the env specified in the token above\n      to provide access to the required secrets\n    is_expanded: true\n    is_required: true\n    summary: The slug for your project environment\n    title: Infisical Env\n- infisical_url: https://app.infisical.com\n  opts:\n    description: The fully qualified URL to access your Infisical secrets. The trailing\n      slash or /api is not required and should only consist of the hostname and TLD.\n      Defaults to the cloud API url.\n    is_expanded: true\n    is_required: false\n    summary: The url of the API to access your Infisical secrets\n    title: Infisical URL\n- infisical_path: null\n  opts:\n    description: The path or folder structure required to access your secrets within\n      Infisical\n    is_expanded: true\n    is_required: false\n    summary: The path to the required secrets\n    title: Infisical Path\n"
  },
  {
    "path": "steps/fetch-infisical-secrets/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/file-downloader/0.9.0/step.yml",
    "content": "title: File Downloader\nsummary: Downloands file\ndescription: Downloands file\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2016-06-21T16:12:51.635139329+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: 2a79576302bc56ba99adde840a0c2f5590b67c7c\nproject_type_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Download source url\n    is_required: true\n    title: Download source url\n  source: null\n- destination: null\n  opts:\n    description: |\n      Download destination path\n    is_required: true\n    title: Download destination path\n"
  },
  {
    "path": "steps/file-downloader/0.9.1/step.yml",
    "content": "title: File Downloader\nsummary: Downloads file\ndescription: Downloads file\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2016-06-29T10:28:36.915091999+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: 8877374cc8d17a599e359ff7bddf465da14e9ba8\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Download source url\n    is_required: true\n    title: Download source url\n  source: null\n- destination: null\n  opts:\n    description: |\n      Download destination path\n    is_required: true\n    title: Download destination path\n"
  },
  {
    "path": "steps/file-downloader/1.0.0/step.yml",
    "content": "title: File Downloader\nsummary: Downloands file\ndescription: Downloands file\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2018-03-01T11:26:52.927484+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: 1e50dedca1ba8e2f2353d2d9bacc54eb5c8a0f58\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Download source url\n    is_required: true\n    title: Download source url\n  source: null\n- destination: null\n  opts:\n    description: |\n      Download destination path\n    is_required: true\n    title: Download destination path\n"
  },
  {
    "path": "steps/file-downloader/1.0.1/step.yml",
    "content": "title: File Downloader\nsummary: Downloands file\ndescription: Downloands file\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2018-07-04T15:16:10.432358972+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: f33fdaa6605c4487fc1cdbd061dcaaa68e328087\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Download source url\n    is_required: true\n    title: Download source url\n  source: null\n- destination: null\n  opts:\n    description: |\n      Download destination path\n    is_required: true\n    title: Download destination path\n"
  },
  {
    "path": "steps/file-downloader/1.0.2/step.yml",
    "content": "title: File Downloader\nsummary: Downloands files\ndescription: Downloands files\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2020-09-29T09:11:13.325778882Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: 1e66a7b58ff6ade8c328db1227f86c548e5f00d8\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Download source url\n    is_required: true\n    title: Download source url\n  source: null\n- destination: null\n  opts:\n    description: |\n      Download destination path\n    is_required: true\n    title: Download destination path\n"
  },
  {
    "path": "steps/file-downloader/1.0.3/step.yml",
    "content": "title: File Downloader\nsummary: Downloads files for your build.\ndescription: \"The Step downloads selected files from a URL and places it where you\n  want it to. \\n\\n### Configuring the Step \\n\\n1. Add a source to the **Download source\n  URL** input. It can be either an Environment Variable or a URL.\\n1. Add a destination\n  to the **Download destination path** input. The path should be relative to the root\n  directory of the repository.\\n\\n### Useful links\\n\\n- [Using the File Downloader\n  Step](https://devcenter.bitrise.io/tutorials/download-or-replace-project-resources/#using-the-file-downloader-step)\\n-\n  [Managing files on Bitrise](https://devcenter.bitrise.io/getting-started/managing-files-on-bitrise/)\\n\\n###\n  Related Steps \\n\\n- [Generate Text File](https://www.bitrise.io/integrations/steps/generate-text-file)\"\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2020-11-19T17:31:24.062063296Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: 8a962c92d980b2d5d4a0f2d6395064b885a3532f\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Download source url\n    is_required: true\n    title: Download source url\n  source: null\n- destination: null\n  opts:\n    description: |\n      Download destination path\n    is_required: true\n    title: Download destination path\n"
  },
  {
    "path": "steps/file-downloader/1.1.0/step.yml",
    "content": "title: File Downloader\nsummary: Download remote files to the build machine.\ndescription: \"The Step downloads selected files from a URL and places it where you\n  want it to. \\n\\n### Configuring the Step \\n\\n1. Add a source to the **Download source\n  URL** input. It can be either an Environment Variable or a URL.\\n1. Add a destination\n  to the **Download destination path** input. The path should be relative to the root\n  directory of the repository.\\n\\n### Useful links\\n\\n- [Using the File Downloader\n  Step](https://devcenter.bitrise.io/tutorials/download-or-replace-project-resources/#using-the-file-downloader-step)\\n-\n  [Managing files on Bitrise](https://devcenter.bitrise.io/getting-started/managing-files-on-bitrise/)\\n\\n###\n  Related Steps \\n\\n- [Generate Text File](https://www.bitrise.io/integrations/steps/generate-text-file)\"\nwebsite: https://github.com/bitrise-steplib/steps-file-downloader\nsource_code_url: https://github.com/bitrise-steplib/steps-file-downloader\nsupport_url: https://github.com/bitrise-steplib/steps-file-downloader/issues\npublished_at: 2021-11-15T09:22:34.872711619Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-file-downloader.git\n  commit: b1340142ab5a6e811f7c6e265d76032a7450500c\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Download source URL\n    title: Download source URL\n  source: null\n- destination: null\n  opts:\n    is_required: true\n    summary: Download destination path\n    title: Download destination path\n- file_permission: null\n  opts:\n    description: |\n      Permission bits for the destination file in the format of `644`.\n\n      This option is useful for sensitive files that should have a permission like `600`.\n    summary: Permission bits for the destination file\n    title: Destination file permission\n"
  },
  {
    "path": "steps/file-downloader/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/find-jira-issue/0.0.1/step.yml",
    "content": "title: Find Jira Issue\nsummary: |\n  Find the jira issue and add it as an environment variable\ndescription: |\n  Step that locates the a jira issue from the input and sets it as an environment variable for future steps\nwebsite: https://github.com/jimmithy/bitrise-step-find-jira-issue\nsource_code_url: https://github.com/jimmithy/bitrise-step-find-jira-issue\nsupport_url: https://github.com/jimmithy/bitrise-step-find-jira-issue/issues\npublished_at: 2020-06-29T16:13:40.854864-04:00\nsource:\n  git: https://github.com/jimmithy/bitrise-step-find-jira-issue.git\n  commit: 4b1566842f7147cbdad6fd65f1d145f56c08c9ed\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- find_issue_content: $BITRISE_GIT_MESSAGE\n  opts:\n    description: |\n      The input text content used to locate the jira ticket number.\n\n      For example, the git commit message or branch name.\n    is_expand: true\n    is_required: true\n    summary: Where should we look for jira issues\n    title: Text Content\n    value_options: []\noutputs:\n- JIRA_ISSUE_LIST: null\n  opts:\n    description: |\n      Unique Jira issues found from the input. Multiple results will have a | delimiter.\n    summary: The jira issues found in the input\n    title: Jira Issue(s)\n"
  },
  {
    "path": "steps/find-jira-issue/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.1.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution\npublished_at: 2019-10-03T15:00:29.831123+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 2f62c82d134b0f1033183050b47f43e4aa6d5981\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3ryNcsDiZnCaHnY-hg9u9nJeosz3iNPe-S-RLdmqdypiJMOjoeOhOGsWK`\n    is_required: true\n    is_sensitive: true\n    title: Firebase Token\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    summary: null\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    summary: null\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    summary: null\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to firebase command.\n      ie. you can specify file inputs for groups, testers, and release notes.\n    is_required: false\n    summary: null\n    title: Additional Command Flags\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.10.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2022-01-30T20:52:36.210469+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: d9cf1973edd2d569ab1790899fdb95b45e9fb36d\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH|$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path of IPA, APK or AAB file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH|$BITRISE_AAB_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Maximum allowed length for release notes. Beyond that the notes will be trimmed in order to prevent a failure on firebase side.\n    is_required: false\n    title: Max Length for Release Notes\n  release_notes_length: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.11.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2024-01-22T21:57:44.942553+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 64be34ce81ed12c6cafaf483b643994afdecc80f\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH|$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path of IPA, APK or AAB file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH|$BITRISE_AAB_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Maximum allowed length for release notes. Beyond that the notes will be trimmed in order to prevent a failure on firebase side.\n    is_required: false\n    title: Max Length for Release Notes\n  release_notes_length: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.12.0/step.yml",
    "content": "title: Firebase App Distribution\nsummary: |\n  Distributes your builds via Firebase App Distribution\ndescription: |\n  Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2025-03-27T13:15:49.42628+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 47b6e7f47dcde29891fdaf8646b6edf9ab26c809\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH|$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path of IPA, APK or AAB file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH|$BITRISE_AAB_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Maximum allowed length for release notes. Beyond that the notes will be trimmed in order to prevent a failure on firebase side.\n    is_required: false\n    title: Max Length for Release Notes\n  release_notes_length: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- FIREBASE_CONSOLE_URL: null\n  opts:\n    summary: The firebase console URL of the deployed app\n    title: Firebase Console URL\n- FIREBASE_APP_DISTRIBUTION_URL: null\n  opts:\n    summary: Share this release with testers who have access\n    title: Firebase App Distribution URL\n- FIREBASE_APP_DISTRIBUTION_RELEASE_ID: null\n  opts:\n    summary: The Firebase App Distribution Release ID of the uploaded build.\n    title: Firebase App Distribution Release ID\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.12.1/step.yml",
    "content": "title: Firebase App Distribution\nsummary: |\n  Distributes your builds via Firebase App Distribution\ndescription: |\n  Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2025-03-28T14:47:40.976642+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 30ae9ac242c4824aa6299d46f0c853973c98fbe7\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH|$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path of IPA, APK or AAB file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH|$BITRISE_AAB_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Maximum allowed length for release notes. Beyond that the notes will be trimmed in order to prevent a failure on firebase side.\n    is_required: false\n    title: Max Length for Release Notes\n  release_notes_length: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\noutputs:\n- FIREBASE_BITRISE_CONSOLE_URL: null\n  opts:\n    summary: The firebase console URL of the deployed app\n    title: Firebase Console URL\n- FIREBASE_BITRISE_APP_DISTRIBUTION_URL: null\n  opts:\n    summary: Share this release with testers who have access\n    title: Firebase App Distribution URL\n- FIREBASE_BITRISE_APP_DISTRIBUTION_RELEASE_ID: null\n  opts:\n    summary: The Firebase App Distribution Release ID of the uploaded build.\n    title: Firebase App Distribution Release ID\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.2.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution\npublished_at: 2019-10-09T14:30:02.127185+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 9b48d12ee1f5c2d7898c3af612ee8e95abd07611\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_required: true\n    is_sensitive: true\n    title: Firebase Token\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, testers, and release notes.\n    is_required: false\n    title: Additional Command Flags\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.3.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2019-10-10T10:59:37.157535+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 10cab751fd88e9ff5afa723c7a920360bae10a7e\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_required: true\n    is_sensitive: true\n    title: Firebase Token\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, testers, and release notes.\n    is_required: false\n    title: Additional Command Flags\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.4.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2019-11-10T11:24:29.821385+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 030afb84313cb23ab29b84e6e6ae0fb148349718\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, testers, and release notes.\n    is_required: false\n    title: Additional Command Flags\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.5.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2019-11-18T14:11:45.225424+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: bb8a17a280e8bac4a94f3a1196005954bfec57bf\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, testers, and release notes.\n    is_required: false\n    title: Additional Command Flags\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.6.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2020-02-19T17:01:27.025268+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: c9e128d0697c7899fd080be63780f6de979b8936\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.7.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2020-04-03T19:18:57.563272+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: 31491fd7db4ab1d1ecd70da5fb674fc1e281e16f\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.8.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2020-09-29T14:36:00.18855+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: d424a820d5af2381d034733ccd399e4c85c7db73\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path of IPA or APK file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.9.0/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2021-07-07T15:09:12.157738+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: ca34c955d653fc82d80801c37a8b02f7c3b23b4a\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH|$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path of IPA, APK or AAB file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH|$BITRISE_AAB_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/0.9.1/step.yml",
    "content": "title: '[BETA] Firebase App Distribution'\nsummary: |\n  [BETA] Distributes your builds via Firebase App Distribution\ndescription: |\n  [BETA] Uploads your app binaries to Firebase and sends email to your testers.\nwebsite: https://github.com/guness/bitrise-step-firebase-app-distribution\nsource_code_url: https://github.com/guness/bitrise-step-firebase-app-distribution\nsupport_url: https://github.com/guness/bitrise-step-firebase-app-distribution/issues\npublished_at: 2021-07-13T12:06:42.411492+03:00\nsource:\n  git: https://github.com/guness/bitrise-step-firebase-app-distribution.git\n  commit: e49199ff4f3dbe2a9b2e7b5aa9fe83d06cb8c726\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- firebase_token: null\n  opts:\n    description: |\n      Firebase CI access token. You can create it by `firebase login:ci` on your local machine.\n\n      It is something in the form of `1/a1gqPSI3r-RLgCQO47pJW7WdmqdypiJMO`\n    is_sensitive: true\n    title: Firebase Token\n- opts:\n    description: |\n      The path or HTTP URL to your [service account](https://firebase.google.com/docs/app-distribution/android/distribute-gradle#authenticate_using_a_service_account) private key JSON file.\n      Required only if you use service account authentication.\n    title: Service Credentials File\n  service_credentials_file: null\n- app_path: $BITRISE_IPA_PATH|$BITRISE_APK_PATH|$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path of IPA, APK or AAB file to deploy.\n\n      Default values:\n      iOS: `$BITRISE_IPA_PATH`\n      Android: `$BITRISE_APK_PATH|$BITRISE_AAB_PATH`\n    is_required: true\n    title: App Path\n- app: null\n  opts:\n    description: |\n      You can find the App ID in the Firebase console, on the [General Settings page](https://console.firebase.google.com/project/_/settings/general/).\n\n      It is something in the form of:\n\n      `1:1234567890:android:0a1b2c3d4e5f67890`\n    is_required: true\n    title: Firebase App ID\n- opts:\n    description: |\n      Release notes for this build.\n    is_required: false\n    title: Release Notes\n  release_notes: null\n- opts:\n    description: |\n      Text file containing release notes for this build.\n    is_required: false\n    title: Release Notes File\n  release_notes_file: null\n- opts:\n    description: |\n      The email addresses of the testers you want to invite.\n\n      You can specify the testers as a comma-separated list of email addresses:\n\n      `ali@example.com, bri@example.com, cal@example.com`\n    is_required: false\n    title: Testers\n  testers: null\n- groups: null\n  opts:\n    description: |\n      The tester groups you want to invite (refer to [Manage testers](https://firebase.google.com/docs/app-distribution/manage-testers)).\n      Groups are specified using group aliases, which you can look up in the Firebase console.\n\n      You can specify the groups as a comma-separated list:\n\n      `qa-team, trusted-testers`\n    is_required: false\n    title: Test Groups\n- flags: null\n  opts:\n    description: |\n      Additional flags to be appended to Firebase command.\n      ie. you can specify file inputs for groups, and testers.\n    is_required: false\n    title: Additional Command Flags\n- opts:\n    description: Firebase tools will be upgraded if enabled.\n    is_required: true\n    summary: Firebase tools will be upgraded if enabled.\n    title: Enable Firebase Tools Upgrade\n    value_options:\n    - \"false\"\n    - \"true\"\n  upgrade_firebase_tools: \"false\"\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: The step will print more verbose logs if enabled.\n    is_required: true\n    summary: The step will print more verbose logs if enabled.\n    title: Enable Debug Mode\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/firebase-app-distribution/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/firebase-change-file-by-env/0.0.2/step.yml",
    "content": "title: Firebase Change File by environment and branch\nsummary: |\n  Utility to be able to differentiate your firebase projects by development environment\ndescription: |\n  Change the firebase connection file according to the development branch that you are using,\n  usually one has two environments such as develop or production which should not consume\n  the same firebase project, this step will help us to switch between firebase projects according to our environment developmental\n  * Important Suggestion *: You must create a folder in the root of your project called 'firebase_env'\n   and inside have two folders for production and development, the step suggests in its variables\n   and the corresponding folders.\nwebsite: https://github.com/manuelabarca/bitrise-step-firebase-change-file-by-env\nsource_code_url: https://github.com/manuelabarca/bitrise-step-firebase-change-file-by-env\nsupport_url: https://github.com/manuelabarca/bitrise-step-firebase-change-file-by-env/issues\npublished_at: 2021-04-02T15:07:42.004408-03:00\nsource:\n  git: https://github.com/manuelabarca/bitrise-step-firebase-change-file-by-env.git\n  commit: 86f34a9f59196d84c3aec777b8dc82d1904dcf54\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ninputs:\n- opts:\n    description: |\n      Branch usually needed for the production environment like 'master' or 'main'\n    is_required: true\n    title: Principal branch for production\n  principal_branch: master\n- opts:\n    description: |\n      Choose the platform where you want to use: iOS, Android or both\n    is_expand: true\n    is_required: true\n    title: Platform to use\n    value_options:\n    - both\n    - iOS\n    - Android\n  platform: both\n- opts:\n    description: |\n      Working Directory of the step, default is for react-native or flutter project\n    title: Working directory for Android platform\n  workdir_android: $BITRISE_SOURCE_DIR/android/\n- opts:\n    description: |\n      Working Directory of the step, default is for react-native or flutter project\n    title: Working directory for ios platform\n  workdir_ios: $BITRISE_SOURCE_DIR/ios/\n- ios_scheme_name: $BITRISE_SCHEME\n  opts:\n    description: |\n      Scheme used, usually the name of your app on iOS like 'Example or MyApp'\n    is_required: true\n    title: Scheme name\n- android_folder: app\n  opts:\n    description: |\n      Folder where src folder is located in android project, in flutter or react native projects it is called app and it is found inside the android folder\n    is_required: true\n    title: Android App Folder\n- google_services_file_android_prod: firebase_env/production/google-services.json\n  opts:\n    description: |\n      Suggested folder and file for android production\n    title: Google services file for android production\n- google_services_file_ios_prod: firebase_env/production/GoogleService-Info.plist\n  opts:\n    description: |\n      Suggested folder and file for iOS production\n    title: Google services file for iOS production\n- google_services_file_android_dev: firebase_env/develop/google-services.json\n  opts:\n    description: |\n      Suggested folder and file for android development\n    title: Google services file for android development\n- google_services_file_ios_dev: firebase_env/develop/GoogleService-Info.plist\n  opts:\n    description: |\n      Suggested folder and file for iOS development\n    title: Google services file for iOS development\n"
  },
  {
    "path": "steps/firebase-change-file-by-env/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/firebase-dsym-upload/1.0.0/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dsym for your iOS project to Firebase\ndescription: |\n  This step uploads the dsym for your iOS project to Firebase\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2019-10-07T17:23:41.883306+01:00\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: 506b18c2bcb86454a580fe2b2e6154fa12baa933\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: ./Pods/Fabric/upload-symbols\n  opts:\n    description: |\n      This is the location of where Fabric is stored. Usually it is ./Pods/Fabric/upload-symbols\n    is_expand: true\n    is_required: true\n    summary: This is the location of where Fabric is stored.\n    title: Location of Fabric\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n"
  },
  {
    "path": "steps/firebase-dsym-upload/1.0.1/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dsym for your iOS project to Firebase\ndescription: |\n  This step uploads the dsym for your iOS project to Firebase\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2019-11-14T17:10:09.39498Z\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: 3bf45ea0e02aae0646ad6553bbcffd124df92a52\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: ./Pods/Fabric/upload-symbols\n  opts:\n    description: |\n      This is the location of where Fabric is stored. Usually it is ./Pods/Fabric/upload-symbols\n    is_expand: true\n    is_required: true\n    summary: This is the location of where Fabric is stored.\n    title: Location of Fabric\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n"
  },
  {
    "path": "steps/firebase-dsym-upload/1.0.2/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dsym for your iOS project to Firebase\ndescription: |\n  This step uploads the dsym for your iOS project to Firebase\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2020-02-18T17:10:46.250885Z\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: e00ee1cd03e6c9f2abac30c4701349d21b1306d1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: ./Pods/Fabric/upload-symbols\n  opts:\n    description: |\n      This is the location of where Fabric is stored. Usually it is ./Pods/Fabric/upload-symbols\n    is_expand: true\n    is_required: true\n    summary: This is the location of where Fabric is stored.\n    title: Location of Fabric\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n"
  },
  {
    "path": "steps/firebase-dsym-upload/1.1.0/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dsym for your iOS project to Firebase\ndescription: |\n  This step uploads the dsym for your iOS project to Firebase\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2020-05-14T09:58:37.310824+01:00\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: 2f288800b2f04969f55898e4f9b260d2bbec18e0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: null\n  opts:\n    description: |\n      For Fabric it is usually `./Pods/Fabric/upload-symbols`\n      and FirebaseCrashlytics it is usually `./Pods/FirebaseCrashlytics/upload-symbols`\n    is_expand: true\n    is_required: true\n    summary: This is the location of where Fabric or FirebaseCrashlytics is stored.\n    title: Location of Fabric or FirebaseCrashlytics\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n- fdu_logging: \"no\"\n  opts:\n    category: Debug\n    description: Prints the location of the Fabric or FirebaseCrashlytics, the GoogleService-Info.plist\n      and the location of the dSYMs on the server.\n    summary: Shows additional logging output\n    title: Show additional logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/firebase-dsym-upload/1.1.1/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dsym for your iOS project to Firebase\ndescription: |\n  This step uploads the dsym for your iOS project to Firebase\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2020-05-20T08:39:53.517933+01:00\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: 62de72af249fd6ac8b175cadd98093794def4f01\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: ./Pods/Fabric/upload-symbols\n  opts:\n    description: |\n      For Fabric it is usually `./Pods/Fabric/upload-symbols`\n      and FirebaseCrashlytics it is usually `./Pods/FirebaseCrashlytics/upload-symbols`\n    is_expand: true\n    is_required: true\n    summary: This is the location of where Fabric or FirebaseCrashlytics is stored.\n    title: Location of Fabric or FirebaseCrashlytics\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n- fdu_logging: \"no\"\n  opts:\n    category: Debug\n    description: Prints the location of the Fabric or FirebaseCrashlytics, the GoogleService-Info.plist\n      and the location of the dSYMs on the server.\n    summary: Shows additional logging output\n    title: Show additional logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/firebase-dsym-upload/2.0.0/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dsym for your iOS project to Firebase\ndescription: |\n  This step uploads the dsym for your iOS project to Firebase\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2020-10-03T15:00:01.19267+01:00\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: 351a0e9890a5607a50b34389210185b3b95f9e31\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: ./Pods/FirebaseCrashlytics/upload-symbols\n  opts:\n    description: |\n      FirebaseCrashlytics it is usually `./Pods/FirebaseCrashlytics/upload-symbols`\n      and for Fabric it is usually `./Pods/Fabric/upload-symbols`\n    is_expand: true\n    is_required: true\n    summary: This is the location of where FirebaseCrashlytics or Fabric is stored.\n    title: Location of Fabric or FirebaseCrashlytics\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n- fdu_logging: \"no\"\n  opts:\n    category: Debug\n    description: Prints the location of the FirebaseCrashlytics or Fabric, the GoogleService-Info.plist\n      and the location of the dSYMs on the server.\n    summary: Shows additional logging output\n    title: Show additional logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/firebase-dsym-upload/2.0.1/step.yml",
    "content": "title: Firebase dSYM Upload\nsummary: |\n  This step uploads the dSYM for your iOS project to Firebase using CocoaPods\ndescription: |\n  You should have installed Firebase Crashlytics via CocoaPods to use this. This step does not support Swift Package Manager (SPM).\nwebsite: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsource_code_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload\nsupport_url: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload/issues\npublished_at: 2022-10-12T14:44:08.121976+01:00\nsource:\n  git: https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload.git\n  commit: 3dcd109c3740f1747deec13150d09de82ac46d62\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- fdu_fabric_location: ./Pods/FirebaseCrashlytics/upload-symbols\n  opts:\n    description: |\n      FirebaseCrashlytics it is usually `./Pods/FirebaseCrashlytics/upload-symbols`\n    is_expand: true\n    is_required: true\n    summary: This is the location of where FirebaseCrashlytics is stored.\n    title: Location of FirebaseCrashlytics\n- fdu_google_services_location: null\n  opts:\n    description: |\n      The location is usually in the form ./YOUR-APP-NAME/GoogleService-Info.plist\n    is_expand: true\n    is_required: true\n    summary: This is the location of your GoogleService-Info.plist\n    title: Location of your GoogleService-Info.plist\n- fdu_dsym_location: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      This is the location of your dSYMs. Usually it is $BITRISE\\_DSYM\\_PATH\n    is_expand: true\n    is_required: true\n    summary: This is the location of your dSYMs that you want to upload to Firebase.\n    title: Location of the bitrise dSYMs\n- fdu_logging: \"no\"\n  opts:\n    category: Debug\n    description: Prints the location of the FirebaseCrashlytics or Fabric, the GoogleService-Info.plist\n      and the location of the dSYMs on the server.\n    summary: Shows additional logging output\n    title: Show additional logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/firebase-dsym-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/flank/0.1.0/step.yml",
    "content": "title: Flank\nsummary: Run your tests using Flank.\ndescription: Run your tests using Flank. The step will automatically detect which\n  project type your flank config uses and the corresponding flank command will be\n  ran.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flank\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flank\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flank/issues\npublished_at: 2019-03-08T10:15:19.621262669Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flank.git\n  commit: e19d16203aa6e67d6d2c3c8e002f05f1ddc7b4a7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flank\ninputs:\n- google_service_account_json: null\n  opts:\n    description: Service Account JSON key file content.\n    is_required: true\n    is_sensitive: true\n    summary: Service Account JSON key file content.\n    title: Google Service Account JSON\n- config_path: null\n  opts:\n    description: Flank config file path.\n    is_required: true\n    summary: Flank config file path.\n    title: Config Path\n- opts:\n    description: Flank binary version. You can use any tag name that is available\n      on https://github.com/TestArmada/flank/releases or latest which will download\n      the latest non-pre-elease version.\n    is_required: true\n    summary: Flank binary version.\n    title: Version\n  version: latest\n- command_flags: null\n  opts:\n    description: These flags will be appended to the flank command. If your flank\n      config is for Android projects then these flags will be appended after `flank\n      android test` otherwise after `flank ios test`.\n    summary: These flags will be appended to the flank command.\n    title: Command Flags\n"
  },
  {
    "path": "steps/flank/0.1.1/step.yml",
    "content": "title: Flank\nsummary: Run your tests using Flank.\ndescription: Run your tests using Flank. The step will automatically detect which\n  project type your flank config uses and the corresponding flank command will be\n  ran.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flank\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flank\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flank/issues\npublished_at: 2020-05-14T07:28:07.590904484Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flank.git\n  commit: f24fe173bb95c64d1530505e1534cf8c1e01146b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flank\ninputs:\n- google_service_account_json: null\n  opts:\n    description: Service Account JSON key file content.\n    is_required: true\n    is_sensitive: true\n    summary: Service Account JSON key file content.\n    title: Google Service Account JSON\n- config_path: null\n  opts:\n    description: Flank config file path.\n    is_required: true\n    summary: Flank config file path.\n    title: Config Path\n- opts:\n    description: Flank binary version. You can use any tag name that is available\n      on https://github.com/Flank/flank/releases or latest which will download the\n      latest non-pre-elease version.\n    is_required: true\n    summary: Flank binary version.\n    title: Version\n  version: latest\n- command_flags: null\n  opts:\n    description: These flags will be appended to the flank command. If your flank\n      config is for Android projects then these flags will be appended after `flank\n      android test` otherwise after `flank ios test`.\n    summary: These flags will be appended to the flank command.\n    title: Command Flags\n"
  },
  {
    "path": "steps/flank/0.1.2/step.yml",
    "content": "title: Flank\nsummary: Run your tests using Flank.\ndescription: Run your tests using Flank. The step will automatically detect which\n  project type your flank config uses and the corresponding flank command will be\n  ran.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flank\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flank\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flank/issues\npublished_at: 2020-08-17T15:54:51.665250491Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flank.git\n  commit: 017d767b9eb1c43d8139c2d799ebced1634dd13e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flank\ninputs:\n- google_service_account_json: null\n  opts:\n    description: Service Account JSON key file content.\n    is_required: true\n    is_sensitive: true\n    summary: Service Account JSON key file content.\n    title: Google Service Account JSON\n- config_path: null\n  opts:\n    description: Flank config file path.\n    is_required: true\n    summary: Flank config file path.\n    title: Config Path\n- opts:\n    description: Flank binary version. You can use any tag name that is available\n      on https://github.com/Flank/flank/releases or latest which will download the\n      latest non-pre-elease version.\n    is_required: true\n    summary: Flank binary version.\n    title: Version\n  version: latest\n- command_flags: null\n  opts:\n    description: These flags will be appended to the flank command. If your flank\n      config is for Android projects then these flags will be appended after `flank\n      android test` otherwise after `flank ios test`.\n    summary: These flags will be appended to the flank command.\n    title: Command Flags\n"
  },
  {
    "path": "steps/flank/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/flowdock/0.1.1/step.yml",
    "content": "title: Flowdock Notification\nsummary: This step posts a notification to your flow's inbox with the build status.\ndescription: |-\n  This is a step for posting a build status notifiction to Flowdock.\n\n  In order to use this step, you must create a shortcut application in your\n  Flowdock account's developer applications. From there create a source token\n  for the desired flow, and use that token here. More information can be found\n  at the [Flowdock API Reference](https://www.flowdock.com/api/developing-integrations)\nwebsite: https://github.com/scottrhoyt/bitrise-flowdock-step\nsource_code_url: https://github.com/scottrhoyt/bitrise-flowdock-step\nsupport_url: https://github.com/scottrhoyt/bitrise-flowdock-step/issues\npublished_at: 2015-12-18T07:33:39.488954095-08:00\nsource:\n  git: https://github.com/scottrhoyt/bitrise-flowdock-step.git\n  commit: 4b6c0e403e7cf0bdf4ad5a725c3ea5fd441bddb6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- messaging\n- notifiction\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- flowdock_source_token: null\n  opts:\n    description: |\n      In order to use this step, you must create a shortcut application in your\n      Flowdock account's developer applications. From there create a source token\n      for the desired flow, and use that token here. More information can be found\n      at the [Flowdock API Reference](https://www.flowdock.com/api/developing-integrations)\n    is_required: true\n    summary: This is the source token for the desired flow to post to.\n    title: Flowdock Source Token\n"
  },
  {
    "path": "steps/flowdock/0.1.2/step.yml",
    "content": "title: Flowdock Notification\nsummary: This step posts a notification to your flow's inbox with the build status.\ndescription: |-\n  This is a step for posting a build status notifiction to Flowdock.\n\n  In order to use this step, you must create a shortcut application in your\n  Flowdock account's developer applications. From there create a source token\n  for the desired flow, and use that token here. More information can be found\n  at the [Flowdock API Reference](https://www.flowdock.com/api/developing-integrations)\nwebsite: https://github.com/scottrhoyt/bitrise-flowdock-step\nsource_code_url: https://github.com/scottrhoyt/bitrise-flowdock-step\nsupport_url: https://github.com/scottrhoyt/bitrise-flowdock-step/issues\npublished_at: 2016-01-28T09:50:34.828310125-08:00\nsource:\n  git: https://github.com/scottrhoyt/bitrise-flowdock-step.git\n  commit: e6a13ae1069bfd5eb703b5d97ada234bdc93a694\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- notification\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- flowdock_source_token: null\n  opts:\n    description: |\n      In order to use this step, you must create a shortcut application in your\n      Flowdock account's developer applications. From there create a source token\n      for the desired flow, and use that token here. More information can be found\n      at the [Flowdock API Reference](https://www.flowdock.com/api/developing-integrations)\n    is_required: true\n    summary: This is the source token for the desired flow to post to.\n    title: Flowdock Source Token\n"
  },
  {
    "path": "steps/flowdock/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/flutter/0.0.1/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-04-20T18:18:13.855945078+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 08e077545839a29bc38120bd340d9317de8cb8b2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: xz-utils\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter version including channel. Without `v` prefix. E.g. `0.2.8-alpha`\n      or `0.3.0-dev`.\n    title: Flutter version\n  version: 0.2.8-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.10/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2020-06-27T03:22:59.401845+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 08299c223a02409cfb10256e8036c7d0d765d62f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.11/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2022-05-26T02:21:28.296729+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 1c0f805d855ce33be09c5d638ea045c998da8c18\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.2/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-05-02T03:39:36.966499418+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 3ea421d3e5efcb8327dab0089ee4fb043e53d0a0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: xz-utils\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter version including channel. Without `v` prefix. E.g. `0.2.8-alpha`\n      or `0.3.0-dev`.\n    title: Flutter version\n  version: 0.2.8-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.3/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-05-07T02:47:25.191078688+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 38af422e16295200026ef19ba7589709be289d17\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter version including channel. Without `v` prefix. E.g. `0.2.8-alpha`\n      or `0.3.0-dev`.\n    title: Flutter version\n  version: 0.3.1-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.4/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-05-24T02:36:11.594125829+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: e4489067d62bbd23f709dac74cc1a51ea3133882\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter version including channel. Without `v` prefix. E.g. `0.2.8-alpha`\n      or `0.3.0-dev`.\n    title: Flutter version\n  version: 0.4.4-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.5/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-09-06T03:40:51.865197808+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 063de0ddb40e2dc62578b59174224f0720c86118\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter version including channel. Without `v` prefix. E.g. `0.2.8-alpha`\n      or `0.3.0-dev`.\n    title: Flutter version\n  version: 0.4.4-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.6/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-10-11T21:39:10.678057285+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 0f1a4fa4742b791805ae213d6054a41f3b92b6e3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter version including channel. Without `v` prefix. E.g. `0.2.8-alpha`\n      or `0.3.0-dev`.\n    title: Flutter version\n  version: 0.9.4-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.7/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2018-11-02T02:34:59.169867863+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 4c3d436a925c237de1c822c8c4d62ae4be2d6b61\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 0.9.4-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.8/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2019-10-30T02:09:34.028498545+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 44a515c4a1ed69e00da944278040764a92d0842f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 0.9.4-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.0.9/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2019-12-18T02:57:18.48774403+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 23704c7ec148f0bd9c4f0e8eb5cb7b599e61b678\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 0.9.4-beta\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.0/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2021-12-15T11:41:54.436378+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 19d48ec2150e0341a200333ae7a96af2b1b741df\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.2/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2022-05-31T15:30:02.74846+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: b58a4f29be4aec651da6bf71ff10c4e6df2426cd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.3/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2022-07-05T17:20:32.375607+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 5445cdde09956372f7c8a56b08212665f29b61bb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.4/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2023-08-12T00:35:42.890745+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: c2774847744ce259c08f719f163501f85c010b7f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.5/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2024-05-27T20:18:00.691717+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 4ddca8041dc822e52993ba90db916d6f83bf7b68\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.6/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2024-10-09T22:01:14.443847+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: 1af3837d8685d1d489e267d18bc749a74e0f8b99\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/0.1.7/step.yml",
    "content": "title: Flutter\nsummary: |\n  Executes one or more Flutter commands. E.g. build, test or install.\ndescription: |\n  Sample `bitrise.yml` snippet for building iOS and Android apps:\n  ```yaml\n  primary:\n  steps:\n  - certificate-and-profile-installer:\n      inputs:\n      - install_defaults: 'no'\n  - activate-ssh-key:\n      run_if: '{{getenv \"SSH_RSA_PRIVATE_KEY\" | ne \"\"}}'\n  - git-clone: {}\n  - flutter:\n      inputs:\n      - commands: test|build ios|build apk\n  ```\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues\npublished_at: 2024-10-25T13:53:14.656674+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git\n  commit: add8cc531d26dcb7726cb2dfa5ba61bd97888fad\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- build\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-flutter\ndeps:\n  brew:\n  - name: git\n  - name: curl\n  - name: unzip\n  apt_get:\n  - name: git\n  - name: curl\n  - name: unzip\n  - name: libglu1-mesa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Flutter release version or repository tag, without `v` prefix. E.g. `0.9.4-beta`\n      or `0.10.0` or `master`.\n    title: Flutter version\n  version: 1.17.4\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The root directory of your Flutter project, where your `pubspec.yaml`\n      file is located.\n    title: Root directory of Flutter project\n  working_dir: $BITRISE_SOURCE_DIR\n- commands: build\n  opts:\n    is_expand: true\n    is_required: true\n    summary: |\n      `|` separated Flutter commands to be executed in order. E.g. `build`, `test` or `install`.\n    title: Flutter commands to be executed\n"
  },
  {
    "path": "steps/flutter/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/flutter-analyze/0.1.0/step.yml",
    "content": "title: Flutter Analyze\nsummary: This step will run `flutter analyze` command in a Flutter project\ndescription: This step will run `flutter analyze` command in a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2019-01-21T09:59:42.465098387Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: 3dceb1ed8427520f3b1cdb76324bdfc2fff51d8b\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/0.1.1/step.yml",
    "content": "title: Flutter Analyze\nsummary: This step will run `flutter analyze` command in a Flutter project\ndescription: This step will run `flutter analyze` command in a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2019-07-19T12:41:40.089487766Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: 558fc61b48acca823bf23ef8af63446f177dbb5e\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/0.1.2/step.yml",
    "content": "title: Flutter Analyze\nsummary: This step will run `flutter analyze` command in a Flutter project\ndescription: This step will run `flutter analyze` command in a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2019-12-03T10:30:11.541934251Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: 6160751fa203aa664f735c84fb872160b68b6598\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/0.2.0/step.yml",
    "content": "title: Flutter Analyze\nsummary: This Step runs the `flutter analyze` command in a Flutter project.\ndescription: |2-\n\n  The `flutter analyze` command is a wrapper around the [dartanalyzer](https://pub.dev/packages/analyzer) tool. It performs static analysis of your code. Check out the [available analysis options](https://github.com/flutter/flutter/blob/master/analysis_options.yaml) in the Flutter repository.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input to the source directory of your app.\n\n     By default, you do not have to change this.\n\n  2. Set the **Fail Severity** input to the minimum level that should make the step fail.\n\n     By default, the step fails on errors only. For example, you can set it to warning to make the step fail on both analyze errors and analyze warnings.\n\n  3. Add any flags you want to the `flutter analyze` command in the **Additional Parameters** input.\n\n     Run `flutter analyze --help` to check out the available flags. For example, you can set a flag so that the command only shows an output when there are some errors, warnings, hints or lints.\n\n  ### Useful links\n\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\n\n  ### Related Steps\n\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2020-07-28T11:09:34.959079349Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: 709f52cd87d66a2e622bec162455cdf256023dae\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- fail_severity: error\n  opts:\n    description: The minimum severity to fail the step, any issue with a severity\n      at least as high as the specified one will make the step fail.\n    is_required: true\n    summary: The minimum severity to fail the step, any issue with a severity at least\n      as high as the specified one will make the step fail.\n    title: Fail Severity\n    value_options:\n    - error\n    - warning\n    - info\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/0.3.0/step.yml",
    "content": "title: Flutter Analyze\nsummary: This Step runs the `flutter analyze` command in a Flutter project.\ndescription: |2-\n\n  The `flutter analyze` command is a wrapper around the [dartanalyzer](https://pub.dev/packages/analyzer) tool. It performs static analysis of your code. Check out the [available analysis options](https://github.com/flutter/flutter/blob/master/analysis_options.yaml) in the Flutter repository.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input to the source directory of your app.\n\n     By default, you do not have to change this.\n\n  2. Set the **Fail Severity** input to the minimum level that should make the step fail.\n\n     By default, the step fails on errors only. For example, you can set it to warning to make the step fail on both analyze errors and analyze warnings.\n\n  3. Add any flags you want to the `flutter analyze` command in the **Additional Parameters** input.\n\n     Run `flutter analyze --help` to check out the available flags. For example, you can set a flag so that the command only shows an output when there are some errors, warnings, hints or lints.\n\n  ### Useful links\n\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\n\n  ### Related Steps\n\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2020-12-04T12:36:14.159241498Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: 93c815dcd88a470df95d6d3c8250e960d41157cc\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- fail_severity: error\n  opts:\n    description: The minimum severity to fail the step, any issue with a severity\n      at least as high as the specified one will make the step fail.\n    is_required: true\n    summary: The minimum severity to fail the step, any issue with a severity at least\n      as high as the specified one will make the step fail.\n    title: Fail Severity\n    value_options:\n    - error\n    - warning\n    - info\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/0.3.1/step.yml",
    "content": "title: Flutter Analyze\nsummary: This Step runs the `flutter analyze` command in a Flutter project.\ndescription: |2-\n\n  The `flutter analyze` command is a wrapper around the [dartanalyzer](https://pub.dev/packages/analyzer) tool. It performs static analysis of your code. Check out the [available analysis options](https://github.com/flutter/flutter/blob/master/analysis_options.yaml) in the Flutter repository.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input to the source directory of your app.\n\n     By default, you do not have to change this.\n\n  2. Set the **Fail Severity** input to the minimum level that should make the Step fail.\n\n     By default, the Step fails on errors only. For example, you can set it to warning to make the Step fail on both analyze errors and analyze warnings.\n\n  3. Add any flags you want to the `flutter analyze` command in the **Additional Parameters** input.\n\n     Run `flutter analyze --help` to check out the available flags. For example, you can set a flag so that the command only shows an output when there are some errors, warnings, hints or lints.\n\n  ### Useful links\n\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\n\n  ### Related Steps\n\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2021-02-10T21:41:03.774879979Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: af44c7b592b9c7435da57d08dd1eb7124c450fab\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- fail_severity: error\n  opts:\n    description: The minimum severity to fail the Step. Any issue with a severity\n      at least as high as the specified one will make the Step fail.\n    is_required: true\n    summary: The minimum severity to fail the Step. Any issue with a severity at least\n      as high as the specified one will make the Step fail.\n    title: Fail Severity\n    value_options:\n    - error\n    - warning\n    - info\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/0.3.2/step.yml",
    "content": "title: Flutter Analyze\nsummary: This Step runs the `flutter analyze` command in a Flutter project.\ndescription: |2-\n\n  The `flutter analyze` command is a wrapper around the [dartanalyzer](https://pub.dev/packages/analyzer) tool. It performs static analysis of your code. Check out the [available analysis options](https://github.com/flutter/flutter/blob/master/analysis_options.yaml) in the Flutter repository.\n\n  ### Configuring the Step\n\n  1. Set the **Project Location** input to the source directory of your app.\n\n     By default, you do not have to change this.\n\n  2. Set the **Fail Severity** input to the minimum level that should make the Step fail.\n\n     By default, the Step fails on errors only. For example, you can set it to warning to make the Step fail on both analyze errors and analyze warnings.\n\n  3. Add any flags you want to the `flutter analyze` command in the **Additional Parameters** input.\n\n     Run `flutter analyze --help` to check out the available flags. For example, you can set a flag so that the command only shows an output when there are some errors, warnings, hints or lints.\n\n  ### Useful links\n\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\n\n  ### Related Steps\n\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze/issues\npublished_at: 2022-02-23T09:00:44.219470488Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-analyze.git\n  commit: 823361b0dcbb764f7621a14cc64a866e050d3b84\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-analyze\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- fail_severity: error\n  opts:\n    description: The minimum severity to fail the Step. Any issue with a severity\n      at least as high as the specified one will make the Step fail.\n    is_required: true\n    summary: The minimum severity to fail the Step. Any issue with a severity at least\n      as high as the specified one will make the Step fail.\n    title: Fail Severity\n    value_options:\n    - error\n    - warning\n    - info\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      analyze` command.\n    summary: The flags from this input field will be appended to the `flutter analyze`\n      command.\n    title: Additional Parameters\n"
  },
  {
    "path": "steps/flutter-analyze/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/flutter-build/0.10.0/step.yml",
    "content": "title: Flutter Build\nsummary: This step will build a Flutter project\ndescription: This step will build a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2019-08-12T16:40:41.260632668Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: 91ef57e516d8b862a8d53664fada558ee346c1cc\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: '*build/app/outputs/apk/*/*.apk'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built APK artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built APK artifacts relative to $BITRISE_SOURCE_DIR\n    title: APK output pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    title: App bundle output pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.11.0/step.yml",
    "content": "title: Flutter Build\nsummary: This step will build a Flutter project\ndescription: This step will build a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2019-08-15T08:26:05.645987498Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: 24545f7dc3ffb46fc1ecc2e45fc3383528fa63d7\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: '*build/app/outputs/apk/*/*.apk'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built APK artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built APK artifacts relative to $BITRISE_SOURCE_DIR\n    title: APK output pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    title: App bundle output pattern\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.12.0/step.yml",
    "content": "title: Flutter Build\nsummary: This step will build a Flutter project\ndescription: This step will build a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2019-08-26T14:02:56.529831946Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: acfbae87b8c6831bf59303eead40a389977b6fae\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR Deprecated,\n      use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.13.0/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: \"This Step builds an iOS and an Android app. By default the Step builds\n  the artifact based on the platform the scanner detects.\\n\\n### Configuring the Step\\n1.\n  In the **Project Location** input the root directory of your Flutter project is\n  automatically filled out.\\n2. Select which platform your project should be built\n  for (`ios`, `android` or `both`).\\n3. Enable **Debug** option to get verbose logs\n  and see where the Step is failing.\\n\\nDepending on the selected platform/s, continue\n  with the rest of the config inputs.\\n\\n#### Configuring for an iOS app\\n1. Make\n  sure the **Platform input** is set to `iOS` or `both`.\\n2. In **Codesign Identity**\n  you can onverride the code signing identities that you set in Flutter.\\n3. In **Additional\n  parameters** add any flag to customize your build (for example, the `--release`\n  flag appended to `flutter build io` builds a deployable iOS app).\\n4. Leave the\n  **Output pattern** input's default value as is or modify it to the pattern if your\n  build artifacts are stored elsewhere.\\n5. Make sure you have the **Xcode Archive\n  & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\\n\\n####\n  Configuring for an Android app\\n1. Insert the **Android Sign** Step after the **Flutter\n  Build** Step and make sure code signing files are uploaded to the **Code Signing**\n  tab.\\n2. Make sure the **Platform input** is set to `Android` or `both`.\\n3. Scroll\n  down to the `Android Platform Configs` input section, and select the preferred output\n  artifact type you wish to generate in the **Android output artifact type** input.\n  The Step can build an APK and an Android App Bundle as well.\\n4. Append any flag\n  to the `build` command in the **Additional parameters** input.\\n5. Leave the **Output\n  pattern** input's default value as is or modify it to the pattern if your build\n  artifacts are stored elsewhere.\\n\\n### Troubleshooting\\n\\nMake sure the **Flutter\n  Install** Step is before the **Flutter Build** Step.\\nIf you have not set up code\n  signing correctly, some code signing related issue will definitely surface by this\n  build Step. \\nIf you're unsure about code signing, consult our guide linked in Useful\n  links.\\n\\n### Useful links\\n- [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\\n-\n  [Available version tags](https://github.com/flutter/flutter/releases)\\n- [Available\n  branches](https://github.com/flutter/flutter/branches)\\n- [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\\n-\n  [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2020-06-24T09:59:50.391289264Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: 05f388f8a7da8a49b17afcd1439c6c78cabd1581\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR Deprecated,\n      use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.13.1/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: \"This Step builds an iOS and an Android app. By default the Step builds\n  the artifact based on the platform the scanner detects.\\n\\n### Configuring the Step\\n1.\n  In the **Project Location** input the root directory of your Flutter project is\n  automatically filled out.\\n2. Select which platform your project should be built\n  for (`ios`, `android` or `both`).\\n3. Enable **Debug** option to get verbose logs\n  and see where the Step is failing.\\n\\nDepending on the selected platform/s, continue\n  with the rest of the config inputs.\\n\\n#### Configuring for an iOS app\\n1. Make\n  sure the **Platform input** is set to `iOS` or `both`.\\n2. In **Codesign Identity**\n  you can onverride the code signing identities that you set in Flutter.\\n3. In **Additional\n  parameters** add any flag to customize your build (for example, the `--release`\n  flag appended to `flutter build io` builds a deployable iOS app).\\n4. Leave the\n  **Output pattern** input's default value as is or modify it to the pattern if your\n  build artifacts are stored elsewhere.\\n5. Make sure you have the **Xcode Archive\n  & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\\n\\n####\n  Configuring for an Android app\\n1. Insert the **Android Sign** Step after the **Flutter\n  Build** Step and make sure code signing files are uploaded to the **Code Signing**\n  tab.\\n2. Make sure the **Platform input** is set to `Android` or `both`.\\n3. Scroll\n  down to the `Android Platform Configs` input section, and select the preferred output\n  artifact type you wish to generate in the **Android output artifact type** input.\n  The Step can build an APK and an Android App Bundle as well.\\n4. Append any flag\n  to the `build` command in the **Additional parameters** input.\\n5. Leave the **Output\n  pattern** input's default value as is or modify it to the pattern if your build\n  artifacts are stored elsewhere.\\n\\n### Troubleshooting\\n\\nMake sure the **Flutter\n  Install** Step is before the **Flutter Build** Step.\\nIf you have not set up code\n  signing correctly, some code signing related issue will definitely surface by this\n  build Step. \\nIf you're unsure about code signing, consult our guide linked in Useful\n  links.\\n\\n### Useful links\\n- [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\\n-\n  [Available version tags](https://github.com/flutter/flutter/releases)\\n- [Available\n  branches](https://github.com/flutter/flutter/branches)\\n- [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\\n-\n  [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2020-06-29T13:27:29.421222525Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: 9d4da7c37769450e5e5f296010282fbc66beb99f\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR Deprecated,\n      use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.13.2/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: \"This Step builds an iOS and an Android app. By default the Step builds\n  the artifact based on the platform the scanner detects.\\n\\n### Configuring the Step\\n1.\n  In the **Project Location** input the root directory of your Flutter project is\n  automatically filled out.\\n2. Select which platform your project should be built\n  for (`ios`, `android` or `both`).\\n3. Enable **Debug** option to get verbose logs\n  and see where the Step is failing.\\n\\nDepending on the selected platform/s, continue\n  with the rest of the config inputs.\\n\\n#### Configuring for an iOS app\\n1. Make\n  sure the **Platform input** is set to `iOS` or `both`.\\n2. In **Codesign Identity**\n  you can onverride the code signing identities that you set in Flutter.\\n3. In **Additional\n  parameters** add any flag to customize your build (for example, the `--release`\n  flag appended to `flutter build io` builds a deployable iOS app).\\n4. Leave the\n  **Output pattern** input's default value as is or modify it to the pattern if your\n  build artifacts are stored elsewhere.\\n5. Make sure you have the **Xcode Archive\n  & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\\n\\n####\n  Configuring for an Android app\\n1. Insert the **Android Sign** Step after the **Flutter\n  Build** Step and make sure code signing files are uploaded to the **Code Signing**\n  tab.\\n2. Make sure the **Platform input** is set to `Android` or `both`.\\n3. Scroll\n  down to the `Android Platform Configs` input section, and select the preferred output\n  artifact type you wish to generate in the **Android output artifact type** input.\n  The Step can build an APK and an Android App Bundle as well.\\n4. Append any flag\n  to the `build` command in the **Additional parameters** input.\\n5. Leave the **Output\n  pattern** input's default value as is or modify it to the pattern if your build\n  artifacts are stored elsewhere.\\n\\n### Troubleshooting\\n\\nMake sure the **Flutter\n  Install** Step is before the **Flutter Build** Step.\\nIf you have not set up code\n  signing correctly, some code signing related issue will definitely surface by this\n  build Step. \\nIf you're unsure about code signing, consult our guide linked in Useful\n  links.\\n\\n### Useful links\\n- [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\\n-\n  [Available version tags](https://github.com/flutter/flutter/releases)\\n- [Available\n  branches](https://github.com/flutter/flutter/branches)\\n- [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\\n-\n  [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2020-07-16T11:12:12.778807616Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: 424490ae8776d86533f62af2c54132046f0ed76e\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built AAB artifacts relative to $BITRISE_SOURCE_DIR Deprecated,\n      use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.13.3/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: \"This Step builds an iOS and an Android app. By default the Step builds\n  the artifact based on the platform the scanner detects.\\n\\n### Configuring the Step\\n1.\n  In the **Project Location** input the root directory of your Flutter project is\n  automatically filled out.\\n2. Select which platform your project should be built\n  for (`ios`, `android` or `both`).\\n3. Enable **Debug** option to get verbose logs\n  and see where the Step is failing.\\n\\nDepending on the selected platform/s, continue\n  with the rest of the config inputs.\\n\\n#### Configuring for an iOS app\\n1. Make\n  sure the **Platform input** is set to `iOS` or `both`.\\n2. In **Codesign Identity**\n  you can onverride the code signing identities that you set in Flutter.\\n3. In **Additional\n  parameters** add any flag to customize your build (for example, the `--release`\n  flag appended to `flutter build io` builds a deployable iOS app).\\n4. Leave the\n  **Output pattern** input's default value as is or modify it to the pattern if your\n  build artifacts are stored elsewhere.\\n5. Make sure you have the **Xcode Archive\n  & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\\n\\n####\n  Configuring for an Android app\\n1. Insert the **Android Sign** Step after the **Flutter\n  Build** Step and make sure code signing files are uploaded to the **Code Signing**\n  tab.\\n2. Make sure the **Platform input** is set to `Android` or `both`.\\n3. Scroll\n  down to the `Android Platform Configs` input section, and select the preferred output\n  artifact type you wish to generate in the **Android output artifact type** input.\n  The Step can build an APK and an Android App Bundle as well.\\n4. Append any flag\n  to the `build` command in the **Additional parameters** input.\\n5. Leave the **Output\n  pattern** input's default value as is or modify it to the pattern if your build\n  artifacts are stored elsewhere.\\n\\n### Troubleshooting\\n\\nMake sure the **Flutter\n  Install** Step is before the **Flutter Build** Step.\\nIf you have not set up code\n  signing correctly, some code signing related issue will definitely surface by this\n  build Step. \\nIf you're unsure about code signing, consult our guide linked in Useful\n  links.\\n\\n### Useful links\\n- [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\\n-\n  [Available version tags](https://github.com/flutter/flutter/releases)\\n- [Available\n  branches](https://github.com/flutter/flutter/branches)\\n- [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\\n-\n  [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2021-05-12T12:33:35.161907253Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: cc9ff67e5233a9eed97b64881c2b8092ef89d589\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`\n    summary: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`.\n      Deprecated, use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.14.0/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: \"This Step builds an iOS and an Android app. By default the Step builds\n  the artifact based on the platform the scanner detects.\\n\\n### Configuring the Step\\n1.\n  In the **Project Location** input the root directory of your Flutter project is\n  automatically filled out.\\n2. Select which platform your project should be built\n  for (`ios`, `android` or `both`).\\n3. Enable **Debug** option to get verbose logs\n  and see where the Step is failing.\\n\\nDepending on the selected platform/s, continue\n  with the rest of the config inputs.\\n\\n#### Configuring for an iOS app\\n1. Make\n  sure the **Platform input** is set to `iOS` or `both`.\\n2. In **Codesign Identity**\n  you can onverride the code signing identities that you set in Flutter.\\n3. In **Additional\n  parameters** add any flag to customize your build (for example, the `--release`\n  flag appended to `flutter build io` builds a deployable iOS app).\\n4. Leave the\n  **Output pattern** input's default value as is or modify it to the pattern if your\n  build artifacts are stored elsewhere.\\n5. Make sure you have the **Xcode Archive\n  & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\\n\\n####\n  Configuring for an Android app\\n1. Insert the **Android Sign** Step after the **Flutter\n  Build** Step and make sure code signing files are uploaded to the **Code Signing**\n  tab.\\n2. Make sure the **Platform input** is set to `Android` or `both`.\\n3. Scroll\n  down to the `Android Platform Configs` input section, and select the preferred output\n  artifact type you wish to generate in the **Android output artifact type** input.\n  The Step can build an APK and an Android App Bundle as well.\\n4. Append any flag\n  to the `build` command in the **Additional parameters** input.\\n5. Leave the **Output\n  pattern** input's default value as is or modify it to the pattern if your build\n  artifacts are stored elsewhere.\\n\\n### Troubleshooting\\n\\nMake sure the **Flutter\n  Install** Step is before the **Flutter Build** Step.\\nIf you have not set up code\n  signing correctly, some code signing related issue will definitely surface by this\n  build Step. \\nIf you're unsure about code signing, consult our guide linked in Useful\n  links.\\n\\n### Useful links\\n- [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\\n-\n  [Available version tags](https://github.com/flutter/flutter/releases)\\n- [Available\n  branches](https://github.com/flutter/flutter/branches)\\n- [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\\n-\n  [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2021-08-23T11:33:48.102231273Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: f27f88f18dbb54b99b1c871dd994a5086656a17e\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- additional_build_params: \"\"\n  opts:\n    description: |-\n      Additional params for flutter build.\n\n      Example: you can specify a Build Number for `flutter build`\n      via the `--build-number` flutter build param.\n      For example, to set it to the `$BITRISE_BUILD_NUMBER` you can set this input\n      to: `--build-number=$BITRISE_BUILD_NUMBER`.\n    is_required: false\n    summary: Additional params for flutter build\n    title: Additional params for flutter build\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release --no-codesign\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`\n    summary: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`.\n      Deprecated, use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.15.0/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: |-\n  This Step builds an iOS and an Android app. By default the Step builds the artifact based on the platform the scanner detects.\n\n  ### Configuring the Step\n  1. In the **Project Location** input the root directory of your Flutter project is automatically filled out.\n  2. Select which platform your project should be built for (`ios`, `android` or `both`).\n  3. Enable **Debug** option to get verbose logs and see where the Step is failing.\n\n  Depending on the selected platform/s, continue with the rest of the config inputs.\n\n  #### Configuring for an iOS app\n  1. Make sure the **Platform input** is set to `iOS` or `both`.\n  2. In **Codesign Identity** you can onverride the code signing identities that you set in Flutter.\n  3. In **Additional parameters** add any flag to customize your build (for example, the `--release` flag appended to `flutter build io` builds a deployable iOS app).\n  4. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n  5. Make sure you have the **Xcode Archive & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\n\n  #### Configuring for an Android app\n  1. Insert the **Android Sign** Step after the **Flutter Build** Step and make sure code signing files are uploaded to the **Code Signing** tab.\n  2. Make sure the **Platform input** is set to `Android` or `both`.\n  3. Scroll down to the `Android Platform Configs` input section, and select the preferred output artifact type you wish to generate in the **Android output artifact type** input. The Step can build an APK and an Android App Bundle as well.\n  4. Append any flag to the `build` command in the **Additional parameters** input.\n  5. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n\n  ### Troubleshooting\n\n  Make sure the **Flutter Install** Step is before the **Flutter Build** Step.\n  If you have not set up code signing correctly, some code signing related issue will definitely surface by this build Step.\n  If you're unsure about code signing, consult our guide linked in Useful links.\n\n  ### Useful links\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n  - [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2022-02-08T13:18:30.982782226Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: f73d216d4a78ce3cf6d3e87799774456a1441a50\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- additional_build_params: \"\"\n  opts:\n    description: |-\n      Additional params for flutter build.\n\n      Example: you can specify a Build Number for `flutter build`\n      via the `--build-number` flutter build param.\n      For example, to set it to the `$BITRISE_BUILD_NUMBER` you can set this input\n      to: `--build-number=$BITRISE_BUILD_NUMBER`.\n    is_required: false\n    summary: Additional params for flutter build\n    title: Additional params for flutter build\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_output_type: app\n  opts:\n    category: iOS Platform Configs\n    description: |-\n      Output type to build when building for iOS. Possible values:\n      - `app`: Build an iOS application bundle via `flutter build ios`\n      - `archive`: Build an iOS archive bundle via `flutter build ipa`\n    is_required: true\n    summary: Output type to build when building for iOS\n    title: iOS output artifact type\n    value_options:\n    - app\n    - archive\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` or `flutter build ipa` command.\n    title: Additional parameters\n- ios_output_pattern: |-\n    *build/ios/iphoneos/*.app\n    *build/ios/archive/*.xcarchive\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`\n    summary: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`.\n      Deprecated, use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated `.app` directory\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory compressed as a ZIP archive\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.15.1/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: |-\n  This Step builds an iOS and an Android app. By default the Step builds the artifact based on the platform the scanner detects.\n\n  ### Configuring the Step\n  1. In the **Project Location** input the root directory of your Flutter project is automatically filled out.\n  2. Select which platform your project should be built for (`ios`, `android` or `both`).\n  3. Enable **Debug** option to get verbose logs and see where the Step is failing.\n\n  Depending on the selected platform/s, continue with the rest of the config inputs.\n\n  #### Configuring for an iOS app\n  1. Make sure the **Platform input** is set to `iOS` or `both`.\n  2. In **Codesign Identity** you can onverride the code signing identities that you set in Flutter.\n  3. In **Additional parameters** add any flag to customize your build (for example, the `--release` flag appended to `flutter build io` builds a deployable iOS app).\n  4. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n  5. Make sure you have the **Xcode Archive & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\n\n  #### Configuring for an Android app\n  1. Insert the **Android Sign** Step after the **Flutter Build** Step and make sure code signing files are uploaded to the **Code Signing** tab.\n  2. Make sure the **Platform input** is set to `Android` or `both`.\n  3. Scroll down to the `Android Platform Configs` input section, and select the preferred output artifact type you wish to generate in the **Android output artifact type** input. The Step can build an APK and an Android App Bundle as well.\n  4. Append any flag to the `build` command in the **Additional parameters** input.\n  5. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n\n  ### Troubleshooting\n\n  Make sure the **Flutter Install** Step is before the **Flutter Build** Step.\n  If you have not set up code signing correctly, some code signing related issue will definitely surface by this build Step.\n  If you're unsure about code signing, consult our guide linked in Useful links.\n\n  ### Useful links\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n  - [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2022-02-23T09:02:51.477422405Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: ac4bb3975938b305b6570bd20605ead3e83949c5\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- additional_build_params: \"\"\n  opts:\n    description: |-\n      Additional params for flutter build.\n\n      Example: you can specify a Build Number for `flutter build`\n      via the `--build-number` flutter build param.\n      For example, to set it to the `$BITRISE_BUILD_NUMBER` you can set this input\n      to: `--build-number=$BITRISE_BUILD_NUMBER`.\n    is_required: false\n    summary: Additional params for flutter build\n    title: Additional params for flutter build\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_output_type: app\n  opts:\n    category: iOS Platform Configs\n    description: |-\n      Output type to build when building for iOS. Possible values:\n      - `app`: Build an iOS application bundle via `flutter build ios`\n      - `archive`: Build an iOS archive bundle via `flutter build ipa`\n    is_required: true\n    summary: Output type to build when building for iOS\n    title: iOS output artifact type\n    value_options:\n    - app\n    - archive\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` or `flutter build ipa` command.\n    title: Additional parameters\n- ios_output_pattern: |-\n    *build/ios/iphoneos/*.app\n    *build/ios/archive/*.xcarchive\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`\n    summary: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`.\n      Deprecated, use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated `.app` directory\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory compressed as a ZIP archive\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.16.0/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: |-\n  This Step builds an iOS and an Android app. By default the Step builds the artifact based on the platform the scanner detects.\n\n  ### Configuring the Step\n  1. In the **Project Location** input the root directory of your Flutter project is automatically filled out.\n  2. Select which platform your project should be built for (`ios`, `android` or `both`).\n  3. Enable **Debug** option to get verbose logs and see where the Step is failing.\n\n  Depending on the selected platform/s, continue with the rest of the config inputs.\n\n  #### Configuring for an iOS app\n  1. Make sure the **Platform input** is set to `iOS` or `both`.\n  2. In **Codesign Identity** you can onverride the code signing identities that you set in Flutter.\n  3. In **Additional parameters** add any flag to customize your build (for example, the `--release` flag appended to `flutter build io` builds a deployable iOS app).\n  4. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n  5. Make sure you have the **Xcode Archive & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\n\n  #### Configuring for an Android app\n  1. Insert the **Android Sign** Step after the **Flutter Build** Step and make sure code signing files are uploaded to the **Code Signing** tab.\n  2. Make sure the **Platform input** is set to `Android` or `both`.\n  3. Scroll down to the `Android Platform Configs` input section, and select the preferred output artifact type you wish to generate in the **Android output artifact type** input. The Step can build an APK and an Android App Bundle as well.\n  4. Append any flag to the `build` command in the **Additional parameters** input.\n  5. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n\n  ### Troubleshooting\n\n  Make sure the **Flutter Install** Step is before the **Flutter Build** Step.\n  If you have not set up code signing correctly, some code signing related issue will definitely surface by this build Step.\n  If you're unsure about code signing, consult our guide linked in Useful links.\n\n  ### Useful links\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n  - [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2023-04-28T10:34:27.274824167Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: f2d76a799e25fffcdc2d89ed1133df735e858161\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- additional_build_params: \"\"\n  opts:\n    description: |-\n      Additional params for flutter build.\n\n      Example: you can specify a Build Number for `flutter build`\n      via the `--build-number` flutter build param.\n      For example, to set it to the `$BITRISE_BUILD_NUMBER` you can set this input\n      to: `--build-number=$BITRISE_BUILD_NUMBER`.\n    is_required: false\n    summary: Additional params for flutter build\n    title: Additional params for flutter build\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_output_type: app\n  opts:\n    category: iOS Platform Configs\n    description: |-\n      Output type to build when building for iOS. Possible values:\n      - `app`: Build an iOS application bundle via `flutter build ios`\n      - `archive`: Build an iOS archive bundle via `flutter build ipa`\n    is_required: true\n    summary: Output type to build when building for iOS\n    title: iOS output artifact type\n    value_options:\n    - app\n    - archive\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` or `flutter build ipa` command.\n    title: Additional parameters\n- ios_output_pattern: |-\n    *build/ios/iphoneos/*.app\n    *build/ios/archive/*.xcarchive\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`\n    summary: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`.\n      Deprecated, use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated `.app` directory\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory compressed as a ZIP archive\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.17.0/step.yml",
    "content": "title: Flutter Build\nsummary: Builds a Flutter project.\ndescription: |-\n  This Step builds an iOS and an Android app. By default the Step builds the artifact based on the platform the scanner detects.\n\n  ### Configuring the Step\n  1. In the **Project Location** input the root directory of your Flutter project is automatically filled out.\n  2. Select which platform your project should be built for (`ios`, `android` or `both`).\n  3. Enable **Debug** option to get verbose logs and see where the Step is failing.\n\n  Depending on the selected platform/s, continue with the rest of the config inputs.\n\n  #### Configuring for an iOS app\n  1. Make sure the **Platform input** is set to `iOS` or `both`.\n  2. In **Codesign Identity** you can onverride the code signing identities that you set in Flutter.\n  3. In **Additional parameters** add any flag to customize your build (for example, the `--release` flag appended to `flutter build io` builds a deployable iOS app).\n  4. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n  5. Make sure you have the **Xcode Archive & Export for iOS** Step after the **Flutter Build** Step in your Workflow.\n\n  #### Configuring for an Android app\n  1. Insert the **Android Sign** Step after the **Flutter Build** Step and make sure code signing files are uploaded to the **Code Signing** tab.\n  2. Make sure the **Platform input** is set to `Android` or `both`.\n  3. Scroll down to the `Android Platform Configs` input section, and select the preferred output artifact type you wish to generate in the **Android output artifact type** input. The Step can build an APK and an Android App Bundle as well.\n  4. Append any flag to the `build` command in the **Additional parameters** input.\n  5. Leave the **Output pattern** input's default value as is or modify it to the pattern if your build artifacts are stored elsewhere.\n\n  ### Troubleshooting\n\n  Make sure the **Flutter Install** Step is before the **Flutter Build** Step.\n  If you have not set up code signing correctly, some code signing related issue will definitely surface by this build Step.\n  If you're unsure about code signing, consult our guide linked in Useful links.\n\n  ### Useful links\n  - [Getting started with Flutter apps](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/#deploying-a-flutter-app)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n  - [Code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Flutter Install](https://www.bitrise.io/integrations/steps/flutter-installer)\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2023-08-30T07:10:33.398065613Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: d26d1d82661155b26fa3ce5969e8d01669ef7edc\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- additional_build_params: \"\"\n  opts:\n    description: |-\n      Additional params for flutter build.\n\n      Example: you can specify a Build Number for `flutter build`\n      via the `--build-number` flutter build param.\n      For example, to set it to the `$BITRISE_BUILD_NUMBER` you can set this input\n      to: `--build-number=$BITRISE_BUILD_NUMBER`.\n    is_required: false\n    summary: Additional params for flutter build\n    title: Additional params for flutter build\n- is_debug_mode: \"false\"\n  opts:\n    description: If debug mode is enabled, the step will print verbose logs\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Debug mode?\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: all\n  opts:\n    description: |-\n      If enabled, will cache:\n      - pub packages\n      - Android (gradle) cache\n      - Carthage / Cocoapods dependencies\n    is_required: true\n    summary: Enable or disable caching\n    title: Build cache\n    value_options:\n    - all\n    - none\n- ios_output_type: app\n  opts:\n    category: iOS Platform Configs\n    description: |-\n      Output type to build when building for iOS. Possible values:\n      - `app`: Build an iOS application bundle via `flutter build ios`\n      - `archive`: Build an iOS archive bundle via `flutter build ipa`\n    is_required: true\n    summary: Output type to build when building for iOS\n    title: iOS output artifact type\n    value_options:\n    - app\n    - archive\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` or `flutter build ipa` command.\n    title: Additional parameters\n- ios_output_pattern: |-\n    *build/ios/iphoneos/*.app\n    *build/ios/archive/*.xcarchive\n  opts:\n    category: iOS Platform Configs\n    description: Separate patterns with a newline.\n    is_required: true\n    summary: Pattern to find built artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output pattern\n- android_output_type: apk\n  opts:\n    category: Android Platform Configs\n    description: The selected output type will be build, either APK or app bundle\n      (AAB)\n    is_required: true\n    summary: The selected output type will be build, either APK or app bundle (AAB)\n    title: Android output artifact type\n    value_options:\n    - apk\n    - appbundle\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: |-\n    *build/app/outputs/apk/*/*.apk\n    *build/app/outputs/bundle/*/*.aab\n  opts:\n    category: Android Platform Configs\n    description: |\n      Will find the APK or AAB files - `depending on the build type input` - with the given pattern.<br/>\n      Separate patterns with a newline.\n      **Note**<br/>\n      The step will export only the selected artifact type - `Android output artifact type` - even if the filter would accept other artifact types as well.\n    is_required: true\n    summary: Pattern to find built APK or AAB artifacts relative to $BITRISE\\_SOURCE\\_DIR\n    title: Output (.apk, .aab) pattern\n- android_bundle_output_pattern: '*build/app/outputs/bundle/*/*.aab'\n  opts:\n    category: Deprecated\n    description: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`\n    summary: Pattern to find built AAB artifacts relative to `$BITRISE_SOURCE_DIR`.\n      Deprecated, use `android_output_pattern` instead.\n    title: '[DEPRECATED] App bundle output pattern'\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated `.app` directory\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    title: The generated `.xcarchive` directory compressed as a ZIP archive\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n"
  },
  {
    "path": "steps/flutter-build/0.9.0/step.yml",
    "content": "title: Flutter Build\nsummary: This step will build a Flutter project\ndescription: This step will build a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2018-12-14T12:22:13.872392269Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: fa7a43027e7a83e8e59bbdb42ee74438286b199a\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: '*build/app/outputs/apk/*/*.apk'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n"
  },
  {
    "path": "steps/flutter-build/0.9.1/step.yml",
    "content": "title: Flutter Build\nsummary: This step will build a Flutter project\ndescription: This step will build a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2018-12-14T14:35:52.59015422Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: 3dfca85ac304a44175d20d6cec5097e99b8ebef1\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: '*build/app/outputs/apk/*/*.apk'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n"
  },
  {
    "path": "steps/flutter-build/0.9.2/step.yml",
    "content": "title: Flutter Build\nsummary: This step will build a Flutter project\ndescription: This step will build a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-build/issues\npublished_at: 2019-01-25T09:29:52.106328047Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-build.git\n  commit: e8725d71e5e6404a43e88ddf650da90de8cd14a1\nproject_type_tags:\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-build\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- ios_codesign_identity: null\n  opts:\n    category: iOS Platform Configs\n    description: Override codesign identity in .flutter_settings\n    summary: Override codesign identity in .flutter_settings\n    title: Codesign Identity\n- ios_additional_params: --release\n  opts:\n    category: iOS Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build ios` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      ios` command.\n    title: Additional parameters\n- ios_output_pattern: '*build/ios/iphoneos/*.app'\n  opts:\n    category: iOS Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\n- android_additional_params: --release\n  opts:\n    category: Android Platform Configs\n    description: The flags from this input field will be appended to the `flutter\n      build apk` command.\n    summary: The flags from this input field will be appended to the `flutter build\n      apk` command.\n    title: Additional parameters\n- android_output_pattern: '*build/app/outputs/apk/*/*.apk'\n  opts:\n    category: Android Platform Configs\n    description: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    summary: Pattern to find built artifacts relative to $BITRISE_SOURCE_DIR\n    title: Output pattern\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    title: The created .apk file's path\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    title: All created .apk file's path list\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n"
  },
  {
    "path": "steps/flutter-build/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/flutter-build-patrol/0.0.8/step.yml",
    "content": "title: Flutter Build Patrol\nsummary: Install and Build Patrol for Flutter Projects\ndescription: |-\n  This steps initialy does:\n  - Installing the Patrol CLI if it is not already installed.\n  - Validates the installed Patrol CLI version and your project's Patrol version.\n  - Builds the Patrol APK, iOS or BOTH if specified.\nwebsite: https://github.com/Gpac-LLC/patrol_build_flutter\nsource_code_url: https://github.com/Gpac-LLC/patrol_build_flutter\nsupport_url: https://github.com/Gpac-LLC/patrol_build_flutter/issues\npublished_at: 2026-01-29T15:53:26.571798+01:00\nsource:\n  git: https://github.com/Gpac-LLC/patrol_build_flutter.git\n  commit: 916c80cd638c3150360acc46fd449bc8430e0eec\nproject_type_tags:\n- flutter\ntype_tags:\n- test\n- build\n- integration\ntoolkit:\n  go:\n    package_name: github.com/Gpac-LLC/patrol_build_flutter\ninputs:\n- custom_patrol_cli_version: \"\"\n  opts:\n    description: |-\n      If you want to use a specific version of Patrol, you can specify it here.\n      If you leave this input empty, the step will use the latest version of Patrol CLI.\n\n      If you specify a version that is not available, the step will fail.\n      **Resources:**\n      - [Compatibility Table](https://patrol.leancode.co/documentation/compatibility-table)\n    is_required: false\n    summary: Custom Patrol CLI Version\n    title: Custom Patrol CLI Version\n- opts:\n    description: \"The directory that will be built by the step.\\nIf you leave this\n      input empty, the step will use the entrypoint test_bundle.dart \\nfrom integration_test\n      or patrol_test folder, depending on your Patrol Version.\"\n    is_required: false\n    summary: The directory that will be built by the step\n    title: Test Target Directory\n  test_target_directory: null\n- opts:\n    description: The selected platform will be built, or both iOs and Android if you\n      select both\n    is_required: true\n    summary: The selected platform will be built, or both iOS and Android if you select\n      both\n    title: Platform\n    value_options:\n    - both\n    - ios\n    - android\n  platform: both\n- opts:\n    description: |-\n      The build type to use for the selected Platform.\n      If you leave this input empty, the step will use the default build type, which is `release`.\n      You can specify `debug` or `release` as the build type.\n    is_required: true\n    summary: The build type to use for the selected Platform\n    title: Build Type\n    value_options:\n    - release\n    - debug\n  test_build_type: release\n- opts:\n    description: |-\n      Tags to filter the tests to run.\n      You can specify multiple tags separated by commas.\n      If you leave this input empty, all tests will be run.\n    is_required: false\n    summary: Tags to filter the tests to run\n    title: Tags\n  tags: \"\"\n- excluded_tags: \"\"\n  opts:\n    description: |-\n      Tags to exclude from the tests to run.\n      You can specify multiple tags separated by commas.\n      If you leave this input empty, no tags will be excluded.\n    is_required: false\n    summary: Tags to exclude from the tests to run\n    title: Excluded Tags\n- is_verbose_mode: \"false\"\n  opts:\n    description: |-\n      If you want to disable verbose output for the step, you can set this input to `false`.\n      If you leave this input empty, the step will enable verbose output.\n      Verbose output can help you debug issues with the step.\n      It will print additional information about the step's execution.\n    is_required: true\n    summary: If debug mode is enabled, the step will print verbose logs\n    title: Print Verbose Output?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- ANDROID_INSTRUMENTATION_APK_PATH: null\n  opts:\n    description: The path to the Instrumentation APK file generated by the step\n    summary: This output contains the path to the Instrumentation APK file\n    title: Patrol Instrumentation APK Path\n- ANDROID_APK_PATH: null\n  opts:\n    description: The path to the APK file generated by the step\n    summary: This output contains the path to the APK file\n    title: Patrol APK Path\n- IOS_APP_UNDER_TEST: null\n  opts:\n    description: The path to the iOS Runner.app generated by the step\n    summary: This output contains the path to the iOS app under test\n    title: iOS App Under Test Path\n- IOS_TEST_INSTRUMENTATION_APP: null\n  opts:\n    description: The path to the RunnerUITests-Runner.app generated by the step\n    summary: This output contains the path to the iOS test instrumentation app\n    title: iOS Test Instrumentation App Path\n- IOS_RUNNER_FILE: null\n  opts:\n    description: The path to the .xctestrun file generated by the step\n    summary: This output contains the path to the iOS xctestrun file\n    title: iOS xctestrun File Path\n- IOS_BUILD_EXPORTS: null\n  opts:\n    description: The path to the zip containing the build directory and the .xctestrun\n      file\n    summary: This output contains the path to the zip with iOS test artifacts\n    title: iOS Build Exports Zip Path\n"
  },
  {
    "path": "steps/flutter-build-patrol/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/flutter-installer/0.10.0/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\ndescription: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2019-04-29T14:05:08.052748217Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: bd585b116b975e6a0c626cb04c5e5b1de8035e5f\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: \"The tag or branch of the Flutter SDK's git repository. \\n\\nTo find\n      the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\\n\\nTo\n      see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\"\n    is_required: true\n    summary: The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK Version\n  version: stable\n"
  },
  {
    "path": "steps/flutter-installer/0.11.0/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\ndescription: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2019-06-07T11:09:56.000812411Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 1a2da99c0448169e2f58d08f058443b2753305f7\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.11.1/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK. Use this step *before*\n  the cache-pull step to make sure pub caching is working correctly.\ndescription: |-\n  This step will git clone the selected branch or tag of the official Flutter repository and will run the initial setup of the Flutter SDK.\n\n  Use this step *before* the cache-pull step to make sure pub caching is working correctly.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2020-06-05T14:11:19.186106928Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: a173d5f704149b016123340980a832285d409143\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.11.2/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK. Use this step *before*\n  the cache-pull step to make sure pub caching is working correctly.\ndescription: |-\n  This step will git clone the selected branch or tag of the official Flutter repository and will run the initial setup of the Flutter SDK.\n\n  Use this step *before* the cache-pull step to make sure pub caching is working correctly.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2020-06-15T12:51:20.133936751Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 1a394f6516e13bb39fe8fa1e68b9810820f7f610\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.11.3/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK. Use this step *before*\n  the cache-pull step to make sure pub caching is working correctly.\ndescription: |-\n  This step will git clone the selected branch or tag of the official Flutter repository and will run the initial setup of the Flutter SDK.\n\n  Use this step *before* the cache-pull step to make sure pub caching is working correctly.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2020-06-18T09:35:29.753073406Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: ae04d800434e726a2ff7744875f9dd79491c4fa8\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.11.4/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2020-07-16T11:11:24.787816312Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 57100c5b6195b9a9abd5edff199a781c2bedd1c7\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.11.5/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2021-05-19T15:22:43.958427084Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: acc0179f8a775cdd1f3b7a925ecabbb210667daf\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.11.6/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2022-04-21T17:14:09.980114201Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 61d93be5abb5498c2b61a01981666b04942e673f\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.12.0/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2023-05-24T11:44:54.507282568Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: f245e79b713b94e0d6f82442cb4512c16475f197\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.13.0/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2023-06-06T08:37:44.185626999Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 1d38e024e352b573ef7ef150616adc7b09b59483\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.13.1/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2023-10-30T08:49:19.573238111Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 0ae472846c88cb5970104836928e2767933d780c\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_update: \"true\"\n  opts:\n    description: |-\n      If the version selected is `stable` and a preinstalled Flutter version from the `stable` channel with version 1.2.1 exists:\n      * Setting to `false` will not update, even if a later release exists.\n      * Setting to `true` will update Flutter to the latest version released in the channel.\n    summary: Set to true to update, if Flutter from a matching channel is preinstalled.\n    title: Update to the latest version\n    value_options:\n    - \"false\"\n    - \"true\"\n- installation_bundle_url: \"\"\n  opts:\n    description: |-\n      Installation bundle URL. If specified, Flutter will be installed from here and git repository version is ignored.\n\n      For a channel other than stable (e.g. beta), it is recommended to use this input. It is faster than cloning from git.\n\n      Official list of Flutter installation bundles: [https://flutter.dev/docs/development/tools/sdk/releases](https://flutter.dev/docs/development/tools/sdk/releases)\n\n      The URL is expected to begin with: `https://storage.googleapis.com/flutter_infra`\n\n      Example value (beta channel, version 1.6.3, macOS): `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n    is_required: false\n    summary: Install from bundle. Prefer this input (for other than stable channel),\n      as it is faster than cloning from git.\n    title: Flutter SDK installation bundle URL\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/0.9.1/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\ndescription: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2018-12-12T13:02:21.998535313Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 95628f911fcd061cf9274401ab27bc6b043eb548\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: \"The tag or branch of the Flutter SDK's git repository. \\n\\nTo find\n      the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\\n\\nTo\n      see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\"\n    is_required: true\n    summary: The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK Version\n  version: stable\n"
  },
  {
    "path": "steps/flutter-installer/0.9.2/step.yml",
    "content": "title: Flutter Install\nsummary: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\ndescription: This step will git clone the selected branch or tag of the official Flutter\n  repository and will run the initial setup of the Flutter SDK.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2018-12-14T12:00:59.055107041Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 20118e6de46ad0c9c484bc0f165c5a6033dfd457\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: \"The tag or branch of the Flutter SDK's git repository. \\n\\nTo find\n      the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\\n\\nTo\n      see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\"\n    is_required: true\n    summary: The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK Version\n  version: stable\n"
  },
  {
    "path": "steps/flutter-installer/1.0.0/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2025-07-08T07:37:11.936935072Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: 0e638c30d526942bba601c190e3ee2341dd78680\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    is_required: false\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/1.0.1/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step git clones the selected branch or tag of the official Flutter repository and runs the initial setup of the Flutter SDK.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK git repository version** input set the tag or branch of the Flutter. The default value is `stable` which clones and installs the latest stable Flutter branch.\n  2. In the **Update to the latest version** input select `false` to use a preinstalled Flutter version or `true` to update Flutter SDK to the latest version released in the [build release channel](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels). By default, this input is set to `true`.\n  4. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, use the **Flutter SDK installation bundle URL** input. Insert the URL of the preferred [bundle](https://flutter.dev/docs/development/tools/sdk/releases), for example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. If the input is filled out correctly, it overrides the value set in the **Flutter SDK git repository version** input.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2025-09-02T14:59:30.195374142Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: de2f8db79824870666cd54eed9b45e8f8d63d9ed\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Use this input to install from the git repository by specifying a tag or branch.\n\n      Use this input for the stable channel, as the stable channel can be preinstalled.\n\n      If the input Flutter SDK installation bundle URL is specified, this input is ignored.\n\n      To find the available version tags see this list: [https://github.com/flutter/flutter/releases](https://github.com/flutter/flutter/releases)\n\n      To see the the avilable branches visit: [https://github.com/flutter/flutter/branches](https://github.com/flutter/flutter/branches)\n    is_required: false\n    summary: Install from git. The tag or branch of the Flutter SDK's git repository.\n    title: Flutter SDK git repository version\n  version: stable\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    is_required: false\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/1.0.2/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step installs the Flutter SDK using FVM, ASDF, or manual installation methods and runs the initial setup.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK version or bundle URL** input set the version, tag, branch, or bundle URL. The default value is `stable`.\n  2. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, provide a Flutter SDK bundle URL in the **Flutter SDK version or bundle URL** input. For example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. When a valid bundle URL is provided, it will download and install from that bundle instead of cloning from git.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2025-09-12T12:20:00.186352042Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: c69c4281a30ae6d3cfa37f52ec6bc10f34387c5f\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Specify the Flutter version using a tag, branch, channel name, or Flutter SDK bundle URL.\n\n      **Installation priority:**\n      1. Use FVM/ASDF if available and has the version installed\n      2. Install via FVM/ASDF if version is available in their releases\n      3. Manual installation: download from bundle URL or clone from git repository\n\n      **Examples:**\n      - Channels: `stable`, `beta`, `dev`\n      - Versions: `3.32.5`, `v1.6.3-beta`\n      - Bundle URL: `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n\n      **Resources:**\n      - [Version tags](https://github.com/flutter/flutter/releases)\n      - [Branches](https://github.com/flutter/flutter/branches)\n      - [Bundle URLs](https://flutter.dev/docs/development/tools/sdk/releases)\n    is_required: false\n    summary: Install from git repository (tag/branch) or from a Flutter SDK bundle\n      URL.\n    title: Flutter SDK version or bundle URL\n  version: stable\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    is_required: false\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/1.1.0/step.yml",
    "content": "title: Flutter Install\nsummary: Install Flutter SDK.\ndescription: |-\n  This Step installs the Flutter SDK using FVM, ASDF, or manual installation methods and runs the initial setup.\n  Use this step *before* the cache-pull step to make sure caching works correctly.\n\n  ### Configuring the Step\n  1. In the **Flutter SDK version or bundle URL** input set the version, tag, branch, or bundle URL. The default value is `stable`.\n  2. Enable **Print debug information** to run `flutter doctor` to see if there are any missing platform dependencies for setting up Flutter.\n\n  ### Troubleshooting\n  If you prefer to install Flutter from an installation bundle instead of the git repository, provide a Flutter SDK bundle URL in the **Flutter SDK version or bundle URL** input. For example, `https://storage.googleapis.com/flutter_infra/releases/dev/windows/flutter_windows_v1.14.5-dev.zip`. When a valid bundle URL is provided, it will download and install from that bundle instead of cloning from git.\n\n  ### Useful links\n  - [About Flutter build release channels](https://github.com/flutter/flutter/wiki/Flutter-build-release-channels)\n  - [Available version tags](https://github.com/flutter/flutter/releases)\n  - [Available branches](https://github.com/flutter/flutter/branches)\n\n  ### Related Steps\n  - [Flutter Test](https://www.bitrise.io/integrations/steps/flutter-test)\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-installer/issues\npublished_at: 2026-02-18T10:39:35.637640168Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-installer.git\n  commit: eaa76f80e291c58d0172a260b90022d44e74fa9f\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/flutter-installer/1.1.0/bin/flutter-installer-darwin-amd64\n    hash: sha256-f33b0b0f4a3fea4ff385bbfce155d03ab913c9dcbadddefb29974bd768ca4e83\n  darwin-arm64:\n    storage_uri: steps/flutter-installer/1.1.0/bin/flutter-installer-darwin-arm64\n    hash: sha256-e432041ec88a79ee74f10155a274fbe357f3ec3dfa8f749fcbc99259049979ea\n  linux-amd64:\n    storage_uri: steps/flutter-installer/1.1.0/bin/flutter-installer-linux-amd64\n    hash: sha256-74f661bfe9329163098c8b7c70260f58e5ea86b07d1e275da8920a5cce916c5e\n  linux-arm64:\n    storage_uri: steps/flutter-installer/1.1.0/bin/flutter-installer-linux-arm64\n    hash: sha256-c5bafb6afc59532bec63839774c35ec718ef6477801228a6f5fc953879bf2758\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-installer\ndeps:\n  brew:\n  - name: git\n  - name: tar\n  apt_get:\n  - name: git\n  - name: tar\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |-\n      Specify the Flutter version using a tag, branch, channel name, or Flutter SDK bundle URL.\n\n      **Installation priority:**\n      1. Use FVM/ASDF if available and has the version installed\n      2. Install via FVM/ASDF if version is available in their releases\n      3. Manual installation: download from bundle URL or clone from git repository\n\n      **Examples:**\n      - Channels: `stable`, `beta`, `dev`\n      - Versions: `3.32.5`, `v1.6.3-beta`\n      - Bundle URL: `https://storage.googleapis.com/flutter_infra/releases/beta/macos/flutter_macos_v1.6.3-beta.zip`\n\n      **Resources:**\n      - [Version tags](https://github.com/flutter/flutter/releases)\n      - [Branches](https://github.com/flutter/flutter/branches)\n      - [Bundle URLs](https://flutter.dev/docs/development/tools/sdk/releases)\n    is_required: false\n    summary: Install from git repository (tag/branch) or from a Flutter SDK bundle\n      URL.\n    title: Flutter SDK version or bundle URL\n  version: stable\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    is_required: false\n    summary: If enabled will run flutter doctor and print value of PATH eniroment\n      variable.\n    title: Print debug information\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/flutter-installer/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/flutter-test/0.10.0/step.yml",
    "content": "title: Flutter Test\nsummary: This step will run tests in a Flutter project\ndescription: This step will run tests in a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2020-06-15T13:07:22.700062247Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: 44af17922050974889857bf040f88e12c4bb8bc0\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      test` command.\n    summary: The flags from this input field will be appended to the `flutter test`\n      command.\n    title: Additional parameters\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/0.10.1/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: \"\\nIf you have tests in your repository, and selected `yes` when prompted\n  during app creation, the primary Workflow will include the **Flutter Test** Step\n  by default. \\nIf you add tests to your app later, add the **Flutter Test** Step\n  to your Workflow manually. The Step runs the `flutter test` command with the specified\n  flags. To check the available flags, open a command line interface on your own machine\n  and run `flutter test --help`.\\n\\n### Configuring the Step\\n1. Provide your project's\n  root directory in the **Project Location** field.\\n2. The **Step's test result directory**\n  is the root directory for all test results created by the Bitrise CLI. This input\n  gets filled out automatically.\\n3. You can append additional flags to the default\n  `flutter test` command in the **Additional parameters** field.\\n4. Select 'yes'\n  in the **Generate code coverage files** input to get detailed analysis of your code.\\n\\n\\n###\n  Troubleshooting\\nMake sure the **Project Location** input of the Flutter Test Step\n  is correct. \\nThe default value is the Environment Variable (Env Var) created for\n  your Flutter project’s location.\\n\\n\\n### Useful links\\n- [Getting started with\n  Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\\n-\n  [About testing](https://devcenter.bitrise.io/testing/testing-index/)\\n\\n### Related\n  Steps\\n- [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\\n-\n  [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2020-06-17T10:27:20.308899949Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: d4fb9534511f4adc73f5cd8248e6f11191080ec7\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      test` command.\n    summary: The flags from this input field will be appended to the `flutter test`\n      command.\n    title: Additional parameters\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/0.10.2/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: \"\\nIf you have tests in your repository, and selected `yes` when prompted\n  during app creation, the primary Workflow will include the **Flutter Test** Step\n  by default. \\nIf you add tests to your app later, add the **Flutter Test** Step\n  to your Workflow manually. The Step runs the `flutter test` command with the specified\n  flags. To check the available flags, open a command line interface on your own machine\n  and run `flutter test --help`.\\n\\n### Configuring the Step\\n1. Provide your project's\n  root directory in the **Project Location** field.\\n2. The **Step's test result directory**\n  is the root directory for all test results created by the Bitrise CLI. This input\n  gets filled out automatically.\\n3. You can append additional flags to the default\n  `flutter test` command in the **Additional parameters** field.\\n4. Select 'yes'\n  in the **Generate code coverage files** input to get detailed analysis of your code.\\n\\n\\n###\n  Troubleshooting\\nMake sure the **Project Location** input of the Flutter Test Step\n  is correct. \\nThe default value is the Environment Variable (Env Var) created for\n  your Flutter project’s location.\\n\\n\\n### Useful links\\n- [Getting started with\n  Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\\n-\n  [About testing](https://devcenter.bitrise.io/testing/testing-index/)\\n\\n### Related\n  Steps\\n- [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\\n-\n  [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2021-01-07T15:33:20.624426645Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: ec8ac22b42cae04d257a3ccd2b4aeb9d378ec6f7\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      test` command.\n    summary: The flags from this input field will be appended to the `flutter test`\n      command.\n    title: Additional parameters\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/0.10.3/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: \"\\nIf you have tests in your repository, and selected `yes` when prompted\n  during app creation, the primary Workflow will include the **Flutter Test** Step\n  by default. \\nIf you add tests to your app later, add the **Flutter Test** Step\n  to your Workflow manually. The Step runs the `flutter test` command with the specified\n  flags. To check the available flags, open a command line interface on your own machine\n  and run `flutter test --help`.\\n\\n### Configuring the Step\\n1. Provide your project's\n  root directory in the **Project Location** field.\\n2. The **Step's test result directory**\n  is the root directory for all test results created by the Bitrise CLI. This input\n  gets filled out automatically.\\n3. You can append additional flags to the default\n  `flutter test` command in the **Additional parameters** field.\\n4. Select 'yes'\n  in the **Generate code coverage files** input to get detailed analysis of your code.\\n\\n\\n###\n  Troubleshooting\\nMake sure the **Project Location** input of the Flutter Test Step\n  is correct. \\nThe default value is the Environment Variable (Env Var) created for\n  your Flutter project’s location.\\n\\n\\n### Useful links\\n- [Getting started with\n  Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\\n-\n  [About testing](https://devcenter.bitrise.io/testing/testing-index/)\\n\\n### Related\n  Steps\\n- [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\\n-\n  [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2021-03-10T12:37:54.424905472Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: 73eafe710839c214114ca07ab7cc629def4c8c94\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      test` command.\n    summary: The flags from this input field will be appended to the `flutter test`\n      command.\n    title: Additional parameters\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/0.9.0/step.yml",
    "content": "title: Flutter Test\nsummary: This step will run tests in a Flutter project\ndescription: This step will run tests in a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2018-12-14T12:07:56.108236789Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: 1f0a60c7bdcfb18c60f4d9d9c139a4b30c19004a\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      test` command.\n    summary: The flags from this input field will be appended to the `flutter test`\n      command.\n    title: Additional parameters\n"
  },
  {
    "path": "steps/flutter-test/0.9.1/step.yml",
    "content": "title: Flutter Test\nsummary: This step will run tests in a Flutter project\ndescription: This step will run tests in a Flutter project\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2018-12-14T14:36:26.47896942Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: eb84589a39c16561925608c6af10083eba8c0526\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- additional_params: null\n  opts:\n    description: The flags from this input field will be appended to the `flutter\n      test` command.\n    summary: The flags from this input field will be appended to the `flutter test`\n      command.\n    title: Additional parameters\n"
  },
  {
    "path": "steps/flutter-test/1.0.0/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: \"\\nIf you have tests in your repository, and selected `yes` when prompted\n  during app creation, the primary Workflow will include the **Flutter Test** Step\n  by default. \\nIf you add tests to your app later, add the **Flutter Test** Step\n  to your Workflow manually. The Step runs the `flutter test` command with the specified\n  flags. To check the available flags, open a command line interface on your own machine\n  and run `flutter test --help`.\\n\\n### Configuring the Step\\n1. Provide your project's\n  root directory in the **Project Location** field.\\n2. The **Step's test result directory**\n  is the root directory for all test results created by the Bitrise CLI. This input\n  gets filled out automatically.\\n3. You can append additional flags to the default\n  `flutter test` command in the **Additional parameters** field.\\n4. Select 'yes'\n  in the **Generate code coverage files** input to get detailed analysis of your code.\\n\\n\\n###\n  Troubleshooting\\nMake sure the **Project Location** input of the Flutter Test Step\n  is correct. \\nThe default value is the Environment Variable (Env Var) created for\n  your Flutter project’s location.\\n\\n\\n### Useful links\\n- [Getting started with\n  Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\\n-\n  [About testing](https://devcenter.bitrise.io/testing/testing-index/)\\n\\n### Related\n  Steps\\n- [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\\n-\n  [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2021-04-30T13:42:25.561962286Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: 763b0785337bb8c7dd2b3a4c3abb4cec30fc587b\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field are appended to the `flutter test`\n      command.\n    summary: The flags from this input field are appended to the `flutter test` command.\n    title: Additional parameters\n- opts:\n    description: \"The pattern from this input field is expanded and fed to the `flutter\n      test` command.  \\nBoth * and ** glob patterns are supported. For example, `lib/**/*_test.dart`.\"\n    summary: This pattern is used as the last argument appended to the `flutter test`\n      command.\n    title: Test files pattern\n  tests_path_pattern: null\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/1.0.1/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: \"\\nIf you have tests in your repository, and selected `yes` when prompted\n  during app creation, the primary Workflow will include the **Flutter Test** Step\n  by default. \\nIf you add tests to your app later, add the **Flutter Test** Step\n  to your Workflow manually. The Step runs the `flutter test` command with the specified\n  flags. To check the available flags, open a command line interface on your own machine\n  and run `flutter test --help`.\\n\\n### Configuring the Step\\n1. Provide your project's\n  root directory in the **Project Location** field.\\n2. The **Step's test result directory**\n  is the root directory for all test results created by the Bitrise CLI. This input\n  gets filled out automatically.\\n3. You can append additional flags to the default\n  `flutter test` command in the **Additional parameters** field.\\n4. Select 'yes'\n  in the **Generate code coverage files** input to get detailed analysis of your code.\\n\\n\\n###\n  Troubleshooting\\nMake sure the **Project Location** input of the Flutter Test Step\n  is correct. \\nThe default value is the Environment Variable (Env Var) created for\n  your Flutter project’s location.\\n\\n\\n### Useful links\\n- [Getting started with\n  Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\\n-\n  [About testing](https://devcenter.bitrise.io/testing/testing-index/)\\n\\n### Related\n  Steps\\n- [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\\n-\n  [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\"\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2021-09-16T15:33:17.205806227Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: 5acdfdf1c136b122aeeee307ed3ddf0c993a9529\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field are appended to the `flutter test`\n      command.\n    summary: The flags from this input field are appended to the `flutter test` command.\n    title: Additional parameters\n- opts:\n    description: \"The pattern from this input field is expanded and fed to the `flutter\n      test` command.  \\nBoth * and ** glob patterns are supported. For example, `lib/**/*_test.dart`.\"\n    summary: This pattern is used as the last argument appended to the `flutter test`\n      command.\n    title: Test files pattern\n  tests_path_pattern: null\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/1.0.2/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: |2-\n\n  If you have tests in your repository, and selected `yes` when prompted during app creation, the primary Workflow will include the **Flutter Test** Step by default.\n  If you add tests to your app later, add the **Flutter Test** Step to your Workflow manually. The Step runs the `flutter test` command with the specified flags. To check the available flags, open a command line interface on your own machine and run `flutter test --help`.\n\n  ### Configuring the Step\n  1. Provide your project's root directory in the **Project Location** field.\n  2. The **Step's test result directory** is the root directory for all test results created by the Bitrise CLI. This input gets filled out automatically.\n  3. You can append additional flags to the default `flutter test` command in the **Additional parameters** field.\n  4. Select 'yes' in the **Generate code coverage files** input to get detailed analysis of your code.\n\n\n  ### Troubleshooting\n  Make sure the **Project Location** input of the Flutter Test Step is correct.\n  The default value is the Environment Variable (Env Var) created for your Flutter project’s location.\n\n\n  ### Useful links\n  - [Getting started with Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\n  - [About testing](https://devcenter.bitrise.io/testing/testing-index/)\n\n  ### Related Steps\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\n  - [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2022-02-23T08:23:59.247031168Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: ce84c8ec4ea1e3c051da119a48005c71430b29f0\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field are appended to the `flutter test`\n      command.\n    summary: The flags from this input field are appended to the `flutter test` command.\n    title: Additional parameters\n- opts:\n    description: |-\n      The pattern from this input field is expanded and fed to the `flutter test` command.\n      Both * and ** glob patterns are supported. For example, `lib/**/*_test.dart`.\n    summary: This pattern is used as the last argument appended to the `flutter test`\n      command.\n    title: Test files pattern\n  tests_path_pattern: null\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/1.0.3/step.yml",
    "content": "title: Flutter Test\nsummary: Performs any test in a Flutter project.\ndescription: |-\n  If you have tests in your repository, and selected `yes` when prompted during app creation, the primary Workflow will include the **Flutter Test** Step by default.\n  If you add tests to your app later, add the **Flutter Test** Step to your Workflow manually. The Step runs the `flutter test` command with the specified flags. To check the available flags, open a command line interface on your own machine and run `flutter test --help`.\n\n  ### Configuring the Step\n  1. Provide your project's root directory in the **Project Location** field.\n  2. The **Step's test result directory** is the root directory for all test results created by the Bitrise CLI. This input gets filled out automatically.\n  3. You can append additional flags to the default `flutter test` command in the **Additional parameters** field.\n  4. Select 'yes' in the **Generate code coverage files** input to get detailed analysis of your code.\n\n  ### Troubleshooting\n  Make sure the **Project Location** input of the Flutter Test Step is correct.\n  The default value is the Environment Variable (Env Var) created for your Flutter project’s location.\n\n  ### Useful links\n  - [Getting started with Flutter](https://devcenter.bitrise.io/getting-started/getting-started-with-flutter-apps/)\n  - [About testing](https://devcenter.bitrise.io/testing/testing-index/)\n\n  ### Related Steps\n  - [Flutter Build](https://www.bitrise.io/integrations/steps/flutter-build)\n  - [Flutter Analyze](https://www.bitrise.io/integrations/steps/flutter-analyze)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-flutter-test/issues\npublished_at: 2026-04-23T13:33:59.760720313Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-flutter-test.git\n  commit: 6f9097f2b8ee54ae5a1abe7eff215e29d7faa94b\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/flutter-test/1.0.3/bin/flutter-test-darwin-amd64\n    hash: sha256-18e2938b559f2ba61bd710007fe5d39031f3c4adafdb4a3a61e679fda492c080\n  darwin-arm64:\n    storage_uri: steps/flutter-test/1.0.3/bin/flutter-test-darwin-arm64\n    hash: sha256-f6154efa355085fb319090f56d21b4e31f46462a83ba4b4c891e0620de3633ab\n  linux-amd64:\n    storage_uri: steps/flutter-test/1.0.3/bin/flutter-test-linux-amd64\n    hash: sha256-29d74feaa7c241144d11d62ba0ac2abac86c1fcc400151d0414db51ca5dd3839\n  linux-arm64:\n    storage_uri: steps/flutter-test/1.0.3/bin/flutter-test-linux-arm64\n    hash: sha256-8d7a963d7bbe396de5414e34525771d8ea82968cd0846b79eaf758906c16a235\nproject_type_tags:\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-flutter-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The root dir of your Flutter project.\n    is_required: true\n    summary: The root dir of your Flutter project.\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_test_result_dir: $BITRISE_TEST_RESULT_DIR\n  opts:\n    description: Root directory for all test results created by the Bitrise CLI\n    is_dont_change_value: true\n    is_required: true\n    title: Step's test result directory\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `flutter test` gets `--coverage` passed\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- additional_params: null\n  opts:\n    description: The flags from this input field are appended to the `flutter test`\n      command.\n    summary: The flags from this input field are appended to the `flutter test` command.\n    title: Additional parameters\n- opts:\n    description: |-\n      The pattern from this input field is expanded and fed to the `flutter test` command.\n      Both * and ** glob patterns are supported. For example, `lib/**/*_test.dart`.\n    summary: This pattern is used as the last argument appended to the `flutter test`\n      command.\n    title: Test files pattern\n  tests_path_pattern: null\noutputs:\n- BITRISE_FLUTTER_COVERAGE_PATH: null\n  opts:\n    description: The path of the generated code coverage `lcov.info` file.\n    title: The path of the generated `lcov.info`\n- BITRISE_FLUTTER_TESTRESULT_PATH: null\n  opts:\n    description: The path of the json file that was generated by the `flutter test`\n      command.\n    title: The path of the generated json test report\n"
  },
  {
    "path": "steps/flutter-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/fortify-on-demand-mobile-assessment/0.0.1/step.yml",
    "content": "title: Fortify on Demand Mobile Assessment\nsummary: |\n  Submits a Fortify on Demand Mobile Assessment\ndescription: |\n  Fortify on Demand delivers comprehensive end-to-end mobile security with real-world mobile application security testing across all three tiers of the mobile ecosystem—client device, network, and web services. Similar to dynamic testing for web applications, mobile assessments utilize the compiled application binary and employ the same techniques hackers utilize to exploit vulnerabilities in mobile applications, whether they are developed internally, outsourced, or acquired. More than just simple reputation or behavioral analysis, Fortify on Demand mobile assessments provide true security testing for companies serious about securing their mobile applications.\n\n  For more information, please refer to the datasheet at https://www.microfocus.com/media/data-sheet/fortify_on_demand_ds.pdf\nwebsite: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nsource_code_url: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nsupport_url: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment/issues\npublished_at: 2021-09-27T21:28:40.763379508+08:00\nsource:\n  git: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment.git\n  commit: 4e501c3ec23f933f81faf0a0ecdfa104d741ad74\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- client_id: null\n  opts:\n    description: Authenticating with Client Credentials. The client credentials are\n      the API keys generated in the portal.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client ID for authentication\n    title: Client ID\n- client_secret: null\n  opts:\n    description: Authenticating with Client Credentials. The client credentials are\n      the API keys generated in the portal.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client secret for authentication\n    title: Client Secret\n- datacenter: ' '\n  opts:\n    description: Select the datacenter assigned to you. This is provided once your\n      are onboarded with Fortify on Demand.\n    is required: true\n    is_expand: true\n    summary: Fortify on Demand Datacenters\n    title: Datacenter\n    value_options:\n    - AMS\n    - APJ\n    - EMEA\n    - FED\n- entitlement_id: null\n  opts:\n    description: The ID assigned to ypur current entitlement. This value can be reterived\n      in Foritfy on Demand portal.\n    is_expand: true\n    is_required: true\n    summary: Entitlement ID for this mobile assessment\n    title: Entitlement ID\n- opts:\n    description: The ID assigned to the created release. This value can be reterived\n      in Foritfy on Demand portal.\n    is_expand: true\n    is_required: true\n    summary: Release ID for this mobile assessment\n    title: Release ID\n  release_id: null\n- assessment_type: ' '\n  opts:\n    description: \"Mobile Assessment includes Vulnerability analysis of mobile binary,\n      Endpoint reputation analysis and Security expert review of prioritized results.\n      \\nMobile+ Assessment includes Manual testing of binary, network and services,\n      and DAST of backend services\\nFor more information, please refer to the datasheet\n      at https://www.microfocus.com/media/data-sheet/fortify_on_demand_ds.pdf\\n\"\n    is required: true\n    is_expand: true\n    summary: Assessment type for this mobile assessment\n    title: Assessment Type\n    value_options:\n    - Mobile Assessment (Single Scan)\n    - Mobile+ Assessment (Single Scan)\n    - Mobile Assessment (Subscription)\n    - Mobile+ Assessment (Subscription)\n- framework_type: ' '\n  opts:\n    is required: true\n    is_expand: true\n    summary: Framework type for this mobile assessment\n    title: Framework Type\n    value_options:\n    - Android\n    - iOS\n- opts:\n    is required: true\n    is_expand: true\n    summary: Platform type for this mobile assessment\n    title: Platform Type\n    value_options:\n    - Phone\n    - Tablet\n    - Both\n  platform_type: ' '\n- file_path: null\n  opts:\n    is required: true\n    is_expand: true\n    title: Path to apk/ipa\n"
  },
  {
    "path": "steps/fortify-on-demand-mobile-assessment/0.0.2/step.yml",
    "content": "title: Fortify on Demand Mobile Assessment\nsummary: |\n  Submits a Fortify on Demand Mobile Assessment\ndescription: |\n  Fortify on Demand delivers comprehensive end-to-end mobile security with real-world mobile application security testing across all three tiers of the mobile ecosystem—client device, network, and web services. Similar to dynamic testing for web applications, mobile assessments utilize the compiled application binary and employ the same techniques hackers utilize to exploit vulnerabilities in mobile applications, whether they are developed internally, outsourced, or acquired. More than just simple reputation or behavioral analysis, Fortify on Demand mobile assessments provide true security testing for companies serious about securing their mobile applications.\n\n  For more information, please refer to the datasheet at https://www.microfocus.com/media/data-sheet/fortify_on_demand_ds.pdf\nwebsite: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nsource_code_url: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nsupport_url: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment/issues\npublished_at: 2021-10-13T19:46:55.531363266+08:00\nsource:\n  git: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment.git\n  commit: 32326a0a4d62942e3eff4d22712efa49cb923d0f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- client_id: null\n  opts:\n    description: Authenticating with Client Credentials. The client credentials are\n      the API keys generated in the portal.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client ID for authentication\n    title: Client ID\n- client_secret: null\n  opts:\n    description: Authenticating with Client Credentials. The client credentials are\n      the API keys generated in the portal.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client secret for authentication\n    title: Client Secret\n- datacenter: ' '\n  opts:\n    description: Select the datacenter assigned to you. This is provided once your\n      are onboarded with Fortify on Demand.\n    is required: true\n    is_expand: true\n    summary: Fortify on Demand Datacenters\n    title: Datacenter\n    value_options:\n    - AMS\n    - APAC\n    - EMEA\n    - FED\n- entitlement_id: null\n  opts:\n    description: The ID assigned to ypur current entitlement. This value can be reterived\n      in Foritfy on Demand portal.\n    is_expand: true\n    is_required: true\n    summary: Entitlement ID for this mobile assessment\n    title: Entitlement ID\n- opts:\n    description: The ID assigned to the created release. This value can be reterived\n      in Foritfy on Demand portal.\n    is_expand: true\n    is_required: true\n    summary: Release ID for this mobile assessment\n    title: Release ID\n  release_id: null\n- assessment_type: ' '\n  opts:\n    description: \"Mobile Assessment includes Vulnerability analysis of mobile binary,\n      Endpoint reputation analysis and Security expert review of prioritized results.\n      \\nMobile+ Assessment includes Manual testing of binary, network and services,\n      and DAST of backend services\\nFor more information, please refer to the datasheet\n      at https://www.microfocus.com/media/data-sheet/fortify_on_demand_ds.pdf\\n\"\n    is required: true\n    is_expand: true\n    summary: Assessment type for this mobile assessment\n    title: Assessment Type\n    value_options:\n    - Mobile Assessment (Single Scan)\n    - Mobile+ Assessment (Single Scan)\n    - Mobile Assessment (Subscription)\n    - Mobile+ Assessment (Subscription)\n- framework_type: ' '\n  opts:\n    is required: true\n    is_expand: true\n    summary: Framework type for this mobile assessment\n    title: Framework Type\n    value_options:\n    - Android\n    - iOS\n- opts:\n    is required: true\n    is_expand: true\n    summary: Platform type for this mobile assessment\n    title: Platform Type\n    value_options:\n    - Phone\n    - Tablet\n    - Both\n  platform_type: ' '\n- file_path: null\n  opts:\n    is required: true\n    is_expand: true\n    title: Path to apk/ipa\n"
  },
  {
    "path": "steps/fortify-on-demand-mobile-assessment/0.1.1/step.yml",
    "content": "title: Fortify on Demand Mobile Assessment\nsummary: |\n  Submits a Fortify on Demand Mobile Assessment\ndescription: |\n  Fortify on Demand delivers comprehensive end-to-end mobile security with real-world mobile application security testing across all three tiers of the mobile ecosystem—client device, network, and web services. Similar to dynamic testing for web applications, mobile assessments utilize the compiled application binary and employ the same techniques hackers utilize to exploit vulnerabilities in mobile applications, whether they are developed internally, outsourced, or acquired. More than just simple reputation or behavioral analysis, Fortify on Demand mobile assessments provide true security testing for companies serious about securing their mobile applications.\n\n  For more information, please refer to the datasheet at https://www.microfocus.com/media/data-sheet/fortify_on_demand_ds.pdf\nwebsite: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nsource_code_url: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nsupport_url: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment/issues\npublished_at: 2021-10-21T07:12:55.86652789+08:00\nsource:\n  git: https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment.git\n  commit: b8279e4ddc19300a0735efd26a32e5d803615dff\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- client_id: null\n  opts:\n    description: Authenticating with Client Credentials. The client credentials are\n      the API keys generated in the portal.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client ID for authentication\n    title: Client ID\n- client_secret: null\n  opts:\n    description: Authenticating with Client Credentials. The client credentials are\n      the API keys generated in the portal.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client secret for authentication\n    title: Client Secret\n- datacenter: AMS\n  opts:\n    description: Select the datacenter assigned to you. This is provided once your\n      are onboarded with Fortify on Demand.\n    is required: true\n    is_expand: true\n    summary: Fortify on Demand Datacenters\n    title: Datacenter\n    value_options:\n    - AMS\n    - APAC\n    - EMEA\n    - FED\n- entitlement_id: null\n  opts:\n    description: The ID assigned to ypur current entitlement. This value can be reterived\n      in Foritfy on Demand portal.\n    is_expand: true\n    is_required: true\n    summary: Entitlement ID for this mobile assessment\n    title: Entitlement ID\n- opts:\n    description: The ID assigned to the created release. This value can be reterived\n      in Foritfy on Demand portal.\n    is_expand: true\n    is_required: true\n    summary: Release ID for this mobile assessment\n    title: Release ID\n  release_id: null\n- assessment_type: Mobile Assessment (Single Scan)\n  opts:\n    description: \"Mobile Assessment includes Vulnerability analysis of mobile binary,\n      Endpoint reputation analysis and Security expert review of prioritized results.\n      \\nMobile+ Assessment includes Manual testing of binary, network and services,\n      and DAST of backend services\\nFor more information, please refer to the datasheet\n      at https://www.microfocus.com/media/data-sheet/fortify_on_demand_ds.pdf\\n\"\n    is required: true\n    is_expand: true\n    summary: Assessment type for this mobile assessment\n    title: Assessment Type\n    value_options:\n    - Mobile Assessment (Single Scan)\n    - Mobile+ Assessment (Single Scan)\n    - Mobile Assessment (Subscription)\n    - Mobile+ Assessment (Subscription)\n- framework_type: Android\n  opts:\n    is required: true\n    is_expand: true\n    summary: Framework type for this mobile assessment\n    title: Framework Type\n    value_options:\n    - Android\n    - iOS\n- opts:\n    is required: true\n    is_expand: true\n    summary: Platform type for this mobile assessment\n    title: Platform Type\n    value_options:\n    - Phone\n    - Tablet\n    - Both\n  platform_type: Phone\n- file_path: null\n  opts:\n    is required: true\n    is_expand: true\n    title: Path to apk/ipa\n"
  },
  {
    "path": "steps/fortify-on-demand-mobile-assessment/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/ftp-upload/2.0.0/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2015-09-08T15:48:13.613910987+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 63028ceca2146d215bdbbb81caf101b462d4be6f\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- ftp\n- uploader\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com)'\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n"
  },
  {
    "path": "steps/ftp-upload/2.0.1/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2016-04-15T14:38:46.838803289+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 1564c10a80d2b4544fcd6a9c8361e66ae1019d34\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- ftp\n- uploader\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com)'\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n"
  },
  {
    "path": "steps/ftp-upload/2.0.2/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-01-18T15:40:46.037618201+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 21685e24e1f6b860ac12fc612f9f8265b23d7334\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- ftp\n- uploader\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com)'\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n"
  },
  {
    "path": "steps/ftp-upload/2.0.3/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-01-26T15:15:10.569092395+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: d8b11b7a05b9a9fab9814f289b260d268861a87a\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- ftp\n- uploader\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com)'\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n"
  },
  {
    "path": "steps/ftp-upload/2.0.4/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-02-20T16:38:49.285204454+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: a88c2e90c6b17f2f8118a41e572e14e5b700f4d7\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com)'\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n"
  },
  {
    "path": "steps/ftp-upload/2.1.1/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-08-09T15:44:50.875175835+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 94aeb8ba3abc35ec408859a37c1a4f6cc7feb49e\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-ftp-upload\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com)'\n    is_required: true\n    summary: \"\"\n    title: Host\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n- debug_mode: \"false\"\n  opts:\n    description: |\n      The step will print more logs if this option is set to true.\n    is_required: true\n    summary: \"\"\n    title: Debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ftp-upload/2.1.2/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-08-10T09:41:48.200340717+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 84a112c405bc668122dd04ef07fb5da14e77e4ff\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-ftp-upload\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com:21)'\n    is_required: true\n    summary: \"\"\n    title: 'Host (example: ftp.someserver.com:21)'\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n- debug_mode: \"false\"\n  opts:\n    description: |\n      The step will print more logs if this option is set to true.\n    is_required: true\n    summary: \"\"\n    title: Debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ftp-upload/2.1.3/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-08-11T12:48:17.541936648+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 5fd1655f6fbb646fe2f3fdcd123a3060811b91cd\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-ftp-upload\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com:21)'\n    is_required: true\n    summary: \"\"\n    title: 'Host (example: ftp.someserver.com:21)'\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n- debug_mode: \"false\"\n  opts:\n    description: |\n      The step will print more logs if this option is set to true.\n    is_required: true\n    summary: \"\"\n    title: Debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ftp-upload/2.1.4/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2017-10-10T14:47:37.357163415+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 0a17164d734cbcf5cb1157b7badffa23febe955d\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-ftp-upload\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: 'Host of the target FTP (example: ftp.someserver.com:21)'\n    is_required: true\n    summary: \"\"\n    title: 'Host (example: ftp.someserver.com:21)'\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target / remote path\n  upload_target_path: \"\"\n- debug_mode: \"false\"\n  opts:\n    description: |\n      The step will print more logs if this option is set to true.\n    is_required: true\n    summary: \"\"\n    title: Debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ftp-upload/2.1.5/step.yml",
    "content": "title: FTP Upload\nsummary: You get what you see, upload a file or directory to the target directory\ndescription: Upload a single file or a folder (recursively) to an FTP server.\nwebsite: https://github.com/bitrise-io/steps-ftp-upload\nsource_code_url: https://github.com/bitrise-io/steps-ftp-upload\nsupport_url: https://github.com/bitrise-io/steps-ftp-upload/issues\npublished_at: 2018-08-31T09:19:48.077399621Z\nsource:\n  git: https://github.com/bitrise-io/steps-ftp-upload.git\n  commit: 3da1d341fdc3b77359d888fd31f239fde524a227\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-ftp-upload\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- hostname: \"\"\n  opts:\n    description: Host of the target FTP (for example, `ftp.someserver.com:21`)\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Host (for example, `ftp.someserver.com:21`)\n- opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Username\n  username: \"\"\n- opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Password\n  password: \"\"\n- opts:\n    description: |\n      The source (local) file or directory for the FTP upload.\n      Format examples: \"$HOME/temp\" or \"$HOME/temp/\")\n    is_required: true\n    summary: \"\"\n    title: Source path\n  upload_source_path: \"\"\n- opts:\n    description: |\n      The target (remote) path for the FTP upload.\n      Target is handled as directory if ends with \"/\", file otherwise.\n    is_required: true\n    summary: \"\"\n    title: Target/remote path\n  upload_target_path: \"\"\n- debug_mode: \"false\"\n  opts:\n    description: |\n      The step will print more logs if this option is set to true.\n    is_required: true\n    summary: \"\"\n    title: Debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ftp-upload/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/gcp-storage-upload/0.0.1/step.yml",
    "content": "title: Google Cloud Storage Upload\nsummary: The Step uploads files to a Google Cloud Storage bucket.\ndescription: |-\n  The Step uploads files to a Google Cloud Storage bucket.\n\n  It can handle both files and directories, uploading the contents to the specified GCS bucket with the desired access control settings.\n\n  Using the Authenticate with GCP Step beforehand is recommended to securely provide short lived GCP credentials.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-gcp-storage-upload\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-gcp-storage-upload\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-gcp-storage-upload/issues\npublished_at: 2025-11-19T08:29:08.166806+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-gcp-storage-upload.git\n  commit: 81e677b75697864707929c9412360a7a870fa97a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-gcp-storage-upload\ninputs:\n- opts:\n    description: |-\n      Path to a file or folder to be uploaded.\n\n      You can use absolute or relative paths.\n    is_required: true\n    summary: Path to a file or folder to be uploaded.\n    title: Path\n  path: null\n- bucket_name: null\n  opts:\n    description: Name of the GCS bucket to upload the file to.\n    is_required: true\n    summary: Name of the GCS bucket to upload the file to.\n    title: Bucket Name\n- bucket_prefix: null\n  opts:\n    description: |-\n      Path in the GCS bucket where the file will be uploaded.\n\n      If not provided, the file will be uploaded to the root of the bucket with its original filename.\n    is_required: false\n    summary: Path in the GCS bucket where the file will be uploaded.\n    title: Bucket Prefix\n- access_token: $GOOGLE_AUTH_TOKEN\n  opts:\n    category: GCP Credentials\n    description: |-\n      The GCP Access Token.\n\n      You can provide it directly or use the Authenticate with GCP Step.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The GCP Access Token.\n    title: GCP Access Token\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/gcp-storage-upload/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/geckoboard-dashboard-build-result/0.1.0/step.yml",
    "content": "title: Geckoboard dashboard build result\nsummary: |\n  Build result on Geckoboard dashboard\ndescription: |\n  Update a text widget on your Geckoboard dashboard with the latest build result\nwebsite: https://github.com/CsabaSzabo/bitrise-step-geckoboard-dashboard-build-result\nsource_code_url: https://github.com/CsabaSzabo/bitrise-step-geckoboard-dashboard-build-result\nsupport_url: https://github.com/CsabaSzabo/bitrise-step-geckoboard-dashboard-build-result/issues\npublished_at: 2018-11-19T10:24:13.211371062+01:00\nsource:\n  git: https://github.com/CsabaSzabo/bitrise-step-geckoboard-dashboard-build-result.git\n  commit: beba05273766c565ebfe7754f93dcd6372012b0c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- geckoboard_api_key: null\n  opts:\n    description: |\n      You can get the Geckoboard API key from your [account page](https://app.geckoboard.com/account/details)\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Geckoboard API key\n    title: Geckoboard API key\n    value_options: []\n- opts:\n    description: |\n      You can get the Geckoboard Custom Widget key from the widget's details page\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Geckoboard Widget key\n    title: Geckoboard Widget key\n    value_options: []\n  widget_key: null\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Bitrise build number\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Bitrise build number\n    title: Bitrise build number\n    value_options: []\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      Bitrise status\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Bitrise status\n    title: Bitrise status\n    value_options: []\n"
  },
  {
    "path": "steps/geckoboard-dashboard-build-result/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/generate-changelog/0.10.0/step.yml",
    "content": "title: Generate Changelog\nsummary: Generates changelog based on git commits\ndescription: |-\n  Generates changelog based on git commits.\n\n  The step collects commits since the latest tag, ignoring merge commits.\n\n  In the case of the first tag, the commits are from the first commit, till there is a new version.\n  In other cases, the first commit is the first commit after the previous tag.\nwebsite: https://github.com/bitrise-steplib/steps-generate-changelog\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-changelog\nsupport_url: https://github.com/bitrise-steplib/steps-generate-changelog/issues\npublished_at: 2021-10-07T13:06:53.592089922Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-changelog.git\n  commit: 628692576481d68f64d08ac9f64ec22a40b5dd3e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-changelog\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- new_version: $BITRISE_GIT_TAG\n  opts:\n    description: Next release version.\n    is_required: true\n    summary: Next release version\n    title: Next version\n- changelog_pth: $BITRISE_DEPLOY_DIR/CHANGELOG.md\n  opts:\n    description: Changelog path.\n    is_required: true\n    summary: Changelog path\n    title: Changelog path\n- opts:\n    description: The directory path where your git repository is initialized.\n    is_required: true\n    summary: The directory path where your git repository is initialized.\n    title: Working dir\n  working_dir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_CHANGELOG: null\n  opts:\n    summary: Bitrise changelog content\n    title: Bitrise changelog content\n"
  },
  {
    "path": "steps/generate-changelog/0.10.1/step.yml",
    "content": "title: Generate Changelog\nsummary: Generates changelog based on git commits\ndescription: |-\n  Generates changelog based on git commits.\n\n  The step collects commits since the latest tag, ignoring merge commits.\n\n  In the case of the first tag, the commits are from the first commit, till there is a new version.\n  In other cases, the first commit is the first commit after the previous tag.\nwebsite: https://github.com/bitrise-steplib/steps-generate-changelog\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-changelog\nsupport_url: https://github.com/bitrise-steplib/steps-generate-changelog/issues\npublished_at: 2022-08-31T13:34:22.688719218Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-changelog.git\n  commit: 78a7c027447237c043a182e308b349236a28f5bd\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-changelog\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- changelog_pth: $BITRISE_DEPLOY_DIR/CHANGELOG.md\n  opts:\n    description: Changelog path.\n    is_required: true\n    summary: Changelog path\n    title: Changelog path\n- opts:\n    description: The directory path where your git repository is initialized.\n    is_required: true\n    summary: The directory path where your git repository is initialized.\n    title: Working dir\n  working_dir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_CHANGELOG: null\n  opts:\n    summary: Bitrise changelog content\n    title: Bitrise changelog content\n"
  },
  {
    "path": "steps/generate-changelog/0.10.2/step.yml",
    "content": "title: Generate Changelog\nsummary: Generates changelog based on git commits\ndescription: |-\n  Generates changelog based on git commits.\n\n  The step collects commits since the latest tag, ignoring merge commits.\n\n  In the case of the first tag, the commits are from the first commit, till there is a new version.\n  In other cases, the first commit is the first commit after the previous tag.\nwebsite: https://github.com/bitrise-steplib/steps-generate-changelog\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-changelog\nsupport_url: https://github.com/bitrise-steplib/steps-generate-changelog/issues\npublished_at: 2024-04-10T13:42:37.64183552Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-changelog.git\n  commit: 84254ebad0137109d01cc080f608ca679b6ba578\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-changelog\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- changelog_pth: $BITRISE_DEPLOY_DIR/CHANGELOG.md\n  opts:\n    description: Changelog path.\n    is_required: true\n    summary: Changelog path\n    title: Changelog path\n- opts:\n    description: The directory path where your git repository is initialized.\n    is_required: true\n    summary: The directory path where your git repository is initialized.\n    title: Working dir\n  working_dir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_CHANGELOG: null\n  opts:\n    summary: Bitrise changelog content\n    title: Bitrise changelog content\n"
  },
  {
    "path": "steps/generate-changelog/0.9.0/step.yml",
    "content": "title: Generate Changelog\nsummary: Generates changelog based on git commits\ndescription: |-\n  Genereates changelog based on git commits.\n\n  The step collects commits since the latest tag.\n\n  In case of first tag, the commits are from the first commit till the new version.\n  In other cases the first commit is the first commit after the previous tag.\nwebsite: https://github.com/bitrise-steplib/steps-generate-changelog\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-changelog\nsupport_url: https://github.com/bitrise-steplib/steps-generate-changelog/issues\npublished_at: 2018-06-26T16:47:16.408281952+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-changelog.git\n  commit: 0659829b7f00d69b400b8017927b3fe4a1a364d2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-changelog\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- new_version: $BITRISE_GIT_TAG\n  opts:\n    description: Next release version.\n    is_required: true\n    summary: Next release version\n    title: Next version\n- changelog_pth: $BITRISE_DEPLOY_DIR/CHANGELOG.md\n  opts:\n    description: Changelog path.\n    is_required: true\n    summary: Changelog path\n    title: Changelog path\n- opts:\n    description: The directory path where your git repository is initialized.\n    is_required: true\n    summary: The directory path where your git repository is initialized.\n    title: Working dir\n  working_dir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_CHANGELOG: null\n  opts:\n    summary: Bitrise changelog content\n    title: Bitrise changelog content\n"
  },
  {
    "path": "steps/generate-changelog/0.9.1/step.yml",
    "content": "title: Generate Changelog\nsummary: Generates changelog based on git commits\ndescription: |-\n  Generates changelog based on git commits.\n\n  The step collects commits since the latest tag.\n\n  In the case of the first tag, the commits are from the first commit, till there is a new version.\n  In other cases, the first commit is the first commit after the previous tag.\nwebsite: https://github.com/bitrise-steplib/steps-generate-changelog\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-changelog\nsupport_url: https://github.com/bitrise-steplib/steps-generate-changelog/issues\npublished_at: 2020-08-25T10:50:44.127824133Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-changelog.git\n  commit: 262938c5fc3d057c538d53553a041e549e1a733a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-changelog\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- new_version: $BITRISE_GIT_TAG\n  opts:\n    description: Next release version.\n    is_required: true\n    summary: Next release version\n    title: Next version\n- changelog_pth: $BITRISE_DEPLOY_DIR/CHANGELOG.md\n  opts:\n    description: Changelog path.\n    is_required: true\n    summary: Changelog path\n    title: Changelog path\n- opts:\n    description: The directory path where your git repository is initialized.\n    is_required: true\n    summary: The directory path where your git repository is initialized.\n    title: Working dir\n  working_dir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_CHANGELOG: null\n  opts:\n    summary: Bitrise changelog content\n    title: Bitrise changelog content\n"
  },
  {
    "path": "steps/generate-changelog/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.0/step.yml",
    "content": "title: Generate cordova build configuration\nsummary: Generate cordova build configuration (build.json) file\ndescription: \"Generate cordova build configuration (build.json) file,  \\nto specify\n  cordova signing parameters.\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2017-04-27T16:05:45.391739733+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-generate-cordova-build-configuration.git\n  commit: 49a4c2b464662b574206a33209d65dfeb9a8d073\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    title: build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing.\n    title: The development team (Team ID)\n- code_sign_identity: null\n  opts:\n    description: Code signing identity to use for signing.\n    title: Code signing identity\n- opts:\n    description: GUID of the provisioning profile to be used for signing.\n    title: GUID of the provisioning profile\n  provisioning_profile: null\n- opts:\n    description: This will determine what type of build is generated by Xcode.\n    title: Package type\n    value_options:\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: development\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    summary: \"\"\n    title: Code signing rules\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration file.\n    title: The development team (Team ID)\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.2/step.yml",
    "content": "title: Generate cordova build configuration\nsummary: Generate cordova build configuration (build.json) file\ndescription: \"Generate cordova build configuration (build.json) file,  \\nto specify\n  cordova signing parameters.\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2017-04-28T15:17:15.98800417+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-generate-cordova-build-configuration.git\n  commit: 5db10d1fbecb7a7291bc9d4985f2d6b5fccb5f91\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    title: build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing.\n    title: The development team (Team ID)\n- code_sign_identity: null\n  opts:\n    description: Code signing identity to use for signing.\n    title: Code signing identity\n- opts:\n    description: GUID of the provisioning profile to be used for signing.\n    title: GUID of the provisioning profile\n  provisioning_profile: null\n- opts:\n    description: |-\n      This will determine what type of build is generated by Xcode.\n\n      Value `none` means: do not specify any iOS Code Singing.\n    title: Package type\n    value_options:\n    - none\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: none\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    summary: \"\"\n    title: Code signing rules\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration file.\n    title: The development team (Team ID)\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.3/step.yml",
    "content": "title: Generate cordova build configuration\nsummary: Generate cordova build configuration (build.json) file\ndescription: \"Generate cordova build configuration (build.json) file,  \\nto specify\n  cordova signing parameters.\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2017-06-13T16:22:15.382112+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-generate-cordova-build-configuration.git\n  commit: 047eb7987d21aa9ddc4b4e6de3d8618197c7a50a\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    title: Build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing.\n    title: Development Team\n- code_sign_identity: null\n  opts:\n    description: Code sign Identity to use for signing.\n    title: Code Sign Identity\n- opts:\n    description: GUID of the provisioning profile to be used for signing.\n    title: Provisioning Profile\n  provisioning_profile: null\n- opts:\n    description: |-\n      This input will control what type of build is generated by Xcode.\n\n      Value `none` means: do not specify any iOS Code Singing.\n    title: Packaging Type\n    value_options:\n    - none\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: none\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      Path to a binary file which can hold a set of keys.\n\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    title: Keystore\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Password to the keystore.\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: The id specifying the private key used for signing.\n    title: Alias\n- opts:\n    description: |\n      Password for the private key specified.\n    title: Password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration's path.\n    title: The generated build configuration's path\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.5/step.yml",
    "content": "title: Generate cordova build configuration\nsummary: Generate cordova build configuration (build.json) file\ndescription: \"Generate cordova build configuration (`build.json`) file,  \\nto specify\n  cordova [ios](http://cordova.apache.org/docs/en/8.x/guide/platforms/ios/index.html#using-buildjson)\n  and [android](http://cordova.apache.org/docs/en/8.x/guide/platforms/android/index.html#using-buildjson)\n  signing parameters.\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2018-05-25T11:55:21.151379118+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-generate-cordova-build-configuration.git\n  commit: a4d8d620955bd4f6fee29ba164703b299cbcfe97\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    summary: Specify build configuration\n    title: Build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing, __example:__\n      `1MZX23ABCD4`\n    summary: The development team (Team ID) to use for code signing, __example:__\n      `1MZX23ABCD4`\n    title: Development Team\n- code_sign_identity: null\n  opts:\n    description: \"Code Signing Identity to use for signing.\\n\\nSpecify Code Signing\n      Identity as full ID ( __example:__ `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      \\ \\nor specify code sign group ( __example:__ `iPhone Developer` or `iPhone\n      Distribution` ).\"\n    summary: Code Signing Identity to use for signing\n    title: Code Signing Identity\n- automatic_provisioning: \"no\"\n  opts:\n    description: \"Enable to allow Xcode to automatically manage provisioning profiles.\\n\\nIf\n      this input is set to: `yes` the `Provisioning Profile` input will be omitted,\n      \\ \\notherwise `Provisioning Profile` is required for iOS code signing.\"\n    summary: Enable to allow Xcode to automatically manage provisioning profiles\n    title: Enable to allow Xcode to automatically manage provisioning profiles\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: \"Provisioning Profile to be used for signing.\\n\\nUse Provisioning\n      Profile's UUID ( __example:__ `c5be4123-1234-4f9d-9843-0d9be985a068` )  \\nor\n      specify Profile's name ( __example:__ `Bitrise development - (com.bitrise.cordovasample)`\n      ).\"\n    summary: Provisioning Profile to be used for signing\n    title: Provisioning Profile\n  provisioning_profile: null\n- opts:\n    description: This input will control what type of build is generated by Xcode.\n    summary: This input will control what type of build is generated by Xcode\n    title: Packaging Type\n    value_options:\n    - none\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: none\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"Path to a binary file which can hold a set of keys.\\n\\nFor __remote\n      keystores__ you can provide any download location, example: `https://URL/TO/keystore.jks`.\n      \\ \\nFor __local keystores__ provide file path, example: `file://PATH/TO/keystore.jks`.\"\n    summary: Path to a binary file which can hold a set of keys\n    title: Keystore\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Password to the keystore.\n    summary: Password to the keystore\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: The id specifying the private key used for signing.\n    summary: The id specifying the private key used for signing\n    title: Alias\n- opts:\n    description: Password for the private key specified.\n    summary: Password for the private key specified\n    title: Password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration's path.\n    title: The generated build configuration's path\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.6/step.yml",
    "content": "title: Generate cordova build configuration\nsummary: Generate cordova build configuration (build.json) file\ndescription: \"Generate cordova build configuration (`build.json`) file,  \\nto specify\n  cordova [ios](http://cordova.apache.org/docs/en/8.x/guide/platforms/ios/index.html#using-buildjson)\n  and [android](http://cordova.apache.org/docs/en/8.x/guide/platforms/android/index.html#using-buildjson)\n  signing parameters.\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2018-08-22T14:49:23.088845204Z\nsource:\n  git: https://github.com/bitrise-community/steps-generate-cordova-build-configuration.git\n  commit: 1817196b0c8cd661f4a08a1eb55e62113fda38b2\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    summary: Specify build configuration\n    title: Build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing, __example:__\n      `1MZX23ABCD4`\n    summary: The development team (Team ID) to use for code signing, __example:__\n      `1MZX23ABCD4`\n    title: Development Team\n- code_sign_identity: null\n  opts:\n    description: \"Code Signing Identity to use for signing.\\n\\nSpecify Code Signing\n      Identity as full ID ( __example:__ `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      \\ \\nor specify code sign group ( __example:__ `iPhone Developer` or `iPhone\n      Distribution` ).\"\n    summary: Code Signing Identity to use for signing\n    title: Code Signing Identity\n- automatic_provisioning: \"no\"\n  opts:\n    description: \"Enable to allow Xcode to automatically manage provisioning profiles.\\n\\nIf\n      this input is set to: `yes` the `Provisioning Profile` input will be omitted,\n      \\ \\notherwise `Provisioning Profile` is required for iOS code signing.\"\n    summary: Enable to allow Xcode to automatically manage provisioning profiles\n    title: Enable to allow Xcode to automatically manage provisioning profiles\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: \"Provisioning Profile to be used for signing.\\n\\nUse Provisioning\n      Profile's UUID ( __example:__ `c5be4123-1234-4f9d-9843-0d9be985a068` )  \\nor\n      specify Profile's name ( __example:__ `Bitrise development - (com.bitrise.cordovasample)`\n      ).\"\n    summary: Provisioning Profile to be used for signing\n    title: Provisioning Profile\n  provisioning_profile: null\n- opts:\n    description: This input will control what type of build is generated by Xcode.\n    summary: This input will control what type of build is generated by Xcode\n    title: Packaging Type\n    value_options:\n    - none\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: none\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"Path to a binary file which can hold a set of keys.\\n\\nFor __remote\n      keystores__ you can provide any download location, example: `https://URL/TO/keystore.jks`.\n      \\ \\nFor __local keystores__ provide file path, example: `file://PATH/TO/keystore.jks`.\"\n    summary: Path to a binary file which can hold a set of keys\n    title: Keystore\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Password to the keystore.\n    is_sensitive: true\n    summary: Password to the keystore\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: The id specifying the private key used for signing.\n    is_sensitive: true\n    summary: The id specifying the private key used for signing\n    title: Alias\n- opts:\n    description: Password for the private key specified.\n    is_sensitive: true\n    summary: Password for the private key specified\n    title: Password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration's path.\n    title: The generated build configuration's path\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.7/step.yml",
    "content": "title: Generate cordova build configuration\nsummary: Generate cordova build configuration (build.json) file\ndescription: \"Generate cordova build configuration (`build.json`) file,  \\nto specify\n  cordova [ios](http://cordova.apache.org/docs/en/8.x/guide/platforms/ios/index.html#using-buildjson)\n  and [android](http://cordova.apache.org/docs/en/8.x/guide/platforms/android/index.html#using-buildjson)\n  signing parameters.\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2020-12-11T08:56:55.265891763Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-cordova-build-configuration.git\n  commit: 910549899f14d485b508c7a4fa88abec6f02da4f\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    summary: Specify build configuration\n    title: Build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing, __for example__\n      `1MZX23ABCD4`\n    summary: The development team (Team ID) to use for code signing, __for example__\n      `1MZX23ABCD4`\n    title: Development Team\n- code_sign_identity: null\n  opts:\n    description: \"Code Signing Identity to use for signing.\\n\\nSpecify Code Signing\n      Identity as full ID ( __for example__ `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      \\ \\nor specify code sign group ( __for example__ `iPhone Developer` or `iPhone\n      Distribution` ).\"\n    summary: Code Signing Identity to use for signing\n    title: Code Signing Identity\n- automatic_provisioning: \"no\"\n  opts:\n    description: \"Enable to allow Xcode to automatically manage provisioning profiles.\\n\\nIf\n      this input is set to `yes`, the `Provisioning Profile` input will be omitted,\n      \\ \\notherwise `Provisioning Profile` is required for iOS code signing.\"\n    summary: Enable to allow Xcode to automatically manage provisioning profiles\n    title: Enable to allow Xcode to automatically manage provisioning profiles\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: \"Provisioning Profile to be used for signing.\\n\\nUse Provisioning\n      Profile's UUID ( __for example__ `c5be4123-1234-4f9d-9843-0d9be985a068` )  \\nor\n      specify Profile's name ( __for example__ `Bitrise development - (com.bitrise.cordovasample)`\n      ).\"\n    summary: Provisioning Profile to be used for signing\n    title: Provisioning Profile\n  provisioning_profile: null\n- opts:\n    description: This input will control what type of build is generated by Xcode.\n    summary: This input will control what type of build is generated by Xcode\n    title: Packaging Type\n    value_options:\n    - none\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: none\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"Path to a binary file which can hold a set of keys.\\n\\nFor __remote\n      keystores__ you can provide any download location, for example, `https://URL/TO/keystore.jks`.\n      \\ \\nFor __local keystores__ provide file path, for example, `file://PATH/TO/keystore.jks`.\"\n    summary: Path to a binary file which can hold a set of keys\n    title: Keystore\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Password to the keystore.\n    is_sensitive: true\n    summary: Password to the keystore\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: The id specifying the private key used for signing.\n    is_sensitive: true\n    summary: The id specifying the private key used for signing\n    title: Alias\n- opts:\n    description: Password for the private key specified.\n    is_sensitive: true\n    summary: Password for the private key specified\n    title: Password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration's path.\n    title: The generated build configuration's path\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/0.9.8/step.yml",
    "content": "title: Generate Cordova build configuration\nsummary: Generate a `build.json` file specifying code signing parameters for the **Cordova\n  Archive** Step.\ndescription: \"\\\"To sign a Cordova app, you need a `build.json` file with the appropriate\n  code signing settings. This Step creates that file based on your inputs, and passes\n  it on to the **Cordova Archive** or **Ionic Archive** Step that builds your app.\n  The Step takes code signing settings for both [iOS](http://cordova.apache.org/docs/en/8.x/guide/platforms/ios/index.html#using-buildjson)\n  and [Android](http://cordova.apache.org/docs/en/8.x/guide/platforms/android/index.html#using-buildjson)\n  projects.\\n\\n### Configuring the Step\\n\\nBefore you start, make sure you have either\n  the **Certificate and profile installer** Step or the **iOS Auto Provisioning Step**\n  in your Workflow. Either one is required for [code signing iOS apps](https://devcenter.bitrise.io/code-signing/ios-code-signing/ionic-cordova-code-signing/).\n  \\n\\nYou also need to upload the appropriate iOS code signing files (certificate\n  and provisioning profile), and an [Android keystore file](https://developer.android.com/studio/publish/app-signing#generate-key).\n  \\n\\n1. Set the build configuration type in the **Build configuration** input.\\n\n  \\  The input value must be the same as the value of the **Build command configuration**\n  input of the **Cordova Archive** Step.\\n2. Configure the Step for iOS apps with\n  the following inputs: \\n   - **Code Sign Identity**: enter a Developer or a Distribution\n  identity.\\n   - **Provisioning Profile**: enter the appropriate Provisioning Profile.\\n\n  \\  - **Packaging Type**: this controls what type of build is generated by Xcode.\n  Make sure it matches the type of code signing files you want to use for the build.\n  \\n3. Configure the Step for Android apps with the following inputs: \\n   - **Keystore\n  password**\\n   - **Alias**\\n   - **Private key password**\\n   \\nIf all goes well,\n  the Step should export the `$BITRISE_CORDOVA_BUILD_CONFIGURATION` Environment Variable\n  that is used by the **Cordova Archive** Step. \\n\\n### Useful links\\n\\n- [Getting\n  started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n-\n  [Code signing with Ionic and Cordova apps](https://devcenter.bitrise.io/code-signing/ios-code-signing/ionic-cordova-code-signing/)\\n-\n  [Android code signing](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n\\n###\n  Related Steps \\n\\n- [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\\n-\n  [Cordova prepare](https://www.bitrise.io/integrations/steps/cordova-prepare)\\n-\n  [Manipulate Cordova config.xml](https://www.bitrise.io/integrations/steps/cordova-config)\\\"\"\nwebsite: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsource_code_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration\nsupport_url: https://github.com/bitrise-community/steps-generate-cordova-build-configuration/issues\npublished_at: 2020-12-11T09:44:17.748658243Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-cordova-build-configuration.git\n  commit: c8d43808d32000a92d5956950f25b16c6b620561\nproject_type_tags:\n- cordova\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-generate-cordova-build-configuration\ndeps:\n  brew:\n  - name: go\ninputs:\n- configuration: debug\n  opts:\n    description: Specify build configuration.\n    is_required: true\n    summary: Specify build configuration\n    title: Build configuration\n    value_options:\n    - release\n    - debug\n- development_team: null\n  opts:\n    description: The development team (Team ID) to use for code signing, __for example__\n      `1MZX23ABCD4`\n    summary: The development team (Team ID) to use for code signing, __for example__\n      `1MZX23ABCD4`\n    title: Development Team\n- code_sign_identity: null\n  opts:\n    description: \"Code Signing Identity to use for signing.\\n\\nSpecify Code Signing\n      Identity as full ID ( __for example__ `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      \\ \\nor specify code sign group ( __for example__ `iPhone Developer` or `iPhone\n      Distribution` ).\"\n    summary: Code Signing Identity to use for signing\n    title: Code Signing Identity\n- automatic_provisioning: \"no\"\n  opts:\n    description: \"Enable to allow Xcode to automatically manage provisioning profiles.\\n\\nIf\n      this input is set to `yes`, the `Provisioning Profile` input will be omitted,\n      \\ \\notherwise `Provisioning Profile` is required for iOS code signing.\"\n    summary: Enable to allow Xcode to automatically manage provisioning profiles\n    title: Enable to allow Xcode to automatically manage provisioning profiles\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: \"Provisioning Profile to be used for signing.\\n\\nUse Provisioning\n      Profile's UUID ( __for example__ `c5be4123-1234-4f9d-9843-0d9be985a068` )  \\nor\n      specify Profile's name ( __for example__ `Bitrise development - (com.bitrise.cordovasample)`\n      ).\"\n    summary: Provisioning Profile to be used for signing\n    title: Provisioning Profile\n  provisioning_profile: null\n- opts:\n    description: This input will control what type of build is generated by Xcode.\n    summary: This input will control what type of build is generated by Xcode\n    title: Packaging Type\n    value_options:\n    - none\n    - development\n    - enterprise\n    - ad-hoc\n    - app-store\n  package_type: none\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: \"Path to a binary file which can hold a set of keys.\\n\\nFor __remote\n      keystores__ you can provide any download location, for example, `https://URL/TO/keystore.jks`.\n      \\ \\nFor __local keystores__ provide file path, for example, `file://PATH/TO/keystore.jks`.\"\n    summary: Path to a binary file which can hold a set of keys\n    title: Keystore\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Password to the keystore.\n    is_sensitive: true\n    summary: Password to the keystore\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: The id specifying the private key used for signing.\n    is_sensitive: true\n    summary: The id specifying the private key used for signing\n    title: Alias\n- opts:\n    description: Password for the private key specified.\n    is_sensitive: true\n    summary: Password for the private key specified\n    title: Password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_CORDOVA_BUILD_CONFIGURATION: null\n  opts:\n    description: The generated build configuration's path.\n    title: The generated build configuration's path\n"
  },
  {
    "path": "steps/generate-cordova-build-configuration/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/generate-gradle-wrapper/0.10.0/step.yml",
    "content": "title: Generate Gradle Wrapper\nsummary: Generates Gradle Wraper if not exists\ndescription: |-\n  Generates Gradle Wraper if not exists.\n\n  The gradlew file will be generated into the same directory where your root build.gradle file exists.\nwebsite: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper\nsupport_url: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper/issues\npublished_at: 2021-01-07T15:41:02.953673874Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper.git\n  commit: 739e11164e1846504b618c5d9146f6a440c9f7d0\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-gradle-wrapper\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Root directory of the project.\n    is_required: true\n    summary: \"\"\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- gradle_version: 6.1.1\n  opts:\n    is_required: true\n    summary: Gradle version to use to generate the wrapper.\n    title: Gradle version to use to generate the wrapper.\noutputs:\n- GRADLEW_PATH: null\n  opts:\n    summary: The generated Gradle Wrapper file path.\n    title: Gradle Wrapper file path\n"
  },
  {
    "path": "steps/generate-gradle-wrapper/0.10.1/step.yml",
    "content": "title: Generate Gradle Wrapper\nsummary: Generates Gradle Wrapper if it doesn't already exist\ndescription: |-\n  Generates Gradle Wrapper if it doesn't already exist.\n\n  The gradlew file will be generated into the same directory where your root build.gradle file exists.\nwebsite: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper\nsupport_url: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper/issues\npublished_at: 2021-01-08T07:15:31.773406602Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper.git\n  commit: 64da1a715f064af090a5de8bfc83d65da9f8a41b\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-gradle-wrapper\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Root directory of the project.\n    is_required: true\n    summary: \"\"\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- gradle_version: 6.1.1\n  opts:\n    is_required: true\n    summary: Gradle version to use to generate the wrapper.\n    title: Gradle version to use to generate the wrapper.\noutputs:\n- GRADLEW_PATH: null\n  opts:\n    summary: The generated Gradle Wrapper file path.\n    title: Gradle Wrapper file path\n"
  },
  {
    "path": "steps/generate-gradle-wrapper/0.9.2/step.yml",
    "content": "title: Generate Gradle Wrapper\nsummary: Generates Gradle Wraper if not exists\ndescription: |-\n  Generates Gradle Wraper if not exists.\n\n  The gradlew file will be generated into the same directory where your root build.gradle file exists.\nwebsite: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper\nsource_code_url: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper\nsupport_url: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper/issues\npublished_at: 2017-04-12T16:18:20.216890848+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-generate-gradle-wrapper.git\n  commit: 85815edc33fa2765ad3963c8a74f08df4a75d536\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generate-gradle-wrapper\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Root directory of the project.\n    is_required: true\n    summary: \"\"\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- gradle_version: 2.14.1\n  opts:\n    is_required: true\n    summary: Gradle version to use to generate the wrapper.\n    title: Gradle version to use to generate the wrapper.\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\noutputs:\n- GRADLEW_PATH: null\n  opts:\n    summary: The generated Gradle Wrapper file path.\n    title: Gradle Wrapper file path\n"
  },
  {
    "path": "steps/generate-gradle-wrapper/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/generate-image-difference/0.0.2/step.yml",
    "content": "title: generate-image-difference\nsummary: |\n  Generate a difference image from two images.\ndescription: |\n  Generate a difference image from two images. Images can be specified by file or directory. Useful for checking UI etc.\nwebsite: https://github.com/kvvzr/bitrise-step-generate-image-difference\nsource_code_url: https://github.com/kvvzr/bitrise-step-generate-image-difference\nsupport_url: https://github.com/kvvzr/bitrise-step-generate-image-difference/issues\npublished_at: 2019-08-21T15:55:11.961935+09:00\nsource:\n  git: https://github.com/kvvzr/bitrise-step-generate-image-difference.git\n  commit: b5711e3f4886bbef227a53a014196c73ddeca1e6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/kvvzr/bitrise-step-generate-image-difference\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- before_images: null\n  opts:\n    description: |\n      Input the file path of the image you want to compare.\n      `Before images path` and `After images path` must both be directories or files.\n    is_required: true\n    summary: The file name or directory of before images.\n    title: Before images path\n- after_images: null\n  opts:\n    description: |\n      Input the file path of the image you want to compare.\n      `Before images path` and `After images path` must both be directories or files.\n    is_required: true\n    summary: The file name or directory of after images.\n    title: After images path\noutputs:\n- GENERATED_DIFF_IMAGES_DIR: null\n  opts:\n    description: |\n      Directory of generated difference images. Note that no image is generated if `before image` and `after image` are the same.\n    summary: Directory of generated difference images.\n    title: Directory of generated difference images\n"
  },
  {
    "path": "steps/generate-image-difference/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/generate-text-file/0.0.2/step.yml",
    "content": "title: Generate Text File\nsummary: Dynamically generate a text file\ndescription: |-\n  This step lets you generate a dynamic text file which can use any environment\n  variables. The path of the file will be made available as\n  `$GENERATED_TEXT_FILE_PATH`. This script can e.g. be used to generate the Play\n  Store's \"What's New\" file based on the Git commit message.\nwebsite: https://github.com/nicolas-fricke/bitrise-step-generate-text-file\nsource_code_url: https://github.com/nicolas-fricke/bitrise-step-generate-text-file\nsupport_url: https://github.com/nicolas-fricke/bitrise-step-generate-text-file/issues\npublished_at: 2017-02-10T17:46:02.07475167+01:00\nsource:\n  git: https://github.com/nicolas-fricke/bitrise-step-generate-text-file.git\n  commit: ab3b6500401b4a5bbe06c3b9aa6336d9cd13f702\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- file\n- utils\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_name: generated_text_file.txt\n  opts:\n    is_required: true\n    title: File Name\n- file_content: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Add content for the text file here. You can also use all ENV variables.\n    title: Content of the text file\noutputs:\n- GENERATED_TEXT_FILE_PATH: null\n  opts:\n    title: Path to the generated text file\n"
  },
  {
    "path": "steps/generate-text-file/0.0.3/step.yml",
    "content": "title: Generate Text File\nsummary: Dynamically generate a text file\ndescription: |-\n  This step lets you generate a dynamic text file which can use any environment\n  variables. The path of the file will be made available as\n  `$GENERATED_TEXT_FILE_PATH`. This script can e.g. be used to generate the Play\n  Store's \"What's New\" file based on the Git commit message.\nwebsite: https://github.com/nicolas-fricke/bitrise-step-generate-text-file\nsource_code_url: https://github.com/nicolas-fricke/bitrise-step-generate-text-file\nsupport_url: https://github.com/nicolas-fricke/bitrise-step-generate-text-file/issues\npublished_at: 2017-02-24T11:56:00.861387565Z\nsource:\n  git: https://github.com/nicolas-fricke/bitrise-step-generate-text-file.git\n  commit: fa648ac4542f1465728d97a41d40f97704506cde\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_name: generated_text_file.txt\n  opts:\n    is_required: true\n    title: File Name\n- file_content: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Add content for the text file here. You can also use all ENV variables.\n    title: Content of the text file\noutputs:\n- GENERATED_TEXT_FILE_PATH: null\n  opts:\n    title: Path to the generated text file\n"
  },
  {
    "path": "steps/generate-text-file/0.1.0/step.yml",
    "content": "title: Generate Text File\nsummary: |\n  Dynamically generate a text file\ndescription: |\n  This step lets you generate a dynamic text file which can use any environment\n  variables. The path of the file will be made available as\n  `$GENERATED_TEXT_FILE_PATH`. This script can e.g. be used to generate the Play\n  Store's \"What's New\" file based on the Git commit message.\nwebsite: https://github.com/bitrise-community/bitrise-step-generate-text-file\nsource_code_url: https://github.com/bitrise-community/bitrise-step-generate-text-file\nsupport_url: https://github.com/bitrise-community/bitrise-step-generate-text-file/issues\npublished_at: 2019-03-28T11:25:52.233677+01:00\nsource:\n  git: https://github.com/bitrise-community/bitrise-step-generate-text-file.git\n  commit: 64bff0968fb44bf265e40764fa2dfa966cc4bbfd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/bitrise-step-generate-text-file\ndeps: {}\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_name: generated_text_file.txt\n  opts:\n    is_required: true\n    title: File Name\n- file_content: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Add content for the text file here. You can also use all ENV variables.\n    title: Content of the text file\noutputs:\n- GENERATED_TEXT_FILE_PATH: null\n  opts:\n    title: Path to the generated text file\n"
  },
  {
    "path": "steps/generate-text-file/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/generate-xcode-html-report/1.0.0/step.yml",
    "content": "title: Generate Xcode test report html\nsummary: The Step converts xcresult summaries to html reports.\ndescription: |-\n  This step will generate html report summaries from your xcresult files. It will also include all of the attachments from your tests.\n\n  The step works seamlessly with the official Xcode testing steps. If you use those then you do not need to configure this step in any way because it will automatically discover all of the generated xcresult files.\n\n  If you use Fastlane or have script step for your building process then you need to tell this step where to find your xcresult files.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report/issues\npublished_at: 2023-10-31T14:32:15.005855Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report.git\n  commit: 357c77980b34089fd3220103acc66cb6e71174e4\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is directory where the official Xcode testing steps save their output\n    title: Bitrise test result directory\n  test_result_dir: $BITRISE_TEST_DEPLOY_DIR\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of all of the xcresult files\n\n      You do not need to specify the xcresult if your are using the official Xcode test steps. This is only needed if you use Fastlane or script based setup.\n\n      This input supports glob patterns. This means you can use exact paths or wildcards. Here are a few examples:\n      ```\n      /path/to/MyApp.xcresult\n      /path/to/output/folder/*.xcresult\n      /path/to/parent/folder/**/*.xcresult\n      ```\n\n      The only requirements are that every pattern must only find xcresult files and they have to be absolute paths.\n    is_required: false\n    summary: A newline (`\\n`) separated list of all of the xcresult files\n    title: Xcresult file paths\n  xcresult_patterns: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_HTML_REPORT_DIR: null\n  opts:\n    summary: This folder contains the generated html test reports and their assets.\n    title: Html test report location\n"
  },
  {
    "path": "steps/generate-xcode-html-report/1.0.1/step.yml",
    "content": "title: Generate Xcode test report html\nsummary: The Step converts xcresult summaries to html reports.\ndescription: |-\n  This step will generate html report summaries from your xcresult files. It will also include all of the attachments from your tests.\n\n  The step works seamlessly with the official Xcode testing steps. If you use those then you do not need to configure this step in any way because it will automatically discover all of the generated xcresult files.\n\n  If you use Fastlane or have script step for your building process then you need to tell this step where to find your xcresult files.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report/issues\npublished_at: 2023-11-01T09:11:31.761043014Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report.git\n  commit: 96b339f4611fabe43ca8dcb5b5ceb0b472d78e8d\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of all of the xcresult files\n\n      You do not need to specify the xcresult if your are using the official Xcode test steps. This is only needed if you use Fastlane or script based setup.\n\n      This input supports glob patterns. This means you can use exact paths or wildcards. Here are a few examples:\n      ```\n      /path/to/MyApp.xcresult\n      /path/to/output/folder/*.xcresult\n      /path/to/parent/folder/**/*.xcresult\n      ```\n\n      The only requirements are that every pattern must only find xcresult files and they have to be absolute paths.\n    is_required: false\n    summary: A newline (`\\n`) separated list of all of the xcresult files\n    title: Xcresult file paths\n  xcresult_patterns: null\n- opts:\n    category: Debugging\n    is_dont_change_value: true\n    is_required: true\n    summary: This is directory where the official Xcode testing steps save their output\n    title: Bitrise test result directory\n  test_result_dir: $BITRISE_TEST_DEPLOY_DIR\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_HTML_REPORT_DIR: null\n  opts:\n    summary: This folder contains the generated html test reports and their assets.\n    title: Html test report location\n"
  },
  {
    "path": "steps/generate-xcode-html-report/1.0.2/step.yml",
    "content": "title: Generate Xcode test report html\nsummary: The Step converts xcresult summaries to html reports.\ndescription: |-\n  This step will generate html report summaries from your xcresult files. It will also include all of the attachments from your tests.\n\n  The step works seamlessly with the official Xcode testing steps. If you use those then you do not need to configure this step in any way because it will automatically discover all of the generated xcresult files.\n\n  If you use Fastlane or have script step for your building process then you need to tell this step where to find your xcresult files.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report/issues\npublished_at: 2023-11-07T13:17:36.986844738Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report.git\n  commit: 83309b29f4abdbfd05d224ddd0a49bec48ebbb9e\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nis_always_run: true\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of all of the xcresult files\n\n      You do not need to specify the xcresult if your are using the official Xcode test steps. This is only needed if you use Fastlane or script based setup.\n\n      This input supports glob patterns. This means you can use exact paths or wildcards. Here are a few examples:\n      ```\n      /path/to/MyApp.xcresult\n      /path/to/output/folder/*.xcresult\n      /path/to/parent/folder/**/*.xcresult\n      ```\n\n      The only requirements are that every pattern must only find xcresult files and they have to be absolute paths.\n    is_required: false\n    summary: A newline (`\\n`) separated list of all of the xcresult files\n    title: Xcresult file paths\n  xcresult_patterns: null\n- opts:\n    category: Debugging\n    is_dont_change_value: true\n    is_required: true\n    summary: This is directory where the official Xcode testing steps save their output\n    title: Bitrise test result directory\n  test_result_dir: $BITRISE_TEST_DEPLOY_DIR\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_HTML_REPORT_DIR: null\n  opts:\n    summary: This folder contains the generated html test reports and their assets.\n    title: Html test report location\n"
  },
  {
    "path": "steps/generate-xcode-html-report/1.1.0/step.yml",
    "content": "title: Generate Xcode test report html\nsummary: The Step converts xcresult summaries to html reports.\ndescription: |-\n  This step will generate html report summaries from your xcresult files. It will also include all of the attachments from your tests.\n\n  The step works seamlessly with the official Xcode testing steps. If you use those then you do not need to configure this step in any way because it will automatically discover all of the generated xcresult files.\n\n  If you use Fastlane or have script step for your building process then you need to tell this step where to find your xcresult files.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report/issues\npublished_at: 2024-02-01T09:08:07.214643905Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report.git\n  commit: ca58a3707dbcda906472d68eb75e28ab74bf59b0\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nis_always_run: true\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of all of the xcresult files\n\n      You do not need to specify the xcresult if your are using the official Xcode test steps. This is only needed if you use Fastlane or script based setup.\n\n      This input supports glob patterns. This means you can use exact paths or wildcards. Here are a few examples:\n      ```\n      /path/to/MyApp.xcresult\n      /path/to/output/folder/*.xcresult\n      /path/to/parent/folder/**/*.xcresult\n      ```\n\n      The only requirements are that every pattern must only find xcresult files and they have to be absolute paths.\n    is_required: false\n    summary: A newline (`\\n`) separated list of all of the xcresult files\n    title: Xcresult file paths\n  xcresult_patterns: null\n- opts:\n    category: Debugging\n    is_dont_change_value: true\n    is_required: true\n    summary: This is directory where the official Xcode testing steps save their output\n    title: Bitrise test result directory\n  test_result_dir: $BITRISE_TEST_DEPLOY_DIR\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_HTML_REPORT_DIR: null\n  opts:\n    summary: This folder contains the generated html test reports and their assets.\n    title: Html test report location\n"
  },
  {
    "path": "steps/generate-xcode-html-report/1.1.1/step.yml",
    "content": "title: Generate Xcode test report html\nsummary: The Step converts xcresult summaries to html reports.\ndescription: |-\n  This step will generate html report summaries from your xcresult files. It will also include all of the attachments from your tests.\n\n  The step works seamlessly with the official Xcode testing steps. If you use those then you do not need to configure this step in any way because it will automatically discover all of the generated xcresult files.\n\n  If you use Fastlane or have script step for your building process then you need to tell this step where to find your xcresult files.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report/issues\npublished_at: 2025-11-10T15:37:17.252321588Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report.git\n  commit: 2ca232802249319c16e54d99fbe68e0144f4ba48\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-generate-xcode-html-report\nis_always_run: true\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of all of the xcresult files\n\n      You do not need to specify the xcresult if your are using the official Xcode test steps. This is only needed if you use Fastlane or script based setup.\n\n      This input supports glob patterns. This means you can use exact paths or wildcards. Here are a few examples:\n      ```\n      /path/to/MyApp.xcresult\n      /path/to/output/folder/*.xcresult\n      /path/to/parent/folder/**/*.xcresult\n      ```\n\n      The only requirements are that every pattern must only find xcresult files and they have to be absolute paths.\n    is_required: false\n    summary: A newline (`\\n`) separated list of all of the xcresult files\n    title: Xcresult file paths\n  xcresult_patterns: null\n- opts:\n    category: Debugging\n    is_dont_change_value: true\n    is_required: true\n    summary: This is directory where the official Xcode testing steps save their output\n    title: Bitrise test result directory\n  test_result_dir: $BITRISE_TEST_DEPLOY_DIR\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_HTML_REPORT_DIR: null\n  opts:\n    summary: This folder contains the generated html test reports and their assets.\n    title: Html test report location\n"
  },
  {
    "path": "steps/generate-xcode-html-report/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/generic-file-storage/0.9.0/step.yml",
    "content": "title: Generic File Storage\nsummary: The step will download all your files you uploaded in the workflow editor's\n  generic file storage section.\ndescription: |\n  The step will download all your files you uploaded in the workflow editor's generic file storage section with the same name, under `$GENERIC_FILE_STORAGE` path.\n  So if you upload `myconfig.ini` to the generic file storage, then the step will download it and it will be available as `$GENERIC_FILE_STORAGE/myconfig.ini`\nwebsite: https://github.com/bitrise-steplib/steps-generic-file-storage\nsource_code_url: https://github.com/bitrise-steplib/steps-generic-file-storage\nsupport_url: https://github.com/bitrise-steplib/steps-generic-file-storage/issues\npublished_at: 2018-05-22T12:06:49.077983311+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-generic-file-storage.git\n  commit: b7d06350677ffdfc96dc44140e071e57d730b653\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generic-file-storage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- enable_debug: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Enables debug mode. If this input is active the log of the step will contain more information for easier debug.\n    is_expand: false\n    is_required: true\n    title: Enable debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- GENERIC_FILE_STORAGE: null\n  opts:\n    description: Path to the files in Generic File Storage.\n    summary: Path to the files in Generic File Storage.\n    title: Generic File Storage Path\n"
  },
  {
    "path": "steps/generic-file-storage/0.9.1/step.yml",
    "content": "title: Generic File Storage\nsummary: The step will download all your files you uploaded in the workflow editor's\n  generic file storage section.\ndescription: |\n  The step will download all your files you uploaded in the workflow editor's generic file storage section with the same name, under `$GENERIC_FILE_STORAGE` path.\n  So if you upload `myconfig.ini` to the generic file storage, then the step will download it and it will be available as `$GENERIC_FILE_STORAGE/myconfig.ini`\nwebsite: https://github.com/bitrise-steplib/steps-generic-file-storage\nsource_code_url: https://github.com/bitrise-steplib/steps-generic-file-storage\nsupport_url: https://github.com/bitrise-steplib/steps-generic-file-storage/issues\npublished_at: 2019-03-14T14:44:11.288691214Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generic-file-storage.git\n  commit: 8eeea3f1d91740a162094579ef0bffdf43e4b252\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generic-file-storage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- enable_debug: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Enables debug mode. If this input is active the log of the step will contain more information for easier debug.\n    is_expand: false\n    is_required: true\n    title: Enable debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- GENERIC_FILE_STORAGE: null\n  opts:\n    description: Path to the files in Generic File Storage.\n    summary: Path to the files in Generic File Storage.\n    title: Generic File Storage Path\n"
  },
  {
    "path": "steps/generic-file-storage/0.9.2/step.yml",
    "content": "title: Generic File Storage\nsummary: The step will download all your files you uploaded in the GENERIC FILE STORAGE\n  section of the Code Signing tab in your Workflow Editor.\ndescription: |\n  The step will download all your files you uploaded in the GENERIC FILE STORAGE section of the Code Signing tab in your Workflow Editor with the same name, under `$GENERIC_FILE_STORAGE` path.\n  As an example, if you upload `myconfig.ini` to GENERIC FILE STORAGE, then the step will download it and it will be available as `$GENERIC_FILE_STORAGE/myconfig.ini`\nwebsite: https://github.com/bitrise-steplib/steps-generic-file-storage\nsource_code_url: https://github.com/bitrise-steplib/steps-generic-file-storage\nsupport_url: https://github.com/bitrise-steplib/steps-generic-file-storage/issues\npublished_at: 2020-09-29T08:57:41.295125432Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generic-file-storage.git\n  commit: 5ebc463bbfa3c7a47de97f4acbfeeb317ac26e4d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generic-file-storage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- enable_debug: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Enables debug mode. If this input is active, the log of the step will contain more information for easier debugging.\n    is_expand: false\n    is_required: true\n    title: Enable debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- GENERIC_FILE_STORAGE: null\n  opts:\n    description: Path to the files in Generic File Storage.\n    summary: Path to the files in GENERIC FILE STORAGE.\n    title: Generic File Storage Path\n"
  },
  {
    "path": "steps/generic-file-storage/0.9.3/step.yml",
    "content": "title: Generic File Storage\nsummary: The step will download all your files you uploaded in the GENERIC FILE STORAGE\n  section of the Code Signing tab in your Workflow Editor.\ndescription: |\n  The step will download all your files you uploaded in the GENERIC FILE STORAGE section of the Code Signing tab in your Workflow Editor with the same name, under `$GENERIC_FILE_STORAGE` path.\n  As an example, if you upload `myconfig.ini` to GENERIC FILE STORAGE, then the step will download it and it will be available as `$GENERIC_FILE_STORAGE/myconfig.ini`\nwebsite: https://github.com/bitrise-steplib/steps-generic-file-storage\nsource_code_url: https://github.com/bitrise-steplib/steps-generic-file-storage\nsupport_url: https://github.com/bitrise-steplib/steps-generic-file-storage/issues\npublished_at: 2020-10-01T14:43:11.867090424Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generic-file-storage.git\n  commit: 76593aa798cf36600806026fe35dfc9692d88766\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generic-file-storage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- enable_debug: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Enables debug mode. If this input is active, the log of the step will contain more information for easier debugging.\n    is_expand: false\n    is_required: true\n    title: Enable debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- GENERIC_FILE_STORAGE: null\n  opts:\n    description: Path to the files in Generic File Storage.\n    summary: Path to the files in GENERIC FILE STORAGE.\n    title: Generic File Storage Path\n"
  },
  {
    "path": "steps/generic-file-storage/0.9.4/step.yml",
    "content": "title: Generic File Storage\nsummary: The step will download all your files you uploaded in the GENERIC FILE STORAGE\n  section of the Code Signing tab in your Workflow Editor.\ndescription: |\n  The step will download all your files you uploaded in the GENERIC FILE STORAGE section of the Code Signing tab in your Workflow Editor with the same name, under `$GENERIC_FILE_STORAGE` path.\n  As an example, if you upload `myconfig.ini` to GENERIC FILE STORAGE, then the step will download it and it will be available as `$GENERIC_FILE_STORAGE/myconfig.ini`\nwebsite: https://github.com/bitrise-steplib/steps-generic-file-storage\nsource_code_url: https://github.com/bitrise-steplib/steps-generic-file-storage\nsupport_url: https://github.com/bitrise-steplib/steps-generic-file-storage/issues\npublished_at: 2020-12-02T15:55:56.953374307Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-generic-file-storage.git\n  commit: 90872ec8e32248f5bbc4ce695e86c4db398ff269\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-generic-file-storage\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- enable_debug: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Enables debug mode. If this input is active, the log of the step will contain more information for easier debugging.\n    is_expand: false\n    is_required: true\n    title: Enable debug mode\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- GENERIC_FILE_STORAGE: null\n  opts:\n    description: Path to the files in Generic File Storage.\n    summary: Path to the files in GENERIC FILE STORAGE.\n    title: Generic File Storage Path\n"
  },
  {
    "path": "steps/generic-file-storage/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.0.1/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2020-01-06T17:33:28.928568045+01:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: 577a9454bd58e9c7c5512e2d077b8eb3163a0073\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: Recipe UUID is the identifier used when starting an instance, Recipe\n      UUID can be retrieved using `gmsaas recipes list`.\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- instance_name: \"\"\n  opts:\n    description: Name given to the newly created instance.\n    is_required: true\n    summary: \"\"\n    title: Instance name\n- adb_serial_port: \"\"\n  opts:\n    description: \"If `adb_serial_port` option is set,  \\nthe instance will be connected\n      to ADB on localhost:`adb_serial_port`.  \\nOtherwise it will be connected to\n      a port given by your system,  \\n`gmsaas instances list` to know which one.\"\n    summary: \"\"\n    title: ADB serial port\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |\n      Return the UUID of the instance started and connected.\n    title: UUID of the instance connected\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      Return the ADB Serial Port of the instance started and connected.\n    title: ADB Serial Port of the instance connected\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.1/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2020-02-21T11:00:35.397384938+01:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: db985fe50d378e54dae8bc601d7f112c99ecfaf7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: \"Recipe UUID is the identifier used when starting an instance, Recipe\n      UUID can be retrieved using `gmsaas recipes list`.\\n\\nFormat:\\nYou can specify\n      several recipe UUIDs in order to start several instances. Recipe UUIDs are separated\n      with a comma.\\n\\nFor example:\\n`e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\\n\\nor\n      specify only one recipe UUID:\\n`e20da1a3-313c-434a-9d43-7268b12fee08`  \"\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: \"If `adb_serial_port` option is set,  \\nthe instance will be connected\n      to ADB on localhost:`adb_serial_port`.  \\nOtherwise it will be connected to\n      a port given by your system,  \\n`gmsaas instances list` to know which one.\\n\\nFormat:\\nYou\n      can specify several ADB Serial ports. ADB Serial ports are separated with a\n      comma.\\n\\nFor example:\\n`4321,4322,4323`\"\n    summary: \"\"\n    title: ADB serial port\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.2/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2020-06-24T11:04:56.55438045+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: 3a24825b31c23835f975c213884129519ce4826b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: |-\n      Instance recipe to use. Recipes can be listed with command line 'gmsaas recipes list',\n      or check https://support.genymotion.com/hc/en-us/articles/360007473658-Supported-Android-devices-templates-for-Genymotion-Cloud-SaaS\n      for a comprehensive list of all currently available recipes UUIDs\n\n      Format:\n      You can specify several recipe UUIDs in order to start several instances. Recipe UUIDs are separated with a comma.\n\n      For example:\n      `e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\n\n      or specify only one recipe UUID:\n      `e20da1a3-313c-434a-9d43-7268b12fee08`\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: |-\n      If `adb_serial_port` option is set,\n      the instance will be connected to ADB on localhost:`adb_serial_port`.\n      Otherwise it will be connected to a port given by your system,\n      `gmsaas instances list` to know which one.\n\n      Format:\n      You can specify several ADB Serial ports. ADB Serial ports are separated with a comma.\n\n      For example:\n      `4321,4322,4323`\n    summary: \"\"\n    title: ADB serial port\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.3/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2020-06-30T17:08:53.064914103+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: 9685a34b454a4e31c296a8056dd77f1d9f11ed40\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: |-\n      Instance recipe to use. Recipes can be listed with command line 'gmsaas recipes list',\n      or check https://support.genymotion.com/hc/en-us/articles/360007473658-Supported-Android-devices-templates-for-Genymotion-Cloud-SaaS\n      for a comprehensive list of all currently available recipes UUIDs\n\n      Format:\n      You can specify several recipe UUIDs in order to start several instances. Recipe UUIDs are separated with a comma.\n\n      For example:\n      `e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\n\n      or specify only one recipe UUID:\n      `e20da1a3-313c-434a-9d43-7268b12fee08`\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: |-\n      If `adb_serial_port` option is set,\n      the instance will be connected to ADB on localhost:`adb_serial_port`.\n      Otherwise it will be connected to a port given by your system,\n      `gmsaas instances list` to know which one.\n\n      Format:\n      You can specify several ADB Serial ports. ADB Serial ports are separated with a comma.\n\n      For example:\n      `4321,4322,4323`\n    summary: \"\"\n    title: ADB serial port\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.4/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2020-07-08T16:42:31.298429399+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: c1873ebd64b67e44cb60d8aac19c7ca604c3143a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: |-\n      Instance recipe to use. Recipes can be listed with command line 'gmsaas recipes list',\n      or check https://support.genymotion.com/hc/en-us/articles/360007473658-Supported-Android-devices-templates-for-Genymotion-Cloud-SaaS\n      for a comprehensive list of all currently available recipes UUIDs\n\n      Format:\n      You can specify several recipe UUIDs in order to start several instances. Recipe UUIDs are separated with a comma.\n\n      For example:\n      `e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\n\n      or specify only one recipe UUID:\n      `e20da1a3-313c-434a-9d43-7268b12fee08`\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: |-\n      If `adb_serial_port` option is set,\n      the instance will be connected to ADB on localhost:`adb_serial_port`.\n      Otherwise it will be connected to a port given by your system,\n      `gmsaas instances list` to know which one.\n\n      Format:\n      You can specify several ADB Serial ports. ADB Serial ports are separated with a comma.\n\n      For example:\n      `4321,4322,4323`\n    summary: \"\"\n    title: ADB serial port\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.5/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2020-09-07T15:08:07.282434538+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: e67e21fda3ee36906d338f513e008cd1c867eba5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: |-\n      Instance recipe to use. Recipes can be listed with command line 'gmsaas recipes list',\n      or check https://support.genymotion.com/hc/en-us/articles/360007473658-Supported-Android-devices-templates-for-Genymotion-Cloud-SaaS\n      for a comprehensive list of all currently available recipes UUIDs\n\n      Format:\n      You can specify several recipe UUIDs in order to start several instances. Recipe UUIDs are separated with a comma.\n\n      For example:\n      `e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\n\n      or specify only one recipe UUID:\n      `e20da1a3-313c-434a-9d43-7268b12fee08`\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: |-\n      If `adb_serial_port` option is set,\n      the instance will be connected to ADB on localhost:`adb_serial_port`.\n      Otherwise it will be connected to a port given by your system,\n      `gmsaas instances list` to know which one.\n\n      Format:\n      You can specify several ADB Serial ports. ADB Serial ports are separated with a comma.\n\n      For example:\n      `4321,4322,4323`\n    summary: \"\"\n    title: ADB serial port\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.6/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2024-06-24T09:37:47.466245615+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: 36e8a389908804e2e7cb0082e47e0f1eb0fbd0b6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: \"\"\n  opts:\n    description: API Token to authenticate to your Genymotion Cloud SaaS account.\n      If you don't have an account please register on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n      and create an [API Token](https://cloud.geny.io/api)\n    summary: \"\"\n    title: Genymotion Cloud SaaS API Token\n- email: \"\"\n  opts:\n    description: 'DEPRECATED : Email of your Genymotion Cloud SaaS account, if you\n      don''t have an account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)'\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: 'DEPRECATED: Password of your Genymotion Cloud SaaS account.'\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: |-\n      Instance recipe to use. Recipes can be listed with command line 'gmsaas recipes list',\n      or check https://support.genymotion.com/hc/en-us/articles/360007473658-Supported-Android-devices-templates-for-Genymotion-Cloud-SaaS\n      for a comprehensive list of all currently available recipes UUIDs\n\n      Format:\n      You can specify several recipe UUIDs in order to start several instances. Recipe UUIDs are separated with a comma.\n\n      For example:\n      `e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\n\n      or specify only one recipe UUID:\n      `e20da1a3-313c-434a-9d43-7268b12fee08`\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: |-\n      If `adb_serial_port` option is set,\n      the instance will be connected to ADB on localhost:`adb_serial_port`.\n      Otherwise it will be connected to a port given by your system,\n      `gmsaas instances list` to know which one.\n\n      Format:\n      You can specify several ADB Serial ports. ADB Serial ports are separated with a comma.\n\n      For example:\n      `4321,4322,4323`\n    summary: \"\"\n    title: ADB serial port\n- gmsaas_version: 1.11.0\n  opts:\n    description: 'Install a specific version of gmsaas, per default it will install\n      the latest compatible gmsaas version : 1.11.0'\n    summary: \"\"\n    title: gmsaas version\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/0.1.7/step.yml",
    "content": "title: Genymotion Cloud Start Android Devices\nsummary: |\n  Start Genymotion Cloud SaaS Android Devices\ndescription: |-\n  This step launches Android devices on Genymotion Cloud SaaS.\n  Appium, Espresso, and others test automation frameworks can be run on those devices.\n  Setup instructions:\n  1. Create a Genymotion Cloud SaaS account: [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n  1. Navigate to Default templates or templates:\n    - Select a device.\n    - Click on dot menu and select details.\n    - On the description field, get the recipe UUID.\n    - Copy paste it to use it in this step.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start/issues\npublished_at: 2025-06-20T15:16:03.166599102+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git\n  commit: 6cd6083bf90c2407e8f9398e6d53be2c2a8beffe\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-start\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: \"\"\n  opts:\n    description: API Token to authenticate to your Genymotion Cloud SaaS account.\n      If you don't have an account please register on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n      and create an [API Token](https://cloud.geny.io/api)\n    summary: \"\"\n    title: Genymotion Cloud SaaS API Token\n- email: \"\"\n  opts:\n    description: 'DEPRECATED : Email of your Genymotion Cloud SaaS account, if you\n      don''t have an account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)'\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: 'DEPRECATED: Password of your Genymotion Cloud SaaS account.'\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- opts:\n    description: |-\n      Instance recipe to use. Recipes can be listed with command line 'gmsaas recipes list',\n      or check https://support.genymotion.com/hc/en-us/articles/360007473658-Supported-Android-devices-templates-for-Genymotion-Cloud-SaaS\n      for a comprehensive list of all currently available recipes UUIDs\n\n      Format:\n      You can specify several recipe UUIDs in order to start several instances. Recipe UUIDs are separated with a comma.\n\n      For example:\n      `e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23`\n\n      or specify only one recipe UUID:\n      `e20da1a3-313c-434a-9d43-7268b12fee08`\n    is_required: true\n    summary: \"\"\n    title: Recipe UUID\n  recipe_uuid: \"\"\n- adb_serial_port: \"\"\n  opts:\n    description: |-\n      If `adb_serial_port` option is set,\n      the instance will be connected to ADB on localhost:`adb_serial_port`.\n      Otherwise it will be connected to a port given by your system,\n      `gmsaas instances list` to know which one.\n\n      Format:\n      You can specify several ADB Serial ports. ADB Serial ports are separated with a comma.\n\n      For example:\n      `4321,4322,4323`\n    summary: \"\"\n    title: ADB serial port\n- gmsaas_version: \"\"\n  opts:\n    description: Install a specific version of gmsaas, per default it will install\n      the latest gmsaas version\n    summary: \"\"\n    title: gmsaas version\noutputs:\n- GMCLOUD_SAAS_INSTANCE_UUID: null\n  opts:\n    description: |-\n      This output will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    title: UUID list of started and connected instances\n- GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT: null\n  opts:\n    description: |\n      This output will include the ADB Serial Port list of connected instances.\n      The  ADB Serial Port are separated with a comma, eg: `localhost:4321,localhost:4322`\n    title: ADB Serial Port list of connected instances\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-start/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-stop/0.0.2/step.yml",
    "content": "title: Genymotion Cloud Stop Android Devices\nsummary: |\n  Stop Genymotion Cloud SaaS instances\ndescription: |\n  Stop Genymotion Cloud SaaS instances.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop/issues\npublished_at: 2020-01-07T14:01:15.690074354+01:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop.git\n  commit: 622ca6978a513ef83377675ea402fd4d0ec5a495\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID\n  opts:\n    description: Instance UUID of the instance you want to stop.\n    is_required: true\n    summary: \"\"\n    title: Instance UUID\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-stop/0.1.1/step.yml",
    "content": "title: Genymotion Cloud Stop Android Devices\nsummary: |\n  Stop Genymotion Cloud SaaS instances\ndescription: |\n  Stop Genymotion Cloud SaaS instances.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop/issues\npublished_at: 2020-02-21T11:01:08.231708033+01:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop.git\n  commit: aea04ca16f0ffe5e403f850630a69b235760be36\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID\n  opts:\n    description: |-\n      Instance UUIDs list you want to stop.\n\n      This input will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    is_required: true\n    summary: \"\"\n    title: Instance UUID\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-stop/0.1.2/step.yml",
    "content": "title: Genymotion Cloud Stop Android Devices\nsummary: |\n  Stop Genymotion Cloud SaaS instances\ndescription: |\n  Stop Genymotion Cloud SaaS instances.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop/issues\npublished_at: 2020-06-24T11:07:15.547480237+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop.git\n  commit: cde177fce4db835795c811365474f99eb966c604\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-cloud-saas-stop\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID\n  opts:\n    description: |-\n      Instance UUIDs list you want to stop.\n\n      This input will include the instances UUIDs of started and connected instances.\n      The UUIDs are separated with a comma, eg: `594d606a-e6f7-43e1-99ac-77e07738a6dc,18e75e62-534e-4407-9700-564d767d6578`\n    is_required: true\n    summary: \"\"\n    title: Instance UUID\n"
  },
  {
    "path": "steps/genymotion-cloud-saas-stop/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/genymotion-saas-install-gmsaas-cli/0.0.1/step.yml",
    "content": "title: Genymotion SaaS install gmsaas cli\nsummary: |\n  Install gmsaas, a command line interface to rule all your virtual devices hosted in Genymotion SaaS solution.\ndescription: |\n  This step installs gmsaas cli, it allows you to rule all your virtual devices hosted in Genymotion SaaS solution without opening an internet browser.\nwebsite: https://github.com/thomascarpentier/bitrise-step-genymotion-saas-install-gmsaas-cli\nsource_code_url: https://github.com/thomascarpentier/bitrise-step-genymotion-saas-install-gmsaas-cli\nsupport_url: https://github.com/thomascarpentier/bitrise-step-genymotion-saas-install-gmsaas-cli/issues\npublished_at: 2023-01-25T11:57:35.878313175+01:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli.git\n  commit: 2ca25eaf9c778cfe35d3a31bc072b24820ead71c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- email: \"\"\n  opts:\n    description: Email of your Genymotion Cloud SaaS account, if you don't have an\n      account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n    is_required: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: Password of your Genymotion Cloud SaaS account.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n"
  },
  {
    "path": "steps/genymotion-saas-install-gmsaas-cli/0.0.3/step.yml",
    "content": "title: Genymotion SaaS install gmsaas cli\nsummary: |\n  Install gmsaas,  command line interface to rule all your virtual devices hosted in Genymotion SaaS solution.\ndescription: |\n  This step installs gmsaas cli, it allaows user to rule all your virtual devices hosted in Genymotion SaaS solution without opening an Internet browser.\nwebsite: https://github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli\nsource_code_url: https://github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli\nsupport_url: https://github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli/issues\npublished_at: 2024-06-28T14:43:25.184948733+02:00\nsource:\n  git: https://github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli.git\n  commit: 4a3926f4a09256e40157512202a72a725e83bd66\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/genymobile/bitrise-step-genymotion-saas-install-gmsaas-cli\ndeps:\n  brew:\n  - name: python3\n  - bin_name: pip3\n  apt_get:\n  - name: python3-pip\n  - bin_name: pip3\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_token: \"\"\n  opts:\n    description: API Token to authenticate to your Genymotion Cloud SaaS account.\n      If you don't have an account please register on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)\n      and create an [API Token](https://cloud.geny.io/api)\n    summary: \"\"\n    title: Genymotion Cloud SaaS API Token\n- email: \"\"\n  opts:\n    description: 'DEPRECATED : Email of your Genymotion Cloud SaaS account, if you\n      don''t have an account please create it first on [https://cloud.geny.io](https://cloud.geny.io/?&utm_source=web-referral&utm_medium=docs&utm_campaign=bitrise&utm_content=signup)'\n    summary: \"\"\n    title: Genymotion Cloud SaaS email\n- opts:\n    description: 'DEPRECATED: Password of your Genymotion Cloud SaaS account.'\n    is_sensitive: true\n    summary: \"\"\n    title: Genymotion Cloud SaaS password\n  password: \"\"\n- gmsaas_version: 1.11.0\n  opts:\n    description: 'Install a specific version of gmsaas, per default it will install\n      the latest gmsaas compatible : 1.11.0'\n    summary: \"\"\n    title: gmsaas version\n"
  },
  {
    "path": "steps/genymotion-saas-install-gmsaas-cli/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/get-app/0.1.0/step.yml",
    "content": "title: getApp\nsummary: |\n  A simple step to get any artifact from other Apps/Workflow downloaded to any directory.\ndescription: |\n  This step would help you to get artifact/app/files from the latest successful build of other workflows or even apps, downloaded to any directory inside your current bitrise/src\n  This step requires authorization key, which you can get from your \"Account Settings -> Security -> Personal Access Token\"\nwebsite: https://github.com/shreyanshp/bitrise-step-getapp\nsource_code_url: https://github.com/shreyanshp/bitrise-step-getapp\nsupport_url: https://github.com/shreyanshp/bitrise-step-getapp/issues\npublished_at: 2019-07-13T00:14:27.994279+09:00\nsource:\n  git: https://github.com/shreyanshp/bitrise-step-getapp.git\n  commit: a4d264342ea3b8a33545069e0ff4c5f9e9e0ec6e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- artifact_name: null\n  opts:\n    description: |\n      Please enter the exact artifact/file name with extension that you want to download.\n    is_expand: true\n    is_required: true\n    summary: Artifact Name\n    title: Artifact Name\n    value_options: []\n- access_token: null\n  opts:\n    description: |\n      Please enter the access token, which you can get from your \"Account Settings -> Security -> Personal Access Token\".\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Access Token\n    title: Access Token\n    value_options: []\n- app_slug: null\n  opts:\n    description: |\n      Please enter the App ID from which you want to download the file.\n    is_expand: true\n    is_required: true\n    summary: App ID\n    title: App ID\n    value_options: []\n- opts:\n    description: |\n      Please enter the workflow name, primary is the default\n    is_expand: true\n    is_required: true\n    summary: Workflow\n    title: Workflow\n    value_options: []\n  workflow: primary\n- directory_name: getApp\n  opts:\n    description: |\n      Please enter the directory name, where you want the artifact/file to be downloaded. It would be created the directory does not exists. Incase the directory with same filename exists, then it would be overwritten.\n    is_expand: true\n    is_required: true\n    summary: Directory Name\n    title: Directory Name\n    value_options: []\n"
  },
  {
    "path": "steps/get-app/0.2.0/step.yml",
    "content": "title: getApp\nsummary: |\n  A simple step to get any artifact from other Apps/Workflow downloaded to any directory.\ndescription: |\n  This step would help you to get artifact/app/files from the latest successful build of other workflows or even apps, downloaded to any directory inside your current bitrise/src\n  This step requires authorization key, which you can get from your \"Account Settings -> Security -> Personal Access Token\"\nwebsite: https://github.com/shreyanshp/bitrise-step-getapp\nsource_code_url: https://github.com/shreyanshp/bitrise-step-getapp\nsupport_url: https://github.com/shreyanshp/bitrise-step-getapp/issues\npublished_at: 2020-06-01T00:14:27.994279+09:00\nsource:\n  git: https://github.com/shreyanshp/bitrise-step-getapp.git\n  commit: acd282c1ae477d2e529026863e0f3708abcd8d08\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: jq\n  apt_get:\n  - name: git\n  - name: wget\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- artifact_name: null\n  opts:\n    description: |\n      Please enter the exact artifact/file name with extension that you want to download.\n    is_expand: true\n    is_required: true\n    summary: Artifact Name\n    title: Artifact Name\n    value_options: []\n- access_token: null\n  opts:\n    description: |\n      Please enter the access token, which you can get from your \"Account Settings -> Security -> Personal Access Token\".\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Access Token\n    title: Access Token\n    value_options: []\n- app_slug: null\n  opts:\n    description: |\n      Please enter the App ID from which you want to download the file.\n    is_expand: true\n    is_required: true\n    summary: App ID\n    title: App ID\n    value_options: []\n- opts:\n    description: |\n      Please enter the workflow name, primary is the default\n    is_expand: true\n    is_required: true\n    summary: Workflow\n    title: Workflow\n    value_options: []\n  workflow: primary\n- directory_name: getApp\n  opts:\n    description: |\n      Please enter the directory name, where you want the artifact/file to be downloaded. It would be created the directory does not exists. Incase the directory with same filename exists, then it would be overwritten.\n    is_expand: true\n    is_required: true\n    summary: Directory Name\n    title: Directory Name\n    value_options: []\n"
  },
  {
    "path": "steps/get-app/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/get-flutter-version/0.0.1/step.yml",
    "content": "title: Get Flutter version from pubspec\nsummary: Extracts minimum required Flutter version from pubspec files\ndescription: Extracts the Flutter version from *pubspec.lock* (if present) or *pubspec.yaml*\n  and sets `$FLUTTER_PUBSPEC_VERSION` environment variable.\nwebsite: https://github.com/dgimb89/bitrise-step-get-flutter-version\nsource_code_url: https://github.com/dgimb89/bitrise-step-get-flutter-version\nsupport_url: https://github.com/dgimb89/bitrise-step-get-flutter-version/issues\npublished_at: 2020-05-19T01:56:39.201454+02:00\nsource:\n  git: https://github.com/dgimb89/bitrise-step-get-flutter-version.git\n  commit: 91bc7d7b2cf1412d9ab79e3bca5e50fce25ce3f7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: perl\n  apt_get:\n  - name: perl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root dir of your Flutter project that contains *pubspec.yaml*\n      and optionally *pubspec.lock*.\n    is_required: true\n    summary: The root dir of your Flutter project\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\noutputs:\n- FLUTTER_PUBSPEC_VERSION: null\n  opts:\n    description: Minimum Flutter version requirement that is defined in pubspec files\n      (*pubspec.lock*, *pubspec.yaml*) at the **project location**.\n    title: Flutter version that is defined by pubspec\n- FLUTTER_PUBSPEC_YAML_VERSION: null\n  opts:\n    description: Minimum Flutter version requirement that is defined in *pubspec.yaml*\n      file at the **project location**.\n    title: Flutter version that is defined by pubspec.yaml\n- FLUTTER_PUBSPEC_LOCK_VERSION: null\n  opts:\n    description: Minimum Flutter version requirement that is defined in *pubspec.lock*\n      file at the **project location**.\n    title: Flutter version that is defined by pubspec.lock\n"
  },
  {
    "path": "steps/get-flutter-version/0.0.2/step.yml",
    "content": "title: Get Flutter version from pubspec\nsummary: Extracts minimum required Flutter version from pubspec files\ndescription: Extracts the Flutter version from *pubspec.lock* (if present) or *pubspec.yaml*\n  and sets `$FLUTTER_PUBSPEC_VERSION` environment variable.\nwebsite: https://github.com/dgimb89/bitrise-step-get-flutter-version\nsource_code_url: https://github.com/dgimb89/bitrise-step-get-flutter-version\nsupport_url: https://github.com/dgimb89/bitrise-step-get-flutter-version/issues\npublished_at: 2022-08-04T12:08:16.140807+02:00\nsource:\n  git: https://github.com/dgimb89/bitrise-step-get-flutter-version.git\n  commit: ff68580c0d5450976a7aebe0603620fec17e6504\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: perl\n  apt_get:\n  - name: perl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root dir of your Flutter project that contains *pubspec.yaml*\n      and optionally *pubspec.lock*.\n    is_required: true\n    summary: The root dir of your Flutter project\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\noutputs:\n- FLUTTER_PUBSPEC_VERSION: null\n  opts:\n    description: Minimum Flutter version requirement that is defined in pubspec files\n      (*pubspec.lock*, *pubspec.yaml*) at the **project location**.\n    title: Flutter version that is defined by pubspec\n- FLUTTER_PUBSPEC_YAML_VERSION: null\n  opts:\n    description: Minimum Flutter version requirement that is defined in *pubspec.yaml*\n      file at the **project location**.\n    title: Flutter version that is defined by pubspec.yaml\n- FLUTTER_PUBSPEC_LOCK_VERSION: null\n  opts:\n    description: Minimum Flutter version requirement that is defined in *pubspec.lock*\n      file at the **project location**.\n    title: Flutter version that is defined by pubspec.lock\n"
  },
  {
    "path": "steps/get-flutter-version/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/get-identity-token/0.0.1/step.yml",
    "content": "title: Get OIDC Identity Token\nsummary: The Step fetches an OIDC identity token.\ndescription: |-\n  The Step fetches an OIDC identity token.\n\n  The token can be used to authenticate with services that support OIDC tokens, such as Google Cloud, AWS, Azure or others.\n  This allows secure, token-based authentication without the need to manage long-lived credentials.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-get-identity-token\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-get-identity-token\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-get-identity-token/issues\npublished_at: 2025-10-31T11:16:46.692596+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-get-identity-token.git\n  commit: 83bf67e7d7138af0ecc5fb2020ac8255fde03fbd\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-get-identity-token\ninputs:\n- audience: null\n  opts:\n    description: |-\n      The audience for the identity token.\n\n      This could be the URL of the service you want to access with the token or a specific identifier provided by the service.\n    is_required: true\n    summary: The audience for the identity token.\n    title: Token audience\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: API settings\n    description: |-\n      Unique build URL of this build on Bitrise.io.\n\n      By default the step will use the Bitrise API.\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io.\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: API settings\n    description: |-\n      The build's API Token for the build on Bitrise.io\n\n      This will be used to communicate with the Bitrise API\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise build token\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_IDENTITY_TOKEN: null\n  opts:\n    summary: The newly generated identity token.\n    title: Identity token\n"
  },
  {
    "path": "steps/get-identity-token/0.0.2/step.yml",
    "content": "title: Get OIDC Identity Token\nsummary: The Step fetches an OIDC identity token.\ndescription: |-\n  The Step fetches an OIDC identity token.\n\n  The token can be used to authenticate with services that support OIDC tokens, such as Google Cloud, AWS, Azure or others.\n  This allows secure, token-based authentication without the need to manage long-lived credentials.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-get-identity-token\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-get-identity-token\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-get-identity-token/issues\npublished_at: 2026-02-04T12:16:36.99277633Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-get-identity-token.git\n  commit: 9c671da88bda23b999076b4071bd5ce01bcf61ff\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-get-identity-token\ninputs:\n- audience: null\n  opts:\n    description: |-\n      The audience for the identity token.\n\n      This could be the URL of the service you want to access with the token or a specific identifier provided by the service.\n    is_required: true\n    summary: The audience for the identity token.\n    title: Token audience\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: API settings\n    description: |-\n      Unique build URL of this build on Bitrise.io.\n\n      By default the step will use the Bitrise API.\n    is_dont_change_value: true\n    is_required: true\n    summary: Unique build URL of this build on Bitrise.io.\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: API settings\n    description: |-\n      The build's API Token for the build on Bitrise.io\n\n      This will be used to communicate with the Bitrise API\n    is_required: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise build token\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_IDENTITY_TOKEN: null\n  opts:\n    summary: The newly generated identity token.\n    title: Identity token\n"
  },
  {
    "path": "steps/get-identity-token/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/get-info-on-android-app-bundle/0.0.1/step.yml",
    "content": "title: Get Info on Android App Bundle\nsummary: |\n  Extracts the version name and the version code from the Android App Bundle(aab).\ndescription: |\n  Extracts the version name and the version code from the Android App Bundle(aab). Android Application Package (apk) is not supported.\nwebsite: https://github.com/nosaka/bitrise-step-get-info-on-android-app-bundle\nsource_code_url: https://github.com/nosaka/bitrise-step-get-info-on-android-app-bundle\nsupport_url: https://github.com/nosaka/bitrise-step-get-info-on-android-app-bundle/issues\npublished_at: 2021-01-20T12:07:11.555171+09:00\nsource:\n  git: https://github.com/nosaka/bitrise-step-get-info-on-android-app-bundle.git\n  commit: 494b7f167884676bca494e5c0df5866898a73ac1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- artifact-info\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- aab_path: $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file `.aab`. You can build the bundle running `:bundleRelease` gradle task\n      Format examples:\n      - `/path/to/my/app.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)`'\n    title: Build artifact path.\noutputs:\n- ANDROID_VERSION_CODE: null\n  opts:\n    summary: versionCode from AndroidManifest.xml\n    title: Version Code\n- ANDROID_VERSION_NAME: null\n  opts:\n    summary: versionName from AndroidManifest.xml\n    title: Version Name\n- ANDROID_PACKAGE_NAME: null\n  opts:\n    summary: package from AndroidManifest.xml\n    title: Package Name\n- ANDROID_MIN_SDK_VERSION: null\n  opts:\n    summary: minSdkVersion from AndroidManifest.xml\n    title: Minimum SDK Version\n- ANDROID_TARGET_SDK_VERSION: null\n  opts:\n    summary: targetSdkVersion from AndroidManifest.xml\n    title: Target SDK Version\n"
  },
  {
    "path": "steps/get-info-on-android-app-bundle/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/get-npm-package-version/1.0.1/step.yml",
    "content": "title: Get npm package version\nsummary: |\n  Sets an environment variable with the npm package version\ndescription: |\n  Sets environment variable `$NPM_PACKAGE_VERSION` with the value found in the \"version\" field of package.json, for use in later steps\nwebsite: https://github.com/lafiosca/bitrise-step-get-npm-package-version\nsource_code_url: https://github.com/lafiosca/bitrise-step-get-npm-package-version\nsupport_url: https://github.com/lafiosca/bitrise-step-get-npm-package-version/issues\npublished_at: 2019-08-22T09:52:42.245098-04:00\nsource:\n  git: https://github.com/lafiosca/bitrise-step-get-npm-package-version.git\n  commit: e5da6956d21638f18643088ece61aef98d98fdd4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: The version field in the specified JSON file will be exported as `$NPM_PACKAGE_VERSION`\n    title: Path of package.json\n  package_json_path: $BITRISE_SOURCE_DIR/package.json\noutputs:\n- NPM_PACKAGE_VERSION: null\n  opts:\n    summary: The value of the version field found in package.json\n    title: npm package version\n"
  },
  {
    "path": "steps/get-npm-package-version/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/get-pubspec-version-and-build-number/1.0.0/step.yml",
    "content": "title: Get pubspec version and build number\nsummary: |\n  Get the `version` from the pubspec and sets the environment variables\ndescription: |\n  Get the `version` from pubspec and sets `$PUBSPEC_VERSION`, `$PUBSPEC_VERSION_NAME` and `$PUBSPEC_BUILD_NUMBER`\nwebsite: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsource_code_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsupport_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number/issues\npublished_at: 2019-11-13T17:52:56.204572-05:00\nsource:\n  git: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number.git\n  commit: e00bffb49f1003e9da160d91adfe06f53f5b9f36\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: yq\n  apt_get:\n  - name: yq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Path to pubspec.yaml\n  pubspec_path: $BITRISE_SOURCE_DIR/pubspec.yaml\noutputs:\n- PUBSPEC_VERSION: null\n  opts:\n    summary: 'Example: `1.2.43+10`'\n    title: Value of the `version` attribute in the pubspec.yml\n- PUBSPEC_VERSION_NAME: null\n  opts:\n    summary: 'Example: `1.2.43`'\n    title: Part before the `+` in the `PUBSPEC_VERSION`\n- PUBSPEC_BUILD_NUMBER: null\n  opts:\n    summary: 'Example: `10`'\n    title: Part after the `+` in the `PUBSPEC_VERSION`\n"
  },
  {
    "path": "steps/get-pubspec-version-and-build-number/1.0.1/step.yml",
    "content": "title: Get pubspec version and build number\nsummary: |\n  Get the `version` from the pubspec and sets the environment variables\ndescription: |\n  Get the `version` from pubspec and sets `$PUBSPEC_VERSION`, `$PUBSPEC_VERSION_NAME` and `$PUBSPEC_BUILD_NUMBER`\nwebsite: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsource_code_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsupport_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number/issues\npublished_at: 2019-11-14T14:40:49.439336-05:00\nsource:\n  git: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number.git\n  commit: ec249d51c0476e3563bc9812e8985246a4e75401\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: yq\n  apt_get:\n  - name: yq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Path to pubspec.yaml\n  pubspec_path: $BITRISE_SOURCE_DIR/pubspec.yaml\noutputs:\n- PUBSPEC_VERSION: null\n  opts:\n    summary: 'Example: `1.2.43+10`'\n    title: Value of the `version` attribute in the pubspec.yml\n- PUBSPEC_VERSION_NAME: null\n  opts:\n    summary: 'Example: `1.2.43`'\n    title: Part before the `+` in the `PUBSPEC_VERSION`\n- PUBSPEC_BUILD_NUMBER: null\n  opts:\n    summary: 'Example: `10`'\n    title: Part after the `+` in the `PUBSPEC_VERSION`\n"
  },
  {
    "path": "steps/get-pubspec-version-and-build-number/1.0.2/step.yml",
    "content": "title: Get pubspec version and build number\nsummary: |\n  Get the `version` from the pubspec and sets the environment variables\ndescription: |\n  Get the `version` from pubspec and sets `$PUBSPEC_VERSION`, `$PUBSPEC_VERSION_NAME` and `$PUBSPEC_BUILD_NUMBER`\nwebsite: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsource_code_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsupport_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number/issues\npublished_at: 2020-01-10T18:03:30.761905-05:00\nsource:\n  git: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number.git\n  commit: 2ac4f5945b262723ef12bbfd425a66a52e29c0aa\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Path to pubspec.yaml\n  pubspec_path: $BITRISE_SOURCE_DIR/pubspec.yaml\noutputs:\n- PUBSPEC_VERSION: null\n  opts:\n    summary: 'Example: `1.2.43+10`'\n    title: Value of the `version` attribute in the pubspec.yml\n- PUBSPEC_VERSION_NAME: null\n  opts:\n    summary: 'Example: `1.2.43`'\n    title: Part before the `+` in the `PUBSPEC_VERSION`\n- PUBSPEC_BUILD_NUMBER: null\n  opts:\n    summary: 'Example: `10`'\n    title: Part after the `+` in the `PUBSPEC_VERSION`\n"
  },
  {
    "path": "steps/get-pubspec-version-and-build-number/1.0.3/step.yml",
    "content": "title: Get pubspec version and build number\nsummary: |\n  Get the `version` from the pubspec and sets the environment variables\ndescription: |\n  Get the `version` from pubspec and sets `$PUBSPEC_VERSION`, `$PUBSPEC_VERSION_NAME` and `$PUBSPEC_BUILD_NUMBER`\nwebsite: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsource_code_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number\nsupport_url: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number/issues\npublished_at: 2020-01-23T19:14:51.218913-05:00\nsource:\n  git: https://github.com/ianko/bitrise-step-get-pubspec-version-and-build-number.git\n  commit: a058e9fc2e15c02b563bac1339ff03c4ca9637a4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Path to pubspec.yaml\n  pubspec_path: $BITRISE_SOURCE_DIR/pubspec.yaml\noutputs:\n- PUBSPEC_VERSION: null\n  opts:\n    summary: 'Example: `1.2.43+10`'\n    title: Value of the `version` attribute in the pubspec.yml\n- PUBSPEC_VERSION_NAME: null\n  opts:\n    summary: 'Example: `1.2.43`'\n    title: Part before the `+` in the `PUBSPEC_VERSION`\n- PUBSPEC_BUILD_NUMBER: null\n  opts:\n    summary: 'Example: `10`'\n    title: Part after the `+` in the `PUBSPEC_VERSION`\n"
  },
  {
    "path": "steps/get-pubspec-version-and-build-number/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/giphy/0.1.0/step.yml",
    "content": "title: Gifs with Giphy\nsummary: Spice up your Bitrise.io logs with a random Gif from Giphy (saved into $GIF_URL)\ndescription: |\n  Spice up your Bitrise.io logs with a random Gif from Giphy\n\n  This script will add a `GIF_URL` variable to your build than you can use in the next steps.\n  Wanna send a Gif with the Slack step? Simply add `$GIF_URL` somewhere in your Gif message ;)\nwebsite: https://github.com/almouro/bitrise-giphy-step\nsource_code_url: https://github.com/almouro/bitrise-giphy-step\nsupport_url: https://github.com/almouro/bitrise-giphy-step/issues\npublished_at: 2016-10-17T20:09:38.225617462+02:00\nsource:\n  git: https://github.com/Almouro/bitrise-giphy-step.git\n  commit: f03d7bcf9451b32a199c7f30cdd6736bad8774e2\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- gif_words: such wow,awesome,shipit,yes,panda,cat,hell yeah,applaud,lgtm,surprise,suprise\n    motherfucker,yeah bitches,high five,legendary,lil bub\n  opts:\n    description: |\n      The step randomly select a gif for one the words you entered.\n\n      You should enter a comma separated list of value.\n      The default is \"such wow,awesome,shipit,yes,panda,cat,hell yeah,applaud,lgtm,surprise,suprise motherfucker,yeah bitches,high five,legendary,lil bub\"\n    is_expand: false\n    is_required: true\n    title: Random Gif words\n"
  },
  {
    "path": "steps/giphy/0.1.1/step.yml",
    "content": "title: Gifs with Giphy\nsummary: Spice up your Bitrise.io logs with a random Gif from Giphy (saved into $GIF_URL)\ndescription: |\n  Spice up your Bitrise.io logs with a random Gif from Giphy\n\n  This script will add a `GIF_URL` variable to your build than you can use in the next steps.\n  Wanna send a Gif with the Slack step? Simply add `$GIF_URL` somewhere in your Gif message ;)\nwebsite: https://github.com/almouro/bitrise-giphy-step\nsource_code_url: https://github.com/almouro/bitrise-giphy-step\nsupport_url: https://github.com/almouro/bitrise-giphy-step/issues\npublished_at: 2016-11-11T12:33:28.486415826+01:00\nsource:\n  git: https://github.com/Almouro/bitrise-giphy-step.git\n  commit: 0492814eef11db70ed8c0dc98eeefce2bf751afd\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- gif_words: such wow,awesome,shipit,yes,panda,cat,hell yeah,applaud,lgtm,surprise,suprise\n    motherfucker,yeah bitches,high five,legendary,lil bub\n  opts:\n    description: |\n      The step randomly select a gif for one the words you entered.\n\n      You should enter a comma separated list of value.\n      The default is \"such wow,awesome,shipit,yes,panda,cat,hell yeah,applaud,lgtm,surprise,suprise motherfucker,yeah bitches,high five,legendary,lil bub\"\n    is_expand: false\n    is_required: true\n    title: Random Gif words\n"
  },
  {
    "path": "steps/giphy/0.2.0/step.yml",
    "content": "title: Gifs with Giphy\nsummary: Spice up your Bitrise.io logs with a random Gif from Giphy (saved into $GIF_URL)\ndescription: |\n  Spice up your Bitrise.io logs with a random Gif from Giphy\n\n  This script will add a `GIF_URL` variable to your build than you can use in the next steps.\n  Wanna send a Gif with the Slack step? Simply add `$GIF_URL` somewhere in your Gif message ;)\n\n  You need to provide your own API key.\nwebsite: https://github.com/almouro/bitrise-giphy-step\nsource_code_url: https://github.com/almouro/bitrise-giphy-step\nsupport_url: https://github.com/almouro/bitrise-giphy-step/issues\npublished_at: 2019-06-11T14:03:52.341075223+02:00\nsource:\n  git: https://github.com/almouro/bitrise-giphy-step.git\n  commit: 869c3f9dfe0485fb2509efdf7eaaaad68cd2232b\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- gif_words: such wow,awesome,shipit,yes,panda,cat,hell yeah,applaud,lgtm,surprise,suprise\n    motherfucker,yeah bitches,high five,legendary,lil bub\n  opts:\n    description: |\n      The step randomly select a gif for one the words you entered.\n\n      You should enter a comma separated list of value.\n      The default is \"such wow,awesome,shipit,yes,panda,cat,hell yeah,applaud,lgtm,surprise,suprise motherfucker,yeah bitches,high five,legendary,lil bub\"\n    is_expand: true\n    is_required: true\n    title: Random Gif words\n- api_key: dc6zaTOxFJmzC\n  opts:\n    description: |\n      Provide app API key.\n\n      You can create your app at https://developers.giphy.com/dashboard/?create=true.\n      The default is dc6zaTOxFJmzC (publicly available API key), but it usually does not work due to reaching the query limit.\n    is_expand: true\n    is_required: true\n    title: Giphy API key\noutputs:\n- GIF_URL: \"\"\n  opts:\n    description: Generated GIF (https://giphy.com/) URL.\n    is_expand: false\n    summary: Generated GIF (https://giphy.com/) URL.\n    title: GIF URL\n"
  },
  {
    "path": "steps/giphy/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/git-clone/2.0.0/step.yml",
    "content": "title: Git Clone Repository\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  **NOTE**: it will remove the specified (local) Destination Directory before cloning!\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nsummary: Clone a repository to the specified path on the VM\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2015-09-04T11:39:25.874815712+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: ab4684790e47aedcbd065977c4f435a8351db2e4\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    title: Git Commit to clone\n- opts:\n    is_expand: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    title: Git Branch to clone\n- opts:\n    is_expand: true\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    is_expand: true\n    title: 'Auth: SSH private key - without a passphrase!'\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/2.1.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  **NOTE**: it will remove the specified (local) Destination Directory before cloning!\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2015-09-10T12:44:18.947029167+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 23a96b4b4fbde779030ebec91f74a54befb7b48c\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    title: Git Commit to clone\n- opts:\n    is_expand: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    title: Git Branch to clone\n- opts:\n    is_expand: true\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    is_expand: true\n    title: 'Auth: SSH private key - without a passphrase!'\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/2.2.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  **NOTE**: it will remove the specified (local) Destination Directory before cloning!\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2015-09-11T14:16:20.934327752+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 83cde19ebd5dd80b5b339a40071c293abeb888b9\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    title: Git Commit to clone\n- opts:\n    is_expand: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    title: Git Branch to clone\n- opts:\n    is_expand: true\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    is_required: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    is_expand: true\n    title: 'Auth: SSH private key - without a passphrase!'\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.0.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2015-09-11T15:31:19.490777899+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: c44326a08d8a4b33fb929c84e2a4a2472c842c16\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    title: Git Commit to clone\n- opts:\n    is_expand: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    title: Git Branch to clone\n- opts:\n    is_expand: true\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    is_required: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    is_expand: true\n    title: 'Auth: SSH private key - without a passphrase!'\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.1.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2015-11-06T15:41:25.636539127+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: bae58987d1a2a61aba4bcf067e7fd989e8f076e4\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    title: Git Commit to clone\n- opts:\n    is_expand: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    title: Git Branch to clone\n- opts:\n    is_expand: true\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    is_required: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    is_expand: true\n    title: 'Auth: SSH private key - without a passphrase!'\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.1.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-03-09T15:24:23.070382046+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 62d8fd8bad2fb5d080229b0632e5027708e8dab7\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    title: Git Commit to clone\n- opts:\n    is_expand: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    title: Git Branch to clone\n- opts:\n    is_expand: true\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_expand: true\n    is_required: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    is_expand: true\n    title: 'Auth: SSH private key - without a passphrase!'\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.2.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-03-31T13:07:43.340657198+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 0bb9ed90bb47df82f417dd0243a5df19c29796de\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- auth_ssh_private_key: $SSH_RSA_PRIVATE_KEY\n  opts:\n    title: 'Auth: SSH private key - without a passphrase!'\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.3.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-07-29T14:06:22.491380532+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 50fa4956f0575f031efdaa095444ac31c7849dc8\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.3.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-08-01T11:08:47.425135737+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: a7bb8a38efdac56bb700400408283234bb261882\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.3.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-08-01T16:37:24.561543658+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 9274d3eb0c7e748b5c93a32e594695ebcc8843be\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.3.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-08-08T13:32:41.874913844+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: febb17a10488a48271d7fa032c1610179fdb0948\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.3.4/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-08-24T14:19:48.016423064+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: d3f9d978a92df2fc98acb6473f0ff6d615963fe6\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $BITRISE_PULL_REQUEST\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.4.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-09-30T14:58:35.117778766+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 26e53e0641a325115ba7fbf97b3a2fba4b46ad45\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    title: Destination git Branch. Used for pull requests\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Unique build URL of this build on Bitrise.io\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: The build's API Token for the build on Bitrise.io\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.4.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2016-11-02T11:42:14.726546915+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 3965ba2987404a8f1cb4a526a7c38e021859bb2f\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    title: Destination git Branch. Used for pull requests\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Unique build URL of this build on Bitrise.io\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: The build's API Token for the build on Bitrise.io\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.4.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-03-03T16:39:30.360633711+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 9026fe2bb3b6bdad9aafc1fc04388831c3107532\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    title: Destination git Branch. Used for pull requests\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Unique build URL of this build on Bitrise.io\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: The build's API Token for the build on Bitrise.io\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.4.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-04-19T13:00:40.779284943+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: b42bf77b6c4b3bd7895e16522aa24df06ea3538e\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    title: Git Commit to clone\n- opts:\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    title: Destination git Branch. Used for pull requests\n- opts:\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Unique build URL of this build on Bitrise.io\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: The build's API Token for the build on Bitrise.io\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.4.4/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-06-09T17:18:24.605015615+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: eb09494c7500e836e80ffa8e10cf2da9d0fb3e66\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.5.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-06-26T14:14:25.20107899+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 4aef1d0f0ba05f7873df5c32c6bf41a6508a9b8a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.5.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-07-14T11:09:17.686810266+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: f23721ee9bb46f5f947a0ac3f739d26621f9c646\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.5.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-09-05T14:37:32.30551608+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: d83bc09a1ce7a2bb4251fd9aa9ede293056e653d\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.5.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-10-31T12:52:08.310511753+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: f3f0e6c2639da62d02a238b4cf5f19f85488c2dd\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.6.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-11-16T11:11:19.070252936+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 3dd1e5f1849b5d08da35b80459cc911e5c713cab\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.6.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-11-16T17:30:07.690252333+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 8e59cfc8c9c882e3c63197d3ec17b7b31470f269\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/3.6.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-11-16T18:41:58.443363972+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 6d08d90681d4d529ca813fdcedadfd1dbda2ae49\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"no\"\n  opts:\n    category: Clone config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-12-14T12:15:35.593083267+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: aa88d38d02f3990f351632ba074c33d50a1b8e92\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.10/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: !!timestamp 2018-03-20T16:12:51.501404866+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: ea87abbe93b6a22726ec2f598fab2709e3999452\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.11/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: !!timestamp 2018-05-07T10:58:04.22410614+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 6f8c88dc6b9b50261773e7b16f435e320e9027a5\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.12/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If a `pull_request_id` is provided, then all other git checkout parameters will be ignored.\n  If a git commit is provided, it will ignore the tag and branch parameters.\n  If a tag is provided instead of a git commit, then it will ignore the branch parameter.\n  If no `branch` parameter is provided, then it'll skip the `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-08-31T14:13:24.808709502Z\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 902d05eb9acf75a548dacf0711bfc4b2fd8f029a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.13/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If a `pull_request_id` is provided, then all other git checkout parameters will be ignored.\n  If a git commit is provided, it will ignore the tag and branch parameters.\n  If a tag is provided instead of a git commit, then it will ignore the branch parameter.\n  If no `branch` parameter is provided, then it'll skip the `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-11-23T13:05:46.079250198Z\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 2d977e852df1c3bd996ccf69828bb38d81ceb68e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.14/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If a `pull_request_id` is provided, then all other git checkout parameters will be ignored.\n  If a git commit is provided, it will ignore the tag and branch parameters.\n  If a tag is provided instead of a git commit, then it will ignore the branch parameter.\n  If no `branch` parameter is provided, then it'll skip the `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-12-17T15:59:19.506725796Z\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: a8ba7ff8b83787d4b94b51b6d99ef0673984aa98\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.15/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If a `pull_request_id` is provided, then all other git checkout parameters will be ignored.\n  If a git commit is provided, it will ignore the tag and branch parameters.\n  If a tag is provided instead of a git commit, then it will ignore the branch parameter.\n  If no `branch` parameter is provided, then it'll skip the `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2019-07-19T09:49:59.236428457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 1619bc32621cc24f05446027b753e04364c00834\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.16/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If a `pull_request_id` is provided, then all other git checkout parameters will be ignored.\n  If a git commit is provided, it will ignore the tag and branch parameters.\n  If a tag is provided instead of a git commit, then it will ignore the branch parameter.\n  If no `branch` parameter is provided, then it'll skip the `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2019-08-02T08:26:07.558987203Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: ffc253be89761e4d1fa96c0ed765c652be686908\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.17/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If a `pull_request_id` is provided, then all other git checkout parameters will be ignored.\n  If a git commit is provided, it will ignore the tag and branch parameters.\n  If a tag is provided instead of a git commit, then it will ignore the branch parameter.\n  If no `branch` parameter is provided, then it'll skip the `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2019-08-08T14:22:38.109971357Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 6e85c0285b5f4395faabdc02e7081c729ee49d2b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.18/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2020-01-13T08:37:25.302420699Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: d8133ebb9901197608c843624ecc511636e2fd02\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.19/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2020-08-26T15:12:30.299534445Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 830b5ff880caab5a4159b3c9c89fef6ea828e24c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-12-14T16:23:16.178315335+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: ae28701fac89091e86471478f892b708a27e83b3\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.20/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2020-08-28T07:42:37.012669588Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 58bb71f1e7b5860f86a168fb625ae1f555d8cf61\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.21/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2020-09-01T14:22:54.124165046Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 05cf90afefbef1ce0ee13d8b1995cf9ac6fa8c1d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.22/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2020-10-26T09:52:32.757942089Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 9876195f23b91d003dc8940242916272e46a5468\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.23/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2020-11-13T10:01:37.118274909Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: d15bd8e09adc4714b5cd98bb3cf42dabc6674ca9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.24/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2020-11-17T13:29:53.698235699Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: b1cbe45b5704863c4c930111edeb7aa67d38f5c1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.25/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2020-12-09T12:05:01.826625841Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 187367357bf855707cc6e9b01df5a403799a51b9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.26/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-09T14:54:35.847588903Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 83f27343245e4baa58ea4be4d8f5476d38f42078\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.27/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-11T13:38:36.104479618Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 47b323a452467d022b4e634256bab92238a1f168\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.28/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-12T10:01:50.56657926Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 9ccf0391564600b855cc32165a5e855a1bb1104d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-12-14T18:09:01.594272145+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 534588be5f4f0c5b5bbd329d22e7b5dbdedca0e7\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.4/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-12-15T12:53:49.174997582+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 0c1097b26d487b7c70efced79ba773b2dd9bcf72\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.5/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2017-12-21T15:23:02.537956411+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: af6340deccd184eb83adf63ceb66b36313783249\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.6/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-01-31T15:56:44.442661556+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: e5c448de991311c18854257b388a48c9fae800ec\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.7/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-01-31T18:51:58.293530157+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 5e0cda37543743e9f6fbd9322acb765c1102c2d4\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.8/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-02-23T15:42:30.550324992+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 6926a8f1fdee99d389d733062c92717ce315b296\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.0.9/step.yml",
    "content": "title: Git Clone Repository\nsummary: Clone a repository to the specified path on the VM\ndescription: |\n  Clones a repository based on the provided inputs.\n\n  If `pull_request_id` is provided then all other git checkout parameters will be ignored.\n  If a git commit is provided it will ignore the tag and branch parameters.\n  If no git commit but a tag is provided then it will ignore the branch parameter.\n  If no `branch` parameter is provided then it'll skip `git checkout`.\nwebsite: https://github.com/bitrise-io/steps-git-clone\nsource_code_url: https://github.com/bitrise-io/steps-git-clone\nsupport_url: https://github.com/bitrise-io/steps-git-clone/issues\npublished_at: 2018-03-02T13:09:13.568857117+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-git-clone.git\n  commit: 7a59a96553a97add9bec27e1523e58df7a8a237a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-git-clone\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch. Used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- clone_depth: null\n  opts:\n    category: Debug\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, example: `10`.\n    title: Limit fetching to the specified number of commits\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\n- opts:\n    category: Debug\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- manual_merge: \"yes\"\n  opts:\n    category: Clone Config\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the PR is from a private repository, set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.1.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-12T12:41:57.171214169Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 1dda0a4dd71480147e2a62b0a63b3b7b45f37b2f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `\"no\"`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.2.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-17T14:26:59.072098921Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: bf04daea4b4170ee17991522ced9a6c70e12fab5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: Update the registered submodules?\n    summary: Update the registered submodules?\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Clone Config\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.2.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-19T09:09:03.662024325Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 152fdb9f324b744609a04796f6c03d9e98acac6c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Destination git Branch, used for pull requests\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone Config\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Clone Config\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Clone Config\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/4.3.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-19T15:06:58.630189872Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 95922f303ea99a99fbdab8efa9367f8c3dfe20bc\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Checkout options\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/5.0.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-24T13:44:09.000656679Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 5a5f284e75381dcab53ab8b67ea5c55457015e54\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Checkout options\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    descriptions: |-\n      yes - fetches all the tags (add `--tags` to git fetch calls)\n      no - does not fetch any tags (add `--no-tags` to git fetch calls)\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/5.0.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-03-29T09:50:10.15765855Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: fe421b497bb9a19d6cbf5079015613978917c64a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Checkout options\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/5.1.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-04-07T13:00:25.355913327Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 6dae3c80db2410c493cce6cdf4b3b6ea040398ea\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Checkout options\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/5.1.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-04-09T13:48:53.579670913Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 02ca0680dad2ba96ac02ddbb0a36f5b6acb508d8\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Checkout options\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/5.1.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-05-06T06:43:10.555267893Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 0cfb786fbe27e5d7d43395a58b09650affd280d9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- limit_submodule_update_depth: \"yes\"\n  opts:\n    category: Checkout options\n    summary: Should submodules be shallow cloned with a history truncated to the latest\n      revisions.\n    title: Shallow update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.0.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-05-18T09:35:18.040355592Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: d9193b8bed8bdb242d3ec7a9eac8b7b9126e5e34\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.1.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-07-15T08:57:51.718243564Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: d10e4259c5d6dbc92b6f816a7af99247d96420cc\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.1.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-08-11T08:53:13.626112684Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 6ef1a17a7b16e7c166f48be92a474f421bd542f4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.1.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: \"The checkout process depends on the checkout properties: the Step either\n  checks out a repository state defined by a git commit or a git tag, or achieves\n  a merged state of a pull / merge request.\\nThe Step uses two solutions to achieve\n  the merged state of the pull / merge request: auto merge in the case of a merge\n  branch or diff file (provided by the Git service) and manual merge otherwise.\\nOnce\n  the desired state is checked out, the Step optionally updates the submodules. In\n  the case of pull / merge request, the Step checks out a detach head and exports\n  the achieved git state properties.\\n\\n### Configuring the Step\\n\\n1. The **Git repository\n  URL** and the ** Clone destination (local)directory path** fields are required fields\n  and are automatically filled out based on your project settings.\\nOptionally, you\n  can modify the following fields in the **Clone Config** section:\\n1. You can set\n  the **Update the registered submodules?** option to `yes` to pull the most up-to-date\n  version of the submodule from the submodule's repository.\\n2. You can set the number\n  of commits you want the Step to fetch in the **Limit fetching to the specified number\n  of commits** option. Make sure you set a decimal number.\\n\\nOther **Clone config**\n  inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid\n  issues, we suggest you to contact our Support team instead.\\n\\n### Troubleshooting\\nIf\n  you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io)\n  than on [github.com](https://github.com). You have to manually set the git clone\n  URL, register the SSH key and the webhook.\\nIf you face network issues in the case\n  of self-hosted git servers, we advise you to contact our Support Team to help you\n  out.\\nIf you face slow clone speed, set the **Limit fetching to the specified number\n  of commits** to the number of commits you want to clone instead of cloning the whole\n  commit history or you can use the Git LFS solution provided by the git provider.\\n\n  \\n### Useful links\\n\\n- [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\\n-\n  [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\\n\\n###\n  Related Steps\\n \\n- [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\\n-\n  [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\\n-\n  [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2021-09-20T13:24:55.210252633Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 3b17afb574c2f60514b0c53b6ea2d78f3171ed7b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: \"If the Git hosting provider system supports and provides this, \\nthis\n      special git ref should point to the source of the pull request.\"\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: \"Update the registered submodules to match what the superproject\n      expects by cloning missing submodules, fetching missing commits in submodules\n      and updating the working tree of the submodules.  \\nIf set to \\\"no\\\" `git fetch`\n      calls will get the `--no-recurse-submodules` flag.\"\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: \"yes - fetch all tags from the remote by adding `--tags` flag to\n      git fetch calls  \\nno - disable automatic tag following by adding `--no-tags`\n      flag to git fetch calls\"\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.2.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: |\n  The checkout process depends on the checkout properties: the Step either checks out a repository state defined by a git commit or a git tag, or achieves a merged state of a pull / merge request.\n  The Step uses two solutions to achieve the merged state of the pull / merge request: auto merge in the case of a merge branch or diff file (provided by the Git service) and manual merge otherwise.\n  Once the desired state is checked out, the Step optionally updates the submodules. In the case of pull / merge request, the Step checks out a detach head and exports the achieved git state properties.\n\n  ### Configuring the Step\n\n  1. The **Git repository URL** and the ** Clone destination (local)directory path** fields are required fields and are automatically filled out based on your project settings.\n  Optionally, you can modify the following fields in the **Clone Config** section:\n  1. You can set the **Update the registered submodules?** option to `yes` to pull the most up-to-date version of the submodule from the submodule's repository.\n  2. You can set the number of commits you want the Step to fetch in the **Limit fetching to the specified number of commits** option. Make sure you set a decimal number.\n\n  Other **Clone config** inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid issues, we suggest you to contact our Support team instead.\n\n  ### Troubleshooting\n  If you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io) than on [github.com](https://github.com). You have to manually set the git clone URL, register the SSH key and the webhook.\n  If you face network issues in the case of self-hosted git servers, we advise you to contact our Support Team to help you out.\n  If you face slow clone speed, set the **Limit fetching to the specified number of commits** to the number of commits you want to clone instead of cloning the whole commit history or you can use the Git LFS solution provided by the git provider.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2022-07-14T18:25:47.247719758Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: e50e62aebefbb97e50a1d7807224cf7ba92a782b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: |-\n      If the Git hosting provider system supports and provides this,\n      this special git ref should point to the source of the pull request.\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: |-\n      Update the registered submodules to match what the superproject expects by cloning missing submodules, fetching missing commits in submodules and updating the working tree of the submodules.\n      If set to \"no\" `git fetch` calls will get the `--no-recurse-submodules` flag.\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to git fetch calls\n      no - disable automatic tag following by adding `--no-tags` flag to git fetch calls\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.2.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: |\n  The checkout process depends on the checkout properties: the Step either checks out a repository state defined by a git commit or a git tag, or achieves a merged state of a pull / merge request.\n  The Step uses two solutions to achieve the merged state of the pull / merge request: auto merge in the case of a merge branch or diff file (provided by the Git service) and manual merge otherwise.\n  Once the desired state is checked out, the Step optionally updates the submodules. In the case of pull / merge request, the Step checks out a detach head and exports the achieved git state properties.\n\n  ### Configuring the Step\n\n  1. The **Git repository URL** and the ** Clone destination (local)directory path** fields are required fields and are automatically filled out based on your project settings.\n  Optionally, you can modify the following fields in the **Clone Config** section:\n  1. You can set the **Update the registered submodules?** option to `yes` to pull the most up-to-date version of the submodule from the submodule's repository.\n  2. You can set the number of commits you want the Step to fetch in the **Limit fetching to the specified number of commits** option. Make sure you set a decimal number.\n\n  Other **Clone config** inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid issues, we suggest you to contact our Support team instead.\n\n  ### Troubleshooting\n  If you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io) than on [github.com](https://github.com). You have to manually set the git clone URL, register the SSH key and the webhook.\n  If you face network issues in the case of self-hosted git servers, we advise you to contact our Support Team to help you out.\n  If you face slow clone speed, set the **Limit fetching to the specified number of commits** to the number of commits you want to clone instead of cloning the whole commit history or you can use the Git LFS solution provided by the git provider.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2022-07-15T12:33:52.846662701Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 75698f32366df16a4a1ee4100a32683e1f9564d0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: |-\n      If the Git hosting provider system supports and provides this,\n      this special git ref should point to the source of the pull request.\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: |-\n      Update the registered submodules to match what the superproject expects by cloning missing submodules, fetching missing commits in submodules and updating the working tree of the submodules.\n      If set to \"no\" `git fetch` calls will get the `--no-recurse-submodules` flag.\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to git fetch calls\n      no - disable automatic tag following by adding `--no-tags` flag to git fetch calls\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.2.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: |\n  The checkout process depends on the checkout properties: the Step either checks out a repository state defined by a git commit or a git tag, or achieves a merged state of a pull / merge request.\n  The Step uses two solutions to achieve the merged state of the pull / merge request: auto merge in the case of a merge branch or diff file (provided by the Git service) and manual merge otherwise.\n  Once the desired state is checked out, the Step optionally updates the submodules. In the case of pull / merge request, the Step checks out a detach head and exports the achieved git state properties.\n\n  ### Configuring the Step\n\n  1. The **Git repository URL** and the ** Clone destination (local)directory path** fields are required fields and are automatically filled out based on your project settings.\n  Optionally, you can modify the following fields in the **Clone Config** section:\n  1. You can set the **Update the registered submodules?** option to `yes` to pull the most up-to-date version of the submodule from the submodule's repository.\n  2. You can set the number of commits you want the Step to fetch in the **Limit fetching to the specified number of commits** option. Make sure you set a decimal number.\n\n  Other **Clone config** inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid issues, we suggest you to contact our Support team instead.\n\n  ### Troubleshooting\n  If you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io) than on [github.com](https://github.com). You have to manually set the git clone URL, register the SSH key and the webhook.\n  If you face network issues in the case of self-hosted git servers, we advise you to contact our Support Team to help you out.\n  If you face slow clone speed, set the **Limit fetching to the specified number of commits** to the number of commits you want to clone instead of cloning the whole commit history or you can use the Git LFS solution provided by the git provider.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2022-11-30T14:36:12.459821684Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: b9bccd63e0a32c85c7c568acdb00c492b0559f63\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: |-\n      If the Git hosting provider system supports and provides this,\n      this special git ref should point to the source of the pull request.\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: |-\n      Update the registered submodules to match what the superproject expects by cloning missing submodules, fetching missing commits in submodules and updating the working tree of the submodules.\n      If set to \"no\" `git fetch` calls will get the `--no-recurse-submodules` flag.\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to git fetch calls\n      no - disable automatic tag following by adding `--no-tags` flag to git fetch calls\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/6.2.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: |\n  The checkout process depends on the checkout properties: the Step either checks out a repository state defined by a git commit or a git tag, or achieves a merged state of a pull / merge request.\n  The Step uses two solutions to achieve the merged state of the pull / merge request: auto merge in the case of a merge branch or diff file (provided by the Git service) and manual merge otherwise.\n  Once the desired state is checked out, the Step optionally updates the submodules. In the case of pull / merge request, the Step checks out a detach head and exports the achieved git state properties.\n\n  ### Configuring the Step\n\n  1. The **Git repository URL** and the ** Clone destination (local)directory path** fields are required fields and are automatically filled out based on your project settings.\n  Optionally, you can modify the following fields in the **Clone Config** section:\n  1. You can set the **Update the registered submodules?** option to `yes` to pull the most up-to-date version of the submodule from the submodule's repository.\n  2. You can set the number of commits you want the Step to fetch in the **Limit fetching to the specified number of commits** option. Make sure you set a decimal number.\n\n  Other **Clone config** inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid issues, we suggest you to contact our Support team instead.\n\n  ### Troubleshooting\n  If you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io) than on [github.com](https://github.com). You have to manually set the git clone URL, register the SSH key and the webhook.\n  If you face network issues in the case of self-hosted git servers, we advise you to contact our Support Team to help you out.\n  If you face slow clone speed, set the **Limit fetching to the specified number of commits** to the number of commits you want to clone instead of cloning the whole commit history or you can use the Git LFS solution provided by the git provider.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2022-12-09T13:08:05.771231638Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: da388c462cf25db303244d11f6a45b50dd991142\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Clone arguments\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Clone arguments\n    description: Pull request number, coming from the Git provider\n    is_dont_change_value: true\n    title: Pull request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: |-\n      Update the registered submodules to match what the superproject expects by cloning missing submodules, fetching missing commits in submodules and updating the working tree of the submodules.\n      If set to \"no\" `git fetch` calls will get the `--no-recurse-submodules` flag.\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to git fetch calls\n      no - disable automatic tag following by adding `--no-tags` flag to git fetch calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/7.0.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-01-03T09:31:01.628992985Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: f6f56378327c4d237889db8ebbc2a85174b8f530\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/7.0.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-01-09T15:31:02.942564237Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 25c3ae2ab6b955f68966dc01f8596b28337e9f88\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/7.0.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-01-30T16:34:12.266729651Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 2237d7df95a9f90e4d005dc258825abe98ad3a62\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/7.0.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: The Step checks out the defined repository state, optionally updates the\n  repository submodules and exports the achieved git repository state properties.\ndescription: |\n  The checkout process depends on the checkout properties: the Step either checks out a repository state defined by a git commit or a git tag, or achieves a merged state of a pull / merge request.\n  The Step uses two solutions to achieve the merged state of the pull / merge request: auto merge in the case of a merge branch or diff file (provided by the Git service) and manual merge otherwise.\n  Once the desired state is checked out, the Step optionally updates the submodules. In the case of pull / merge request, the Step checks out a detach head and exports the achieved git state properties.\n\n  ### Configuring the Step\n\n  1. The **Git repository URL** and the ** Clone destination (local)directory path** fields are required fields and are automatically filled out based on your project settings.\n  Optionally, you can modify the following fields in the **Clone Config** section:\n  1. You can set the **Update the registered submodules?** option to `yes` to pull the most up-to-date version of the submodule from the submodule's repository.\n  2. You can set the number of commits you want the Step to fetch in the **Limit fetching to the specified number of commits** option. Make sure you set a decimal number.\n\n  Other **Clone config** inputs are not editable unless you go to the **bitrise.yml** tab, however, to avoid issues, we suggest you to contact our Support team instead.\n\n  ### Troubleshooting\n  If you have GitHub Enterprise set up, it works slightly differently on [bitrise.io](https://www.bitrise.io) than on [github.com](https://github.com). You have to manually set the git clone URL, register the SSH key and the webhook.\n  If you face network issues in the case of self-hosted git servers, we advise you to contact our Support Team to help you out.\n  If you face slow clone speed, set the **Limit fetching to the specified number of commits** to the number of commits you want to clone instead of cloning the whole commit history or you can use the Git LFS solution provided by the git provider.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Bitrise.io Cache:Pull](https://www.bitrise.io/integrations/steps/cache-pull)\n  - [Bitrise.io Cache:Push](https://www.bitrise.io/integrations/steps/cache-push)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-02-06T22:20:49.466658422Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: b1bf5cbb9d54df0330b30813f173e6055ce8f093\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    is_required: true\n    title: Clone destination (local) directory path\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Commit to clone\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git Tag to clone\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Git branch to clone\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Destination git branch, used for pull requests\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request ID on GitHub\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Pull request git URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Clone arguments\n    is_dont_change_value: true\n    title: Merged pull request branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Clone arguments\n    description: |-\n      If the Git hosting provider system supports and provides this,\n      this special git ref should point to the source of the pull request.\n    is_dont_change_value: true\n    title: Pull request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Checkout options\n    description: |-\n      Update the registered submodules to match what the superproject expects by cloning missing submodules, fetching missing commits in submodules and updating the working tree of the submodules.\n      If set to \"no\" `git fetch` calls will get the `--no-recurse-submodules` flag.\n    title: Update the registered submodules?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- clone_depth: null\n  opts:\n    category: Checkout options\n    description: |-\n      Limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Limit fetching to the specified number of commits\n- opts:\n    category: Checkout options\n    description: |-\n      Truncate the history to the specified number of revisions.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- merge_pr: \"yes\"\n  opts:\n    category: Checkout options\n    description: |-\n      Disables merging the source and destination branches.\n      - `yes`: The default setting. Merges the source branch into the destination branch.\n      - `no`: Treats Pull Request events as Push events on the source branch.\n    summary: Allows to validate a temporary merged state.\n    title: Merge the Pull Request source branch into destination\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Checkout options\n    description: |-\n      Limit which directories should be cloned during the build. This could be useful if a repository contains multiple platforms, so called monorepositories, and the build is only targeting a single platform.\n      For example, specifying \"src/android\" the Step will only clone:\n      - contents of the root directory and\n      - contents of the \"src/android\" directory and all subdirectories of \"src/android\".\n      On the other hand, \"src/ios\" and any other directories will not be cloned.\n    title: Specify which directories to clone.\n  sparse_directories: \"\"\n- opts:\n    category: Debug\n    summary: Reset repository contents with git reset --hard HEAD and git clean -f\n      after repository updated.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- manual_merge: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      Prefer to do a manual `git merge` by default.\n      When the Pull Request is from a GitHub or Bitbucket private fork repository set this to `no`.\n    summary: Prefer to do a manual `git merge` by default.\n    title: Manual merge\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fetch_tags: \"no\"\n  opts:\n    category: Clone Config\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to git fetch calls\n      no - disable automatic tag following by adding `--no-tags` flag to git fetch calls\n    title: Should the Step fetch tags?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    title: Cloned git commit's commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    title: Cloned git commit's message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    title: Cloned git commit's message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Count will only work properly if no `--depth` option is set.\n\n      If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Cloned git commit counts\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    title: Cloned git commit's author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    title: Cloned git commit's author email address\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    title: Cloned git commit's committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    title: Cloned git commit's committer email\n"
  },
  {
    "path": "steps/git-clone/8.0.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-02-14T10:19:32.195452705Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 51506309591e323b4c666d8feb4f17dabfca5858\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.0.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-03-21T08:25:32.500633403Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: f29bfca8665382673bb64f8e9f75aed2d58e2c4a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.1.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-06-19T10:23:52.639996715Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 67b0d018398a6b028462389c9d3fe48fdf10da08\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.1.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2023-07-11T11:48:10.310181904Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: b37dd5bbbfb17bd29d1e17eeb231f352b0d57824\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\ndeps:\n  brew:\n  - name: git-lfs\n  apt_get:\n  - name: git-lfs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.1.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2024-01-23T16:12:19.057942592Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: d169faad6be55fc06f09ecab796e2a6e08d05231\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.2.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2024-02-23T09:34:48.884322423Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 51ad7701280932152113b13f9839f59639d747b2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.2.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2024-03-18T08:20:36.94209416Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: cacdd02a01f867fed632415e86f7263142f6417b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.2.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2024-06-03T06:38:20.120933072Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: bed9fb1a27d3904197977a90c643f234deedad29\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.2.3/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2025-01-06T14:24:15.943282693Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 6f23135d1fe258ed635eee0509eb28742a00c001\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.2.4/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2025-04-16T11:48:24.381783525Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 93b66d49ebe9d8bd2b87ce70371ae3ba7ca7074d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.2.5/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2025-05-05T11:54:17.056316218Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: f6cdf8f2132f22516bb4d71e326e66a45850eb04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.3.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2025-05-14T06:49:25.827395654Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 3d206a7cb9b2cd6861bce4abe653f04d14524aef\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- opts:\n    category: Debug\n    description: Prints extra performance related information for every git operation.\n    summary: Enable performance monitoring.\n    title: Performance monitoring\n    value_options:\n    - \"no\"\n    - \"yes\"\n  performance_monitoring: \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.4.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit on a branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2025-05-14T07:17:48.830340826Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 399de1bb3155e68036f96c81ea6d71e10d63303d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- opts:\n    category: Debug\n    description: Prints extra performance related information for every git operation.\n    summary: Enable performance monitoring.\n    title: Performance monitoring\n    value_options:\n    - \"no\"\n    - \"yes\"\n  performance_monitoring: \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.4.1/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit (by hash)\n  - a commit on a specific branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2026-02-24T10:25:43.288764451Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: a64e76bb6dfa8f413a889a58cdc924b8cd947da0\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/git-clone/8.4.1/bin/git-clone-darwin-amd64\n    hash: sha256-a86e24b94108a5ec26209c8ead347f9f2f6229d3d7ea97308731694ff97a47fc\n  darwin-arm64:\n    storage_uri: steps/git-clone/8.4.1/bin/git-clone-darwin-arm64\n    hash: sha256-5c38f74988f4538efe797f592675937d17c862631b6888a1ac763561b695e83f\n  linux-amd64:\n    storage_uri: steps/git-clone/8.4.1/bin/git-clone-linux-amd64\n    hash: sha256-8a35c55b5ea7c46ecd8c4099e44d0b2c9261adcd48a64d939c3986dd1d4b6dc7\n  linux-arm64:\n    storage_uri: steps/git-clone/8.4.1/bin/git-clone-linux-arm64\n    hash: sha256-d6c1705e463a4b099b21bf81316c7801331d421403a5fdca52f5d5bb3ff9b38b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- opts:\n    category: Debug\n    description: Prints extra performance related information for every git operation.\n    summary: Enable performance monitoring.\n    title: Performance monitoring\n    value_options:\n    - \"no\"\n    - \"yes\"\n  performance_monitoring: \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.4.2/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit (by hash)\n  - a commit on a specific branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2026-02-24T15:57:46.641929607Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: 839019075bc47f292c207d997f425be1b7e608c8\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/git-clone/8.4.2/bin/git-clone-darwin-amd64\n    hash: sha256-688455ad2851dbe52e834e8f052235b72de5e6ffe8f81fdae4b8ae42361fdc35\n  darwin-arm64:\n    storage_uri: steps/git-clone/8.4.2/bin/git-clone-darwin-arm64\n    hash: sha256-ed41e88c612d57026521eb5cb3ef2d26fa8f3bc55a0cb2f11cf8ae851e204d3a\n  linux-amd64:\n    storage_uri: steps/git-clone/8.4.2/bin/git-clone-linux-amd64\n    hash: sha256-bebd975b031fa384f81c70eaef24a078fd7dbff8cb3d3e00a3646175dbaba89f\n  linux-arm64:\n    storage_uri: steps/git-clone/8.4.2/bin/git-clone-linux-arm64\n    hash: sha256-223b24f23f6b6287a1f0ac73fe696b7567e97ba1460e3b849f47ac3db26d925b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- opts:\n    category: Debug\n    description: Prints extra performance related information for every git operation.\n    summary: Enable performance monitoring.\n    title: Performance monitoring\n    value_options:\n    - \"no\"\n    - \"yes\"\n  performance_monitoring: \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/8.5.0/step.yml",
    "content": "title: Git Clone Repository\nsummary: Checks out the repository, updates submodules and exports git metadata as\n  Step outputs.\ndescription: |\n  The checkout process depends on the Step settings and the build trigger parameters (coming from your git server).\n\n  Depending on the conditions, the step can checkout:\n  - the merged state of a Pull Request\n  - the head of a Pull Request\n  - a git tag\n  - a specific commit (by hash)\n  - a commit on a specific branch\n  - the head of a branch\n\n  The Step also supports more advanced features, such as updating submodules and sparse checkouts.\n\n  ### Configuring the Step\n\n  The step should work with its default configuration if build triggers and webhooks are set up correctly.\n\n  By default, the Step performs a shallow clone in most cases (fetching only the latest commit) to make the clone fast and efficient. If your workflow requires a deeper commit history, you can override this using the **Clone depth** input.\n\n  ### Useful links\n\n  - [How to register a GitHub Enterprise repository](https://discuss.bitrise.io/t/how-to-register-a-github-enterprise-repository/218)\n  - [Code security](https://devcenter.bitrise.io/getting-started/code-security/)\n\n  ### Related Steps\n\n  - [Activate SSH key (RSA private key)](https://www.bitrise.io/integrations/steps/activate-ssh-key)\n  - [Generate changelog](https://bitrise.io/integrations/steps/generate-changelog)\nwebsite: https://github.com/bitrise-steplib/steps-git-clone\nsource_code_url: https://github.com/bitrise-steplib/steps-git-clone\nsupport_url: https://github.com/bitrise-steplib/steps-git-clone/issues\npublished_at: 2026-03-10T12:57:02.304173106Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-git-clone.git\n  commit: df4081a169df74a8185a653919d223703b2200f6\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/git-clone/8.5.0/bin/git-clone-darwin-amd64\n    hash: sha256-9fa46d766238d946e851a2751b61488b422831a45bf1aa81e6afccf272deb841\n  darwin-arm64:\n    storage_uri: steps/git-clone/8.5.0/bin/git-clone-darwin-arm64\n    hash: sha256-ee75fc91ef4a4844d48b2f1413b696cc16f4b6167a7e05bf47494088b3abab28\n  linux-amd64:\n    storage_uri: steps/git-clone/8.5.0/bin/git-clone-linux-amd64\n    hash: sha256-fa440a922b61ac01f66dbd2173314249d97d595d018101cb5650b35481ddd02c\n  linux-arm64:\n    storage_uri: steps/git-clone/8.5.0/bin/git-clone-linux-arm64\n    hash: sha256-4db1f8d6536bebe74560a5d50191c704913242abebe5f403a7cdb962e434ca1f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-git-clone\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- merge_pr: \"yes\"\n  opts:\n    description: |-\n      This only applies to builds triggered by pull requests.\n\n      Options:\n      - `yes`: Depending on the information in the build trigger, either fetches the PR merge ref or creates the merged state locally.\n      - `no`: Checks out the head of the PR branch without merging it into the destination branch.\n    summary: Checkout the merged PR state instead of the PR head\n    title: Checkout merged PR state\n    value_options:\n    - \"yes\"\n    - \"no\"\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- clone_into_dir: $BITRISE_SOURCE_DIR\n  opts:\n    category: Clone options\n    description: Local directory where the repository is cloned\n    is_required: true\n    title: Clone destination directory\n- clone_depth: null\n  opts:\n    category: Clone options\n    description: |-\n      Limit fetching to the specified number of commits.\n\n      By default, the Step tries to do a shallow clone (depth of 1) if it's possible based on the build trigger parameters. If it's not possible, it applies a low depth value, unless another value is specified here.\n\n      It's not recommended to define this input because a shallow clone ensures fast clone times. Examples of when you want to override the clone depth:\n\n      - A Step in the workflow reads the commit history in order to generate a changelog\n      - A Step in the workflow runs a git diff against a previous commit\n\n      Use the value `-1` to disable the depth limit completely and fetch the entire repo history.\n    summary: Number of commits to fetch\n    title: Clone depth\n- opts:\n    category: Clone options\n    description: |-\n      Update registered submodules to match what the superproject expects.\n      If set to `no`, `git fetch` calls will use the `--no-recurse-submodules` flag.\n    title: Update submodules\n    value_options:\n    - \"yes\"\n    - \"no\"\n  update_submodules: \"yes\"\n- opts:\n    category: Clone options\n    description: |-\n      When updating submodules, limit fetching to the specified number of commits.\n      The value should be a decimal number, for example `10`.\n    title: Submodule update depth\n  submodule_update_depth: null\n- fetch_tags: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      yes - fetch all tags from the remote by adding `--tags` flag to `git fetch` calls\n      no - disable automatic tag following by adding `--no-tags` flag to `git fetch` calls\n    title: Fetch tags\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Clone options\n    description: |-\n      Limit which directories to clone using [sparse-checkout](https://git-scm.com/docs/git-sparse-checkout). This is useful for monorepos where the current workflow only needs a subfolder.\n\n      For example, specifying `src/android` the Step will only clone:\n      - contents of the root directory and\n      - contents of the `src/android` directory and all of its subdirectories\n      On the other hand, `src/ios` will not be cloned.\n\n      This input accepts one path per line, separate entries by a linebreak.\n    title: Sparse checkout directories\n  sparse_directories: \"\"\n- ignore_branch_for_commit_fetch: \"no\"\n  opts:\n    category: Clone options\n    description: |-\n      If both commit SHA and the branch are available in the build trigger params, the Step normally fetches the entire branch history.\n\n      This input overrides that default behavior:\n\n      - `yes`: Only fetch a single commit according to the provided commit SHA, ignoring older commits of the same branch. This requires the Git server to support fetching commits by SHA (uploadpack.allowReachableSHA1InWant).\n      - `no` (default): Fetch the entire branch history and check out the provided commit SHA.\n    summary: Override the default fetch behavior when checking out a specific commit.\n    title: Ignore branch for commit fetch\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Build trigger parameters\n    description: SSH or HTTPS URL of the repository to clone\n    is_dont_change_value: true\n    is_required: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    category: Build trigger parameters\n    description: Commit SHA to checkout\n    is_dont_change_value: true\n    title: Git commit to checkout\n- opts:\n    category: Build trigger parameters\n    description: Git tag to checkout\n    is_dont_change_value: true\n    title: Git tag\n  tag: $BITRISE_GIT_TAG\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Build trigger parameters\n    description: Git branch to checkout\n    is_dont_change_value: true\n    title: Git branch\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    category: Build trigger parameters\n    description: The branch that the pull request targets, such as `main`\n    is_dont_change_value: true\n    title: Pull request destination branch\n- opts:\n    category: Build trigger parameters\n    description: |-\n      URL of the source repository of a pull request.\n\n      This points to the fork repository in builds triggered by pull requests.\n    is_dont_change_value: true\n    summary: URL of the source repository of a pull request.\n    title: Pull request source repository\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the result of merging the PR branch into the destination branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/merge`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request merge ref\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: This input is the same as **Pull request merge ref**, but the provided\n      merge ref can be potentially outdated. The Step will make an attempt to check\n      it's validity and only use it for the checkout if it's up-to-date with the PR\n      head.\n    is_dont_change_value: true\n    title: Unverified pull request merge ref\n  pull_request_unverified_merge_branch: $BITRISEIO_PULL_REQUEST_UNVERIFIED_MERGE_BRANCH\n- opts:\n    category: Build trigger parameters\n    description: |-\n      Git ref pointing to the head of the PR branch. Even if the source of the PR is a fork, this is a reference to the destination repository.\n\n      Example: `refs/pull/14/head`\n\n      Note: not all Git services provide this value.\n    is_dont_change_value: true\n    title: Pull request head ref\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- opts:\n    category: Debug\n    description: Reset repository contents with `git reset --hard HEAD` and `git clean\n      -f` before fetching.\n    summary: Reset repository before fetching.\n    title: Reset repository\n    value_options:\n    - \"No\"\n    - \"Yes\"\n  reset_repository: \"No\"\n- opts:\n    category: Debug\n    description: Prints extra performance related information for every git operation.\n    summary: Enable performance monitoring.\n    title: Performance monitoring\n    value_options:\n    - \"no\"\n    - \"yes\"\n  performance_monitoring: \"no\"\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Unique build URL of this build on Bitrise.io\n    is_dont_change_value: true\n    summary: Unique build URL of this build on Bitrise.io\n    title: Bitrise Build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: The build's API Token for the build on Bitrise.io\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: The build's API Token for the build on Bitrise.io\n    title: Bitrise Build API Token\noutputs:\n- GIT_CLONE_COMMIT_HASH: null\n  opts:\n    description: SHA hash of the checked-out commit.\n    title: Commit hash\n- GIT_CLONE_COMMIT_MESSAGE_SUBJECT: null\n  opts:\n    description: Commit message of the checked-out commit.\n    title: Commit message subject\n- GIT_CLONE_COMMIT_MESSAGE_BODY: null\n  opts:\n    description: Commit message body of the checked-out commit.\n    title: Commit message body\n- GIT_CLONE_COMMIT_COUNT: null\n  opts:\n    description: |-\n      Commit count after checkout.\n\n      Count will only work properly if no `--depth` option is set. If `--depth` is set then the history truncated to the specified number of commits. Count will **not** fail but will be the clone depth.\n    title: Commit count\n- GIT_CLONE_COMMIT_AUTHOR_NAME: null\n  opts:\n    description: Author of the checked-out commit.\n    title: Commit author name\n- GIT_CLONE_COMMIT_AUTHOR_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Commit author email\n- GIT_CLONE_COMMIT_COMMITTER_NAME: null\n  opts:\n    description: Committer name of the checked-out commit.\n    title: Committer name\n- GIT_CLONE_COMMIT_COMMITTER_EMAIL: null\n  opts:\n    description: Email of the checked-out commit.\n    title: Committer email\n"
  },
  {
    "path": "steps/git-clone/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/git-commit-changelog/1.0.2/step.yml",
    "content": "title: Git Commit Changelog\nsummary: Generates a changelog for deployment between two tags\ndescription: Generates a changelog for deployment between two tags\nwebsite: https://github.com/nodes-android/ci-bitrise-changelog-step\nsource_code_url: https://github.com/nodes-android/ci-bitrise-changelog-step\nsupport_url: https://github.com/nodes-android/ci-bitrise-changelog-step/issues\npublished_at: 2017-06-01T12:18:44.054369497+02:00\nsource:\n  git: https://github.com/nodes-android/ci-bitrise-changelog-step.git\n  commit: 149376f461a9506f14a345c05c71bedf95be8de0\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"true\"\noutputs:\n- COMMIT_CHANGELOG: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Environment variable containing the generated commit changelog\n"
  },
  {
    "path": "steps/git-commit-changelog/1.0.3/step.yml",
    "content": "title: Git Commit Changelog\nsummary: Generates a changelog for deployment between two tags\ndescription: Generates a changelog for deployment between two tags\nwebsite: https://github.com/nodes-android/ci-bitrise-changelog-step\nsource_code_url: https://github.com/nodes-android/ci-bitrise-changelog-step\nsupport_url: https://github.com/nodes-android/ci-bitrise-changelog-step/issues\npublished_at: 2017-06-07T18:42:30.777602554+02:00\nsource:\n  git: https://github.com/nodes-android/ci-bitrise-changelog-step.git\n  commit: e55c4fa96cb4b7194a708b3276c419b77e85c58d\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"true\"\noutputs:\n- COMMIT_CHANGELOG: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Environment variable containing the generated commit changelog\n"
  },
  {
    "path": "steps/git-commit-changelog/1.0.4/step.yml",
    "content": "title: Git Commit Changelog\nsummary: Generates a changelog for deployment between two tags\ndescription: Generates a changelog for deployment between two tags\nwebsite: https://github.com/nodes-android/ci-bitrise-changelog-step\nsource_code_url: https://github.com/nodes-android/ci-bitrise-changelog-step\nsupport_url: https://github.com/nodes-android/ci-bitrise-changelog-step/issues\npublished_at: 2017-08-08T11:08:26.154102525+02:00\nsource:\n  git: https://github.com/nodes-android/ci-bitrise-changelog-step.git\n  commit: 84004b46d3b7b767624cc57902ff51d0d3a0a53f\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"true\"\noutputs:\n- COMMIT_CHANGELOG: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Environment variable containing the generated commit changelog\n"
  },
  {
    "path": "steps/git-commit-changelog/1.0.5/step.yml",
    "content": "title: Git Commit Changelog\nsummary: Generates a changelog for deployment between two tags\ndescription: Generates a changelog for deployment between two tags\nwebsite: https://github.com/nodes-android/ci-bitrise-changelog-step\nsource_code_url: https://github.com/nodes-android/ci-bitrise-changelog-step\nsupport_url: https://github.com/nodes-android/ci-bitrise-changelog-step/issues\npublished_at: 2017-08-18T10:29:46.627644616+02:00\nsource:\n  git: https://github.com/nodes-android/ci-bitrise-changelog-step.git\n  commit: bc3fbd78684d397ecd1ba8684ec021110882e983\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"true\"\noutputs:\n- COMMIT_CHANGELOG: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Environment variable containing the generated commit changelog\n"
  },
  {
    "path": "steps/git-commit-changelog/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/git-last-commit-date/1.0.0/step.yml",
    "content": "title: Git Last Commit Date\nsummary: |\n  Reads the date of the last git commit\ndescription: |\n  Reads the date of the last git commit, then export that data to\n  environemnt variables LAST_COMMIT_DATE and LAST_COMMIT_DATE_NUMBERS.\n\n  After this you can use these environment variables in other steps.\nwebsite: https://github.com/tomcurran/bitrise-step-git-last-commit-date\nsource_code_url: https://github.com/tomcurran/bitrise-step-git-last-commit-date\nsupport_url: https://github.com/tomcurran/bitrise-step-git-last-commit-date/issues\npublished_at: 2017-09-18T22:40:35.77834787+01:00\nsource:\n  git: https://github.com/tomcurran/bitrise-step-git-last-commit-date.git\n  commit: f665b491fcbc4c345d307d06530a283d044d2cdc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\noutputs:\n- LAST_COMMIT_DATE: null\n  opts:\n    summary: The date for the last git commit in ISO 8601 format.\n    title: Last commit date\n- LAST_COMMIT_DATE_NUMBERS: null\n  opts:\n    description: |\n      The date numbers are intended to fit in the 32-bit signed two's complement integer range.\n    summary: The date for the last git commit in format YYMMDDHHmm.\n    title: Last commit date numbers\n"
  },
  {
    "path": "steps/git-last-commit-date/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/git-tag/1.0.0/step.yml",
    "content": "title: Git tag\nsummary: A simple step that create a tag to the current commit\ndescription: A simple step that create a tag to the current commit\nwebsite: https://github.com/Itelios/bitrise-steps-git-tag\nsource_code_url: https://github.com/Itelios/bitrise-steps-git-tag\nsupport_url: https://github.com/Itelios/bitrise-steps-git-tag/issues\npublished_at: 2015-12-11T16:50:07.069088152+01:00\nsource:\n  git: https://github.com/Itelios/bitrise-steps-git-tag.git\n  commit: 159632ca375ed7a90fd649f8daddf1f5262fb56f\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- git\n- vcs\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: You can set a custom tag or keep default value to tag with current build\n      number\n    title: Tag to set on current commit\n  tag: $BITRISE_BUILD_NUMBER\n- opts:\n    is_expand: true\n    is_required: false\n    title: The message associated to the tag in case you want an annoted tag\n  tag_message: null\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_required: true\n    title: Determine if your want to push the tag to your remote repository or not\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: true\n"
  },
  {
    "path": "steps/git-tag/1.1.0/step.yml",
    "content": "title: Git tag\nsummary: A simple step that create a tag to the current commit\ndescription: A simple step that create a tag to the current commit\nwebsite: https://github.com/Itelios/bitrise-steps-git-tag\nsource_code_url: https://github.com/Itelios/bitrise-steps-git-tag\nsupport_url: https://github.com/Itelios/bitrise-steps-git-tag/issues\npublished_at: 2016-12-05T10:05:39.168932446+01:00\nsource:\n  git: https://github.com/Itelios/bitrise-steps-git-tag.git\n  commit: ae8d7cbe28abacc68e9612808bdfbb15623b121c\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    summary: You can set a custom tag or keep default value to tag with current build\n      number\n    title: Tag to set on current commit\n  tag: $BITRISE_BUILD_NUMBER\n- opts:\n    is_expand: true\n    is_required: false\n    title: The message associated to the tag in case you want an annoted tag\n  tag_message: null\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_required: true\n    title: Determine if your want to push the tag to your remote repository or not\n    value_options:\n    - \"true\"\n    - \"false\"\n  push: \"true\"\n"
  },
  {
    "path": "steps/git-tag/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.0/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number/issues\npublished_at: 2018-06-14T21:16:51.282274243+02:00\nsource:\n  git: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: e2cb1a7eff22ceca25843e0eaa65adf489e9dc1a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v%s(%s)\n  opts:\n    description: |\n      Provide format of generated tag & build number\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.1/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number/issues\npublished_at: 2018-06-14T21:16:51.282274243+02:00\nsource:\n  git: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: 7d6ce6e2e1d0d03db147e296ea86d863731655c1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v%s(%s)\n  opts:\n    description: |\n      Provide format of generated tag & build number\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.10/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2020-05-27T23:27:07.765171+02:00\nsource:\n  git: https://github.com/denys-meloshyn/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: 1a61726ca3c0d34b0714c8cf65687865bf4bd969\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.13/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2021-11-18T12:24:47.192642+01:00\nsource:\n  git: https://github.com/denys-meloshyn/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: b9e4e1127fd5f4b9db69c16b1531d84a4560177c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\n- opts:\n    category: Config\n    description: |\n      If yes, the previous tag will be removed and recreated with the latest commit\n    title: Update tag if already exists?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  update_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.14/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2023-11-10T17:10:03.098767+01:00\nsource:\n  git: https://github.com/denys-meloshyn/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: 959eae61a829005d39759306974580faa6452269\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\n- opts:\n    category: Config\n    description: |\n      If yes, the previous tag will be removed and recreated with the latest commit\n    title: Update tag if already exists?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  update_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.3/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2019-08-13T22:03:47.265169+02:00\nsource:\n  git: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: 38913417a617bba5d2512704b79245825110f522\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.4/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2019-10-17T22:59:29.14586+02:00\nsource:\n  git: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: 3e618b8e4041c824d157e4ea1d22f471be330aa4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.5/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2019-12-14T10:04:46.910757+01:00\nsource:\n  git: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: f6b249853663509cfa5cda3d6a93fab3e6096126\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.6/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2020-01-05T11:42:43.322202+01:00\nsource:\n  git: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: f4a45cb2937f908fb31fb2f202a921e3d7ed6124\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.7/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2020-04-20T23:50:52.2468+02:00\nsource:\n  git: https://github.com/denys-meloshyn/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: d40a4ba7749b89996d0f701cb73a7a0b98a49fda\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/1.0.9/step.yml",
    "content": "title: Git tag project version and build number\nsummary: |\n  Git tag project version and build number\ndescription: |\n  This step will create Git tag with project version and build number\nwebsite: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsource_code_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\nsupport_url: https://github.com/ned1988/bitrise-step-git-tag-project-version-and-build-number\npublished_at: 2020-05-22T00:17:31.619066+02:00\nsource:\n  git: https://github.com/denys-meloshyn/bitrise-step-git-tag-project-version-and-build-number.git\n  commit: 81dec62316708da2357247d265cd0a2c95fa5878\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_tag_xcodeproj_path: \"\"\n  opts:\n    description: |\n      Use it with Xcode 11 and higher.\n    is_required: false\n    summary: Path to the 'xcodeproj'\n    title: Path to the 'xcodeproj'\n- bitrise_tag_info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n    is_required: true\n    summary: Path to the 'Info.plist' file\n    title: Path to the 'Info.plist'\n- bitrise_tag_format: v_VERSION_(_BUILD_)\n  opts:\n    description: |\n      Provide format of generated tag & build number. You can use the following placeholders: ``_VERSION_``, ``_BUILD_``\n    is_required: false\n    summary: Provide format of generated tag & build number\n    title: Result format\n- opts:\n    category: Config\n    description: |\n      If yes, the tag will be lightweight, i.e. not trigger a commit/push\n    title: Use lightweight tag?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  use_lightweight_tag: \"no\"\noutputs:\n- EXAMPLE_STEP_OUTPUT: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Example Step Output\n"
  },
  {
    "path": "steps/git-tag-project-version-and-build-number/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/github-release/0.10.0/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2018-11-15T10:28:18.367221274Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: 85696907023a0dc9123cb9f48373a44cdb896cf7\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scope needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    is_sensitive: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    is_sensitive: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: \"yes\"\n  opts:\n    description: Select `yes` to create a draft (unpublished) release, select `no`\n      to create a published one.\n    is_required: true\n    summary: If `no` is selected, the release will be published.\n    title: Draft\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      Specifies whether the release is identified as pre-release or not.\n      Select `yes` to identify release as pre-release, select `no` to identify the release as full release.\n      Default: `no`.\n    is_required: false\n    summary: If 'yes' is selected, the release is identifed as pre-release.\n    title: Pre-release\n    value_options:\n    - \"yes\"\n    - \"no\"\n  pre_release: \"no\"\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n"
  },
  {
    "path": "steps/github-release/0.10.1/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2019-07-19T07:57:11.281696682Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: b29bd20146494395b9d4c7676505dc89814d8ef3\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scope needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    is_sensitive: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    is_sensitive: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: \"yes\"\n  opts:\n    description: Select `yes` to create a draft (unpublished) release, select `no`\n      to create a published one.\n    is_required: true\n    summary: If `no` is selected, the release will be published.\n    title: Draft\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      Specifies whether the release is identified as pre-release or not.\n      Select `yes` to identify release as pre-release, select `no` to identify the release as full release.\n      Default: `no`.\n    is_required: false\n    summary: If 'yes' is selected, the release is identifed as pre-release.\n    title: Pre-release\n    value_options:\n    - \"yes\"\n    - \"no\"\n  pre_release: \"no\"\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n"
  },
  {
    "path": "steps/github-release/0.11.0/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2019-08-07T12:02:35.145265478Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: 3aa0adfa91bdd0516bc9ad38160818a859b4932d\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scope needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    is_sensitive: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    is_sensitive: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: \"yes\"\n  opts:\n    description: Select `yes` to create a draft (unpublished) release, select `no`\n      to create a published one.\n    is_required: true\n    summary: If `no` is selected, the release will be published.\n    title: Draft\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      Specifies whether the release is identified as pre-release or not.\n      Select `yes` to identify release as pre-release, select `no` to identify the release as full release.\n      Default: `no`.\n    is_required: false\n    summary: If 'yes' is selected, the release is identifed as pre-release.\n    title: Pre-release\n    value_options:\n    - \"yes\"\n    - \"no\"\n  pre_release: \"no\"\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n- api_base_url: https://api.github.com\n  opts:\n    description: The default value is https://api.github.com.\n    is_expand: true\n    is_required: true\n    summary: API URL for GitHub or Github Enterprise.\n    title: GitHub API base url\n- opts:\n    description: The default value is https://uploads.github.com.\n    is_expand: true\n    is_required: true\n    summary: Upload URL for GitHub or Github Enterprise.\n    title: GitHub Upload base url\n  upload_base_url: https://uploads.github.com\n"
  },
  {
    "path": "steps/github-release/0.12.0/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2024-06-05T07:28:46.337636049Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: e51f92341fad2be109b2f505469c0aaa5fd86641\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scope needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    is_sensitive: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    is_sensitive: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    summary: The body of the release.\n    title: Release body\n- generate_release_notes: \"no\"\n  opts:\n    is_required: true\n    summary: If `yes` is selected, GitHub will automatically generate release notes.\n    title: Generate Release Notes\n    value_options:\n    - \"yes\"\n    - \"no\"\n- draft: \"yes\"\n  opts:\n    description: Select `yes` to create a draft (unpublished) release, select `no`\n      to create a published one.\n    is_required: true\n    summary: If `no` is selected, the release will be published.\n    title: Draft\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      Specifies whether the release is identified as pre-release or not.\n      Select `yes` to identify release as pre-release, select `no` to identify the release as full release.\n      Default: `no`.\n    is_required: false\n    summary: If 'yes' is selected, the release is identifed as pre-release.\n    title: Pre-release\n    value_options:\n    - \"yes\"\n    - \"no\"\n  pre_release: \"no\"\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n- api_base_url: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The URL format should be http(s)://[hostname]/api/v3/\n    title: API base url for GitHub Enterprise\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The URL format should be http(s)://[hostname]/api/uploads/\n    title: Upload URL for GitHub Enterprise\n  upload_base_url: null\n"
  },
  {
    "path": "steps/github-release/0.9.1/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2018-06-25T15:00:39.206370842+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: 9bf0f818403aeca67d38bdca1057b55123876656\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scopes needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: true\n  opts:\n    description: '`true` to create a draft (unpublished) release, `false` to create\n      a published one.'\n    is_required: true\n    summary: If `no` selected the release will be published.\n    title: Draft\n    value_options:\n    - true\n    - false\n"
  },
  {
    "path": "steps/github-release/0.9.2/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2018-07-05T17:21:57.005917955+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: 1b21beebebd247a3c9582029ed578e57011b4131\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scopes needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: true\n  opts:\n    description: '`true` to create a draft (unpublished) release, `false` to create\n      a published one.'\n    is_required: true\n    summary: If `no` selected the release will be published.\n    title: Draft\n    value_options:\n    - true\n    - false\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n"
  },
  {
    "path": "steps/github-release/0.9.3/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2018-07-11T11:43:09.771088906+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: 51cfe1f27e511949ebe32da6fe9f80499cc6dbec\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scopes needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: true\n  opts:\n    description: '`yes` to create a draft (unpublished) release, `no` to create a\n      published one.'\n    is_required: true\n    summary: If `no` selected the release will be published.\n    title: Draft\n    value_options:\n    - \"yes\"\n    - \"no\"\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n"
  },
  {
    "path": "steps/github-release/0.9.4/step.yml",
    "content": "title: Github Release\nsummary: Create Github Release\ndescription: Create Github Release\nwebsite: https://github.com/bitrise-steplib/steps-github-release\nsource_code_url: https://github.com/bitrise-steplib/steps-github-release\nsupport_url: https://github.com/bitrise-steplib/steps-github-release/issues\npublished_at: 2018-08-31T14:14:08.559827423Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-release.git\n  commit: 0a8c1f961326aabdadccc43e597f7ae594aa5266\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-release\ninputs:\n- api_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scope needs to be enabled for the token:\n\n      - repo/public_repo\n    is_required: true\n    is_sensitive: true\n    summary: Github Personal API token used to access the GitHub API.\n    title: Personal API token\n- opts:\n    description: Your Github user name\n    is_required: true\n    is_sensitive: true\n    summary: Your Github user name\n    title: Username\n  username: null\n- opts:\n    description: |-\n      URL of the Github repository to release.\n\n      Available formats:\n\n      - https://hostname/owner/repository.git\n      - git@hostname:owner/repository.git\n      - ssh://git@hostname:port/owner/repository.git\n    is_required: true\n    summary: Github repository URL\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    is_required: true\n    summary: The name of the tag.\n    title: Tag\n  tag: $BITRISE_GIT_TAG\n- commit: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"Specifies the commitish value that determines where the Git tag\n      is created from. \\nCan be any branch or commit SHA. \\nUnused if the Git tag\n      already exists. \\nDefault: the repository's default branch (usually master).\"\n    is_required: true\n    summary: The commit of the tag\n    title: Commit\n- name: null\n  opts:\n    is_required: true\n    summary: The name of the release.\n    title: Release name\n- body: null\n  opts:\n    is_required: true\n    summary: The body of the release.\n    title: Release body\n- draft: \"yes\"\n  opts:\n    description: Select `yes` to create a draft (unpublished) release, select `no`\n      to create a published one.\n    is_required: true\n    summary: If `no` is selected, the release will be published.\n    title: Draft\n    value_options:\n    - \"yes\"\n    - \"no\"\n- files_to_upload: null\n  opts:\n    description: |-\n      One file path per line to upload to the release assets section. Optionally you can use a `|` separator at the end of the path\n      to set the uploaded file's name.\n\n      Example to use the file's __original name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk\n      ```\n\n      Example to use __custom file name__:\n\n      ```\n      $BITRISE_DEPLOY_DIR/app-debug.apk|mycompany_debug_app.apk\n      $BITRISE_DEPLOY_DIR/app-debug-androidTest.apk|mycompany_debug_app_test.apk\n      ```\n    summary: One file path per line to upload to the release assets section.\n    title: Files to upload\n"
  },
  {
    "path": "steps/github-release/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/github-release-downloader/0.0.1/step.yml",
    "content": "title: github-release-downloader\nsummary: |\n  Download any assets from GitHub releases\ndescription: |\n  Download any assets from GitHub releases\nwebsite: https://github.com/wakwak3125/bitrise-step-github-release-downloader\nsource_code_url: https://github.com/wakwak3125/bitrise-step-github-release-downloader\nsupport_url: https://github.com/wakwak3125/bitrise-step-github-release-downloader/issues\npublished_at: 2018-07-31T10:48:07.574647392+09:00\nsource:\n  git: https://github.com/wakwak3125/bitrise-step-github-release-downloader.git\n  commit: 7b9794088d191fcc5ed06d15b031bd8159aaf233\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/wakwak3125/bitrise-step-github-release-downloader\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n      Create your own token: https://github.com/settings/tokens\n      The following scopes needs to be enabled for the token:\n      - repo/publick_repo\n    is_expand: true\n    is_required: true\n    summary: Your access token to access the repository\n    title: GitHub Access Token\n- opts:\n    description: |-\n      Tag for download.\n      Set **latest** to always download latest assets.\n    title: Tag for download\n  tag: null\n- opts:\n    description: Download file names.(You can separete with comma. e.g)file1,file2,file3)\n    is_required: true\n    title: Download file names\n  source: null\n- opts:\n    description: Repository Url that you want to access\n    is_required: true\n    title: Repository Url that you want to access\n  repository_url: null\n"
  },
  {
    "path": "steps/github-release-downloader/0.0.2/step.yml",
    "content": "title: github-release-downloader\nsummary: |\n  Download any assets from GitHub releases\ndescription: |\n  Download any assets from GitHub releases\nwebsite: https://github.com/wakwak3125/bitrise-step-github-release-downloader\nsource_code_url: https://github.com/wakwak3125/bitrise-step-github-release-downloader\nsupport_url: https://github.com/wakwak3125/bitrise-step-github-release-downloader/issues\npublished_at: 2018-08-01T16:34:53.260145684+09:00\nsource:\n  git: https://github.com/wakwak3125/bitrise-step-github-release-downloader.git\n  commit: 0b9c91f2f59849ac85c50ea5442b0da5ef0a387b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/wakwak3125/bitrise-step-github-release-downloader\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scopes needs to be enabled for the token:\n\n        - repo/publick_repo\n    is_expand: true\n    is_required: true\n    summary: Your access token to access the repository\n    title: GitHub Access Token\n- opts:\n    description: |-\n      Tag for download.\n      Set **latest** to always download latest assets.\n    is_expand: true\n    is_required: true\n    title: Tag for download\n  tag: latest\n- opts:\n    description: \"Download file names.(You can separete with comma. \\n\\ne.g)file1,file2,file3\"\n    is_expand: true\n    is_required: true\n    title: Download file names\n  source: null\n- opts:\n    description: Repository Url that you want to access\n    is_expand: true\n    is_required: true\n    title: Repository Url that you want to access\n  repository_url: null\n"
  },
  {
    "path": "steps/github-release-downloader/0.0.3/step.yml",
    "content": "title: github-release-downloader\nsummary: |\n  Download any assets from GitHub releases\ndescription: |\n  Download any assets from GitHub releases\nwebsite: https://github.com/wakwak3125/bitrise-step-github-release-downloader\nsource_code_url: https://github.com/wakwak3125/bitrise-step-github-release-downloader\nsupport_url: https://github.com/wakwak3125/bitrise-step-github-release-downloader/issues\npublished_at: 2018-08-01T21:24:37.409281258+09:00\nsource:\n  git: https://github.com/wakwak3125/bitrise-step-github-release-downloader.git\n  commit: 334d0dcc351aeb07880abe4a9555aa0640810442\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/wakwak3125/bitrise-step-github-release-downloader\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\ninputs:\n- github_access_token: null\n  opts:\n    description: |-\n      Github Personal API token used to access the GitHub API.\n\n      Create your own token: https://github.com/settings/tokens\n\n      The following scopes needs to be enabled for the token:\n\n        - repo/publick_repo\n    is_expand: true\n    is_required: true\n    summary: Your access token to access the repository\n    title: GitHub Access Token\n- opts:\n    description: |-\n      Tag for download.\n      Set **latest** to always download latest assets.\n    is_expand: true\n    is_required: true\n    title: Tag for download\n  tag: latest\n- opts:\n    description: \"Download file names.(You can separete with comma. \\n\\ne.g)file1,file2,file3\"\n    is_expand: true\n    is_required: true\n    title: Download file names\n  source: null\n- opts:\n    description: Repository Url that you want to access\n    is_expand: true\n    is_required: true\n    title: Repository Url that you want to access\n  repository_url: null\n"
  },
  {
    "path": "steps/github-release-downloader/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/github-script-runner/0.0.1/step.yml",
    "content": "title: GitHub Script Runner\nsummary: Downloads and Runs a bash script stored on a private GitHub repo.\ndescription: |\n  Downloads and Runs a bash script stored on a private GitHub repo.\n\n  ### Configuring the Step\n\n  Before using the step, you need to push your bash script into a private GitHub repository and set up a GitHub personal access token with read permission on the same repository.\n\n  1. The \"file raw path\" param expects the full path of the script file\n  \"https://raw.githubusercontent.com/{owner}/{repo}/{branch}/{file}\"\n\n  2. The \"run script\" param indicates that the script should be run after the download\n  \"yes\" to run the bash script and \"no\" to just download the raw file\n\n  3. The \"github access token\" param must be a Bitrise Secret config\n\n  ### Troubleshooting\n\n  If the Step fails, check if the given GitHub Personal Access Token has read permission on the script's repository.\n\n  ### Useful links\n\n  https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token\nwebsite: https://github.com/AndersonLasak/bitrise-step-github-script-runner\nsource_code_url: https://github.com/AndersonLasak/bitrise-step-github-script-runner\nsupport_url: https://github.com/AndersonLasak/bitrise-step-github-script-runner/issues\npublished_at: 2021-06-25T18:56:15.109701-03:00\nsource:\n  git: https://github.com/AndersonLasak/bitrise-step-github-script-runner.git\n  commit: a0f3739d2390b52a1e7aefdcad4f1a1db8489ce8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path should contain the owner, repository, branch and filename with its extension, like follow:\\n\\n\n      \"https://raw.githubusercontent.com/{owner}/{repo}/{branch}/{file}\"\n    is_expand: true\n    is_required: true\n    title: The file raw path\n    value_options: []\n  raw_file_path: null\n- opts:\n    description: |\n      Indicates if the downloaded file is a bash script that should be run, use \"yes\" to run the bash script and \"no\" to just download the raw file.\n    is_expand: true\n    is_required: true\n    title: Field that says if the script should be run\n    value_options:\n    - \"no\"\n    - \"yes\"\n  run_script: \"yes\"\n- github_access_token: null\n  opts:\n    description: |\n      A personal access token is required to download the raw file via GitHub v3 API.\\n\\n\n      For more information visit the official page:\\n\n      https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: The personal access token from your GitHub account\n    value_options: []\n"
  },
  {
    "path": "steps/github-script-runner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/github-status/0.9.0/step.yml",
    "content": "title: Step GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2016-12-01T16:09:35.004645704+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 6b1d49a77835794a21a81c3ed041304d4b5a0c4b\ntype_tags:\n- github\n- status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n"
  },
  {
    "path": "steps/github-status/0.9.1/step.yml",
    "content": "title: Step GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2017-01-27T10:58:32.360251309+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: b3b5af4c084b790491a5c7ff8a22035afc6d8a0b\ntype_tags:\n- github\n- status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n"
  },
  {
    "path": "steps/github-status/1.0.1/step.yml",
    "content": "title: Step GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2017-02-09T10:47:28.289019904+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: f5e1717c1586b08eedc60b9dddff11c1fd62c43e\ntype_tags:\n- github\n- status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, success, error, or failure.\n    summary: \"\"\n    title: Set Specific Status\n  set_specific_status: \"\"\n"
  },
  {
    "path": "steps/github-status/1.0.3/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2017-03-21T14:14:47.232081751+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 33231478d2563e6c3bea321c60163dd309cab12d\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, success, error, or failure.\n    summary: \"\"\n    title: Set Specific Status\n  set_specific_status: \"\"\n"
  },
  {
    "path": "steps/github-status/1.0.4/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-02-23T13:34:43.113199227+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: e6e68a2f17f87a6d49e60ad6eeafcafcc9faedd7\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, success, error, or failure.\n    summary: \"\"\n    title: Set Specific Status\n  set_specific_status: \"\"\n"
  },
  {
    "path": "steps/github-status/1.1.0/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-02-26T15:57:19.651323309+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 35d0aaba55e278e1daa84c3ba0d32e0f3e8cad60\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: The Identifier to be used for this status\n    is_required: true\n    summary: \"\"\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, success, error, or failure.\n    summary: \"\"\n    title: Set Specific Status\n  set_specific_status: \"\"\n"
  },
  {
    "path": "steps/github-status/1.1.1/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-03-05T12:54:58.493419534+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 4c0c0a30f53ae55b08066c73eccb448ba1b64278\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Build URL with detailed information for the build\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: The Identifier to be used for this status\n    is_required: true\n    summary: \"\"\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, success, error, or failure.\n    summary: \"\"\n    title: Set Specific Status\n  set_specific_status: \"\"\n"
  },
  {
    "path": "steps/github-status/2.0.0/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-03-09T11:46:54.245300945+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: e817f780d85df6fdf6cd35cbd05c78174ca56812\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n"
  },
  {
    "path": "steps/github-status/2.1.0/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: !!timestamp 2018-03-14T12:09:22.769304533+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 4f3c7693b1154f67959c17087e7cff9909045866\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_required: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n"
  },
  {
    "path": "steps/github-status/2.2.0/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-08-31T08:05:54.458360791Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 7a8c194dc98ac8203dc9b9773e6504e379e73c93\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n"
  },
  {
    "path": "steps/github-status/2.2.1/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-09-13T11:01:18.900468078Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 7d74c00ce4e7ad2d8ab5f4d82e90324fb5fc457f\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n"
  },
  {
    "path": "steps/github-status/2.2.2/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2018-09-17T10:23:22.980931228Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 5f642e09f372ec9b87b9d4624b4367baf8263ba4\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n"
  },
  {
    "path": "steps/github-status/2.3.1/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2020-05-27T16:22:23.941886515Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: f7bd7c4815be2e946690f89dbc73e52bf5ec7e05\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself at the following url:\n      [https://github.com/settings/tokens](https://github.com/settings/tokens)\n\n      Add repo/repo:status scope to the generated token, to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- opts:\n    description: Prints extra logs.\n    summary: Prints extra logs.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/github-status/2.3.3/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories\ndescription: Update commit status for GitHub repositories\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2020-10-01T11:54:44.300632572Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: f526598f5e719d6a46af2d1dda1d8b7d55035e17\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself [here](https://github.com/settings/tokens).\n\n      Add repo/repo:status scope to the generated token to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: GitHub auth token with proper scopes\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: The URL of the repository\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: Commit hash to check\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    summary: Build URL for this status\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    summary: GitHub API base URL\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- opts:\n    description: Prints extra logs.\n    summary: Prints extra logs.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/github-status/2.3.4/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories.\ndescription: \"This Step updates the commit status for a GitHub repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  In the **Authorization token for GitHub applications** Step input, you need to provide\n  a token you generated on [GitHub](https://github.com/settings/tokens), with `repo/repo:status`\n  scope.\\n2. The **Repository URL** input is populated automatically with a variable\n  the value of which is taken from the repository field of the Settings of your app.\\n3.\n  The **Commit hash** input is filled in by default with the variable inherited from\n  the **Git Clone** Step.\\n4. The **Build URL** Step input is also filled in automatically,\n  this is the URL that is forwarded to GitHub as the source of the status.\\n5. The\n  **GitHub API base URL** is the URL for GitHub's API service, has to be modified\n  if you are running an Enterprise GitHub instance.\\n6. With the **Status Identifier**\n  Step input, you can adjust under what name which CI status shows up.\\n7. The input\n  **Set Specific Status** has a default value of `auto` which reflects the status\n  of the build, but this input allows you to update the commit with any given status,\n  regardless of the outcome of the build.\\n8. The **Description** input allows you\n  to provide a short description for the status. \\n9. **Verbose logging** can be turned\n  on to print out additional information within the build logs. \\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitHub Enterprise, make sure your API base URL is set to `http(s)://hostname/api/v3/`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitHub Statuses](https://developer.github.com/v3/repos/statuses/)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2020-11-20T12:53:02.172841707Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 42b5ba207bbbeb2292ae227b11aae2f5cc964283\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself [here](https://github.com/settings/tokens).\n\n      Add repo/repo:status scope to the generated token to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: GitHub auth token with proper scopes\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: The URL of the repository\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: Commit hash to check\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    summary: Build URL for this status\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    summary: GitHub API base URL\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no Step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- opts:\n    description: Prints extra logs.\n    summary: Prints extra logs.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/github-status/2.4.0/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories.\ndescription: \"This Step updates the commit status for a GitHub repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  In the **Authorization token for GitHub applications** Step input, you need to provide\n  a token you generated on [GitHub](https://github.com/settings/tokens), with `repo/repo:status`\n  scope.\\n2. The **Repository URL** input is populated automatically with a variable\n  the value of which is taken from the repository field of the Settings of your app.\\n3.\n  The **Commit hash** input is filled in by default with the variable inherited from\n  the **Git Clone** Step.\\n4. The **Build URL** Step input is also filled in automatically,\n  this is the URL that is forwarded to GitHub as the source of the status.\\n5. The\n  **GitHub API base URL** is the URL for GitHub's API service, has to be modified\n  if you are running an Enterprise GitHub instance.\\n6. With the **Status Identifier**\n  Step input, you can adjust under what name which CI status shows up.\\n7. The input\n  **Set Specific Status** has a default value of `auto` which reflects the status\n  of the build, but this input allows you to update the commit with any given status,\n  regardless of the outcome of the build.\\n8. The **Description** input allows you\n  to provide a short description for the status. \\n9. **Verbose logging** can be turned\n  on to print out additional information within the build logs. \\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitHub Enterprise, make sure your API base URL is set to `http(s)://hostname/api/v3/`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitHub Statuses](https://developer.github.com/v3/repos/statuses/)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2021-06-23T16:40:55.873749043Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: faffdc295cf0c24d3f21571c3ba3c6bd5c89638e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself [here](https://github.com/settings/tokens).\n\n      Add repo/repo:status scope to the generated token to allow to update the repo status.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: GitHub auth token with proper scopes\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: The URL of the repository\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: Commit hash to check\n    title: Commit hash\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_expand: true\n    is_required: true\n    summary: Build URL for this status\n    title: Build URL\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_expand: true\n    summary: GitHub API base URL\n    title: GitHub API base url\n- opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n      Default: `default`\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no Step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- opts:\n    description: Prints extra logs.\n    summary: Prints extra logs.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n"
  },
  {
    "path": "steps/github-status/3.0.0/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories.\ndescription: \"This Step updates the commit status for a GitHub repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  In the **Authorization token for GitHub applications** Step input, you need to provide\n  a token you generated on [GitHub](https://github.com/settings/tokens), with `repo/repo:status`\n  scope.\\n2. The **Repository URL** input is populated automatically with a variable\n  the value of which is taken from the repository field of the Settings of your app.\\n3.\n  The **Commit hash** input is filled in by default with the variable inherited from\n  the **Git Clone** Step.\\n4. The **Build URL** Step input is also filled in automatically,\n  this is the URL that is forwarded to GitHub as the source of the status.\\n5. The\n  **GitHub API base URL** is the URL for GitHub's API service, has to be modified\n  if you are running an Enterprise GitHub instance.\\n6. With the **Status Identifier**\n  Step input, you can adjust under what name which CI status shows up.\\n7. The input\n  **Set Specific Status** has a default value of `auto` which reflects the status\n  of the build, but this input allows you to update the commit with any given status,\n  regardless of the outcome of the build.\\n8. The **Description** input allows you\n  to provide a short description for the status. \\n9. **Verbose logging** can be turned\n  on to print out additional information within the build logs. \\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitHub Enterprise, make sure your API base URL is set to `http(s)://hostname/api/v3/`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitHub Statuses](https://developer.github.com/v3/repos/statuses/)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2023-03-20T14:06:46.382900356Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 3b58eaf387b72b646ca27d63f3baec1df7572d22\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself [here](https://github.com/settings/tokens).\n\n      Add repo/repo:status scope to the generated token to allow to update the repo status.\n    is_required: true\n    is_sensitive: true\n    summary: GitHub auth token with proper scopes\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: The URL of the repository\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: Commit hash to check\n    title: Commit hash\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no Step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- opts:\n    description: A string label to differentiate this status from the status of other\n      systems.\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: GitHub API base URL\n    title: GitHub API base url\n- opts:\n    description: Prints extra logs.\n    summary: Prints extra logs.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Build.\n    is_dont_change_value: true\n    summary: It sets the status as if the Build had finished already\n    title: Build Status\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_dont_change_value: true\n    summary: Build URL for this status\n    title: Build URL\n- opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Pipeline Build.\n    is_dont_change_value: true\n    summary: It sets the status as if the Pipeline Build had finished with the previous\n      stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- opts:\n    description: |-\n      The target URL of the Pipeline Build to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_dont_change_value: true\n    summary: The URL of the Pipeline Build (if applicable)\n    title: Pipeline Build URL\n  pipeline_build_url: $BITRISEIO_PIPELINE_BUILD_URL\n"
  },
  {
    "path": "steps/github-status/3.0.1/step.yml",
    "content": "title: GitHub Status\nsummary: Update commit status for GitHub repositories.\ndescription: \"This Step updates the commit status for a GitHub repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  In the **Authorization token for GitHub applications** Step input, you need to provide\n  a token you generated on [GitHub](https://github.com/settings/tokens), with `repo/repo:status`\n  scope.\\n2. The **Repository URL** input is populated automatically with a variable\n  the value of which is taken from the repository field of the Settings of your app.\\n3.\n  The **Commit hash** input is filled in by default with the variable inherited from\n  the **Git Clone** Step.\\n4. The **Build URL** Step input is also filled in automatically,\n  this is the URL that is forwarded to GitHub as the source of the status.\\n5. The\n  **GitHub API base URL** is the URL for GitHub's API service, has to be modified\n  if you are running an Enterprise GitHub instance.\\n6. With the **Status Identifier**\n  Step input, you can adjust under what name which CI status shows up.\\n7. The input\n  **Set Specific Status** has a default value of `auto` which reflects the status\n  of the build, but this input allows you to update the commit with any given status,\n  regardless of the outcome of the build.\\n8. The **Description** input allows you\n  to provide a short description for the status. \\n9. **Verbose logging** can be turned\n  on to print out additional information within the build logs. \\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitHub Enterprise, make sure your API base URL is set to `http(s)://hostname/api/v3/`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitHub Statuses](https://developer.github.com/v3/repos/statuses/)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-github-status\nsource_code_url: https://github.com/bitrise-steplib/steps-github-status\nsupport_url: https://github.com/bitrise-steplib/steps-github-status/issues\npublished_at: 2023-04-20T07:56:07.066830713Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-github-status.git\n  commit: 889ac241a9c3e7f0e63cf262c117b67a3e9319d3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-github-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- auth_token: \"\"\n  opts:\n    description: |-\n      Authorization token for GitHub applications\n\n      You can create one for yourself [here](https://github.com/settings/tokens).\n\n      Add repo/repo:status scope to the generated token to allow to update the repo status.\n    is_required: true\n    is_sensitive: true\n    summary: GitHub auth token with proper scopes\n    title: GitHub auth token\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: The URL of the repository\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: Commit hash to check\n    title: Commit hash\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no Step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  set_specific_status: auto\n- description: null\n  opts:\n    description: |-\n      A short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- opts:\n    description: A string label to differentiate this status from the status of other\n      systems.\n    summary: The Identifier to be used for this status\n    title: Status Identifier\n  status_identifier: continuous-integration/bitrise\n- api_base_url: https://api.github.com\n  opts:\n    description: API URL for GitHub or Github Enterprise\n    is_required: true\n    summary: GitHub API base URL\n    title: GitHub API base url\n- opts:\n    description: Prints extra logs.\n    summary: Prints extra logs.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Build.\n    is_dont_change_value: true\n    summary: It sets the status as if the Build had finished already\n    title: Build Status\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_dont_change_value: true\n    summary: Build URL for this status\n    title: Build URL\n- opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Pipeline Build.\n    is_dont_change_value: true\n    summary: It sets the status as if the Pipeline Build had finished with the previous\n      stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- opts:\n    description: |-\n      The target URL of the Pipeline Build to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_dont_change_value: true\n    summary: The URL of the Pipeline Build (if applicable)\n    title: Pipeline Build URL\n  pipeline_build_url: $BITRISEIO_PIPELINE_BUILD_URL\n"
  },
  {
    "path": "steps/github-status/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/gitlab-status/0.10.0/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2019-11-13T16:09:18.634634019Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 8c2a80d89b9a60adb1ca13b8ef3ba3d0c6ed8402\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, pending, running, success, failed or canceled.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed\n      previously) and `failed` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.11.0/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2020-03-16T11:51:56.591449188Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 222f187ee5a12b3523709a9e92bc2d0fcaf4896d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the step will send `success`\n      status if the current build status is `success` \\n(no step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.0/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2020-04-28T07:57:42.452385168Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: acaaaf14085cc5c4d2a2fb71bf3e36bb923af9ea\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the step will send `success`\n      status if the current build status is `success` \\n(no step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.1/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2020-05-22T14:00:53.405640206Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 341a6f87065cfbfb7063cf985966d0b994fbb805\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the step will send `success`\n      status if the current build status is `success` \\n(no step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.2/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2020-07-10T08:32:21.597238967Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 18a987ed31713ee5abed71dae9f5448bebd8a380\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the step will send `success`\n      status if the current build status is `success` \\n(no step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.3/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2020-08-13T10:53:20.866072928Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 638baefe9602eacb0a8c3b83ec578e6fb24524b0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the step will send `success`\n      status if the current build status is `success` \\n(no step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.4/step.yml",
    "content": "title: GitLab Status\nsummary: Update commit status for GitLab repositories.\ndescription: \"This Step updates the commit status for a GitLab repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  The **GitLab API base URL** should be `https://gitlab.com/api/v4/` for cloud-hosted\n  GitLabs. \\n2. In the **GitLab private token** Step input, you need to provide an\n  access token you generated in your User Settings on GitLab.\\n3. The **Repository\n  URL** input is populated automatically with a variable the value of which is taken\n  from the repository field of the Settings of your app.\\n4. You can also select a\n  specific branch or tag to post the status to, but it's going to be sent to the default\n  branch unless you change it.\\n5. The **Commit hash** input is filled in by default\n  with the variable inherited from the **Git Clone** Step.\\n6. The **Target URL**\n  Step input is the URL of the build, which is forwarded to GitHub as the source of\n  the status.\\n7. The **Context** Step input, allows you to label the status with\n  a name.\\n8. The input **Set Specific Status** input has a default value of `auto`\n  which reflects the status of the build, but this input allows you to update the\n  commit with any given status, regardless of the outcome of the build.\\n9. The **Description**\n  input allows you to provide a short description for the status. \\n10. Code **Coverage**\n  percent can also be sent from the build to the commit. \\n\\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitLab Enterprise, make sure your API base URL is set to `https://gitlab.local.domain/api/v4`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitLab access tokens](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2020-11-20T12:47:48.237316339Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 767074fc1b57c8d97f1b0b8a6da4170c652742d1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this Step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the Step will send `success`\n      status if the current build status is `success` \\n(no Step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.5/step.yml",
    "content": "title: GitLab Status\nsummary: Update commit status for GitLab repositories.\ndescription: \"This Step updates the commit status for a GitLab repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  The **GitLab API base URL** should be `https://gitlab.com/api/v4/` for cloud-hosted\n  GitLabs. \\n2. In the **GitLab private token** Step input, you need to provide an\n  access token you generated in your User Settings on GitLab.\\n3. The **Repository\n  URL** input is populated automatically with a variable the value of which is taken\n  from the repository field of the Settings of your app.\\n4. You can also select a\n  specific branch or tag to post the status to, but it's going to be sent to the default\n  branch unless you change it.\\n5. The **Commit hash** input is filled in by default\n  with the variable inherited from the **Git Clone** Step.\\n6. The **Target URL**\n  Step input is the URL of the build, which is forwarded to GitHub as the source of\n  the status.\\n7. The **Context** Step input, allows you to label the status with\n  a name.\\n8. The input **Set Specific Status** input has a default value of `auto`\n  which reflects the status of the build, but this input allows you to update the\n  commit with any given status, regardless of the outcome of the build.\\n9. The **Description**\n  input allows you to provide a short description for the status. \\n10. Code **Coverage**\n  percent can also be sent from the build to the commit. \\n\\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitLab Enterprise, make sure your API base URL is set to `https://gitlab.local.domain/api/v4`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitLab access tokens](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2021-04-27T18:14:22.283876199Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 190413086d96fea9737c9ff3652921ee9814b946\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this Step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the Step will send `success`\n      status if the current build status is `success` \\n(no Step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.6/step.yml",
    "content": "title: GitLab Status\nsummary: Update commit status for GitLab repositories.\ndescription: \"This Step updates the commit status for a GitLab repository (repo) of\n  your choice with this build's status. Useful anytime you can not or do not want\n  to provide Bitrise write access to your git repo.\\n\\n### Configuring the Step\\n\\n1.\n  The **GitLab API base URL** should be `https://gitlab.com/api/v4/` for cloud-hosted\n  GitLabs. \\n2. In the **GitLab private token** Step input, you need to provide an\n  access token you generated in your User Settings on GitLab.\\n3. The **Repository\n  URL** input is populated automatically with a variable the value of which is taken\n  from the repository field of the Settings of your app.\\n4. You can also select a\n  specific branch or tag to post the status to, but it's going to be sent to the default\n  branch unless you change it.\\n5. The **Commit hash** input is filled in by default\n  with the variable inherited from the **Git Clone** Step.\\n6. The **Target URL**\n  Step input is the URL of the build, which is forwarded to GitHub as the source of\n  the status.\\n7. The **Context** Step input, allows you to label the status with\n  a name.\\n8. The input **Set Specific Status** input has a default value of `auto`\n  which reflects the status of the build, but this input allows you to update the\n  commit with any given status, regardless of the outcome of the build.\\n9. The **Description**\n  input allows you to provide a short description for the status. \\n10. Code **Coverage**\n  percent can also be sent from the build to the commit. \\n\\n\\n### Troubleshooting\\n\\nIf\n  you get a 404 response when running the Step, check your token's scope and validity.\\nIf\n  you use GitLab Enterprise, make sure your API base URL is set to `https://gitlab.local.domain/api/v4`.\\nIf\n  you do not see your status being reflected, double-check **Repository URL** and\n  **Commit hash** input values. \\n\\n### Useful links\\n\\n- [GitLab access tokens](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html)\\n\\n###\n  Related Steps\\n\\n- [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\\n-\n  [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\"\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2021-05-07T10:02:40.082951237Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 1ec1596ba44ded3094f92645b52c364a231dc331\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance.\n      2. Go to User Settings > Access Tokens.\n      3. Pick a _name_ and set a _scope_ for the token.\n      4. Click on **Create personal access token** and save your new token.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    summary: \"\"\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: \"If set, this Step will set a specific status instead of reporting\n      the current build status.\\n\\nCan be one of `auto`, `pending`, `running`, `success`,\n      `failed` or `canceled`.\\nIf you select `auto`, the Step will send `success`\n      status if the current build status is `success` \\n(no Step failed previously)\n      and `failed` status if the build previously failed.\"\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.12.7/step.yml",
    "content": "title: GitLab Status\nsummary: Update commit status for GitLab repositories.\ndescription: |-\n  This Step updates the commit status for a GitLab repository (repo) of your choice with this build's status. Useful anytime you can not or do not want to provide Bitrise write access to your git repo.\n\n  ### Configuring the Step\n\n  1. The **GitLab API base URL** should be `https://gitlab.com/api/v4/` for cloud-hosted GitLabs.\n  2. In the **GitLab private token** Step input, you need to provide an access token you generated in your Project Settings or User Profile on GitLab.\n  3. The **Repository URL** input is populated automatically with a variable the value of which is taken from the repository field of the Settings of your app.\n  4. You can also select a specific branch or tag to post the status to, but it's going to be sent to the default branch unless you change it.\n  5. The **Commit hash** input is filled in by default with the variable inherited from the **Git Clone** Step.\n  6. The **Target URL** Step input is the URL of the build, which is forwarded to GitHub as the source of the status.\n  7. The **Context** Step input, allows you to label the status with a name.\n  8. The input **Set Specific Status** input has a default value of `auto` which reflects the status of the build, but this input allows you to update the commit with any given status, regardless of the outcome of the build.\n  9. The **Description** input allows you to provide a short description for the status.\n  10. Code **Coverage** percent can also be sent from the build to the commit.\n\n  ### Troubleshooting\n\n  If you get a 404 response when running the Step, check your token's scope and validity.\n  If you use GitLab Enterprise, make sure your API base URL is set to `https://gitlab.local.domain/api/v4`.\n  If you do not see your status being reflected, double-check **Repository URL** and **Commit hash** input values.\n\n  ### Useful links\n\n  - [GitLab project access tokens](https://docs.gitlab.com/user/project/settings/project_access_tokens/#create-a-project-access-token)\n  - [GitLab personal access tokens](https://docs.gitlab.com/user/profile/personal_access_tokens/#create-a-personal-access-token)\n\n  ### Related Steps\n\n  - [Git-Clone](https://www.bitrise.io/integrations/steps/git-clone)\n  - [Build Status Change](https://www.bitrise.io/integrations/steps/build-status-change)\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2026-05-12T13:56:21.930602223Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 41388b6e5b49bc9af00e7586c38949b7e0b308d0\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gitlab-status/0.12.7/bin/gitlab-status-darwin-amd64\n    hash: sha256-7550525276e494914a77d4a062528339a20956061d09861623a08fa9c41d9b1a\n  darwin-arm64:\n    storage_uri: steps/gitlab-status/0.12.7/bin/gitlab-status-darwin-arm64\n    hash: sha256-07595d45897001907c450ed3b5bd1eaf5cffd88238038cb24cfc422e856d687c\n  linux-amd64:\n    storage_uri: steps/gitlab-status/0.12.7/bin/gitlab-status-linux-amd64\n    hash: sha256-4aee66d66d59559e8c3fe8bdc267dc70f1712b4260d58d7632f68b6c3d452d08\n  linux-arm64:\n    storage_uri: steps/gitlab-status/0.12.7/bin/gitlab-status-linux-arm64\n    hash: sha256-ae3f1e39855bf6b711bc37334cc30b9a7686d2f050e3473b33e8a9d86e9c4aad\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: null\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a [project access token](https://docs.gitlab.com/user/project/settings/project_access_tokens/#create-a-project-access-token):\n      1. Log in to your GitLab instance.\n      1. Go to **Project -> Settings > Access Tokens**.\n      1. Select **Add new token**.\n      1. In **Token name**, enter a name.\n      1. Select a role for the token.\n      1. Select **scope** *api* and *read_api*.\n      1. Select **Create project access token**.\n\n      Alternatively generating a [personal access tokens](https://docs.gitlab.com/user/profile/personal_access_tokens/#create-a-personal-access-token):\n      1. Log in to your GitLab instance.\n      1. In the upper-right corner, select your avatar. Select **Edit profile**.\n      1. In the left sidebar, select **Access > Personal access tokens**.\n      1. From the **Generate token** dropdown list, select **Legacy token**.\n      1. In **Token name**, enter a name for the token.\n      1. In **Expiration date**, enter an expiry date for the token\n      1. Select **scope** *api* and *read_api*.\n      1. Select **Generate token**.\n    is_required: true\n    is_sensitive: true\n    title: GitLab private token\n  private_token: null\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- git_ref: $BITRISE_GIT_BRANCH\n  opts:\n    description: |-\n      The name of a repository branch or tag for which the status needs to be reported\n\n      In case of a same commit hash on multiple branches, _ref_  will be used so the pipeline status is updated on the correct branch.\n    is_required: true\n    title: The name of a repository branch or tag or, if not given, the default branch\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: |-\n      If set, this Step will set a specific status instead of reporting the current build status.\n\n      Can be one of `auto`, `pending`, `running`, `success`, `failed` or `canceled`.\n      If you select `auto`, the Step will send `success` status if the current build status is `success`\n      (no Step failed previously) and `failed` status if the build previously failed.\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n- coverage: null\n  opts:\n    description: |-\n      The test coverage.\n\n      Must be a floating point number between 0.0 and 100.0.\n    is_required: false\n    summary: Test coverage\n    title: Coverage\n"
  },
  {
    "path": "steps/gitlab-status/0.9.0/step.yml",
    "content": "title: GitLab status\nsummary: |\n  Update commit status for GitLab repositories\ndescription: |\n  Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2018-02-26T13:32:36.078857423+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 5ddafecdb811caaae86dac2ccdcede718cf3ac6c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitHub API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, running, success, failed or canceled.\n    summary: \"\"\n    title: Set Specific Status\n  preset_status: \"\"\n"
  },
  {
    "path": "steps/gitlab-status/0.9.1/step.yml",
    "content": "title: GitLab status\nsummary: |\n  Update commit status for GitLab repositories\ndescription: |\n  Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2018-02-26T16:07:44.732907388+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: a1c84e8b375d84c4fb42729325ac1d0f94dbc607\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, running, success, failed or canceled.\n    summary: \"\"\n    title: Set Specific Status\n  preset_status: \"\"\n"
  },
  {
    "path": "steps/gitlab-status/0.9.2/step.yml",
    "content": "title: GitLab status\nsummary: |\n  Update commit status for GitLab repositories\ndescription: |\n  Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2018-03-02T13:44:47.522955524+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: df4e5e11239d5c21f353959befeb923e191ca3bb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of pending, running, success, failed or canceled.\n    summary: \"\"\n    title: Set Specific Status\n  preset_status: \"\"\n"
  },
  {
    "path": "steps/gitlab-status/0.9.3/step.yml",
    "content": "title: GitLab status\nsummary: |\n  Update commit status for GitLab repositories\ndescription: |\n  Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2018-03-07T10:55:19.091387124+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 920f7b1d320a2d5ccb99c48bc49a126a528420a2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, pending, running, success, failed or canceled.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      and `failed` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n"
  },
  {
    "path": "steps/gitlab-status/0.9.5/step.yml",
    "content": "title: GitLab status\nsummary: |\n  Update commit status for GitLab repositories\ndescription: |\n  Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: !!timestamp 2018-03-15T12:41:34.110290714+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: c200f49a952634ffeef18bc63534eb2044a1bf26\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, pending, running, success, failed or canceled.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      and `failed` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n"
  },
  {
    "path": "steps/gitlab-status/0.9.6/step.yml",
    "content": "title: GitLab status\nsummary: Update commit status for GitLab repositories\ndescription: Update commit status for GitLab repositories\nwebsite: https://github.com/bitrise-steplib/steps-gitlab-status\nsource_code_url: https://github.com/bitrise-steplib/steps-gitlab-status\nsupport_url: https://github.com/bitrise-steplib/steps-gitlab-status/issues\npublished_at: 2018-08-31T09:28:45.084464157Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gitlab-status.git\n  commit: 11ecba6bc1bb425b8692e62c627e5f6b14eecbc6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-gitlab-status\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_base_url: \"\"\n  opts:\n    description: |-\n      API URL for GitLab or GitLab Enterprise\n\n      Example: \"https://gitlab.example.com/api/v4\"\n    is_required: true\n    summary: \"\"\n    title: GitLab API base url\n- opts:\n    description: |-\n      Authorization token for GitLab applications\n\n      Generating a personal access token:\n      1. Log in to your GitLab instance\n      2. Go to User Settings > Access Tokens\n      3. Pick a _name_ and set a _scope_ for the token\n      4. Click on **Create personal access token** and save your new token\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: GitLab private token\n  private_token: \"\"\n- opts:\n    description: The URL for the repository we are working with\n    is_required: true\n    summary: \"\"\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    description: The commit hash for the commit we are working with\n    is_required: true\n    summary: \"\"\n    title: Commit hash\n- opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitLab UI to allow users to easily see the source of the status.\n    summary: \"\"\n    title: Target URL\n  target_url: $BITRISE_BUILD_URL\n- context: Bitrise\n  opts:\n    description: |-\n      A string label to differentiate this status from the status of other systems.\n\n      If left empty, it will be `default`.\n    summary: The Identifier to be used for this status\n    title: Context\n- opts:\n    description: |-\n      If set, this step will set a specific status instead of reporting the current build status.\n\n      Can be one of auto, pending, running, success, failed or canceled.\n      If you select `auto` the step will send `success` status if the current build status is success (no step failed previously)\n      and `failed` status if the build previously failed.\n    summary: \"\"\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - running\n    - success\n    - failed\n    - canceled\n  preset_status: auto\n- description: null\n  opts:\n    description: |-\n      The short description of the status.\n\n      If left empty, it will be the status of the build.\n    summary: A short description of the status.\n    title: Description\n"
  },
  {
    "path": "steps/gitlab-status/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/go-list/0.10.0/step.yml",
    "content": "title: Go list\nsummary: Runs go list ./... command\ndescription: |-\n  Runs `go list ./...` command in the current working directory (should be your go project's dir).\n  The package list is filtered by the given exclude patterns.\nwebsite: https://github.com/bitrise-steplib/steps-go-list\nsource_code_url: https://github.com/bitrise-steplib/steps-go-list\nsupport_url: https://github.com/bitrise-steplib/steps-go-list/issues\npublished_at: 2020-09-28T10:44:41.488764887Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-list.git\n  commit: 41f6579de7b821bffbbeecca2b96bbab8e7d51a1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-list\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- exclude: '*/vendor/*'\n  opts:\n    description: \"Skip matching go packages.  \\nMultiple patterns can be specified\n      as a newline separated list.\\n\\nExamples:\\n\\n- \\\"*/vendor/*\\\"\\n- \\\"*/steps-go-list*\\\\n*/gotool*\\\"\"\n    summary: Skip matching go packages.\n    title: Exclude patterns\noutputs:\n- BITRISE_GO_PACKAGES: null\n  opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    title: List of go packages.\n"
  },
  {
    "path": "steps/go-list/0.10.1/step.yml",
    "content": "title: Go list\nsummary: Runs go list ./... command\ndescription: |-\n  Runs `go list ./...` command in the current working directory (should be your go project's dir).\n  The package list is filtered by the given exclude patterns.\nwebsite: https://github.com/bitrise-steplib/steps-go-list\nsource_code_url: https://github.com/bitrise-steplib/steps-go-list\nsupport_url: https://github.com/bitrise-steplib/steps-go-list/issues\npublished_at: 2020-10-08T10:26:30.129769307Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-list.git\n  commit: 71c4197fccc9b06f360d6a55a192067dcab719a3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-list\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- exclude: '*/vendor/*'\n  opts:\n    description: \"Skip matching go packages.  \\nMultiple patterns can be specified\n      as a newline separated list.\\n\\nExamples:\\n\\n- \\\"*/vendor/*\\\"\\n- \\\"*/steps-go-list*\\\\n*/gotool*\\\"\"\n    summary: Skip matching go packages.\n    title: Exclude patterns\noutputs:\n- BITRISE_GO_PACKAGES: null\n  opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    title: List of go packages.\n"
  },
  {
    "path": "steps/go-list/0.9.0/step.yml",
    "content": "title: Go list\nsummary: Runs go list ./... command\ndescription: |-\n  Runs `go list ./...` command in the current working directory (should be your go project's dir).\n  The package list is filtered by the given exclude patterns.\nwebsite: https://github.com/bitrise-steplib/steps-go-list\nsource_code_url: https://github.com/bitrise-steplib/steps-go-list\nsupport_url: https://github.com/bitrise-steplib/steps-go-list/issues\npublished_at: 2018-04-11T15:14:55.838752176+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-list.git\n  commit: b3cae7e63417af45674ae29a0705d3624c6d43bb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-list\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- exclude: '*/vendor/*'\n  opts:\n    description: \"Skip matching go packages.  \\nMultiple patterns can be specified\n      as a newline separated list.\\n\\nExamples:\\n\\n- \\\"*/vendor/*\\\"\\n- \\\"*/steps-go-list*\\\\n*/gotool*\\\"\"\n    summary: Skip matching go packages.\n    title: Exclude patterns\noutputs:\n- BITRISE_GO_PACKAGES: null\n  opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    title: List of go packages.\n"
  },
  {
    "path": "steps/go-list/1.0.0/step.yml",
    "content": "title: Go list\nsummary: This step runs the `go list ./...` command for you to list the go packages\n  named by the import paths.\ndescription: \"This step runs the `go list ./...` command for you to list the go packages\n  named by the import paths, starting from the current working directory.  \\nIt can\n  return a filtered package list in line with the exclude patterns.\"\nwebsite: https://www.bitrise.io/integrations/steps/go-list\nsource_code_url: https://github.com/bitrise-steplib/steps-go-list\nsupport_url: https://github.com/bitrise-steplib/steps-go-list/issues\npublished_at: 2021-04-07T14:13:57.7725138Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-list.git\n  commit: 5939f5cec5a4cbbcfbf2086ac03ca7ec102d426f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-list\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- exclude: '*/vendor/*'\n  opts:\n    description: \"Skip matching go packages.  \\nMultiple patterns can be specified\n      as a newline separated list.\\n\\nExamples:\\n\\n- \\\"*/vendor/*\\\"\\n- \\\"*/steps-go-list*\\\\n*/gotool*\\\"\"\n    summary: Skip matching go packages.\n    title: Exclude patterns\noutputs:\n- BITRISE_GO_PACKAGES: null\n  opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    title: List of go packages.\n"
  },
  {
    "path": "steps/go-list/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/go-test/0.9.0/step.yml",
    "content": "title: Go test\nsummary: Runs go test\ndescription: |-\n  Runs go test on the given packages one-by-one:\n\n  `go test -v <package>`\nwebsite: https://github.com/bitrise-steplib/steps-go-test\nsource_code_url: https://github.com/bitrise-steplib/steps-go-test\nsupport_url: https://github.com/bitrise-steplib/steps-go-test/issues\npublished_at: 2018-04-11T15:27:25.616467447+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-test.git\n  commit: a0d3bf08f31dffcb3652aa50ab746f1b12756a07\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages, to run the go test command against.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    summary: go test target packages\n    title: go test target packages\n  packages: $BITRISE_GO_PACKAGES\n"
  },
  {
    "path": "steps/go-test/1.0.1/step.yml",
    "content": "title: Go test\nsummary: Runs Go test\ndescription: |-\n  Runs Go test on the given packages one-by-one:\n\n  `go test -v <package>`\nwebsite: https://github.com/bitrise-steplib/steps-go-test\nsource_code_url: https://github.com/bitrise-steplib/steps-go-test\nsupport_url: https://github.com/bitrise-steplib/steps-go-test/issues\npublished_at: 2018-07-05T16:53:35.015023834+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-test.git\n  commit: 4e539a6abb00f8a23f7f3b158d4838aeb85c29e3\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline separated list of Go packages, to run the Go test command against.\n\n      __Example:__\n\n      ```\n      github.com/my/step\n      github.com/bitrise/step/tool\n      ```\n    summary: List of Go packages to test.\n    title: Go test target packages\n  packages: $BITRISE_GO_PACKAGES\noutputs:\n- GO_CODE_COVERAGE_REPORT_PATH: null\n  opts:\n    description: Path to the code coverage report file, which contains each package's\n      code coverage report.\n    summary: Path to the code coverage report file.\n    title: Code coverage report file path\n"
  },
  {
    "path": "steps/go-test/1.0.2/step.yml",
    "content": "title: Go test\nsummary: Runs Go test\ndescription: |-\n  Runs Go test on the given packages one-by-one:\n\n  `go test -v <package>`\nwebsite: https://github.com/bitrise-steplib/steps-go-test\nsource_code_url: https://github.com/bitrise-steplib/steps-go-test\nsupport_url: https://github.com/bitrise-steplib/steps-go-test/issues\npublished_at: 2018-08-07T11:56:28.006304582Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-go-test.git\n  commit: 22533596abc21e889137a0ead9b7bcb592731dd6\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-go-test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline separated list of Go packages, to run the Go test command against.\n\n      __Example:__\n\n      ```\n      github.com/my/step\n      github.com/bitrise/step/tool\n      ```\n    summary: List of Go packages to test.\n    title: Go test target packages\n  packages: $BITRISE_GO_PACKAGES\noutputs:\n- GO_CODE_COVERAGE_REPORT_PATH: null\n  opts:\n    description: Path to the code coverage report file, which contains each package's\n      code coverage report.\n    summary: Path to the code coverage report file.\n    title: Code coverage report file path\n"
  },
  {
    "path": "steps/go-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/golint/0.9.0/step.yml",
    "content": "title: Golint\nsummary: Runs golint\ndescription: |-\n  Runs golint command on the given packages one-by-one:\n\n  `golint -set_exit_status <package>`\nwebsite: https://github.com/bitrise-steplib/steps-golint\nsource_code_url: https://github.com/bitrise-steplib/steps-golint\nsupport_url: https://github.com/bitrise-steplib/steps-golint/issues\npublished_at: 2018-04-11T15:20:24.210013925+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-golint.git\n  commit: 817a863c2498eba8b326cc07b2062fef22dd0382\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-golint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages, to run the golint command against.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    summary: golint target packages\n    title: golint target packages\n  packages: $BITRISE_GO_PACKAGES\n"
  },
  {
    "path": "steps/golint/0.9.1/step.yml",
    "content": "title: Golint\nsummary: Runs golint\ndescription: |-\n  Runs golint command on the given packages one-by-one:\n\n  `golint -set_exit_status <package>`\nwebsite: https://github.com/bitrise-steplib/steps-golint\nsource_code_url: https://github.com/bitrise-steplib/steps-golint\nsupport_url: https://github.com/bitrise-steplib/steps-golint/issues\npublished_at: 2020-12-16T16:35:53.750615602Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-golint.git\n  commit: 1b9692a4a6bc64a2ddb2090c4761465b61fbac22\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-golint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Newline (`\\n`) separated list of go packages, to run the golint command against.\n\n      Example: `github.com/my/step\\ngithub.com/bitrise/step/tool`\n    summary: golint target packages\n    title: golint target packages\n  packages: $BITRISE_GO_PACKAGES\n"
  },
  {
    "path": "steps/golint/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/google-play-deploy/0.9.0/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n  0, You have to upload the first apk manually\n  See: https://play.google.com/apps/publish ->All applications->Add new application\n\n  1, You must link your Google Play Developer Console to an API project.\n  See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  2, Setting Up API Access Clients:\n  See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n  When you create your service account on the google developer console chose P12 as Key Type.\n\n  3, Grant Access to provide the service account the necessary rights\n  See: https://play.google.com/apps/publish ->Settings->User account & rights->Invite new user and give the privileges\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2015-12-16T22:47:54.034136274+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: e066d6f2d9a6bf92be56945268af578524f09247\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Service account email\n    is_required: true\n    summary: Service account email\n    title: Service account email\n  service_account_email: null\n- opts:\n    description: Package name\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: APK file path\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- key_file_path: null\n  opts:\n    description: P12 service account key file path\n    is_required: true\n    summary: Key file path\n    title: Key file path\n- opts:\n    description: Track\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - production\n    - rollout\n  track: alpha\n"
  },
  {
    "path": "steps/google-play-deploy/0.9.1/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n  0, You have to upload the first apk manually\n  See: https://play.google.com/apps/publish ->All applications->Add new application\n\n  1, You must link your Google Play Developer Console to an API project.\n  See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  2, Setting Up API Access Clients:\n  See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n  When you create your service account on the google developer console chose P12 as Key Type.\n\n  3, Grant Access to provide the service account the necessary rights\n  See: https://play.google.com/apps/publish ->Settings->User account & rights->Invite new user and give the privileges\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2016-02-11T12:42:55.969125589+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: ade12b72c88effc66fa5318ee31d50c02c4e2673\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Service account email\n    is_required: true\n    summary: Service account email\n    title: Service account email\n  service_account_email: null\n- opts:\n    description: Package name\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: APK file path\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- key_file_path: null\n  opts:\n    description: P12 service account key file path\n    is_required: true\n    summary: Key file path\n    title: Key file path\n- opts:\n    description: Track\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - production\n    - rollout\n  track: alpha\n"
  },
  {
    "path": "steps/google-play-deploy/0.9.2/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose P12 as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2016-05-02T17:04:18.980031139+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 88c64913a1877831694afbda989f13ff37d3fd33\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- deploy\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Service account email\n    is_required: true\n    summary: Service account email\n    title: Service account email\n  service_account_email: null\n- opts:\n    description: Package name\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: APK file path\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- key_file_path: null\n  opts:\n    description: |-\n      P12 service account key file path.\n\n      You can specify local path: `~/key_file.p12` or remote URL as well.\n    is_required: true\n    summary: Key file path\n    title: Key file path\n- opts:\n    description: Track\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - production\n    - rollout\n  track: alpha\n"
  },
  {
    "path": "steps/google-play-deploy/1.0.0/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2016-10-25T11:18:38.911790133+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 5cc68dea8e0e689d8114353284388b4fc1340b27\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n"
  },
  {
    "path": "steps/google-play-deploy/1.0.1/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2016-11-21T12:31:04.37912376+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: c6e7175c8bed79f09dce759fae94b87c923e1e64\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n"
  },
  {
    "path": "steps/google-play-deploy/1.1.0/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2016-11-22T17:25:03.053087431+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: e7dcc5229a2758260994cd670fca8dce35356474\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the local.\n\n      whatsnew file name pattern: `whatsnew-LOCAL`\n\n      Example:\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n"
  },
  {
    "path": "steps/google-play-deploy/1.2.1/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2017-03-22T13:49:47.715522499+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 3ede230a48d6f8e9f559715b506c137ac5ce64be\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the local.\n\n      whatsnew file name pattern: `whatsnew-LOCAL`\n\n      Example:\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    title: Untrack blocking versions?\n  untrack_blocking_versions: \"true\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n"
  },
  {
    "path": "steps/google-play-deploy/1.2.2/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2017-04-13T14:39:14.645752319+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 8ddd63d2ae7b729c980d48c020ea9c444245e07c\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the local.\n\n      whatsnew file name pattern: `whatsnew-LOCAL`\n\n      Example:\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    title: Untrack blocking versions?\n  untrack_blocking_versions: \"true\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n"
  },
  {
    "path": "steps/google-play-deploy/1.2.3/step.yml",
    "content": "title: Step google play deploy [beta]\nsummary: Step google play deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2017-06-08T17:21:43.139946828+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: a414c0bc2c00c0d8160529fa0c7bb7973fbc325f\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the local.\n\n      whatsnew file name pattern: `whatsnew-LOCAL`\n\n      Example:\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    title: Untrack blocking versions?\n  untrack_blocking_versions: \"true\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n"
  },
  {
    "path": "steps/google-play-deploy/1.3.1/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2017-11-10T16:50:38.621311663+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: dcd41dbbb728cbd00f47746ab037e4b77fe894ee\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the local.\n\n      whatsnew file name pattern: `whatsnew-LOCAL`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    title: Untrack blocking versions?\n  untrack_blocking_versions: \"true\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n- mapping_file: null\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    summary: Location of your mapping.txt file\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/1.3.2/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2017-11-10T17:56:45.534582073+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: ad35f2d1e4470acfae6cef9abb4653b6fc0c0205\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the local.\n\n      whatsnew file name pattern: `whatsnew-LOCAL`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    title: Untrack blocking versions?\n  untrack_blocking_versions: \"true\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    summary: Location of your mapping.txt file\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/1.3.3/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2017-11-28T15:07:23.36917477+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 866064bff6ac85b552189546f83b30d8701cbcfe\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    summary: Service Account JSON key file path\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    summary: Package name\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: APK file path\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    summary: Track\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    summary: User Fraction\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the locale.\n\n      whatsnew file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Direcotry of localised whatsnew files\n  whatsnews_dir: null\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    title: Untrack blocking versions?\n  untrack_blocking_versions: \"true\"\n- opts:\n    description: \"__DEPRECATED!__\\nUse JSON key instead of P12 key and `service_account_json_key_path`\n      input.\\n\\nThe `Service account ID` of the Service Account you want to use to\n      authorize the deploy. \"\n    summary: '[DEPRECATED!] Service account ID'\n    title: '[DEPRECATED!] Service account ID'\n  service_account_email: null\n- key_file_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n      Use JSON key instead of P12 key and `service_account_json_key_path` input.\n\n      Path to the Service Account's p12 key file .\n\n      For remote P12 key file you can provide any download location (ex: `https://URL/TO/key.p12`).\n      For local P12 key file provide file path url. (ex: `file://PATH/TO/key.p12`).\n    summary: '[DEPRECATED!] Service Account p12 key file path'\n    title: '[DEPRECATED!] Service Account p12 key file path'\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    summary: Location of your mapping.txt file\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/1.4.1/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2018-01-19T15:25:30.149786+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: ae2778c2d831bcc2bb7b8ab8d3c07f68b741fccc\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    is_required: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    title: Track\n    value_options:\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the locale.\n\n      whatsnew file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Directory of localised whatsnew files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n"
  },
  {
    "path": "steps/google-play-deploy/1.4.2/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: !!timestamp 2018-03-20T16:23:04.146609034+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: e25b0ce46871010008e1a0d5ccf2b1bc5a88eb65\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    is_required: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    title: Track\n    value_options:\n    - internal\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the locale.\n\n      whatsnew file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Directory of localised whatsnew files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n"
  },
  {
    "path": "steps/google-play-deploy/1.4.3/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started (Linking your API Project section)\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started (Using a service account)\n    When you create your service account on the google developer console choose json as Key Type.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your whats news to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: !!timestamp 2018-03-29T14:45:06.054292041+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: d200042293afcef1fc0afc303e1e76044d2d3188\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    is_required: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK to deploy.\n    is_required: true\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format emxamples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    title: APK file path\n- opts:\n    description: Track to assign the APK(s).\n    is_required: true\n    title: Track\n    value_options:\n    - internal\n    - alpha\n    - beta\n    - rollout\n    - production\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localised whatsnew files directory.\n\n      This directory should contain whatsnew files postfixed with the locale.\n\n      whatsnew file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Directory of localised whatsnew files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see error, like this:\\n\\n`Version 42 of this app can not be downloaded\n      by any devices as they will all receive APKs with higher version codes`\\n\\nTo\n      avoid this issue set this input to: `\\\"true\\\"` and the step will deactivate\n      every apk with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n"
  },
  {
    "path": "steps/google-play-deploy/1.5.0/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started. Check the __Linking your API Project section__.\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started. Check the __Using a service account__ section.\n    When you create your service account on the google developer console, choose json as `Key Type`.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2018-08-01T10:35:12.462903053Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 9f3352d2893841f1368df0c15ea799ab2e0f48fd\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    is_required: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK or App bundle to deploy.\n    is_required: true\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK or App Bundle to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `/path/to/my/bundle.aab`\n    is_required: true\n    title: APK or App Bundle file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in apk_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded APK(s). \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, rollout, production.\\n\\nOr\n      you can set your custom track name as well. \\n\\nFor example: `pre-release`,\n      or any of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded APK(s).\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localized 'whatsnew' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      whatsnew file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Directory of localized whatsnew files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see an error:\\n\\n`Version 42 of this app can not be downloaded by any\n      devices as they will all receive APKs with higher version codes`\\n\\nTo avoid\n      this issue set this input to: `\\\"true\\\"` and the step will deactivate every\n      apk with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n"
  },
  {
    "path": "steps/google-play-deploy/1.5.1/step.yml",
    "content": "title: Google Play Deploy\nsummary: Google Play Deploy\ndescription: |-\n  To use this step:\n\n  1. You have to upload the first apk manually (using the web interface).\n    See: https://play.google.com/apps/publish -> All applications -> Add new application\n\n  2. You must link your Google Play Developer Console to an API project.\n    See: https://developers.google.com/android-publisher/getting_started. Check the __Linking your API Project section__.\n\n  3. Setting Up API Access Clients, using a service account:\n    See: https://developers.google.com/android-publisher/getting_started. Check the __Using a service account__ section.\n    When you create your service account on the google developer console, choose json as `Key Type`.\n\n  4. Grant Access to provide the service account the necessary rights.\n    See: https://play.google.com/apps/publish -> Settings -> User account & rights -> Invite new user and give the privileges.\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n     - Edit store listing, pricing & distribution\n     - Manage Production APKs\n     - Manage Alpha & Beta APKs\n     - Manage Alpha & Beta users\n\n  5. OPTIONAL - Add translations for your Store Listing.\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n    See: https://support.google.com/googleplay/android-developer/answer/3125566?hl=en (Add translations for your Store Listing)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2018-08-31T08:35:42.448366261Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 2bd7c4e03320ae07d371a544a22f99c56ba862e5\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Path to the Service Account's JSON key file.\n\n      For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the APK or App bundle to deploy.\n    is_required: true\n    title: Package name\n  package_name: null\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK or App Bundle to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `/path/to/my/bundle.aab`\n    is_required: true\n    title: APK or App Bundle file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in apk_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded APK(s). \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, rollout, production.\\n\\nOr\n      you can set your custom track name as well. \\n\\nFor example: `pre-release`,\n      or any of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded APK(s).\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the APK.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localized 'whatsnew' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      whatsnew file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEWS]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # whatsnew files are in the repo root directory\n      - \"./whatsnew\" # whatsnew files are in the whatsnew directory\n    title: Directory of localized whatsnew files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apks, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see an error:\\n\\n`Version 42 of this app can not be downloaded by any\n      devices as they will all receive APKs with higher version codes`\\n\\nTo avoid\n      this issue set this input to: `\\\"true\\\"` and the step will deactivate every\n      apk with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n"
  },
  {
    "path": "steps/google-play-deploy/1.6.0/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the google developer console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2019-05-22T08:26:15.728258344Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 393a2871140e56db87fef09e1f450f0300fcef7d\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path.\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, rollout, production.\\n\\nOr\n      you can set your custom track name as well. \\n\\nFor example: `pre-release`,\n      or any of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the app.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apps, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see an error:\\n\\n`Version 42 of this app can not be downloaded by any\n      devices as they will all receive APKs with higher version codes`\\n\\nTo avoid\n      this issue set this input to: `\\\"true\\\"` and the step will deactivate every\n      app with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `/path/to/my/bundle.aab`\n    title: APK file path\n"
  },
  {
    "path": "steps/google-play-deploy/1.6.1/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the google developer console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2019-05-23T08:57:26.305215233Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 9ecdcda7cc94401ea2090cfbec2185279ba2e4e1\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, rollout, production.\\n\\nOr\n      you can set your custom track name as well. \\n\\nFor example: `pre-release`,\n      or any of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      __Only available if `track` is `rollout`.__\n\n      Portion of the users who should get the staged rollout version of the app.\n    is_required: true\n    title: User Fraction\n    value_options:\n    - \"0.05\"\n    - \"0.1\"\n    - \"0.2\"\n    - \"0.5\"\n  user_fraction: \"0.5\"\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apps, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see an error:\\n\\n`Version 42 of this app can not be downloaded by any\n      devices as they will all receive APKs with higher version codes`\\n\\nTo avoid\n      this issue set this input to: `\\\"true\\\"` and the step will deactivate every\n      app with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `/path/to/my/bundle.aab`\n    title: APK file path\n"
  },
  {
    "path": "steps/google-play-deploy/2.0.1/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the google developer console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2019-10-02T13:48:28.747639686Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 64e6a70817413acbbeb5001e58d54f67862b17e3\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, rollout, production.\\n\\nOr\n      you can set your custom track name as well. \\n\\nFor example: `pre-release`,\n      or any of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: \"Should deactivate apps, with lower version code, on lower level\n      tracks?\\n\\nE.g.: \\nIf you have an __active apk on alpha__ track with version\n      code: `42`.\\nAnd you try to __upload a new version (`43`), to the beta track__,\n      you will see an error:\\n\\n`Version 42 of this app can not be downloaded by any\n      devices as they will all receive APKs with higher version codes`\\n\\nTo avoid\n      this issue set this input to: `\\\"true\\\"` and the step will deactivate every\n      app with lower version code, on lower level tracks.\"\n    is_required: true\n    title: Untrack blocking versions?\n    value_options:\n    - \"true\"\n    - \"false\"\n  untrack_blocking_versions: \"true\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `/path/to/my/bundle.aab`\n    title: APK file path\n"
  },
  {
    "path": "steps/google-play-deploy/3.0.0/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the Google Play Developer Console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2019-11-19T15:17:52.590347525Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: eba532cf96510e392446e6027cdb615f456d9a7d\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.0.1/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the Google Play Developer Console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2019-12-09T16:58:24.636775548Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 8dba7be97b04c53fb2a573f910b76436f032e550\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.0.2/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the Google Play Developer Console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2020-03-05T16:00:24.486398696Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 27e5ba1a046cf0a02c17ae50a64a47186ee9cce8\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.1.1/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the Google Play Developer Console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2020-08-13T09:44:07.131259872Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 87d90507c3269c5786fe842d3ed5bd468a25b720\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.1.2/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the Google Play Developer Console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2020-08-28T11:14:19.156066964Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: fb33d31ef4c0487194aa94fe7c4225991c226b05\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle or APK file(s) to deploy.\n\n      In case of [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: \"This allows your app to decide how strongly to recommend an update\n      to the user. \\nAccepts values between 0 and 5 (inclusive-inclusive) with 0 being\n      the lowest priority and 5 being the highest priority.\\nBy default this value\n      is 0.\\nFor more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\"\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.2.0/step.yml",
    "content": "title: Deploy to Google Play\nsummary: Uploads and releases apps to Google Play Store\ndescription: |-\n  Uploads and releases apps to Google Play Store.\n\n  The step supports single APK, [multiple APK](https://developer.android.com/google/play/publishing/multiple-apks.html) and Bundle deploys.\n\n  To use this step:\n\n  1. Upload the first apk/aab manually (using the web interface):\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> All applications -> CREATE APPLICATION\n\n  2. Link your Google Play Developer Console to an API project:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Linking your API Project__ section\n\n  3. Setup API Access Clients, using a service account:\n\n    Described in [Google Play Developer API](https://developers.google.com/android-publisher/getting_started)'s __Using a service account__ section\n\n    __NOTE__: When you create your service account on the Google Play Developer Console, choose json as `Key Type`.\n\n  4. Grant the necessary rights to the service account:\n\n    Visit the [Google Play Console](https://play.google.com/apps/publish) -> Settings -> Users & permissions -> Invite new user.\n\n    Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n\n      - ACCESS LEVEL: View app information\n      - RELEASE MANAGEMENT: Manage production releases, Manage testing track releases\n      - STORE PRESENCE: Edit store listing, pricing & distribution\n\n  5. OPTIONAL - Add translations for your Store Listing:\n\n    To allow the step to assign your 'whatsnew' files to the uploaded apk version.\n\n    Visit [Play Console Help](https://support.google.com/googleplay/android-developer/answer/3125566?hl=en)'s __Add translations for your Store Listing__ section\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-02-02T09:47:17.232550385Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 725c6c4d9dc0c5e3f2dd4152c232ba84e3dca613\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the Service Account's JSON key file.\\n\\nFor remote JSON\n      key file you can provide any download location (ex: `https://URL/TO/key.json`).\n      \\ \\nFor local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).\"\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the App Bundle file(s) or APK file(s) to deploy.\n\n      In case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n\n      Format examples:\n\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track in which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed track you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's versionName.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: \"This allows your app to decide how strongly to recommend an update\n      to the user. \\nAccepts values between 0 and 5 (inclusive-inclusive) with 0 being\n      the lowest priority and 5 being the highest priority.\\nBy default this value\n      is 0.\\nFor more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\"\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n\n      This directory should contain 'whatsnew' files postfixed with the locale.\n\n      what's new file name pattern: `whatsnew-LOCALE`\n\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n\n      Format examples:\n\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.2.1/step.yml",
    "content": "title: Google Play Deploy\nsummary: Uploads your Android app to Google Play.\ndescription: \"\\nThe Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-02-08T14:08:03.091053534Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 8a91e65f3cc78719d29d40ded46a23259ab91986\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track to which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed tracks you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's versionName.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: \"This allows your app to decide how strongly to recommend an update\n      to the user. \\nAccepts values between 0 and 5 with 0 being the lowest priority\n      and 5 being the highest priority.\\nBy default this value is 0.\\nFor more information\n      see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\"\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.2.2/step.yml",
    "content": "title: Google Play Deploy\nsummary: Uploads your Android app to Google Play.\ndescription: \"\\nThe Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-03-18T10:41:44.496524333Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 727e315001e2b518bce87da2a18d4d4e2c3bb712\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track to which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed tracks you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's versionName.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: \"This allows your app to decide how strongly to recommend an update\n      to the user. \\nAccepts values between 0 and 5 with 0 being the lowest priority\n      and 5 being the highest priority.\\nBy default this value is 0.\\nFor more information\n      see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\"\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.3.0/step.yml",
    "content": "title: Google Play Deploy\nsummary: Uploads your Android app to Google Play.\ndescription: \"\\nThe Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-03-23T14:59:24.725249323Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 4fc0eb01690e287dd24ee0659536eb1aaa29b0e5\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: \"The track to which you want to assign the uploaded app. \\n\\nCan\n      be one of the built-in tracks: internal, alpha, beta, production.\\n\\nOr you\n      can set your custom track name as well. \\n\\nFor example: `pre-release`, or any\n      of your closed tracks you added in Google Play Developer Console.\"\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see here: https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's versionName.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: \"This allows your app to decide how strongly to recommend an update\n      to the user. \\nAccepts values between 0 and 5 with 0 being the lowest priority\n      and 5 being the highest priority.\\nBy default this value is 0.\\nFor more information\n      see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\"\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n"
  },
  {
    "path": "steps/google-play-deploy/3.4.0/step.yml",
    "content": "title: Google Play Deploy\nsummary: Uploads your Android app to Google Play.\ndescription: \"\\nThe Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-08-11T15:42:44.574273684Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 342d263c23eae93cc6e01b0a2dd6b7e069930207\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline `\\n` or pipe `|` separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the expansion file.\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks: internal, alpha, beta, production.\n\n      Or you can set your custom track name as well.\n\n      For example: `pre-release`, or any of your closed tracks you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see here: https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's versionName.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.5.0/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: \"The Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-09-06T07:17:32.074399842Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 5cafe57f86a6c8fe1fa44653cc0a519535314f30\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: The `mapping.txt` file provides a translation between the original\n      and obfuscated class, method, and field names.\n    title: Location of your mapping.txt file\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.6.0/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: \"The Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-09-06T10:56:42.934459977Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: dbf4167cd14816ec94eee670f46ae0b3dc2da505\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.7.1/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: \"The Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-10-04T08:01:21.116081032Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: e45fe90ac79134f4ee9728cb5cefbd61ee3c91e1\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.7.2/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: \"The Step uploads your Android app to Google Play. It works with both\n  APK and AAB files.\\n\\nPlease note that in order to successfully use this Step, you\n  must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1),\n  using Google's own web interface! \\nOnce you uploaded one APK or AAB of your app\n  to Google Play manually, you can use our Step for all subsequent versions. \\n\\n###\n  Configuring the Step\\n\\nThe Step uses Google's API so before attempting to use the\n  Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access).\n  This includes:\\n- [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\\n-\n  [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\\n-\n  Granting the necessary access rights to the service account. \\n- Upload the service\n  account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n  \\n\\nDue to the way the Google Play Publisher API works, you have to grant at least\n  the following permissions to that service account:\\n- Edit store listing, pricing\n  & distribution\\n- Manage Production APKs\\n- Manage Alpha & Beta APKs\\n- Manage Alpha\n  & Beta users\\n\\nRead the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\\n\\nTo\n  deploy your app with the Step:\\n\\n1. In the **Service Account JSON key file path**,\n  add the Secret that stores your service account JSON key. \\n1. In the **App file\n  path** input, set the path to your APK and/or AAB files. You can add multiple paths\n  here, separated with a newline. \\n   In most cases, the default values work well\n  unless you changed the output variable of the Step that build your APK or AAB.\\n1.\n  In the **Package name**  input, set the package name of your app.  \\n1. In the **Track**\n  input, add the track to which you want to assign the app. This can be any of the\n  built-in tracks or a custom track of your own.\\n\\n### Troubleshooting \\n\\nIf the\n  Step fails, check the following:\\n- If it's an authentication error, check that\n  your Secret points to the correct file (and that a file is uploaded at all). \\n-\n  Make sure your service account has the necessary access rights.\\n- Check that there's\n  no typo in the package name and that you selected an existing track for the app.\n  \\n\\n### Useful links \\n\\n- [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\\n-\n  [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\\n\\n###\n  Related Steps \\n\\n- [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\\n-\n  [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\\n-\n  [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n-\n  [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\"\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2021-10-08T15:20:52.068106539Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 3a19333bdaf5879951ffa7c33303ef8cebac0cc2\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.7.3/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2022-11-16T13:01:07.761606755Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 2049e4237946b3ffd8f557346b7e8fc1438d3f07\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.7.4/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2023-09-18T14:28:07.46366103Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 19a3fb5477b50a0089471f090c9dc977172f0535\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.7.5/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2023-09-18T16:10:04.091332429Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 26aa360af996eab443a0e34d1849a6ea0c31502a\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n"
  },
  {
    "path": "steps/google-play-deploy/3.7.6/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2024-08-07T09:43:43.782088622Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: c341208126338a0f8b917c23c6bc4c97ab29214b\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- FAILURE_REASON: null\n  opts:\n    summary: Response given from Google about why aab/apk was not uploaded\n    title: Error upload reason\n"
  },
  {
    "path": "steps/google-play-deploy/3.8.0/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2024-09-26T08:19:59.284956136Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: fe37a303ae555788b797dc9712676940a743cf9c\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n- dry_run: \"false\"\n  opts:\n    description: |-\n      If set to `true` then the changes will not be committed to create a real release in the Play\n      Console. Use this flag to validate your configuration without triggering a new review.\n    is_required: false\n    title: Dry Run\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- FAILURE_REASON: null\n  opts:\n    summary: Response given from Google about why aab/apk was not uploaded\n    title: Error upload reason\n"
  },
  {
    "path": "steps/google-play-deploy/3.8.1/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2025-11-13T12:49:54.995646546Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 71b18f3a8d762e1dec43475c85f753dc12dce90b\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n- dry_run: \"false\"\n  opts:\n    description: |-\n      If set to `true` then the changes will not be committed to create a real release in the Play\n      Console. Use this flag to validate your configuration without triggering a new review.\n    is_required: false\n    title: Dry Run\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- FAILURE_REASON: null\n  opts:\n    summary: Response given from Google about why aab/apk was not uploaded\n    title: Error upload reason\n"
  },
  {
    "path": "steps/google-play-deploy/3.8.2/step.yml",
    "content": "title: Google Play Deploy\nsummary: Upload your Android app to Google Play.\ndescription: |-\n  The Step uploads your Android app to Google Play. It works with both APK and AAB files.\n\n  Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!\n  Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.\n\n  ### Configuring the Step\n\n  The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:\n  - [Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).\n  - [Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).\n  - Granting the necessary access rights to the service account.\n  - Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).\n\n  Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:\n  - Edit store listing, pricing & distribution\n  - Manage Production APKs\n  - Manage Alpha & Beta APKs\n  - Manage Alpha & Beta users\n\n  Read the full process in our [Deploying Android apps guide](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/).\n\n  To deploy your app with the Step:\n\n  1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.\n  1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.\n     In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.\n  1. In the **Package name**  input, set the package name of your app.\n  1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.\n\n  ### Troubleshooting\n\n  If the Step fails, check the following:\n  - If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).\n  - Make sure your service account has the necessary access rights.\n  - Check that there's no typo in the package name and that you selected an existing track for the app.\n\n  ### Useful links\n\n  - [Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)\n  - [Deploying Android apps](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/)\n\n  ### Related Steps\n\n  - [TestFairy Deploy Android](https://www.bitrise.io/integrations/steps/testfairy-deploy-android)\n  - [AppCenter Android Deploy](https://www.bitrise.io/integrations/steps/appcenter-deploy-android)\n  - [Appetize.io Deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\nwebsite: https://github.com/bitrise-io/steps-google-play-deploy\nsource_code_url: https://github.com/bitrise-io/steps-google-play-deploy\nsupport_url: https://github.com/bitrise-io/steps-google-play-deploy/issues\npublished_at: 2026-01-30T13:08:51.498265251Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-google-play-deploy.git\n  commit: 90cb68f03be1a6290191240d3e38c574b39a6495\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-google-play-deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: Path to the service account's JSON key file. It must be a Secret\n      Environment Variable, pointing to either a file uploaded to Bitrise or to a\n      remote download location.\n    is_required: true\n    is_sensitive: true\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    description: Package name of the app.\n    is_required: true\n    title: Package name\n  package_name: null\n- app_path: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path to the app bundle file(s) or APK file(s) to deploy.\n      In the case of [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html) deploy, you can specify multiple APKs and AABs as a newline (`\\n`) or pipe (`|`) separated list.\n    is_required: true\n    title: App file path\n- expansionfile_path: \"\"\n  opts:\n    description: |-\n      Path to the [expansion file](https://developer.android.com/google/play/expansion-files).\n      Leave empty or provide exactly the same number of paths as in app_path, separated by `|` character and start each path with the expansion file's type\n      separated by a `:`. (main, patch)\n      Format examples:\n      - `main:/path/to/my/app.obb`\n      - `patch:/path/to/my/app1.obb|main:/path/to/my/app2.obb|main:/path/to/my/app3.obb`\n    title: Expansion file Path\n- opts:\n    description: |-\n      The track to which you want to assign the uploaded app.\n\n      Can be one of the built-in tracks (internal, alpha, beta, production), or a custom track name you added in Google Play Developer Console.\n    is_required: true\n    summary: The track in which you want to assign the uploaded app.\n    title: Track\n  track: alpha\n- opts:\n    description: |-\n      Portion of the users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive).\n      Only applies if `Status` is `inProgress` or `halted`.\n\n      To release to all users, this input should not be defined (or should be blank).\n    is_required: false\n    title: User Fraction\n  user_fraction: null\n- opts:\n    description: |-\n      The status of a release.\n      For more information see the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status).\n    is_required: false\n    title: Status\n  status: null\n- opts:\n    description: The name of the release. By default Play Store generates the name\n      from the APK's `versionName` value.\n    is_required: false\n    title: Name of the release\n  release_name: null\n- opts:\n    description: |-\n      This allows your app to decide how strongly to recommend an update to the user.\n      Accepts values between 0 and 5 with 0 being the lowest priority and 5 being the highest priority.\n      By default this value is 0.\n      For more information see here: https://developer.android.com/guide/playcore/in-app-updates#check-priority.\n    is_required: false\n    title: Update Priority\n  update_priority: 0\n- opts:\n    description: |-\n      Use this input to specify localized 'what's new' files directory.\n      This directory should contain 'whatsnew' files postfixed with the locale.\n      what's new file name pattern: `whatsnew-LOCALE`\n      Example:\n\n      ```\n      + - [PATH/TO/WHATSNEW]\n          |\n          + - whatsnew-en-US\n          |\n          + - whatsnew-de-DE\n      ```\n      Format examples:\n      - \"./\"         # what's new files are in the repo root directory\n      - \"./whatsnew\" # what's new files are in the whatsnew directory\n    title: Directory of localized what's new files\n  whatsnews_dir: null\n- mapping_file: $BITRISE_MAPPING_PATH\n  opts:\n    description: |-\n      The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names.\n\n      Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself.\n\n      In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\\n`) or pipe (`|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input.\n    title: Mapping txt file path\n- opts:\n    description: |-\n      If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent\n      for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically\n      sent to review.\n    is_required: true\n    title: Retry changes without sending to review\n    value_options:\n    - \"true\"\n    - \"false\"\n  retry_without_sending_to_review: \"false\"\n- ack_bundle_installation_warning: \"false\"\n  opts:\n    description: |-\n      Must be set to `true` if the App Bundle installation may trigger a warning on user devices\n      (for example, if installation size may be over a threshold, typically 100 MB).\n    is_required: true\n    title: Acknowledge Bundle Installation Warning\n    value_options:\n    - \"true\"\n    - \"false\"\n- dry_run: \"false\"\n  opts:\n    description: |-\n      If set to `true` then the changes will not be committed to create a real release in the Play\n      Console. Use this flag to validate your configuration without triggering a new review.\n    is_required: false\n    title: Dry Run\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- FAILURE_REASON: null\n  opts:\n    summary: Response given from Google about why aab/apk was not uploaded\n    title: Error upload reason\n"
  },
  {
    "path": "steps/google-play-deploy/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/google-play-rollout-update/0.0.2/step.yml",
    "content": "title: Update Google Play Rollout\nsummary: |\n  This step connects to Google Play and check if there is a release in production with an in progress rollout. If found, it increases it to the next rollout percentage [2%, 5%, 10%, 20%, 50%, 100%]\ndescription: |\n  The step makes use of the python library and Edits Api from Google Play. It downloads the info from the production track, and looks if any release in there has a 'userFraction' property defined. In case it has, and it is between 0 and 1, then it just modifies it to the next step, or completes the release if next is 100%\nwebsite: https://github.com/angelolloqui/bitrise-step-google-play-rollout-update\nsource_code_url: https://github.com/angelolloqui/bitrise-step-google-play-rollout-update\nsupport_url: https://github.com/angelolloqui/bitrise-step-google-play-rollout-update/issues\npublished_at: 2022-01-09T23:07:51.199324+01:00\nsource:\n  git: https://github.com/angelolloqui/bitrise-step-google-play-rollout-update.git\n  commit: 23a177cced4cae12ba87ca46f58f57cf69a56dfd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: pipenv\n  - name: wget\n  apt_get:\n  - name: pipenv\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: false\n    is_sensitive: true\n    summary: Path to the service account's JSON key file. It must be a Secret Environment\n      Variable, pointing to either a file uploaded to Bitrise or to a remote download\n      location. Either this or service_account_json_key_content\n    title: Service Account JSON key file path\n  service_account_json_key_path: null\n- opts:\n    is_required: false\n    is_sensitive: true\n    summary: Content of a previously donwloaded service account's JSON key file. It\n      must be a Secret Environment Variable, containing the data from the Google key\n      file. Either this or service_account_json_key_path needs to be provided\n    title: Service Account JSON key content\n  service_account_json_key_content: null\n- opts:\n    is_required: true\n    summary: Package name of the app.\n    title: Package name\n  package_name: null\n"
  },
  {
    "path": "steps/google-play-rollout-update/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/gradle-coveralls/1.0.0/step.yml",
    "content": "title: Gradle Coveralls\nsummary: Runs Coveralls with `./gradlew`.\ndescription: Sends code coverage to www.coveralls.io. Uses `./gradlew coveralls` task.\n  You have to configure [org.kt3k.gradle.plugin:coveralls-gradle-plugin](https://github.com/kt3k/coveralls-gradle-plugin)\n  in your project first.\nwebsite: https://github.com/donvigo/steps-gradle-coveralls\nsource_code_url: https://github.com/donvigo/steps-gradle-coveralls\nsupport_url: https://github.com/donvigo/steps-gradle-coveralls/issues\npublished_at: 2016-01-17T21:09:55.984310417+02:00\nsource:\n  git: https://github.com/donvigo/steps-gradle-coveralls.git\n  commit: 630046c6d818d35760ef2a1c73cecb3c777ce9c9\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- coveralls\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_expand: true\n    is_required: true\n    title: Path for the gradlew file\n- coveralls_task: coveralls\n  opts:\n    description: |\n      The coveralls task to execute by gradlew\n    is_expand: true\n    is_required: true\n    title: Coveralls gradle task\n"
  },
  {
    "path": "steps/gradle-coveralls/1.0.1/step.yml",
    "content": "title: Gradle Coveralls\nsummary: Runs Coveralls with `./gradlew`.\ndescription: Sends code coverage to www.coveralls.io. Uses `./gradlew coveralls` task.\n  You have to configure [org.kt3k.gradle.plugin:coveralls-gradle-plugin](https://github.com/kt3k/coveralls-gradle-plugin)\n  in your project first.\nwebsite: https://github.com/donvigo/steps-gradle-coveralls\nsource_code_url: https://github.com/donvigo/steps-gradle-coveralls\nsupport_url: https://github.com/donvigo/steps-gradle-coveralls/issues\npublished_at: 2016-01-18T13:09:09.295008122+02:00\nsource:\n  git: https://github.com/donvigo/steps-gradle-coveralls.git\n  commit: 83e6ca708c9ffc4924108a8635d3c3dd32581d40\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_expand: true\n    is_required: true\n    title: Path for the gradlew file\n- coveralls_task: coveralls\n  opts:\n    description: |\n      The coveralls task to execute by gradlew\n    is_expand: true\n    is_required: true\n    title: Coveralls gradle task\n- coveralls_repo_token: null\n  opts:\n    description: \"The secret repo token for your repository, \\nfound at the bottom\n      of your repository's page on Coveralls. \\nStrongly recommended to keep this\n      variable in \\\"Secret Environment Variables\\\" section.\\t\\n\"\n    is_expand: true\n    is_required: true\n    title: Coveralls repo token\n"
  },
  {
    "path": "steps/gradle-coveralls/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/gradle-dependency-checker/1.0.1/step.yml",
    "content": "title: gradle-dependency-check\nsummary: |\n  OWASP dependency analysis for Gradle files\ndescription: |\n  Uses [jeremylong/DependencyCheck](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html) to search Gradle for CVE vulnerabilites.\n  It must be setup on the project before a first run\n\n  The generated report will be placed into $BITRISE_DEPLOY_DIR by default.\n  Remember to run the \"Deploy to bitrise.io\" step in order to persist artifacts.\nwebsite: https://github.com/odemolliens/bitrise-step-gradle-dependency-checker\nsource_code_url: https://github.com/odemolliens/bitrise-step-gradle-dependency-checker\nsupport_url: https://github.com/odemolliens/bitrise-step-gradle-dependency-checker/issues\npublished_at: 2021-05-26T09:36:21.630899+02:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-gradle-dependency-checker.git\n  commit: e0f1e7fa13cc7e1df7643dbb90cb43b4dd30698c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- react-native\n- flutter\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    title: Android Source Code Directory path; For react-native project, please use\n      './android'\n  source_root_path: $BITRISE_SOURCE_DIR\n- android_target_name: app\n  opts:\n    is_required: true\n    title: The module that will be analyzed\n- deploy_dir: $BITRISE_DEPLOY_DIR\n  opts:\n    is_required: true\n    title: Deploy directory to output scan artifacts\n"
  },
  {
    "path": "steps/gradle-dependency-checker/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/gradle-runner/0.9.0/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `./gradlew`.\ndescription: Runs Unit Tests with `./gradlew`. You can specify the test tasks to run\n  and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-10-29T17:12:53.790629855Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 2f12b73ab17e6f75971f3e17e6c87794f10a3064\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- gradle\ndeps:\n  check_only:\n  - name: gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_task: null\n  opts:\n    description: |\n      Gradle task to run\n    is_expand: true\n    is_required: false\n    title: Gradle task to run\n"
  },
  {
    "path": "steps/gradle-runner/0.9.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a gradle task\ndescription: Runs a gradle task\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-10-29T18:52:50.97101866Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: cc24394874678e54b9d4ecc17c6329cf63477412\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_task: null\n  opts:\n    description: |\n      Gradle task to run\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n"
  },
  {
    "path": "steps/gradle-runner/0.9.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a gradle task\ndescription: Runs a gradle task and copies all - or specified - generated APKs to\n  `$BITRISE_DEPLOY_DIR`\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-10-30T23:40:35.389644784Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 3e96ed65730b8bf38c1c27fc4ca4af9ea1e8b71a\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: null\n  opts:\n    description: |\n      Path for the gradle file to run\n    is_expand: true\n    is_required: true\n    title: Path for the gradle file to run\n- gradle_task: null\n  opts:\n    description: |\n      Gradle task to run\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- apk_file_filter: null\n  opts:\n    description: |\n      The steps moves all the found apk files under `$BITRISE_DEPLOY_DIR`.\n      You can specify a filter to move only the selected APKs.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file filter\n"
  },
  {
    "path": "steps/gradle-runner/0.9.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a gradle task\ndescription: Runs a gradle task and copies all - or specified - generated APKs to\n  `$BITRISE_DEPLOY_DIR`\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-10-31T12:31:13.977848783Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: ee2650b0c287e3917c0bf310ba3028fb682febd0\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: null\n  opts:\n    description: |\n      Path for the gradle file to run\n    is_expand: true\n    is_required: true\n    title: Path for the gradle file to run\n- gradle_task: null\n  opts:\n    description: |\n      Gradle task to run\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- apk_file_filter: null\n  opts:\n    description: |\n      The steps moves all the found apk files under `$BITRISE_DEPLOY_DIR`.\n      You can specify a filter to move only the selected APKs.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file filter\n"
  },
  {
    "path": "steps/gradle-runner/1.0.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-11-11T17:23:44.487891503+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 5f35ecc666851487484ae3bfd45ec43bbd296172\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: null\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_expand: true\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      Example: `*unaligned*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file exclude filter\n"
  },
  {
    "path": "steps/gradle-runner/1.1.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-11-19T11:12:29.392498778+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 5ea3a71e8437ca3d48c2482afa253520e7627e7c\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_expand: true\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      **Optional**\n\n      If specified the `gradle` commands will be\n      executed with this `gradlew` file, instead of with `gradle` directly;\n      for example: `./gradlew assemble` instead of `gradle assemble`.\n\n      **The path should be relative** to the repository root / `workdir`,\n      for example: `./gradlew`.\n    is_expand: true\n    is_required: false\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      Example: `*unaligned*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file exclude filter\n"
  },
  {
    "path": "steps/gradle-runner/1.1.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-11-24T11:47:30.337056993+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 0b1ebf78721601b74990dbbd1268461a6dc63395\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_expand: true\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    is_expand: true\n    is_required: false\n    title: Additional options for Gradle call\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      **Optional**\n\n      If specified the `gradle` commands will be\n      executed with this `gradlew` file, instead of with `gradle` directly;\n      for example: `./gradlew assemble` instead of `gradle assemble`.\n\n      **The path should be relative** to the repository root / `workdir`,\n      for example: `./gradlew`.\n    is_expand: true\n    is_required: false\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      Example: `*unaligned*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file exclude filter\n"
  },
  {
    "path": "steps/gradle-runner/1.2.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2015-12-16T16:32:38.486090959+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 1a370566cf8c8b68c70de9c5cc9a81834b523d9c\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_expand: true\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    is_expand: true\n    is_required: false\n    title: Additional options for Gradle call\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      **Optional**\n\n      If specified the `gradle` commands will be\n      executed with this `gradlew` file, instead of with `gradle` directly;\n      for example: `./gradlew assemble` instead of `gradle assemble`.\n\n      **The path should be relative** to the repository root / `workdir`,\n      for example: `./gradlew`.\n    is_expand: true\n    is_required: false\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      Example: `*unaligned*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n"
  },
  {
    "path": "steps/gradle-runner/1.3.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-02-09T15:21:32.648357562+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 889fabf70d8dbe99e8a5a4c3977027c417fce47e\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_expand: true\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_expand: true\n    is_required: true\n    title: Gradle task to run\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    is_expand: true\n    is_required: false\n    title: Additional options for Gradle call\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      **Optional**\n\n      If specified the `gradle` commands will be\n      executed with this `gradlew` file, instead of with `gradle` directly;\n      for example: `./gradlew assemble` instead of `gradle assemble`.\n\n      **The path should be relative** to the repository root / `workdir`,\n      for example: `./gradlew`.\n    is_expand: true\n    is_required: false\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      Example: `*release*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** moves generated apk files that match with this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      Example: `*unaligned*.apk`\n    is_expand: true\n    is_required: false\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.3.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-02-10T12:33:55.780146146+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 271ae0513e97d79d1c67aeba3d87b098e122b115\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      **Optional**\n\n      If specified the `gradle` commands will be\n      executed with this `gradlew` file, instead of with `gradle` directly;\n      for example: `./gradlew assemble` instead of `gradle assemble`.\n\n      **The path should be relative** to the repository root / `workdir`,\n      for example: `./gradlew`.\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.4.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-08-17T13:17:58.336199515+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 2efa72494d559ae573c05bbff798fa450709b0c4\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root / `workdir`, for example: `./gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.4.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-08-17T19:24:15.676082448+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: d7dccea86625d6e87622d0b064e0697e000f95d2\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.5.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-09-14T17:24:08.345656934+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: d0419a9d77437ae8aac281365cf7842e906fe588\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.5.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-09-16T10:49:51.610294681+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: dcaee74c0c0de0a744f2d60725661f9996c28ed9\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.5.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2016-09-27T14:00:31.396434193+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 96f53fd4c3178ef7f03d8d3f02962522b27436c0\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.5.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-01-26T16:16:23.741528144+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 347b6751f3009071946e5496b4b9f96753938dc6\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- gradle\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: |\n      The step will move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*release*.apk`\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: |\n      The step will **not** move the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standerd bash find commands negated -name pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*unaligned*.apk`\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      This filter is a standerd bash find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/release/mapping.txt`\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** move the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\n\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standerd bash find commands negated -path pattern, see: http://linux.die.net/man/1/find\n\n      Example: `*/beta/mapping.txt`\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and moved) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and moved) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.5.4/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-01-30T13:37:17.159777277+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 33f820502c558b4fbec219e12d48bf728f3743a6\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: \"The step will copy the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find \\n\\nIf you specify an empty\n      filter, the step will set this filter to: `*.apk`.\\n\\nExample: \\n\\n- `*release*.apk`\n      - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\\n\"\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: \"The step will **not** copy the generated apk files that match this\n      filter into the Bitrise Deploy Directory.\\nYou can use this filter to avoid\n      moving unalinged or unsigned apk files.\\n\\nThis filter is a standard find commands\n      negated -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an\n      empty filter, every apk file (selected by `apk_file_include_filter`) will be\n      copied.\\n\\nExample: \\n\\n- `*unaligned*.apk` - Avoid to copy apk if filename\n      contains `unaligned`.\\n\"\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.5.6/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-05-04T14:26:30.829634283+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: e0146655a0457c6dd01944e10dbf7f3e25683838\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: \"The step will copy the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find \\n\\nIf you specify an empty\n      filter, the step will set this filter to: `*.apk`.\\n\\nExample: \\n\\n- `*release*.apk`\n      - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\\n\"\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: \"The step will **not** copy the generated apk files that match this\n      filter into the Bitrise Deploy Directory.\\nYou can use this filter to avoid\n      moving unalinged or unsigned apk files.\\n\\nThis filter is a standard find commands\n      negated -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an\n      empty filter, every apk file (selected by `apk_file_include_filter`) will be\n      copied.\\n\\nExample: \\n\\n- `*unaligned*.apk` - Avoid to copy apk if filename\n      contains `unaligned`.\\n\"\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.6.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-05-26T16:21:50.860734168+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 957b09d19782e07fd9b2c30ca9f6b426e30d79fd\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: \"The step will copy the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find \\n\\nIf you specify an empty\n      filter, the step will set this filter to: `*.apk`.\\n\\nExample: \\n\\n- `*release*.apk`\n      - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\\n\"\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: \"The step will **not** copy the generated apk files that match this\n      filter into the Bitrise Deploy Directory.\\nYou can use this filter to avoid\n      moving unalinged or unsigned apk files.\\n\\nThis filter is a standard find commands\n      negated -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an\n      empty filter, every apk file (selected by `apk_file_include_filter`) will be\n      copied.\\n\\nExample: \\n\\n- `*unaligned*.apk` - Avoid to copy apk if filename\n      contains `unaligned`.\\n\"\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.6.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-05-30T12:50:40.436951703+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 62365fbd550e1906b5a8f14edba686e14e15e38d\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: \"The step will copy the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find \\n\\nIf you specify an empty\n      filter, the step will set this filter to: `*.apk`.\\n\\nExample: \\n\\n- `*release*.apk`\n      - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\\n\"\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: \"The step will **not** copy the generated apk files that match this\n      filter into the Bitrise Deploy Directory.\\nYou can use this filter to avoid\n      moving unalinged or unsigned apk files.\\n\\nThis filter is a standard find commands\n      negated -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an\n      empty filter, every apk file (selected by `apk_file_include_filter`) will be\n      copied.\\n\\nExample: \\n\\n- `*unaligned*.apk` - Avoid to copy apk if filename\n      contains `unaligned`.\\n\"\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.6.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-05-31T17:25:23.938276257+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 9dd55aad540052ac3cf3c3c490be4a9bd1ee38e2\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: '*.apk'\n  opts:\n    description: \"The step will copy the generated apk files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find \\n\\nIf you specify an empty\n      filter, the step will set this filter to: `*.apk`.\\n\\nExample: \\n\\n- `*release*.apk`\n      - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\\n\"\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    description: \"The step will **not** copy the generated apk files that match this\n      filter into the Bitrise Deploy Directory.\\nYou can use this filter to avoid\n      moving unalinged or unsigned apk files.\\n\\nThis filter is a standard find commands\n      negated -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an\n      empty filter, every apk file (selected by `apk_file_include_filter`) will be\n      copied.\\n\\nExample: \\n\\n- `*unaligned*.apk` - Avoid to copy apk if filename\n      contains `unaligned`.\\n\"\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_MAPPING_PATH: \"\"\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-06-08T14:35:34.733274433+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 2a7cc80ca795f5c8cbb71cde74e08270ca9f4139\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-06-26T16:55:47.637577081+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 881b09f27a913e1e607d746e800effcd36583474\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-07-14T11:13:17.545766565+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: f98e8fc37c023d3d169197b681e2db5cf5cf27a9\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-07-21T10:15:35.71323261+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: abafec5c2f078da6e0a68d77eeceaf86494a34fa\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.5/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-07-28T14:23:19.928097578+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 05cc5a8ece825a9b0a8e338ad8c750f3923eee03\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.6/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-07-28T16:26:35.094701101+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 4d0f01b0ea234b224035015e6e16c9ccd0166a5e\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.7/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-09-05T10:55:04.636203092+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: b8c43bc77d1eacd1d883ef09982a17b9d58821fc\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      - `*release*.apk` - Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`).\n    title: APK file include filter\n- apk_file_exclude_filter: '*-unaligned.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      - `*unaligned*.apk` - Avoid to copy apk if filename contains `unaligned`.\n    title: APK file exclude filter\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, no mapping files will be copied.\n\n      Example: `*mapping.txt` - Copy every mapping.txt file.\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: |\n      The step will **not** copy the generated mapping files that match this filter into the Bitrise Deploy Directory.\n      You can use this step to avoid moving beta mapping file.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every mapping files (selected by `mapping_file_include_filter`) will be copied.\n\n      Example: `*/beta/mapping.txt` - Avoid to copy mapping.txt file in a `beta` directoy.\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.7.8/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-10-20T12:12:55.736022195+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: c6b0bfba2fad55dab4426e001141e4cbd4fb395a\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Avoid to copy apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Avoid to copy apk if filename contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk which filename contains `Test`, like (`./app/build/outputs/apk/app-debug-androidTest-unaligned.apk`):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Avoid to copy test apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nAvoid to copy mapping.txt file in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.8.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2017-10-26T14:25:28.028502579+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: ee0b18f1efba51c53880609436770578cbd9f7b4\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Avoid to copy apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Avoid to copy apk if filename contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk which filename contains `Test`, like (`./app/build/outputs/apk/app-debug-androidTest-unaligned.apk`):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Avoid to copy test apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nAvoid to copy mapping.txt file in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.8.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2018-01-26T11:34:51.608797398+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 2b5fbd035cc4fdceb644e855d536a1e7cd906e83\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Avoid to copy apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Avoid to copy apk if filename contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk which filename contains `Test`, like (`./app/build/outputs/apk/app-debug-androidTest-unaligned.apk`):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Avoid to copy test apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nAvoid to copy mapping.txt file in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.8.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2018-02-07T13:43:31.233866536+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: c55105b1b2fc27b8cb2cd2ea3e7b5c299e4d7e4b\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Avoid to copy apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Avoid to copy apk if filename contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk which filename contains `Test`, like (`./app/build/outputs/apk/app-debug-androidTest-unaligned.apk`):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Avoid to copy test apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nAvoid to copy mapping.txt file in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.8.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2018-02-21T14:09:43.366060081+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: 645e70272d65ccd0cecff2f460d418e327f2fe23\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Avoid to copy apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Avoid to copy apk if filename contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk which filename contains `Test`, like (`./app/build/outputs/apk/app-debug-androidTest-unaligned.apk`):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Avoid to copy test apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nAvoid to copy mapping.txt file in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.8.4/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APKs into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2018-12-21T13:38:08.761068496Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-runner.git\n  commit: e1afcced10cb449c67b526f5da945aa8ca5f7004\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every apk which filename contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Avoid to copy apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Avoid to copy apk if filename contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every apk which filename contains `Test`, like (`./app/build/outputs/apk/app-debug-androidTest-unaligned.apk`):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every apk file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Avoid to copy test apk if filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nAvoid to copy mapping.txt file in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK - after filtering.\n    title: Path of the generated test APK\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK paths - after filtering.\n    title: List of the generated APK paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.8.5/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2019-04-12T12:28:25.560242561Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 116546870e2bdbfb272a44b0ba0686e77562f68a\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- apk_file_include_filter: '*.apk'\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      This filter is a standard find commands -path pattern, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, the step will set this filter to: `*.apk`.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK files that match these filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unaligned and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      This filter is a standard find commands negated -path flag, see: http://linux.die.net/man/1/find\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nThis filter is a standard find commands\n      -path pattern, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, no mapping files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt\n      file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nThis filter is a standard find commands negated\n      -path flag, see: http://linux.die.net/man/1/find\\n\\nIf you specify an empty\n      filter, every mapping files (selected by `mapping_file_include_filter`) will\n      be copied.\\n\\nExample: \\n\\nDo not copy any mapping.txt file that is in a `beta`\n      directoy:\\n\\n```\\n*/beta/mapping.txt\\n``` \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2019-05-17T14:47:30.422083887Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 8def79b61e3185d8af1316a6a5ae603c9e227bd1\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK and AAB files that match this filter into the Bitrise Deploy Directory.\n\n      Seperate patterns with a newline.\n\n      Example:\n\n      Copy every APK and AAB file:\n\n      ```\n      *.apk\n      *.aab\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK and AAB files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned APK and AAB files.\n\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n\n      Seperate patterns with a newline.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK files that match these filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unaligned and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nIf you specify an empty filter, no mapping\n      files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nIf you specify an empty filter, every mapping files\n      (selected by `mapping_file_include_filter`) will be copied.\\n\\nExample: \\n\\nDo\n      not copy any mapping.txt file that is in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2019-12-16T12:39:21.53747857Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: e19792c015eb4b2dd3650f32c63eaf29b8c30d2c\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK and AAB files that match this filter into the Bitrise Deploy Directory.\n\n      Seperate patterns with a newline.\n\n      Example:\n\n      Copy every APK and AAB file:\n\n      ```\n      *.apk\n      *.aab\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK and AAB files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned APK and AAB files.\n\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n\n      Seperate patterns with a newline.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK files that match these filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unaligned and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nIf you specify an empty filter, no mapping\n      files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nIf you specify an empty filter, every mapping files\n      (selected by `mapping_file_include_filter`) will be copied.\\n\\nExample: \\n\\nDo\n      not copy any mapping.txt file that is in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2020-02-17T12:52:25.03157879Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 2f275978dc9d8140ba307b0d116bf4bd6502a545\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK and AAB files that match this filter into the Bitrise Deploy Directory.\n\n      Seperate patterns with a newline.\n\n      Example:\n\n      Copy every APK and AAB file:\n\n      ```\n      *.apk\n      *.aab\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK and AAB files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned APK and AAB files.\n\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n\n      Seperate patterns with a newline.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nIf you specify an empty filter, no mapping\n      files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nIf you specify an empty filter, every mapping files\n      (selected by `mapping_file_include_filter`) will be copied.\\n\\nExample: \\n\\nDo\n      not copy any mapping.txt file that is in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2020-02-27T15:37:45.886521485Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 7497bb7e3a9a86ec0ae83ddc9bdd842a1c5ceb3d\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK and AAB files that match this filter into the Bitrise Deploy Directory.\n\n      Seperate patterns with a newline.\n\n      Example:\n\n      Copy every APK and AAB file:\n\n      ```\n      *.apk\n      *.aab\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK and AAB files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned APK and AAB files.\n\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n\n      Seperate patterns with a newline.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nIf you specify an empty filter, no mapping\n      files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nIf you specify an empty filter, every mapping files\n      (selected by `mapping_file_include_filter`) will be copied.\\n\\nExample: \\n\\nDo\n      not copy any mapping.txt file that is in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.4/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2020-07-23T11:13:45.430617843Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 90953f9b75cb0d06a4dfe50af48a22a35bff9567\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK and AAB files that match this filter into the Bitrise Deploy Directory.\n\n      Seperate patterns with a newline.\n\n      Example:\n\n      Copy every APK and AAB file:\n\n      ```\n      *.apk\n      *.aab\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK and AAB files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned APK and AAB files.\n\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n\n      Seperate patterns with a newline.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nIf you specify an empty filter, no mapping\n      files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nIf you specify an empty filter, every mapping files\n      (selected by `mapping_file_include_filter`) will be copied.\\n\\nExample: \\n\\nDo\n      not copy any mapping.txt file that is in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the $BITRISE_GRADLE_RAW_RESULT_TEXT_PATH variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.5/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs the specified gradle task.\ndescription: |-\n  Runs the specified gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`).\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2020-09-02T10:01:46.855019426Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 016515ea1b596ebaea2dfe63d0e8b614b17cc3b4\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The step will copy the generated APK and AAB files that match this filter into the Bitrise Deploy Directory.\n\n      Seperate patterns with a newline.\n\n      Example:\n\n      Copy every APK and AAB file:\n\n      ```\n      *.apk\n      *.aab\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated APK and AAB files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned APK and AAB files.\n\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n\n      Seperate patterns with a newline.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The step will copy the generated apk files that match this filter into the Bitrise Deploy Directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The step will **not** copy the generated apk files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n\n      Example:\n\n      Do not copy the test APK file if its filename contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The step will copy the generated mapping files that match this filter\n      into the Bitrise Deploy Directory.\\n\\nIf you specify an empty filter, no mapping\n      files will be copied.\\n\\nExample: \\n\\nCopy every mapping.txt file:\\n\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The step will **not** copy the generated mapping files that match\n      this filter into the Bitrise Deploy Directory.\\nYou can use this step to avoid\n      moving beta mapping file.\\n\\nIf you specify an empty filter, every mapping files\n      (selected by `mapping_file_include_filter`) will be copied.\\n\\nExample: \\n\\nDo\n      not copy any mapping.txt file that is in a `beta` directoy:\\n\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the $BITRISE_GRADLE_RAW_RESULT_TEXT_PATH variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n\n      Example:\n\n      Copy every APK file:\n\n      ```\n      \"*.apk\"\n      ```\n\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n\n      Examples:\n\n      Do not copy APK files with a filename that contains `unaligned`:\n\n      ```\n      *unaligned*.apk\n      ```\n\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.6/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: \"The Step runs the specified Gradle task and copies the generated APK\n  and AAB files into\\nthe Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is\n  capable of doing everything that you can do with Gradle on your own machine. \\n\\n###\n  Configuring the Step \\n\\nTo use this Step, you need at least two things:\\n\\n* [Gradle\n  Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\\n* A Gradle\n  task that is correctly configured in your Gradle project.\\n\\nThe Step can run the\n  specified task with the Gradle Wrapper. For the basic configuration:\\n\\n1. Open\n  the **Config** input group.\\n1. In the **Gradle task to run** input, add the task\n  you want to run. Without an existing, valid task, the Step will fail. \\n1. Set the\n  `gradlew` file path: this is the path where the Gradle Wrapper lives in your project.\n  The path should be relative to the project's root. \\n1. Optionally, you can set\n  a `build.gradle` file for the Step in the **Optional path to the gradle build file\n  to use** input.\\n\\nTo configure exporting an APK or AAB file generated by the Step:\\n\\n1.\n  Open the **Export config** input group. \\n1. Filter the files you want the Step\n  to export. You can filter:\\n   * APK and AAB files.\\n   * Test APK files.\\n   *\n  Mapping files.\\n   Both exclude and include filters can be used. Each filter option\n  can take multiple patterns, with each pattern on its own line in the input field.\n  \\n   \\n### Troubleshooting \\n\\nIf the Step keeps failing because it can't download\n  the dependencies, check the `repositories` section in your `build.gradle` file.\n  \\nIt's possible that one or more of the services listed there are down so we Bitrise\n  can't connect to them to download the dependencies you need.\\n\\nIf you use a `build.gradle`\n  file and get the error `Issue with input: GradleFile does not exist`, check the\n  **Optional path to the gradle build file to use** input. \\nRemember, the path must\n  be relative to the root of the repository.\\n\\n### Useful links \\n\\n* [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\\n*\n  [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n*\n  [Gradle Runner vs Android Build](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#gradle-runner-vs-android-build)\\n\\n###\n  Related Steps \\n\\n* [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\\n*\n  [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\\n*\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\"\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2020-11-20T13:02:14.979368049Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 611c78ccbf6f6fe70f482c62f8d035984dc0714f\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The Step will copy the generated mapping files that match this filter\n      into the Bitrise deploy directory.\\nIf you specify an empty filter, no mapping\n      files will be copied.\\nExample: \\n\\nCopy every mapping.txt file:\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The Step will **not** copy the generated mapping files that match\n      this filter into the Bitrise deploy directory.\\nYou can use this input to avoid\n      moving a beta mapping file, for example.\\nIf you specify an empty filter, every\n      mapping file (selected by `mapping_file_include_filter`) will be copied.\\nExample:\n      \\n\\nDo not copy any mapping.txt file that is in a `beta` directoy:\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the $BITRISE_GRADLE_RAW_RESULT_TEXT_PATH variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n      Example:\n      Copy every APK file:\n      ```\n      \"*.apk\"\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.7/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: \"The Step runs the specified Gradle task and copies the generated APK\n  and AAB files into\\nthe Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is\n  capable of doing everything that you can do with Gradle on your own machine. \\n\\n###\n  Configuring the Step \\n\\nTo use this Step, you need at least two things:\\n\\n* [Gradle\n  Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\\n* A Gradle\n  task that is correctly configured in your Gradle project.\\n\\nThe Step can run the\n  specified task with the Gradle Wrapper. For the basic configuration:\\n\\n1. Open\n  the **Config** input group.\\n1. In the **Gradle task to run** input, add the task\n  you want to run. Without an existing, valid task, the Step will fail. \\n1. Set the\n  `gradlew` file path: this is the path where the Gradle Wrapper lives in your project.\n  The path should be relative to the project's root. \\n1. Optionally, you can set\n  a `build.gradle` file for the Step in the **Optional path to the gradle build file\n  to use** input.\\n\\nTo configure exporting an APK or AAB file generated by the Step:\\n\\n1.\n  Open the **Export config** input group. \\n1. Filter the files you want the Step\n  to export. You can filter:\\n   * APK and AAB files.\\n   * Test APK files.\\n   *\n  Mapping files.\\n   Both exclude and include filters can be used. Each filter option\n  can take multiple patterns, with each pattern on its own line in the input field.\n  \\n   \\n### Troubleshooting \\n\\nIf the Step keeps failing because it can't download\n  the dependencies, check the `repositories` section in your `build.gradle` file.\n  \\nIt's possible that one or more of the services listed there are down so we Bitrise\n  can't connect to them to download the dependencies you need.\\n\\nIf you use a `build.gradle`\n  file and get the error `Issue with input: GradleFile does not exist`, check the\n  **Optional path to the gradle build file to use** input. \\nRemember, the path must\n  be relative to the root of the repository.\\n\\n### Useful links \\n\\n* [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\\n*\n  [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n*\n  [Gradle Runner vs Android Build](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#gradle-runner-vs-android-build)\\n\\n###\n  Related Steps \\n\\n* [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\\n*\n  [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\\n*\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\"\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2021-04-12T09:10:48.936072554Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: b05cc929a2efed50c1adcd00f00d3329b1c2d58a\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The Step will copy the generated mapping files that match this filter\n      into the Bitrise deploy directory.\\nIf you specify an empty filter, no mapping\n      files will be copied.\\nExample: \\n\\nCopy every mapping.txt file:\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The Step will **not** copy the generated mapping files that match\n      this filter into the Bitrise deploy directory.\\nYou can use this input to avoid\n      moving a beta mapping file, for example.\\nIf you specify an empty filter, every\n      mapping file (selected by `mapping_file_include_filter`) will be copied.\\nExample:\n      \\n\\nDo not copy any mapping.txt file that is in a `beta` directoy:\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n      Example:\n      Copy every APK file:\n      ```\n      \"*.apk\"\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.8/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: \"The Step runs the specified Gradle task and copies the generated APK\n  and AAB files into\\nthe Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is\n  capable of doing everything that you can do with Gradle on your own machine. \\n\\n###\n  Configuring the Step \\n\\nTo use this Step, you need at least two things:\\n\\n* [Gradle\n  Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\\n* A Gradle\n  task that is correctly configured in your Gradle project.\\n\\nThe Step can run the\n  specified task with the Gradle Wrapper. For the basic configuration:\\n\\n1. Open\n  the **Config** input group.\\n1. In the **Gradle task to run** input, add the task\n  you want to run. Without an existing, valid task, the Step will fail. \\n1. Set the\n  `gradlew` file path: this is the path where the Gradle Wrapper lives in your project.\n  The path should be relative to the project's root. \\n1. Optionally, you can set\n  a `build.gradle` file for the Step in the **Optional path to the gradle build file\n  to use** input.\\n\\nTo configure exporting an APK or AAB file generated by the Step:\\n\\n1.\n  Open the **Export config** input group. \\n1. Filter the files you want the Step\n  to export. You can filter:\\n   * APK and AAB files.\\n   * Test APK files.\\n   *\n  Mapping files.\\n   Both exclude and include filters can be used. Each filter option\n  can take multiple patterns, with each pattern on its own line in the input field.\n  \\n   \\n### Troubleshooting \\n\\nIf the Step keeps failing because it can't download\n  the dependencies, check the `repositories` section in your `build.gradle` file.\n  \\nIt's possible that one or more of the services listed there are down so we Bitrise\n  can't connect to them to download the dependencies you need.\\n\\nIf you use a `build.gradle`\n  file and get the error `Issue with input: GradleFile does not exist`, check the\n  **Optional path to the gradle build file to use** input. \\nRemember, the path must\n  be relative to the root of the repository.\\n\\n### Useful links \\n\\n* [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\\n*\n  [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n*\n  [Gradle Runner vs Android Build](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#gradle-runner-vs-android-build)\\n\\n###\n  Related Steps \\n\\n* [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\\n*\n  [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\\n*\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\"\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2021-05-28T12:22:58.674477267Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 6fdb353159a3118e26624e2818dbfa928eeb8118\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The Step will copy the generated mapping files that match this filter\n      into the Bitrise deploy directory.\\nIf you specify an empty filter, no mapping\n      files will be copied.\\nExample: \\n\\nCopy every mapping.txt file:\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The Step will **not** copy the generated mapping files that match\n      this filter into the Bitrise deploy directory.\\nYou can use this input to avoid\n      moving a beta mapping file, for example.\\nIf you specify an empty filter, every\n      mapping file (selected by `mapping_file_include_filter`) will be copied.\\nExample:\n      \\n\\nDo not copy any mapping.txt file that is in a `beta` directoy:\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n      Example:\n      Copy every APK file:\n      ```\n      \"*.apk\"\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/1.9.9/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: \"The Step runs the specified Gradle task and copies the generated APK\n  and AAB files into\\nthe Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is\n  capable of doing everything that you can do with Gradle on your own machine. \\n\\n###\n  Configuring the Step \\n\\nTo use this Step, you need at least two things:\\n\\n* [Gradle\n  Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\\n* A Gradle\n  task that is correctly configured in your Gradle project.\\n\\nThe Step can run the\n  specified task with the Gradle Wrapper. For the basic configuration:\\n\\n1. Open\n  the **Config** input group.\\n1. In the **Gradle task to run** input, add the task\n  you want to run. Without an existing, valid task, the Step will fail. \\n1. Set the\n  `gradlew` file path: this is the path where the Gradle Wrapper lives in your project.\n  The path should be relative to the project's root. \\n1. Optionally, you can set\n  a `build.gradle` file for the Step in the **Optional path to the gradle build file\n  to use** input.\\n\\nTo configure exporting an APK or AAB file generated by the Step:\\n\\n1.\n  Open the **Export config** input group. \\n1. Filter the files you want the Step\n  to export. You can filter:\\n   * APK and AAB files.\\n   * Test APK files.\\n   *\n  Mapping files.\\n   Both exclude and include filters can be used. Each filter option\n  can take multiple patterns, with each pattern on its own line in the input field.\n  \\n   \\n### Troubleshooting \\n\\nIf the Step keeps failing because it can't download\n  the dependencies, check the `repositories` section in your `build.gradle` file.\n  \\nIt's possible that one or more of the services listed there are down so we Bitrise\n  can't connect to them to download the dependencies you need.\\n\\nIf you use a `build.gradle`\n  file and get the error `Issue with input: GradleFile does not exist`, check the\n  **Optional path to the gradle build file to use** input. \\nRemember, the path must\n  be relative to the root of the repository.\\n\\n### Useful links \\n\\n* [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\\n*\n  [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n*\n  [Gradle Runner vs Android Build](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#gradle-runner-vs-android-build)\\n\\n###\n  Related Steps \\n\\n* [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\\n*\n  [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\\n*\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\"\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2021-06-24T13:25:30.323361844Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 2fc1fca0247921661e8473ba9070381cb2e85ebd\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The Step will copy the generated mapping files that match this filter\n      into the Bitrise deploy directory.\\nIf you specify an empty filter, no mapping\n      files will be copied.\\nExample: \\n\\nCopy every mapping.txt file:\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The Step will **not** copy the generated mapping files that match\n      this filter into the Bitrise deploy directory.\\nYou can use this input to avoid\n      moving a beta mapping file, for example.\\nIf you specify an empty filter, every\n      mapping file (selected by `mapping_file_include_filter`) will be copied.\\nExample:\n      \\n\\nDo not copy any mapping.txt file that is in a `beta` directoy:\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- opts:\n    category: Debug\n    description: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    title: Retry failed Gradle command, in case of temporary failure (for example\n      a network timeout).\n    value_options:\n    - \"no\"\n    - \"yes\"\n  retry_on_failure: \"yes\"\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n      Example:\n      Copy every APK file:\n      ```\n      \"*.apk\"\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/2.0.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: \"The Step runs the specified Gradle task and copies the generated APK\n  and AAB files into\\nthe Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is\n  capable of doing everything that you can do with Gradle on your own machine. \\n\\n###\n  Configuring the Step \\n\\nTo use this Step, you need at least two things:\\n\\n* [Gradle\n  Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\\n* A Gradle\n  task that is correctly configured in your Gradle project.\\n\\nThe Step can run the\n  specified task with the Gradle Wrapper. For the basic configuration:\\n\\n1. Open\n  the **Config** input group.\\n1. In the **Gradle task to run** input, add the task\n  you want to run. Without an existing, valid task, the Step will fail. \\n1. Set the\n  `gradlew` file path: this is the path where the Gradle Wrapper lives in your project.\n  The path should be relative to the project's root. \\n1. Optionally, you can set\n  a `build.gradle` file for the Step in the **Optional path to the gradle build file\n  to use** input.\\n\\nTo configure exporting an APK or AAB file generated by the Step:\\n\\n1.\n  Open the **Export config** input group. \\n1. Filter the files you want the Step\n  to export. You can filter:\\n   * APK and AAB files.\\n   * Test APK files.\\n   *\n  Mapping files.\\n   Both exclude and include filters can be used. Each filter option\n  can take multiple patterns, with each pattern on its own line in the input field.\n  \\n   \\n### Troubleshooting \\n\\nIf the Step keeps failing because it can't download\n  the dependencies, check the `repositories` section in your `build.gradle` file.\n  \\nIt's possible that one or more of the services listed there are down so we Bitrise\n  can't connect to them to download the dependencies you need.\\n\\nIf you use a `build.gradle`\n  file and get the error `Issue with input: GradleFile does not exist`, check the\n  **Optional path to the gradle build file to use** input. \\nRemember, the path must\n  be relative to the root of the repository.\\n\\n### Useful links \\n\\n* [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\\n*\n  [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n*\n  [Gradle Runner vs Android Build](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#gradle-runner-vs-android-build)\\n\\n###\n  Related Steps \\n\\n* [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\\n*\n  [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\\n*\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\"\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2021-07-13T10:12:43.795318182Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: cfb44972cfdf9bd1224c54d4b775440b19b4cce3\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The Step will copy the generated mapping files that match this filter\n      into the Bitrise deploy directory.\\nIf you specify an empty filter, no mapping\n      files will be copied.\\nExample: \\n\\nCopy every mapping.txt file:\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: null\n  opts:\n    category: Export Config\n    description: \"The Step will **not** copy the generated mapping files that match\n      this filter into the Bitrise deploy directory.\\nYou can use this input to avoid\n      moving a beta mapping file, for example.\\nIf you specify an empty filter, every\n      mapping file (selected by `mapping_file_include_filter`) will be copied.\\nExample:\n      \\n\\nDo not copy any mapping.txt file that is in a `beta` directoy:\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n      Example:\n      Copy every APK file:\n      ```\n      \"*.apk\"\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/2.0.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: \"The Step runs the specified Gradle task and copies the generated APK\n  and AAB files into\\nthe Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is\n  capable of doing everything that you can do with Gradle on your own machine. \\n\\n###\n  Configuring the Step \\n\\nTo use this Step, you need at least two things:\\n\\n* [Gradle\n  Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\\n* A Gradle\n  task that is correctly configured in your Gradle project.\\n\\nThe Step can run the\n  specified task with the Gradle Wrapper. For the basic configuration:\\n\\n1. Open\n  the **Config** input group.\\n1. In the **Gradle task to run** input, add the task\n  you want to run. Without an existing, valid task, the Step will fail. \\n1. Set the\n  `gradlew` file path: this is the path where the Gradle Wrapper lives in your project.\n  The path should be relative to the project's root. \\n1. Optionally, you can set\n  a `build.gradle` file for the Step in the **Optional path to the gradle build file\n  to use** input.\\n\\nTo configure exporting an APK or AAB file generated by the Step:\\n\\n1.\n  Open the **Export config** input group. \\n1. Filter the files you want the Step\n  to export. You can filter:\\n   * APK and AAB files.\\n   * Test APK files.\\n   *\n  Mapping files.\\n   Both exclude and include filters can be used. Each filter option\n  can take multiple patterns, with each pattern on its own line in the input field.\n  \\n   \\n### Troubleshooting \\n\\nIf the Step keeps failing because it can't download\n  the dependencies, check the `repositories` section in your `build.gradle` file.\n  \\nIt's possible that one or more of the services listed there are down so we Bitrise\n  can't connect to them to download the dependencies you need.\\n\\nIf you use a `build.gradle`\n  file and get the error `Issue with input: GradleFile does not exist`, check the\n  **Optional path to the gradle build file to use** input. \\nRemember, the path must\n  be relative to the root of the repository.\\n\\n### Useful links \\n\\n* [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\\n*\n  [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\\n*\n  [Gradle Runner vs Android Build](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#gradle-runner-vs-android-build)\\n\\n###\n  Related Steps \\n\\n* [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\\n*\n  [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\\n*\n  [Android Build](https://www.bitrise.io/integrations/steps/android-build)\"\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2021-08-16T09:43:15.847412443Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 47a5e9b4238ef092da17485dd2729b0244935b53\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: \"The Step will copy the generated mapping files that match this filter\n      into the Bitrise deploy directory.\\nIf you specify an empty filter, no mapping\n      files will be copied.\\nExample: \\n\\nCopy every mapping.txt file:\\n```\\n*mapping.txt\\n```\\n\"\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: \"The Step will **not** copy the generated mapping files that match\n      this filter into the Bitrise deploy directory.\\nYou can use this input to avoid\n      moving a beta mapping file, for example.\\nIf you specify an empty filter, every\n      mapping file (selected by `mapping_file_include_filter`) will be copied.\\nExample:\n      \\n\\nDo not copy any mapping.txt file that is in a `beta` directoy:\\n```\\n*/beta/mapping.txt\\n```\n      \\n\"\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace --no-daemon\n  opts:\n    category: Debug\n    description: |-\n      Options added to the end of the Gradle call.\n      You can use multiple options, separated by a space\n      character. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as an artifact.\n    title: Additional options for Gradle call\n- apk_file_include_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file include filter` input instead and set this input to empty value.\n      The step will copy the generated APK files that match this filter into the Bitrise Deploy Directory.\n      If you specify an empty filter, the new input \"APK and AAB file include filter\" will be used.\n      Example:\n      Copy every APK file:\n      ```\n      \"*.apk\"\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK file include filter\n- apk_file_exclude_filter: null\n  opts:\n    category: Deprecated\n    description: |\n      This input is **DEPRECATED** - use the `APK and AAB file exclude filter` input instead and set this input to empty value.\n      One filter per line. The step will **not** copy the generated APK files that match this filters into the Bitrise Deploy Directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, the new input \"APK and AAB file exclude filter\" will be used.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK file exclude filter\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/3.0.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n  1. Optionally, you can set a `build.gradle` file for the Step in the **Optional path to the gradle build file to use** input.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2024-11-27T09:57:31.223552408Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 25dbfa549983e7a016a67fea3c246885d98a697e\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    category: Config\n    description: |\n      Optional path to the Gradle build file to use. It should be relative to the root of the project.\n    title: Optional path to the Gradle build file to use\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/4.0.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2025-08-25T07:40:20.427544213Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: d447797f72e1c559dafbee5ecd2bba4998b6e0fe\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/4.0.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2025-08-28T11:49:11.081625315Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: ae787f64a978ec08c32895277c0c875ff2757353\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/4.0.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2025-11-13T08:22:03.044627412Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 75d572e0dee24fc0936d4b4588e1ec9fb7970172\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- cache_level: only_deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only_deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only_deps\n    - none\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.0.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-01-29T10:28:04.01732958Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: d70fee1ddc23f6fad38811ba298cff53e423d136\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.1.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-04-29T14:16:44.115194066Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: bd2a3a61c32d35bc9ad1f890bc8894bd3abd5bed\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.1.0/bin/gradle-runner-darwin-amd64\n    hash: sha256-fd3972c619537011a4c35ab6a2975420eceadb8337c19edbfa4488af020f253a\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.1.0/bin/gradle-runner-darwin-arm64\n    hash: sha256-5509642a9270ca3ec1f01ec361cc97627c3cf43bcb213f81419808d48a5a056f\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.1.0/bin/gradle-runner-linux-amd64\n    hash: sha256-c5f31d5c48aeec4c57d55c8d863793be2ad8c1443b8e2e1c1a82ecc20e72c5d6\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.1.0/bin/gradle-runner-linux-arm64\n    hash: sha256-1b6affd3070de1569f6bbff6f5987ec4b4aaa1aac223bd857629231e722009a2\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.1.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-04-30T07:24:47.735239096Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: fd3f630906d69ebca867c59611f8f920dbe1154b\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.1.1/bin/gradle-runner-darwin-amd64\n    hash: sha256-44268e49a4cdbbfff356838dc1b36c605486b3fc71eceec79042ec43f081e752\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.1.1/bin/gradle-runner-darwin-arm64\n    hash: sha256-d0a5312b0e951b4ede4c8921c877579152d27e6d0c6ff666b0215a93c9a23fc7\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.1.1/bin/gradle-runner-linux-amd64\n    hash: sha256-bbf1dee2a24f0f2b88e3368cf5a0872f8c923cba6c689bcef46b23deb69acbee\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.1.1/bin/gradle-runner-linux-arm64\n    hash: sha256-62516ea67fb09476b824cc903a27eba419b6e8c61ea5405768d48b8e6e51ceaa\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.1.2/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-04-30T10:43:21.895541124Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: d9dddf3164905d951df8ac3d6eaf1a949cef6d81\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.1.2/bin/gradle-runner-darwin-amd64\n    hash: sha256-b1ad9f18c7834a675dd8731d302d9cb5aa851898466e3a4faf98a23ec9ab0638\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.1.2/bin/gradle-runner-darwin-arm64\n    hash: sha256-d79f6d61a882cf4a973beef682c530764707a138e232dde52ae4d4b6efbb46c5\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.1.2/bin/gradle-runner-linux-amd64\n    hash: sha256-d97e59a80f43ad14ab6c1badd31154cbf3ce07c6969353bd5a1c24f066eb75d4\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.1.2/bin/gradle-runner-linux-arm64\n    hash: sha256-db00b17e15793feb44bfda294d628577f8acb779c6c0de28461413113ad1b17c\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.1.3/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-04-30T12:22:00.55530665Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: b8f0b12f3612f06bca31af947614eff65930f407\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.1.3/bin/gradle-runner-darwin-amd64\n    hash: sha256-4fd538888f4be6df32cd9cfece97b54a4fafdc352372e46af0955e6568e9411a\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.1.3/bin/gradle-runner-darwin-arm64\n    hash: sha256-6f07437a616406d34d73d88f8b67c3411be6db3ff6963ad8ae100dc70dad7f36\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.1.3/bin/gradle-runner-linux-amd64\n    hash: sha256-0cc41ab95574fee2b8a568d608e9ecf9409cdf02e8d0c0108927a09da036e41d\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.1.3/bin/gradle-runner-linux-arm64\n    hash: sha256-2e4472b2a49937ae2385b923ece1cc42d67374239eb0c1b0a41d21d668eb36e4\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.1.4/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-04-30T15:58:05.777448294Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: db8e30f1e68d8ecf5dbd9164df3609b16b8989fc\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.1.4/bin/gradle-runner-darwin-amd64\n    hash: sha256-b4a1724fccbd13939d3286bb676807e6d5050d6bd3fca97f06682675b4c5f35b\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.1.4/bin/gradle-runner-darwin-arm64\n    hash: sha256-432a4db22fa5827f25f271891559e09553e275ca6c95b73299a68b582ce575c1\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.1.4/bin/gradle-runner-linux-amd64\n    hash: sha256-acb2441993cdcd1acc994bde1aea9092f9995b5525b5772533dcb0c6ffcf90bb\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.1.4/bin/gradle-runner-linux-arm64\n    hash: sha256-ffb964279a792f195129595b98b8da33fb8411a1f53d7e67e2f6d59ac4132984\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.2.0/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-05-05T13:52:08.095074115Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: aeafd22314806672b158cc563e5145a41a788b33\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.2.0/bin/gradle-runner-darwin-amd64\n    hash: sha256-6d106a161cbd033d2a323ec22f66898cc07ec63c642d9e16f090a77172f882d3\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.2.0/bin/gradle-runner-darwin-arm64\n    hash: sha256-4c66144666486849e5940dcfcb95fb73dc1cad76a1b0130622c57f2f1fa437b0\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.2.0/bin/gradle-runner-linux-amd64\n    hash: sha256-dd114e6b6ffbe66af26be844226a3507785a8abbf236bd7d3e7c90ac25406e9a\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.2.0/bin/gradle-runner-linux-arm64\n    hash: sha256-9ba349b71533db251420d3d42587dace3df7cbe342b6d8ed68fa8ed6769b5aa6\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/5.2.1/step.yml",
    "content": "title: Gradle Runner\nsummary: Runs a specified Gradle task.\ndescription: |-\n  The Step runs the specified Gradle task and copies the generated APK and AAB files into\n  the Bitrise Deploy Directory (`$BITRISE_DEPLOY_DIR`). It is capable of doing everything that you can do with Gradle on your own machine.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  The Step can run the specified task with the Gradle Wrapper. For the basic configuration:\n\n  1. Open the **Config** input group.\n  1. In the **Gradle task to run** input, add the task you want to run. Without an existing, valid task, the Step will fail.\n  1. Set the `gradlew` file path: this is the path where the Gradle Wrapper lives in your project. The path should be relative to the project's root.\n\n  To configure exporting an APK or AAB file generated by the Step:\n\n  1. Open the **Export config** input group.\n  1. Filter the files you want the Step to export. You can filter:\n     * APK and AAB files.\n     * Test APK files.\n     * Mapping files.\n     Both exclude and include filters can be used. Each filter option can take multiple patterns, with each pattern on its own line in the input field.\n\n  ### Troubleshooting\n\n  If the Step keeps failing because it can't download the dependencies, check the `repositories` section in your `build.gradle` file.\n  It's possible that one or more of the services listed there are down so we Bitrise can't connect to them to download the dependencies you need.\n\n  If you use a `build.gradle` file and get the error `Issue with input: GradleFile does not exist`, check the **Optional path to the gradle build file to use** input.\n  Remember, the path must be relative to the root of the repository.\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n\n  ### Related Steps\n\n  * [Gradle Unit Test](https://www.bitrise.io/integrations/steps/gradle-unit-test)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  * Gradle cache [save](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache) Steps\nwebsite: https://github.com/bitrise-io/steps-gradle-runner\nsource_code_url: https://github.com/bitrise-io/steps-gradle-runner\nsupport_url: https://github.com/bitrise-io/steps-gradle-runner/issues\npublished_at: 2026-05-12T08:59:52.566987033Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-runner.git\n  commit: 1f2caee4f61fb912ae3f63832cda97b6226a22fc\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-runner/5.2.1/bin/gradle-runner-darwin-amd64\n    hash: sha256-6c8c1f7d5a8223d22af105f5bd481cf15461af5b23211469c8c1a7e56f820877\n  darwin-arm64:\n    storage_uri: steps/gradle-runner/5.2.1/bin/gradle-runner-darwin-arm64\n    hash: sha256-ce536eeec4803d5e2b3032e453744d2190190b4e2099db38b3b0f416ce29158f\n  linux-amd64:\n    storage_uri: steps/gradle-runner/5.2.1/bin/gradle-runner-linux-amd64\n    hash: sha256-c33801f55bd4dca77805b174e044f5d3df1f6064976045e44d0d35f9a1073515\n  linux-arm64:\n    storage_uri: steps/gradle-runner/5.2.1/bin/gradle-runner-linux-arm64\n    hash: sha256-5d323c1f3b720f161a59588567b580019429d9c8d61168303f353a1c70b97509\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-runner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- build_root_directory: .\n  opts:\n    category: Config\n    description: |\n      The root directory of the Gradle project where the gradlew file and build.gradle are located.\n      This can be either a relative path (relative to the working directory) or an absolute path.\n      For example, if your Android project is in a subdirectory called `android`, set this to `./android`.\n    title: Build root directory\n- gradle_task: assemble\n  opts:\n    category: Config\n    description: |\n      Gradle task to run.\n      You can call `gradle tasks` or `gradle tasks --all` in your\n      Gradle project directory to get the list of available tasks.\n    is_required: true\n    title: Gradle task to run\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the build_root_directory input. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: Gradle Wrapper path\n- app_file_include_filter: |\n    *.apk\n    *.aab\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated APK and AAB files that match this filter into the Bitrise deploy directory.\n      Seperate patterns with a newline.\n      Example:\n      Copy every APK and AAB file:\n      ```\n      *.apk\n      *.aab\n      ```\n      Copy every APK file with a filename that contains `release`, like (`./app/build/outputs/apk/app-release-unsigned.apk`):\n      ```\n      *release*.apk\n      ```\n    title: APK and AAB file include filter\n- app_file_exclude_filter: |\n    *unaligned.apk\n    *Test*.apk\n    */intermediates/*\n  opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated APK and AAB files that match these filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unaligned and/or unsigned APK and AAB files.\n      If you specify an empty filter, every APK and AAB file (selected by `APK and AAB file include filter`) will be copied.\n      Seperate patterns with a newline.\n      Examples:\n      Do not copy APK files with a filename that contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n      Do not copy APK files with a filename that contains `unaligned` and/or `Test`:\n      ```\n      *unaligned*.apk\n      *Test*.apk\n      ```\n    title: APK and AAB file exclude filter\n- opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated apk files that match this filter into the Bitrise deploy directory.\n\n      Example:\n      Copy every APK if its filename contains Test, like (./app/build/outputs/apk/app-debug-androidTest-unaligned.apk):\n\n      ```\n      *Test*.apk\n      ```\n    title: Test APK file include filter\n  test_apk_file_include_filter: '*Test*.apk'\n- opts:\n    category: Export Config\n    description: |\n      One filter per line. The Step will NOT copy the generated apk files that match this filters into the Bitrise deploy directory.\n      You can use this filter to avoid moving unalinged and/or unsigned apk files.\n      If you specify an empty filter, every APK file (selected by `apk_file_include_filter`) will be copied.\n      Example:\n      Do not copy the test APK file if its filename contains `unaligned`:\n      ```\n      *unaligned*.apk\n      ```\n    title: Test APK file exclude filter\n  test_apk_file_exclude_filter: \"\"\n- mapping_file_include_filter: '*/mapping.txt'\n  opts:\n    category: Export Config\n    description: |\n      The Step will copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      If you specify an empty filter, no mapping files will be copied.\n      Example:\n\n      Copy every mapping.txt file:\n      ```\n      *mapping.txt\n      ```\n    title: Mapping file include filter\n- mapping_file_exclude_filter: '*/tmp/*'\n  opts:\n    category: Export Config\n    description: |\n      The Step will **not** copy the generated mapping files that match this filter into the Bitrise deploy directory.\n      You can use this input to avoid moving a beta mapping file, for example.\n      If you specify an empty filter, every mapping file (selected by `mapping_file_include_filter`) will be copied.\n      Example:\n\n      Do not copy any mapping.txt file that is in a `beta` directoy:\n      ```\n      */beta/mapping.txt\n      ```\n    title: Mapping file exclude filter\n- gradle_options: --stacktrace\n  opts:\n    category: Debug\n    description: |-\n      Flags added to the end of the Gradle call.\n      You can use multiple options, separated by a space. Example: `--stacktrace --debug`\n      If `--debug` or `-d` options are set then only the last 20 lines of the raw gradle output will be visible in the build log.\n      The full raw output will be exported to the `$BITRISE_GRADLE_RAW_RESULT_TEXT_PATH` variable and will be added as a build artifact.\n    title: Additional flags for Gradle\noutputs:\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) APK file - after filtering.\n    title: Path of the generated APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB file,\n      after filtering based on the filter inputs.\n      If the build generates more than one AAB file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) AAB file - after filtering.\n    title: Path of the generated AAB\n- BITRISE_TEST_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated test APK file,\n      after filtering based on the filter inputs.\n      If the build generates more than one APK file which fulfills the\n      filter inputs this output will contain the last one's path.\n    summary: Path of the generated (and copied) test APK file - after filtering.\n    title: Path of the generated test APK file\n- BITRISE_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APK files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the generated (and copied) APK file paths - after filtering.\n    title: List of the generated APK file paths\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AAB files,\n      after filtering based on the filter inputs.\n      The paths are separated with `|` character, eg: `app.aab|app2.aab`\n    summary: List of the generated (and copied) AAB file paths - after filtering.\n    title: List of the generated AAB file paths\n- BITRISE_MAPPING_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated mapping.txt.\n      If more than one mapping.txt exist in project this output will contain the last one's path.\n    summary: Path of the generated (and copied) mapping.txt.\n    title: Path of the generated mapping.txt\n"
  },
  {
    "path": "steps/gradle-runner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/gradle-unit-test/0.9.0/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `./gradlew`.\ndescription: Runs Unit Tests with `./gradlew`. You can specify the test tasks to run\n  and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2015-10-29T17:22:47.128710587Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: 90a0722143cb5645b4aab48599a418a843e7e221\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- unit test\n- gradle\ndeps:\n  check_only:\n  - name: gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_expand: true\n    is_required: false\n    title: Test task\n  unit_test_task: test\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    is_expand: true\n    is_required: false\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/0.9.1/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `./gradlew`.\ndescription: Runs Unit Tests with `./gradlew`. You can specify the test tasks to run\n  and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2015-10-29T19:04:18.890650813Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: 3235ea8696f3ab9a83a6839848282d9b1a10f266\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- unit test\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_expand: true\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    is_expand: true\n    is_required: false\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/0.9.2/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `./gradlew`.\ndescription: Runs Unit Tests with `./gradlew`. You can specify the test tasks to run\n  and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2015-10-31T12:57:12.091135288Z\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: 3113ce9c2226c05da6c5f84ffe33c59b819c69a9\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- unit test\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradlew_file_path: ./gradlew\n  opts:\n    description: |\n      Path for the gradlew file\n    is_expand: true\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_expand: true\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    is_expand: true\n    is_required: false\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/0.9.3/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2016-02-09T14:54:29.534708768+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: e31a16574a5c3eef6915de6798b08dbfc628e952\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- unit test\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_expand: true\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_expand: true\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    is_expand: true\n    is_required: false\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.0/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2016-10-20T12:21:51.618291173+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: a557bc3996467bcecb37e9316e9056d7f50d34d8\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- unit test\n- gradle\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.1/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2016-10-20T12:50:00.06957284+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: 6657dfb8b99cd86c4b159c4d47f732c9e473dfc7\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Path to the gradle file to use\n    is_required: true\n    title: Path to the gradle file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.2/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2017-07-04T10:31:39.991408747+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: dbb1f1e347a26572f770fec61a7dcc725b4c80c4\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    is_required: true\n    title: Optional path to the gradle build file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.3/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2017-08-04T11:09:58.409759899+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: 2a64808b113bb2263560f14f1adfae348fed05e3\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.4/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2017-10-10T16:51:57.468480436+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: afc7320111c3c4b1d9ad8699f1dc531a61549a32\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\n- cache_level: all\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.5/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and the task flags to run ony specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2018-02-22T09:10:23.382738041+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-gradle-unit-test.git\n  commit: 26b9bffd8f229774ee23de6ffe1ccae2ebcf5f74\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path for the gradlew file\n    is_required: true\n    title: Path for the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for only a couple of files like: `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\n- cache_level: only deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.7/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and set task flags to run specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2020-09-03T16:29:45.897926168Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-unit-test.git\n  commit: d55e128970a580efaa916308746bd9c691de9e5a\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path to the gradlew file\n    is_required: true\n    title: Path to the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for specified files. For example, `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\n- cache_level: only deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/1.0.8/step.yml",
    "content": "title: Gradle Unit Test\nsummary: Runs Unit Tests with `gradlew`.\ndescription: |-\n  Runs Unit Tests with `gradlew`.\n  You can specify the test tasks to run and set task flags to run specific files.\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2021-05-28T12:29:46.05541038Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-unit-test.git\n  commit: d3726ad91e857ce17bff7a879dc9d0cca15da016\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradle_file: $GRADLE_BUILD_FILE_PATH\n  opts:\n    description: |\n      Optional path to the gradle build file to use\n    title: Optional path to the gradle build file to use\n- opts:\n    description: |\n      The test task to execute by gradlew\n    is_required: true\n    title: Test task\n  unit_test_task: test\n- gradlew_file_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Path to the gradlew file\n    is_required: true\n    title: Path to the gradlew file\n- opts:\n    description: |\n      Use this flag to execute tests for specified files. For example, `--tests='*.MyTestClass'`\n    title: Test flags\n  unit_test_flags: --continue\n- cache_level: only deps\n  opts:\n    category: Debug\n    description: |-\n      `all` - will cache build-cache and dependencies\n      `only deps` - will cache dependencies only\n      `none` - won't cache any of the above\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - all\n    - only deps\n    - none\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/2.0.0/step.yml",
    "content": "title: Run Gradle Tests\nsummary: Runs tests with `gradlew`.\ndescription: |-\n  This Step runs tests with `gradlew`.\n  You can specify the test tasks to run and set flags to the executed `gradlew` command.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  To configure the Step:\n  1. Set the Gradle project root directory in the **Project root directory** input.\n  1. Add the task you want to run in the **Test task** input.\n  1. (Optional) Add any flags you want to pass to the executed gradlew command in the **Additional flags** input. For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n  1. (Optional) You can set the file path to a `build.gradle` file for the Step in the **Path to the Gradle build script to use** input.\n\n  ### Troubleshooting\n\n  If you receive an error that Gradle Wrapper (gradlew) is required, make sure to generate one if you don't have one already. You can read\n  more about it in the [official Gradle guide](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n  * [Running a unit test](https://devcenter.bitrise.io/en/testing/android-unit-tests.html#running-a-unit-test)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2025-05-20T08:36:56.227221476Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-unit-test.git\n  commit: 32e6681801913a75cff01a2821e9f4779acabe07\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      The root directory of the Gradle project.\n      This is the directory which contains all source files from your project, as well as Gradle files, including the `gradlew` file.\n    is_required: true\n    summary: The root directory of the Gradle project.\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: The test task to be executed.\n    is_required: true\n    summary: The test task to be executed.\n    title: Test task\n  test_task: test\n- gradlew_command_flags: --continue\n  opts:\n    description: |\n      Flags to pass to the executed gradlew command.\n      For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n    summary: Flags to pass to the executed gradlew command.\n    title: Additional flags\n- gradle_build_script_path: null\n  opts:\n    description: |-\n      Path to the Gradle build script to use.\n      The path should be relative to the **Project root directory**.\n    summary: Path to the Gradle build script to use.\n    title: Path to the Gradle build script to use.\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests (`succeeded` or `failed`).\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/gradle-unit-test/2.1.0/step.yml",
    "content": "title: Run Gradle Tests\nsummary: Runs tests with `gradlew`.\ndescription: |-\n  This Step runs tests with `gradlew`.\n  You can specify the test tasks to run and set flags to the executed `gradlew` command.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  To configure the Step:\n  1. Set the Gradle project root directory in the **Project root directory** input.\n  1. Add the task you want to run in the **Test task** input.\n  1. (Optional) Add any flags you want to pass to the executed gradlew command in the **Additional flags** input. For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n  1. (Optional) You can set the file path to a `build.gradle` file for the Step in the **Path to the Gradle build script to use** input.\n\n  ### Troubleshooting\n\n  If you receive an error that Gradle Wrapper (gradlew) is required, make sure to generate one if you don't have one already. You can read\n  more about it in the [official Gradle guide](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n  * [Running a unit test](https://devcenter.bitrise.io/en/testing/android-unit-tests.html#running-a-unit-test)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2025-09-05T12:41:08.910862482Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-unit-test.git\n  commit: f41f73b38aa14885ab049427d6761102d5930162\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      The root directory of the Gradle project.\n      This is the directory which contains all source files from your project, as well as Gradle files, including the `gradlew` file.\n    is_required: true\n    summary: The root directory of the Gradle project.\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: The test task to be executed.\n    is_required: true\n    summary: The test task to be executed.\n    title: Test task\n  test_task: test\n- gradlew_command_flags: --continue\n  opts:\n    description: |\n      Flags to pass to the executed gradlew command.\n      For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n    summary: Flags to pass to the executed gradlew command.\n    title: Additional flags\n- gradle_build_script_path: null\n  opts:\n    description: |-\n      Path to the Gradle build script to use.\n      The path should be relative to the **Project root directory**.\n    summary: Path to the Gradle build script to use.\n    title: Path to the Gradle build script to use.\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    title: Result of the tests (`succeeded` or `failed`).\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/gradle-unit-test/2.1.1/step.yml",
    "content": "title: Run Gradle Tests\nsummary: Runs tests with `gradlew`.\ndescription: |-\n  This Step runs tests with `gradlew`.\n  You can specify the test tasks to run and set flags to the executed `gradlew` command.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  To configure the Step:\n  1. Set the Gradle project root directory in the **Project root directory** input.\n  1. Add the task you want to run in the **Test task** input.\n  1. (Optional) Add any flags you want to pass to the executed gradlew command in the **Additional flags** input. For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n  1. (Optional) You can set the file path to a `build.gradle` file for the Step in the **Path to the Gradle build script to use** input.\n\n  ### Troubleshooting\n\n  If you receive an error that Gradle Wrapper (gradlew) is required, make sure to generate one if you don't have one already. You can read\n  more about it in the [official Gradle guide](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n  * [Running a unit test](https://devcenter.bitrise.io/en/testing/android-unit-tests.html#running-a-unit-test)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2025-11-13T12:51:13.309963709Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-unit-test.git\n  commit: 3cabd785adad576773d444e1d314b2827ce36501\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      The root directory of the Gradle project.\n      This is the directory which contains all source files from your project, as well as Gradle files, including the `gradlew` file.\n    is_required: true\n    summary: The root directory of the Gradle project.\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: The test task to be executed.\n    is_required: true\n    summary: The test task to be executed.\n    title: Test task\n  test_task: test\n- gradlew_command_flags: --continue\n  opts:\n    description: |-\n      Flags to pass to the executed gradlew command.\n      For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n    summary: Flags to pass to the executed gradlew command.\n    title: Additional flags\n- gradle_build_script_path: null\n  opts:\n    description: |-\n      Path to the Gradle build script to use.\n      The path should be relative to the **Project root directory**.\n    summary: Path to the Gradle build script to use.\n    title: Path to the Gradle build script to use.\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    description: The result of the tests executed by this Step.\n    title: Result of the tests (`succeeded` or `failed`).\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/gradle-unit-test/2.1.2/step.yml",
    "content": "title: Run Gradle Tests\nsummary: Runs tests with `gradlew`.\ndescription: |-\n  This Step runs tests with `gradlew`.\n  You can specify the test tasks to run and set flags to the executed `gradlew` command.\n\n  ### Configuring the Step\n\n  To use this Step, you need at least two things:\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n  * A Gradle task that is correctly configured in your Gradle project.\n\n  To configure the Step:\n  1. Set the Gradle project root directory in the **Project root directory** input.\n  1. Add the task you want to run in the **Test task** input.\n  1. (Optional) Add any flags you want to pass to the executed gradlew command in the **Additional flags** input. For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n  1. (Optional) You can set the file path to a `build.gradle` file for the Step in the **Path to the Gradle build script to use** input.\n\n  ### Troubleshooting\n\n  If you receive an error that Gradle Wrapper (gradlew) is required, make sure to generate one if you don't have one already. You can read\n  more about it in the [official Gradle guide](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n  ### Useful links\n\n  * [Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html)\n  * [Caching Gradle](https://devcenter.bitrise.io/builds/caching/caching-gradle/)\n  * [Running a unit test](https://devcenter.bitrise.io/en/testing/android-unit-tests.html#running-a-unit-test)\n\n  ### Related Steps\n\n  * [Generate Gradle Wrapper](https://www.bitrise.io/integrations/steps/generate-gradle-wrapper)\n  * [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  * [Android Build](https://www.bitrise.io/integrations/steps/android-build)\nwebsite: https://github.com/bitrise-io/steps-gradle-unit-test\nsource_code_url: https://github.com/bitrise-io/steps-gradle-unit-test\nsupport_url: https://github.com/bitrise-io/steps-gradle-unit-test/issues\npublished_at: 2026-03-27T11:54:08.025559446Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-gradle-unit-test.git\n  commit: c252d2ba4bd8483ec0542556701d1f57d45c1c06\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/gradle-unit-test/2.1.2/bin/gradle-unit-test-darwin-amd64\n    hash: sha256-42e15e1c6f71b9986327be1a25ff8e90bf19ccc2f86675eb855c69833f3c3816\n  darwin-arm64:\n    storage_uri: steps/gradle-unit-test/2.1.2/bin/gradle-unit-test-darwin-arm64\n    hash: sha256-b5f62a860602976d30959974369dec328a89de6830984a86b2889cb2f7552695\n  linux-amd64:\n    storage_uri: steps/gradle-unit-test/2.1.2/bin/gradle-unit-test-linux-amd64\n    hash: sha256-0a2720940782b1beeed78835f68ce1a11e2897383ad127117030d4f5b03d6606\n  linux-arm64:\n    storage_uri: steps/gradle-unit-test/2.1.2/bin/gradle-unit-test-linux-arm64\n    hash: sha256-4581ec18cf748d6ec1ad3b44434a765c7a8f387d91c2f5d24b0d97a589ef9433\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-gradle-unit-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      The root directory of the Gradle project.\n      This is the directory which contains all source files from your project, as well as Gradle files, including the `gradlew` file.\n    is_required: true\n    summary: The root directory of the Gradle project.\n    title: Project root directory\n  project_root_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: The test task to be executed.\n    is_required: true\n    summary: The test task to be executed.\n    title: Test task\n  test_task: test\n- gradlew_command_flags: --continue\n  opts:\n    description: |-\n      Flags to pass to the executed gradlew command.\n      For example, you can use `--tests='*.MyTestClass'` to run a specific test class.\n    summary: Flags to pass to the executed gradlew command.\n    title: Additional flags\n- gradle_build_script_path: null\n  opts:\n    description: |-\n      Path to the Gradle build script to use.\n      The path should be relative to the **Project root directory**.\n    summary: Path to the Gradle build script to use.\n    title: Path to the Gradle build script to use.\noutputs:\n- BITRISE_GRADLE_TEST_RESULT: null\n  opts:\n    description: The result of the tests executed by this Step.\n    title: Result of the tests (`succeeded` or `failed`).\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/gradle-unit-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/gulp/0.1.0/step.yml",
    "content": "title: Run gulp command\nsummary: Runs `gulp` with the given command and args.\ndescription: Runs `gulp` with the given command and args.\nwebsite: https://github.com/nhammond101/steps-gulp\nsource_code_url: https://github.com/nhammond101/steps-gulp\nsupport_url: https://github.com/nhammond101/steps-gulp/issues\npublished_at: 2016-11-23T15:40:06.868356835Z\nsource:\n  git: https://github.com/nhammond101/steps-gulp.git\n  commit: cd8af8700492d7cd6bd8c0c77c43ed6a688e0aed\ntype_tags:\n- gulp\ndeps:\n  brew:\n  - name: npm\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: Specify the command to run with `gulp`. For example `install`, or\n      `test`.\n    title: The `gulp` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `gulp` command. You can specify multiple arguments, separated\n      by a space character. For example `-dd -ll`\n    title: Arguments for running `gulp` commands\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/gulp/0.1.1/step.yml",
    "content": "title: Run gulp command\nsummary: Runs `gulp` with the given command and args.\ndescription: Runs `gulp` with the given command and args.\nwebsite: https://github.com/nhammond101/steps-gulp\nsource_code_url: https://github.com/nhammond101/steps-gulp\nsupport_url: https://github.com/nhammond101/steps-gulp/issues\npublished_at: 2016-12-02T12:12:33.124897245Z\nsource:\n  git: https://github.com/nhammond101/steps-gulp.git\n  commit: 3fc1b99594544775412df580ac034ea957756b2f\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: npm\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: Specify the command to run with `gulp`. For example `install`, or\n      `test`.\n    title: The `gulp` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `gulp` command. You can specify multiple arguments, separated\n      by a space character. For example `-dd -ll`\n    title: Arguments for running `gulp` commands\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/gulp/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/heroku-deploy/0.10.0/step.yml",
    "content": "title: Heroku Deploy\nsummary: Deploy to Heroku\ndescription: |-\n  Deploy to [Heroku](https://heroku.com).\n\n  This step installs the [Heroku Toolbelt](https://toolbelt.heroku.com)\n  if it's not yet installed, and it also **logs in** with the Toolbelt\n  if you're not logged in already.\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2018-08-31T08:35:20.970730301Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: 96d4c9b927d657bff006549a7beda998f4198d4b\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_token: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Heroku App ID\n"
  },
  {
    "path": "steps/heroku-deploy/0.11.0/step.yml",
    "content": "title: Heroku Deploy\nsummary: Deploy to Heroku\ndescription: |-\n  Deploy to [Heroku](https://heroku.com).\n\n  This step installs the [Heroku Toolbelt](https://toolbelt.heroku.com)\n  if it's not yet installed, and it also **logs in** with the Toolbelt\n  if you're not logged in already.\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2018-09-21T11:51:37.610721674Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: 615399833ee1a2e746496a46ae2cb59070a06a40\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_token: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n    is_required: true\n    is_sensitive: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_required: true\n    is_sensitive: true\n    title: Heroku App ID\n- force_push: \"false\"\n  opts:\n    description: |-\n      If this option is allowed the project will be\n      force-pushed to the Heroku repository. This might\n      be necessary if the repository already exists there.\n    is_required: true\n    summary: |-\n      If this option is allowed the project will be\n      force-pushed to the Heroku repository.\n    title: Force push to Heroku repository?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/heroku-deploy/0.11.1/step.yml",
    "content": "title: Heroku Deploy\nsummary: Deploy to Heroku\ndescription: |-\n  Deploy to [Heroku](https://heroku.com).\n\n  This step installs the [Heroku Toolbelt](https://toolbelt.heroku.com)\n  if it's not yet installed, and it also **logs in** with the Toolbelt\n  if you're not logged in already.\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2021-10-04T08:01:44.200961149Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: 52d96ebcfc4e3294891da4fbd7ce2b23f12b3405\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku/brew/heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_token: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n    is_required: true\n    is_sensitive: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_required: true\n    is_sensitive: true\n    title: Heroku App ID\n- force_push: \"false\"\n  opts:\n    description: |-\n      If this option is allowed the project will be\n      force-pushed to the Heroku repository. This might\n      be necessary if the repository already exists there.\n    is_required: true\n    summary: |-\n      If this option is allowed the project will be\n      force-pushed to the Heroku repository.\n    title: Force push to Heroku repository?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/heroku-deploy/0.9.0/step.yml",
    "content": "title: Deploy to Heroku\nsummary: Deploy to Heroku\ndescription: Deploy to [Heroku](https://heroku.com).\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2016-02-19T15:17:08.216664637+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: 2266e929780a7471abbb188fe8b053b159a63801\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_key: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n\n      **Security**: instead of specifying the api token here, you should\n      set it in your Bitrise Secrets! If you don't change the default\n      value of this input, you can simply specify the value for the\n      key: `HEROKU_API_TOKEN`.\n    is_required: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_required: true\n    title: Heroku App ID\n"
  },
  {
    "path": "steps/heroku-deploy/0.9.1/step.yml",
    "content": "title: Heroku Deploy\nsummary: Deploy to Heroku\ndescription: Deploy to [Heroku](https://heroku.com).\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2016-02-19T16:04:41.122177898+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: e78d587cadc9f1e97a8b10e1ae39bd283bb9bb87\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_token: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n\n      **Security**: instead of specifying the api token here, you should\n      set it in your Bitrise Secrets! If you don't change the default\n      value of this input, you can simply specify the value for the\n      key: `HEROKU_API_TOKEN`.\n    is_required: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_required: true\n    title: Heroku App ID\n"
  },
  {
    "path": "steps/heroku-deploy/0.9.2/step.yml",
    "content": "title: Heroku Deploy\nsummary: Deploy to Heroku\ndescription: Deploy to [Heroku](https://heroku.com).\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2016-02-19T17:46:40.016994822+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: 71fbf427c176eea33c4ba1d54bb231a96391640a\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_token: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n\n      **Security**: instead of specifying the api token here, you should\n      set it in your Bitrise Secrets! If you don't change the default\n      value of this input, you can simply specify the value for the\n      key: `HEROKU_API_TOKEN`.\n    is_required: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_required: true\n    title: Heroku App ID\n"
  },
  {
    "path": "steps/heroku-deploy/0.9.3/step.yml",
    "content": "title: Heroku Deploy\nsummary: Deploy to Heroku\ndescription: |-\n  Deploy to [Heroku](https://heroku.com).\n\n  This step installs the [Heroku Toolbelt](https://toolbelt.heroku.com)\n  if it's not yet installed, and it also **logs in** with the Toolbelt\n  if you're not logged in already.\nwebsite: https://github.com/bitrise-steplib/steps-heroku-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-heroku-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-heroku-deploy/issues\npublished_at: 2016-04-07T07:41:16.659416689+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-heroku-deploy.git\n  commit: d6c3fe093c4350c19ab03ab3aee457392c7eca98\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\nproject_type_tags:\n- web\ntype_tags:\n- deploy\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: heroku\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- heroku_api_token: $HEROKU_API_TOKEN\n  opts:\n    description: |\n      You can get your API Token by running `heroku auth:token` in\n      your Terminal/Command Line, if you have the [Heroku Toolbelt](https://toolbelt.heroku.com) installed,\n      or you can follow the [official guide on Heroku](https://devcenter.heroku.com/articles/platform-api-quickstart).\n\n      **Security**: instead of specifying the api token here, you should\n      set it in your Bitrise Secrets! If you don't change the default\n      value of this input, you can simply specify the value for the\n      key: `HEROKU_API_TOKEN`.\n    is_required: true\n    title: Heroku API Token\n- heroku_app_id: $HEROKU_APP_ID\n  opts:\n    description: |\n      Your webapp's Heroku App ID. This is the ID of the App you\n      can see on your [Heroku Dashboard](https://dashboard.heroku.com/apps).\n    is_required: true\n    title: Heroku App ID\n"
  },
  {
    "path": "steps/heroku-deploy/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.0.0/step.yml",
    "content": "title: HockeyApp Deploy\nsummary: |-\n  Deploy your awesome Application to HockeyApp, add notes even in markdown\n  format, notify testers, restrict download\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net).\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2015-09-08T13:39:43.645350445+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 15522d77b89b2e95868e444e798b109eba9529db\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      Although the dSYM is marked as optional in the HockeyApp\n      API documentations it seems that HockeyApp can't parse\n      the required App information from the IPA in case no\n      dSYM is generated (if dSYM generation is turned off\n      in the Xcode project settings).\n\n      To turn on dSYM generation open you Xcode\n      project, select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: dSYM file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      Identifier of the HockeyApp application\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so.\n      Once the app is registered select it from the Apps list of the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: App ID\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.1.0/step.yml",
    "content": "title: HockeyApp Deploy\nsummary: |-\n  Deploy your awesome Application to HockeyApp, add notes even in markdown\n  format, notify testers, restrict download\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net).\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2015-09-11T19:54:10.071905678+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: c323e73280dbaf91271dd623a13dc0dcae3267a3\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      Although the dSYM is marked as optional in the HockeyApp\n      API documentations it seems that HockeyApp can't parse\n      the required App information from the IPA in case no\n      dSYM is generated (if dSYM generation is turned off\n      in the Xcode project settings).\n\n      To turn on dSYM generation open you Xcode\n      project, select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: dSYM file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      Identifier of the HockeyApp application\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so.\n      Once the app is registered select it from the Apps list of the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: App ID\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.1.1/step.yml",
    "content": "title: HockeyApp Deploy\nsummary: |-\n  Deploy your awesome Application to HockeyApp, add notes even in markdown\n  format, notify testers, restrict download\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net).\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2015-10-11T11:08:04.002419706+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 8abcf33d214bfcfffda705eacd0e642ae7f5c5b1\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      Although the dSYM is marked as optional in the HockeyApp\n      API documentations it seems that HockeyApp can't parse\n      the required App information from the IPA in case no\n      dSYM is generated (if dSYM generation is turned off\n      in the Xcode project settings).\n\n      To turn on dSYM generation open you Xcode\n      project, select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: dSYM file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      Identifier of the HockeyApp application\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so.\n      Once the app is registered select it from the Apps list of the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: App ID\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.2.0/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your awesome iOS Application to HockeyApp.\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the ipa will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2015-12-15T17:08:44.096203977+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: d12dda4702b6a8045ac3a12996f7d8612f365b9d\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      Although the dSYM is marked as optional in the HockeyApp\n      API documentations it seems that HockeyApp can't parse\n      the required App information from the IPA in case no\n      dSYM is generated (if dSYM generation is turned off\n      in the Xcode project settings).\n\n      To turn on dSYM generation open you Xcode\n      project, select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: dSYM file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.2.1/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your awesome iOS Application to HockeyApp.\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the ipa will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2016-02-12T17:01:02.263987784+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 0a1c58a021ec2f6d5cca0e3420cee5c39a595154\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      Although the dSYM is marked as optional in the HockeyApp\n      API documentations it seems that HockeyApp can't parse\n      the required App information from the IPA in case no\n      dSYM is generated (if dSYM generation is turned off\n      in the Xcode project settings).\n\n      To turn on dSYM generation open you Xcode\n      project, select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: dSYM file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.2.2/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your awesome iOS Application to HockeyApp.\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the ipa will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2016-02-15T12:51:34.336947743+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 4f338288a9f5ad6cb204ab4ef1422ceaf194a17a\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      Although the dSYM is marked as optional in the HockeyApp\n      API documentations it seems that HockeyApp can't parse\n      the required App information from the IPA in case no\n      dSYM is generated (if dSYM generation is turned off\n      in the Xcode project settings).\n\n      To turn on dSYM generation open you Xcode\n      project, select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: dSYM file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.3.0/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your awesome iOS Application to HockeyApp.\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the ipa will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2016-02-18T10:58:25.983943066+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 2bf1d2ff04e75f0ec5dd4b577828bb07e3b88fa6\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path (optional)\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    title: (optional) Build job URL (on your build server)\n- opts:\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.4.0/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your awesome iOS Application to HockeyApp.\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the ipa will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2017-01-05T13:26:32.915488185+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: fcfca29f7ec8117ab16862443d598cc793436202\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-hockeyapp-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path (optional)\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    title: (optional) Build job URL (on your build server)\n- opts:\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.4.2/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your awesome iOS Application to HockeyApp.\ndescription: |-\n  Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the ipa will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2017-07-03T14:42:02.006633477+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 8d61570324bffe395c3a632c8cc968b7b139253a\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-hockeyapp-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path (optional)\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    title: (optional) Build job URL (on your build server)\n- opts:\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.4.3/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your iOS Application to HockeyApp.\ndescription: \"Deploy an iOS application to [HockeyApp](http://hockeyapp.net),\\nadd\n  notes even in markdown format, notify testers, restrict download.\\n\\nRegister a\n  HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\\nand create an\n  app to utilize this step.\\nYou also need to create a *HockeyApp Token* for your\n  app.\\n\\nIf an `app_id` is provided, the IPA file will be uploaded to the specified\n  app on HockeyApp. \\nOtherwise HockeyApp will decide whether it's a new app or an\n  update to an existing app based on the bundle ID.\"\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2018-08-31T12:26:21.504016744Z\nsource:\n  git: https://github.com/bitrise-io/steps-hockeyapp-deploy.git\n  commit: 07c8b4f04b0f16c2ec21bfe7c1f99359cbbe7d37\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-hockeyapp-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path (optional)\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    is_sensitive: true\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_sensitive: true\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    title: (optional) Build job URL (on your build server)\n- opts:\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/2.4.4/step.yml",
    "content": "title: HockeyApp iOS Deploy\nsummary: Deploy your iOS Application to HockeyApp. (Deprecated.)\ndescription: \"__Deprecated__, see [https://www.hockeyapp.net/blog/2019/11/16/hockeyApp-is-being-retired.html](https://www.hockeyapp.net/blog/2019/11/16/hockeyApp-is-being-retired.html).\\n\\nDeploy\n  an iOS application to [HockeyApp](http://hockeyapp.net),\\nadd notes even in markdown\n  format, notify testers, restrict download.\\n\\nRegister a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\\nand\n  create an app to utilize this step.\\nYou also need to create a *HockeyApp Token*\n  for your app.\\n\\nIf an `app_id` is provided, the IPA file will be uploaded to the\n  specified app on HockeyApp. \\nOtherwise HockeyApp will decide whether it's a new\n  app or an update to an existing app based on the bundle ID.\"\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues\npublished_at: 2019-11-20T08:48:45.654828776Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-deploy.git\n  commit: fcfec5e017498c2ea03cacfd97a09df0381aba08\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-hockeyapp-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    title: IPA file path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |-\n      To turn on dSYM generation open your Xcode project,\n      select *Project Settings - Build Settings - Debug Information Format*\n      and make sure it's set to the *DWARF with dSYM File* option.\n      After dsym generated, zip it and provide the zipped path as input.\n    title: dSYM zip file path (optional)\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    is_sensitive: true\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_sensitive: true\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    title: (optional) Build job URL (on your build server)\n- opts:\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/0.9.0/step.yml",
    "content": "title: HockeyApp Android Deploy [beta]\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: |-\n  Deploy an Android application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the apk will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the bundle id, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2015-12-16T22:05:50.595138121+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: 997ec1249e0697fb64077e76c8cbea98e76158b1\nhost_os_tags:\n- ubuntu\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: apk file path\n- mapping_path: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the bundle ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's bundle ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.0.0/step.yml",
    "content": "title: HockeyApp Android Deploy [beta]\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: |-\n  Deploy an Android application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the apk will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the package ID, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2016-02-15T12:49:12.894762299+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: c1ab33cbc47825b92ab22e0222d018dd77a80570\nhost_os_tags:\n- ubuntu\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\n- HockeyApp\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: apk file path\n- mapping_path: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.1.0/step.yml",
    "content": "title: HockeyApp Android Deploy [beta]\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: |-\n  Deploy an Android application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the apk will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the package ID, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2016-09-15T16:15:39.551989894+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: 16d429350dfd04f10475b39b055464e83683ab9e\nhost_os_tags:\n- ubuntu\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- deploy\n- HockeyApp\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-hockeyapp-android-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk file path\n- mapping_path: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.1.1/step.yml",
    "content": "title: HockeyApp Android Deploy\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: |-\n  Deploy an Android application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the apk will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the package ID, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2017-01-24T21:57:34.766619461+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: 1d0ad40e01780b19bbad38fc901bcc6c59f838d0\nhost_os_tags:\n- ubuntu\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-hockeyapp-android-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk file path\n- mapping_path: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.1.4/step.yml",
    "content": "title: HockeyApp Android Deploy\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: |-\n  Deploy an Android application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the apk will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the package ID, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2017-10-12T09:49:01.206222097+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: 11233370485401715cf749c2db8507a9fa47939b\nhost_os_tags:\n- ubuntu\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-hockeyapp-android-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk file path\n- mapping_path: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.2.1/step.yml",
    "content": "title: HockeyApp Android Deploy\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: |-\n  Deploy an Android application to [HockeyApp](http://hockeyapp.net),\n  add notes even in markdown format, notify testers, restrict download.\n\n  Register a HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\n  and create an app to utilize this step.\n  You also need to create a *HockeyApp Token* for your app.\n\n  If app_id is provided the apk will be upload to the specified app on HockeyApp,\n  otherwise HockeyApp will decide based on the package ID, if it's a new app, or update.\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2017-12-07T11:06:05.326319741+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: ba823f2cac42f6298cccc08d179a8f32018f20fc\nhost_os_tags:\n- ubuntu\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-hockeyapp-android-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `\"$BITRISE_APK_PATH_LIST\"`\n    is_required: true\n    summary: \"\"\n    title: apk file path(s)\n- mapping_path: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n- HOCKEYAPP_DEPLOY_PUBLIC_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of Public URLs of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of HockeyApp build URLs\n- HOCKEYAPP_DEPLOY_CONFIG_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of HockeyApp config view URLs\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.2.2/step.yml",
    "content": "title: HockeyApp Android Deploy\nsummary: Deploy your awesome Android app to HockeyApp.\ndescription: \"Deploy an Android application to [HockeyApp](http://hockeyapp.net),\\nadd\n  notes even in markdown format, notify testers, restrict download.\\n\\nRegister a\n  HockeyApp account at [http://hockeyapp.net/](http://hockeyapp.net)\\nand create an\n  app to utilize this step.\\nYou also need to create a *HockeyApp Token* for your\n  app.\\n\\nIf an `app_id` is provided, the APK file will be uploaded to the specified\n  app on HockeyApp. \\nOtherwise HockeyApp will decide whether it's a new app or an\n  update to an existing app based on the package ID.\"\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2018-08-31T12:48:54.756743706Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: 24eff3f43fa1888b95786420d68b92d3b36f6857\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-hockeyapp-android-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `\"$BITRISE_APK_PATH_LIST\"`\n    is_required: true\n    summary: \"\"\n    title: apk file path(s)\n- mapping_path: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_sensitive: true\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textile\n      * 1: Markdown\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n- HOCKEYAPP_DEPLOY_PUBLIC_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of Public URLs of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of HockeyApp build URLs\n- HOCKEYAPP_DEPLOY_CONFIG_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of HockeyApp config view URLs\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/1.3.3/step.yml",
    "content": "title: HockeyApp Android Deploy\nsummary: Deploy your awesome Android app to HockeyApp. (Deprecated.)\ndescription: \"__Deprecated__, see [https://www.hockeyapp.net/blog/2019/11/16/hockeyApp-is-being-retired.html](https://www.hockeyapp.net/blog/2019/11/16/hockeyApp-is-being-retired.html).\\n\\nDeploy\n  an Android application to [HockeyApp](http://hockeyapp.net),\\nadd notes even in\n  markdown format, notify testers, restrict download.\\n\\nRegister a HockeyApp account\n  at [http://hockeyapp.net/](http://hockeyapp.net)\\nand create an app to utilize this\n  step.\\nYou also need to create a *HockeyApp Token* for your app.\\n\\nIf an `app_id`\n  is provided, the APK file will be uploaded to the specified app on HockeyApp. \\nOtherwise\n  HockeyApp will decide whether it's a new app or an update to an existing app based\n  on the package ID.\"\nwebsite: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsource_code_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy\nsupport_url: https://github.com/bitrise-io/steps-hockeyapp-android-deploy/issues\npublished_at: 2019-11-20T08:50:45.802718251Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-hockeyapp-android-deploy.git\n  commit: cb0b057e6b89b260204bf26d19e6ad2a126a1316\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-hockeyapp-android-deploy\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to deploy.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n      - `\"$BITRISE_APK_PATH_LIST\"`\n    is_required: true\n    summary: \"\"\n    title: apk file path(s)\n- mapping_path: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: mapping.txt file path\n- api_token: \"\"\n  opts:\n    description: |-\n      Note: different access types exist when obtaining a api_token on your account page.\n\n      ## Where to get the HockeyApp API Token?\n\n      Sign in to your [http://hockeyapp.net/](http://hockeyapp.net) account,\n      click on your username at the top right corner to get to the\n      *Manage Account* page. Select the *API Tokens* option on the left side\n      and if you don't have an appropriate API Token for your app or account\n      you can register one here.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *Active API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: API Token\n- app_id: \"\"\n  opts:\n    description: |-\n      **Important:**\n      *If no App ID is specified HockeyApp will attach the build\n      to an app on HockeyApp based on the package ID, or create a new app on HockeyApp\n      if it does not match any existing HockeyApp app's package ID.*\n\n      *If you set the App ID the build will be uploaded for the specified\n      HockeyApp app/project!*\n\n      ## Where to get the HockeyApp App ID?\n\n      If you didn't register your app on [http://hockeyapp.net/](http://hockeyapp.net)\n      you first have to do so to get an App ID.\n\n      Once the app is registered select it from the Apps list on the\n      Dashboard page and on the left side you'll find the **App ID**\n      of the app. Copy and paste it here.\n    is_sensitive: true\n    summary: \"\"\n    title: 'HockeyApp: App ID'\n- notes: Deploy with Bitrise HockeyApp Deploy Step.\n  opts:\n    description: Additional notes to the deploy.\n    summary: \"\"\n    title: Notes attached to the deploy\n- notes_type: \"0\"\n  opts:\n    description: |-\n      Possible values:\n\n      * 0: Textfile\n      * 1: Markdown\n    is_required: true\n    summary: \"\"\n    title: Notes type\n    value_options:\n    - \"0\"\n    - \"1\"\n- notify: \"2\"\n  opts:\n    description: |-\n      Sets who should be notified on deployment.\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 0 - Don't notify testers\n      * 1 - Notify all testers that can install this app\n      * 2 - Notify all testers\n    is_required: true\n    summary: \"\"\n    title: Notify Testers?\n    value_options:\n    - \"0\"\n    - \"1\"\n    - \"2\"\n- opts:\n    description: |\n      Download status.\n\n      **Requires full-access tokens.**\n\n      Possible values:\n\n      * 1 - do not allow users to download the version\n      * 2 - make the version available for download.\n    is_required: true\n    summary: \"\"\n    title: Allow Download?\n    value_options:\n    - \"1\"\n    - \"2\"\n  status: \"2\"\n- mandatory: \"false\"\n  opts:\n    description: |\n      Set if version is mandatory to install.\n    is_required: true\n    summary: \"\"\n    title: Mandatory?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      Restrict download to comma-separated list of tags.\n    summary: \"\"\n    title: '(optional) Restrict download: Tags'\n  tags: \"\"\n- commit_sha: $BITRISE_GIT_COMMIT\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Git commit sha for this build\n- build_server_url: $BITRISE_BUILD_URL\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Build job URL (on your build server)\n- opts:\n    description: \"\"\n    summary: \"\"\n    title: (optional) Source Code Repository URL\n  repository_url: \"\"\noutputs:\n- HOCKEYAPP_DEPLOY_STATUS: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: 'Deployment result: ''success'' or ''failed'''\n- HOCKEYAPP_DEPLOY_PUBLIC_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Public URL of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp build\n- HOCKEYAPP_DEPLOY_CONFIG_URL: \"\"\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: URL of the HockeyApp config view\n- HOCKEYAPP_DEPLOY_PUBLIC_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of Public URLs of the newly deployed version\n- HOCKEYAPP_DEPLOY_BUILD_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of HockeyApp build URLs\n- HOCKEYAPP_DEPLOY_CONFIG_URL_LIST: \"\"\n  opts:\n    description: 'The urls are separated with `|` character, eg: `https://rink.hockeyapp.net/url/id1|https://rink.hockeyapp.net/url/id2`'\n    summary: \"\"\n    title: List of HockeyApp config view URLs\n"
  },
  {
    "path": "steps/hockeyapp-deploy-android/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/image-overlayer/1.0.2/step.yml",
    "content": "title: Image overlayer\nsummary: |\n  Add icon to an image\ndescription: |\n  This step will add icon (on the left and/or right bottom side) on the source image.\n\n  ### Usage\n\n  To give to our step the information about the expected values:\n  - Provide the source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n    - You can provide just one image's path, the step will add icons to this one only\n    - You can provide a folder's path where we many images, the step will add icons to them\n  - Left **and/or** right icons which will be added on the source image\nwebsite: https://github.com/odemolliens/bitrise-step-image-overlayer\nsource_code_url: https://github.com/odemolliens/bitrise-step-image-overlayer\nsupport_url: https://github.com/odemolliens/bitrise-step-image-overlayer/issues\npublished_at: 2021-12-14T14:11:18.857538+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-image-overlayer.git\n  commit: d4a36b68a13248ba93f5eb581fcb61ce5442e676\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n        - You can provide just one image's path, the step will add icons to this one only (eg.: `./src/assets/app_icon.png`)\n        - You can provide a folder's path where we many images, the step will add icons to them (eg.: `./src/assets/`)\n    is_expand: true\n    is_required: true\n    summary: Source image or folder path?\n    title: Source image or folder path\n  source_image: \"\"\n- left_icon: \"\"\n  opts:\n    description: The path of the icon which will be added on the left side of the\n      source image(s) (eg. `./src/assets/left_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Left icon's path\n    title: Left icon's path\n- opts:\n    description: The path of the icon which will be added on the right side of the\n      source image(s) (eg. `./src/assets/right_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Right icon's path\n    title: Right icon's path\n  right_icon: \"\"\n- opts:\n    description: Per default, the script will replace the original source image. If\n      this key is provided, it will create a new one at this path. (eg. `./src/assets/result.png)\n    is_expand: true\n    is_required: false\n    summary: Output file's path\n    title: Output file's path\n  output_path: \"\"\n- opts:\n    description: 'If the left_icon and/or right_icon are not images, it will use this\n      key to set the text color in image which will be generated (default: #FFFFFF)'\n    is_expand: true\n    is_required: false\n    summary: Text color (hexa color)\n    title: Text color (hexa color)\n  text_color: \"\"\n- center_icon: \"False\"\n  opts:\n    description: If the value is true, the step will add a mask on full source image\n      and center the left_icon at the middle of source image and the right_icon at\n      the bottom right of the left_icon\n    is_expand: true\n    is_required: false\n    summary: If you want center the icoon in the background image\n    title: If you want center the icon in the background image\n    value_options:\n    - \"True\"\n    - \"False\"\n"
  },
  {
    "path": "steps/image-overlayer/1.0.5/step.yml",
    "content": "title: Image overlayer\nsummary: |\n  Add icon to an image\ndescription: |\n  This step will add icon (on the left and/or right bottom side) on the source image.\n\n  ### Usage\n\n  To give to our step the information about the expected values:\n  - Provide the source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n    - You can provide just one image's path, the step will add icons to this one only\n    - You can provide a folder's path where we many images, the step will add icons to them\n  - Left **and/or** right icons which will be added on the source image\nwebsite: https://github.com/odemolliens/bitrise-step-image-overlayer\nsource_code_url: https://github.com/odemolliens/bitrise-step-image-overlayer\nsupport_url: https://github.com/odemolliens/bitrise-step-image-overlayer/issues\npublished_at: 2022-01-03T18:19:42.446288+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-image-overlayer.git\n  commit: 70dbeb74d3bdf4ff2aaa60c63397361699f59c3c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n        - You can provide just one image's path, the step will add icons to this one only (eg.: `./src/assets/app_icon.png`)\n        - You can provide a folder's path where we many images, the step will add icons to them (eg.: `./src/assets/`)\n    is_expand: true\n    is_required: true\n    summary: Source image or folder path?\n    title: Source image or folder path\n  source_image: \"\"\n- left_icon: \"\"\n  opts:\n    description: The path of the icon which will be added on the left side of the\n      source image(s) (eg. `./src/assets/left_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Left icon's path\n    title: Left icon's path\n- opts:\n    description: The path of the icon which will be added on the right side of the\n      source image(s) (eg. `./src/assets/right_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Right icon's path\n    title: Right icon's path\n  right_icon: \"\"\n- opts:\n    description: Per default, the script will replace the original source image. If\n      this key is provided, it will create a new one at this path. (eg. `./src/assets/result.png)\n    is_expand: true\n    is_required: false\n    summary: Output file's path\n    title: Output file's path\n  output_path: \"\"\n- opts:\n    description: 'If the left_icon and/or right_icon are not images, it will use this\n      key to set the text color in image which will be generated (default: #FFFFFF)'\n    is_expand: true\n    is_required: false\n    summary: Text color (hexa color)\n    title: Text color (hexa color)\n  text_color: \"\"\n- center_icon: \"False\"\n  opts:\n    description: If the value is true, the step will add a mask on full source image\n      and center the left_icon at the middle of source image and the right_icon at\n      the bottom right of the left_icon\n    is_expand: true\n    is_required: false\n    summary: If you want center the icoon in the background image\n    title: If you want center the icon in the background image\n    value_options:\n    - \"True\"\n    - \"False\"\n"
  },
  {
    "path": "steps/image-overlayer/1.0.6/step.yml",
    "content": "title: Add image overlay\nsummary: |\n  Add icon to an image\ndescription: |\n  This step will add icon (on the left and/or right bottom side) on the source image.\n\n  ### Usage\n\n  To give to our step the information about the expected values:\n  - Provide the source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n    - You can provide just one image's path, the step will add icons to this one only\n    - You can provide a folder's path where we many images, the step will add icons to them\n  - Left **and/or** right icons which will be added on the source image\nwebsite: https://github.com/odemolliens/bitrise-step-image-overlayer\nsource_code_url: https://github.com/odemolliens/bitrise-step-image-overlayer\nsupport_url: https://github.com/odemolliens/bitrise-step-image-overlayer/issues\npublished_at: 2022-01-18T12:42:55.783128+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-image-overlayer.git\n  commit: c19db83ea9e7bc4b60207eda818e45f54d64e917\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n        - You can provide just one image's path, the step will add icons to this one only (eg.: `./src/assets/app_icon.png`)\n        - You can provide a folder's path where we many images, the step will add icons to them (eg.: `./src/assets/`)\n    is_expand: true\n    is_required: true\n    summary: Source image or folder path?\n    title: Source image or folder path\n  source_image: \"\"\n- left_icon: \"\"\n  opts:\n    description: The path of the icon which will be added on the left side of the\n      source image(s) (eg. `./src/assets/left_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Left icon's path\n    title: Left icon's path\n- opts:\n    description: The path of the icon which will be added on the right side of the\n      source image(s) (eg. `./src/assets/right_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Right icon's path\n    title: Right icon's path\n  right_icon: \"\"\n- opts:\n    description: Per default, the script will replace the original source image. If\n      this key is provided, it will create a new one at this path. (eg. `./src/assets/result.png)\n    is_expand: true\n    is_required: false\n    summary: Output file's path\n    title: Output file's path\n  output_path: \"\"\n- opts:\n    description: 'If the left_icon and/or right_icon are not images, it will use this\n      key to set the text color in image which will be generated (default: #FFFFFF)'\n    is_expand: true\n    is_required: false\n    summary: Text color (hexa color)\n    title: Text color (hexa color)\n  text_color: \"\"\n- center_icon: \"False\"\n  opts:\n    description: If the value is true, the step will add a mask on full source image\n      and center the left_icon at the middle of source image and the right_icon at\n      the bottom right of the left_icon\n    is_expand: true\n    is_required: false\n    summary: If you want center the icoon in the background image\n    title: If you want center the icon in the background image\n    value_options:\n    - \"True\"\n    - \"False\"\n- archive_result: \"False\"\n  opts:\n    description: If the value is true, the step will compress the folder where we\n      will place all ressources according to this step\n    is_expand: true\n    is_required: false\n    summary: If you want archive assets at the end\n    title: If you want archive assets at the end\n    value_options:\n    - \"True\"\n    - \"False\"\n- export_results: \"False\"\n  opts:\n    description: If the value is true, the step will export the folder where we will\n      place all ressources according to this step\n    is_expand: true\n    is_required: false\n    summary: If you want export assets at the end\n    title: If you want export assets at the end\n    value_options:\n    - \"True\"\n    - \"False\"\n"
  },
  {
    "path": "steps/image-overlayer/1.0.7/step.yml",
    "content": "title: Add image overlay\nsummary: |\n  Add icon to an image\ndescription: |\n  This step will add icon (on the left and/or right bottom side) on the source image.\n\n  ### Usage\n\n  To give to our step the information about the expected values:\n  - Provide the source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n    - You can provide just one image's path, the step will add icons to this one only\n    - You can provide a folder's path where we many images, the step will add icons to them\n  - Left **and/or** right icons which will be added on the source image\nwebsite: https://github.com/odemolliens/bitrise-step-image-overlayer\nsource_code_url: https://github.com/odemolliens/bitrise-step-image-overlayer\nsupport_url: https://github.com/odemolliens/bitrise-step-image-overlayer/issues\npublished_at: 2022-02-09T09:06:05.970849+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-image-overlayer.git\n  commit: 8ca7add34c7a8311d538aa46962a313d983b0f38\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Source image's (or folder's) **path**, where we have the image or list of images on which we will add the icon(s)\n        - You can provide just one image's path, the step will add icons to this one only (eg.: `./src/assets/app_icon.png`)\n        - You can provide a folder's path where we many images, the step will add icons to them (eg.: `./src/assets/`)\n    is_expand: true\n    is_required: true\n    summary: Source image or folder path?\n    title: Source image or folder path\n  source_image: \"\"\n- left_icon: \"\"\n  opts:\n    description: The path of the icon which will be added on the left side of the\n      source image(s) (eg. `./src/assets/left_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Left icon's path\n    title: Left icon's path\n- opts:\n    description: The path of the icon which will be added on the right side of the\n      source image(s) (eg. `./src/assets/right_icon.png)\n    is_expand: true\n    is_required: false\n    summary: Right icon's path\n    title: Right icon's path\n  right_icon: \"\"\n- opts:\n    description: Per default, the script will replace the original source image. If\n      this key is provided, it will create a new one at this path. (eg. `./src/assets/result.png)\n    is_expand: true\n    is_required: false\n    summary: Output file's path\n    title: Output file's path\n  output_path: \"\"\n- opts:\n    description: 'If the left_icon and/or right_icon are not images, it will use this\n      key to set the text color in image which will be generated (default: #FFFFFF)'\n    is_expand: true\n    is_required: false\n    summary: Text color (hexa color)\n    title: Text color (hexa color)\n  text_color: \"\"\n- center_icon: \"False\"\n  opts:\n    description: If the value is true, the step will add a mask on full source image\n      and center the left_icon at the middle of source image and the right_icon at\n      the bottom right of the left_icon\n    is_expand: true\n    is_required: false\n    summary: If you want center the icoon in the background image\n    title: If you want center the icon in the background image\n    value_options:\n    - \"True\"\n    - \"False\"\n- archive_result: \"True\"\n  opts:\n    description: If the value is true, the step will compress the folder where we\n      will place all ressources according to this step\n    is_expand: true\n    is_required: false\n    summary: If you want archive assets at the end\n    title: If you want archive assets at the end\n    value_options:\n    - \"True\"\n    - \"False\"\n- export_results: \"True\"\n  opts:\n    description: If the value is true, the step will export the folder where we will\n      place all ressources according to this step\n    is_expand: true\n    is_required: false\n    summary: If you want export assets at the end\n    title: If you want export assets at the end\n    value_options:\n    - \"True\"\n    - \"False\"\n"
  },
  {
    "path": "steps/image-overlayer/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/instabug-android-mapping-file-upload/1.0.2/step.yml",
    "content": "title: Instabug Android Mapping File Upload\nsummary: |\n  This step uploads Android mapping file to Instabug through Bitrise CI integration.\ndescription: |\n  Upload Android mapping file to Instabug through Bitrise CI.\n\n  ### Configuring the Step\n  1. Add the **Instabug Android Mapping File Upload** step to your Workflow after any build Step.\n  2. Set the **build.gradle Path**. In general, it should work with the default value.\n  3. Set the **Instabug App Token**. It's highly recommended to have this value in a secret env var and reference that.\n\n\n  ### Troubleshooting\n  Make sure you insert the Step after any build Step so that every dependency and env var is already setted.\nwebsite: https://github.com/mendozammatias/bitrise-step-instabug-android-mapping-file-upload\nsource_code_url: https://github.com/mendozammatias/bitrise-step-instabug-android-mapping-file-upload\nsupport_url: https://github.com/mendozammatias/bitrise-step-instabug-android-mapping-file-upload/issues\npublished_at: 2024-02-28T00:40:15.39657-03:00\nsource:\n  git: https://github.com/mendozammatias/bitrise-step-instabug-android-mapping-file-upload.git\n  commit: fceb74d3bb1a4c806784196148675606a48a55ee\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- flutter\ntype_tags:\n- artifact-info\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- instabug_app_token: $INSTABUG_APP_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Instabug App Token for the given environment.\n    title: Instabug App Token\n- build_gradle_path: $BITRISE_SOURCE_DIR/android/app/build.gradle\n  opts:\n    is_required: true\n    summary: build.gradle file path. In general, it should work with the default value.\n    title: build.gradle Path.\noutputs:\n- VERSION_CODE: null\n  opts:\n    summary: Version Code extracted from build.gradle file.\n    title: Version Code\n- VERSION_NAME: null\n  opts:\n    summary: Version Name extracted from build.gradle file.\n    title: Version Name\n"
  },
  {
    "path": "steps/instabug-android-mapping-file-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/instabug-ios-symbol-upload/1.0.4/step.yml",
    "content": "title: Instabug iOS Symbol Upload\nsummary: This step uploads iOS debug symbols to Instabug through Bitrise CI integration.\ndescription: |-\n  Upload iOS debug symbols to Instabug through Bitrise CI.\n\n  ### Configuring the Step\n  1. Add the **Instabug iOS Symbol Upload** Step to your Workflow after any build Step.\n  2. Set the **Working directory**.\n  3. Set the **Instabug App Token**. It's highly recommended to have this value in a secret env var and reference that.\n\n  ### Troubleshooting\n  Make sure you insert the Step after any build Step so that every dependency and env var is already setted.\nwebsite: https://github.com/mendozammatias/bitrise-step-instabug-ios-symbol-upload\nsource_code_url: https://github.com/mendozammatias/bitrise-step-instabug-ios-symbol-upload\nsupport_url: https://github.com/mendozammatias/bitrise-step-instabug-ios-symbol-upload/issues\npublished_at: 2024-02-28T00:30:04.097539-03:00\nsource:\n  git: https://github.com/mendozammatias/bitrise-step-instabug-ios-symbol-upload.git\n  commit: 8129e8dc14c90db8ce765a9adbe695e5293b1e6c\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- flutter\ntype_tags:\n- artifact-info\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- instabug_app_token: $INSTABUG_APP_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Instabug App Token for the given environment.\n    title: Instabug App Token\n- opts:\n    summary: Working directory of the step. You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/instabug-ios-symbol-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/install-bundler/1.0.0/step.yml",
    "content": "title: Install specific bundler version\nsummary: This step allows you to uninstall the system bundler version, and match the\n  one in your Gemfile.\ndescription: This step allows you to uninstall the system bundler version, and match\n  the one in your Gemfile..\nwebsite: https://github.com/FutureWorkshops/bitrise-step-install-bundler\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-install-bundler.git\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-install-bundler/issues\npublished_at: 2019-02-12T10:54:45.526724+01:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-install-bundler.git\n  commit: b7359e328f7db1f3b471d157e74ebd6e6458dd96\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- dependency\n- utility\n- installer\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"true\"\ninputs:\n- gemfile_path: ./Gemfile.lock\n  opts:\n    description: Gemfile lock that will be used to base the bundler version\n    is_expand: true\n    is_required: true\n    summary: Gemfile lock that will be used to base the bundler version\n    title: Path to the Gemfile lock\n"
  },
  {
    "path": "steps/install-bundler/1.2.0/step.yml",
    "content": "title: Install specific bundler version\nsummary: This step allows you to uninstall the system bundler version, and match the\n  one in your Gemfile.\ndescription: This step allows you to uninstall the system bundler version, and match\n  the one in your Gemfile..\nwebsite: https://github.com/FutureWorkshops/bitrise-step-install-bundler\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-install-bundler\nsupport_url: https://github.com/FutureWorkshops/bitrise-step-install-bundler/issues\npublished_at: 2022-05-12T11:56:47.099737+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-install-bundler.git\n  commit: 2531a1fda45e317d478c6dd3c25c3efd14359010\nhost_os_tags:\n- osx-10.14\ntype_tags:\n- utility\ndeps: {}\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- gemfile_path: ./Gemfile.lock\n  opts:\n    description: Gemfile lock that will be used to base the bundler version\n    is_expand: true\n    is_required: true\n    summary: Gemfile lock that will be used to base the bundler version\n    title: Path to the Gemfile lock\n- gemfilelock_dir: ./\n  opts:\n    category: Deprecated\n    description: Directory where the Gemfile lock is located (Deprecated)\n    is_expand: true\n    is_required: false\n    summary: Directory where the Gemfile lock is located (Deprecated)\n    title: Gemfile lock directory (Deprecated)\n"
  },
  {
    "path": "steps/install-bundler/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/install-dotnetcore/1.0.0/step.yml",
    "content": "title: Install .NET Core\nsummary: Installs the .NET Core SDK\ndescription: Installs the .NET Core SDK\nwebsite: https://github.com/stefandevo/bitrise-dotnetcore-step\nsource_code_url: https://github.com/stefandevo/bitrise-dotnetcore-step\nsupport_url: https://github.com/stefandevo/bitrise-dotnetcore-step/issues\npublished_at: 2017-04-30T21:00:13.660280264+02:00\nsource:\n  git: https://github.com/stefandevo/bitrise-dotnetcore-step.git\n  commit: cf27f88a0974c68fe97fef66758c5341b2432926\nhost_os_tags:\n- osx-10.10\nproject_type_tags: []\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- channel: null\n  opts:\n    description: |\n      Specifies the source channel for the installation. Currently \"production\" does not exists.\n      Leave empty to get latest \"stable\" (if this exists :-))\n      Possible known values are rel-1.0.0, rel-1.0.1, master (=daily version)\n    is_expand: true\n    is_required: false\n    title: Channel\n- opts:\n    description: \"Specifies the version of CLI to install. You must specify the version\n      as a 3-part version (for example, 1.0.0-13232). \\nIf it isn't present, it will\n      use the latest version.\\n\"\n    is_expand: true\n    is_required: false\n    title: Version\n  version: null\n"
  },
  {
    "path": "steps/install-dotnetcore/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2020-11-30\"\ndeprecate_notes: |\n  This step is deprecated as it is no longer maintained.\n"
  },
  {
    "path": "steps/install-flutter-version-manager/1.0.2/step.yml",
    "content": "title: Install Flutter Version Manager\nsummary: |\n  Installs Flutter Version Manager for the project\ndescription: |\n  Installs FVM (Flutter Version Manager): https://github.com/leoafarias/fvm.\n  It reads fvm config the project and replaces Flutter with version from fvm config so that other Bitrise steps can use it.\nwebsite: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise\nsource_code_url: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise.git\nsupport_url: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise/issues\npublished_at: 2021-01-21T13:38:41.205583+01:00\nsource:\n  git: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise.git\n  commit: b2a251852da0d8e77e7dc906567121bb9667a361\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\n"
  },
  {
    "path": "steps/install-flutter-version-manager/1.0.3/step.yml",
    "content": "title: Install Flutter Version Manager\nsummary: |\n  Installs Flutter Version Manager for the project\ndescription: |\n  Installs FVM (Flutter Version Manager): https://github.com/leoafarias/fvm.\n  It reads fvm config the project and replaces Flutter with version from fvm config so that other Bitrise steps can use it.\nwebsite: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise\nsource_code_url: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise.git\nsupport_url: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise/issues\npublished_at: 2022-07-15T11:30:04.701784+02:00\nsource:\n  git: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise.git\n  commit: a600193f47be01e14a35a42567388125f087efdd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- flutter\ntype_tags:\n- installer\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\n"
  },
  {
    "path": "steps/install-flutter-version-manager/2.0.0/step.yml",
    "content": "title: Extract FVM Flutter version\nsummary: |\n  Extracts Flutter version from FVM configuration file.\ndescription: |\n  Extracts Flutter version from FVM configuration file (`.fvmrc`).\nwebsite: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise\nsource_code_url: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise.git\nsupport_url: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise/issues\npublished_at: 2024-02-16T10:50:23.576595+01:00\nsource:\n  git: https://github.com/infinum/Install-Flutter-Version-Manager-Bitrise.git\n  commit: ae74f2ebc9609903d908b0002e6d228a93d667c0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\noutputs:\n- FVM_FLUTTER_VERSION: null\n  opts:\n    summary: Flutter version extracted from FVM configuration file.\n    title: Flutter version\n"
  },
  {
    "path": "steps/install-flutter-version-manager/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/install-missing-android-tools/0.9.1/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-01-17T13:05:06.456239704+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 11b63aa67f4f4eb0122862e1d69ad2e1dacd773c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'Path to the root build.gradle file. '\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- opts:\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/0.9.2/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-01-18T12:32:21.110177912+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: a87902796d2d281206a87027270b116f2ba1af4b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- script\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'Path to the root build.gradle file. '\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- opts:\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/1.0.0/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-03-23T17:05:49.812938263+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: fd07f117a2fb0bb07ab1ebf3b229a4d9ffb92ac1\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'Path to the root build.gradle file. '\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- opts:\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/1.0.1/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-03-28T11:29:25.060040631+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: bb7fa922c99741ca63f821741ebacfc8a1bc2887\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'Path to the root build.gradle file. '\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- opts:\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/1.0.2/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-04-25T11:59:03.577982975+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 96a5a7376ce0d88bdafcd805985544d1a154d460\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: 'Path to the root build.gradle file. '\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- opts:\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/1.0.3/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-06-12T15:20:33.602769537+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 1197873a0419100ba4fefc38b525634cd4bec14d\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- opts:\n    category: Debug\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/1.1.0/step.yml",
    "content": "title: Install missing Android tools\nsummary: Install missing Android tools\ndescription: |-\n  This step analyze your root settings.gradle file, to collect the active build.gradle files.\n\n  Based on the build.gradle files it will:\n\n  - install required `compileSdkVersion`s if missing\n  - install required `buildToolsVersion`s if missing\n  - update `Support Library` if used\n  - update `Google Play Services` if used\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-08-10T13:44:45.612155813+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: bef02aa086d5a9f716abd0196da50b370b587312\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- opts:\n    category: Debug\n    description: |-\n      If project uses `Support Library` and/or `Google Play Services` they will be updated by default.\n\n      Set this input to `\"false\"` if you wan to skip `Support Library` and/or `Google Play Services` updates.\n    is_required: true\n    summary: \"\"\n    title: Should the step update `Support Library` and `Google Play Services`\n    value_options:\n    - \"true\"\n    - \"false\"\n  update_support_library_and_play_services: \"true\"\noutputs:\n- COMPILE_SDK_VERSIONS: null\n  opts:\n    description: \"The compileSdkVersions used by the project.\\n\\nIf the project contains\n      multiple modules,\\nthis output will contain every different \\ncompileSdkVersion\n      in a pipe (`|`) separated list:\\n\\n`android-22|android-23`\"\n    title: The compileSdkVersions\n- BUILD_TOOLS_VERSIONS: null\n  opts:\n    description: \"The buildToolsVersions used by the project.\\n\\nIf the project contains\n      multiple modules,\\nthis output will contain every different \\nbuildToolsVersion\n      in a pipe (`|`) separated list:\\n\\n`22.0.1|20.0.0`\"\n    title: The buildToolsVersions\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: \"This step makes sure that required Android SDK components (platforms\n  and build-tools) are installed.\\n\\nFirst, the step determines your project's Android\n  Gradle Plugin version.\\n\\nThen the step runs the `gradle dependencies` command.\\n\\nIf\n  the Plugin version is 2.2.0 or later, the plugin will download and install the missing\n  components during the Gradle command.   \\nOtherwise the command will fail, the step\n  parses the command's output to determine which components are missing and installs\n  them.\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-08-23T13:35:45.409992157+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 9e945dc6d335c705f13f126b96a851a47fd5605d\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: \"This step makes sure that required Android SDK components (platforms\n  and build-tools) are installed.\\n\\nThe step runs the `gradlew dependencies` command.\\n\\nIf\n  the Plugin version is 2.2.0 or later, the plugin will download and install the missing\n  components during the Gradle command.   \\nOtherwise the command will fail, the step\n  parses the command's output to determine which SDK components are missing and installs\n  them.\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-08-24T11:40:09.587530684+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: abdeb047b1fb985331bf01f272cd4603956eb584\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.2/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: \"This step makes sure that required Android SDK components (platforms\n  and build-tools) are installed.\\n\\nThe step runs the `gradlew dependencies` command.\\n\\nIf\n  the Plugin version is 2.2.0 or later, the plugin will download and install the missing\n  components during the Gradle command.   \\nOtherwise the command will fail, the step\n  parses the command's output to determine which SDK components are missing and installs\n  them.\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-09-05T10:10:24.845878619+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: bd76c4a0dfe121b25b845d655f314d1a1b797fe9\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.3/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: \"This step makes sure that required Android SDK components (platforms\n  and build-tools) are installed.\\n\\nThe step runs the `gradlew dependencies` command.\\n\\nIf\n  the Plugin version is 2.2.0 or later, the plugin will download and install the missing\n  components during the Gradle command.   \\nOtherwise the command will fail, the step\n  parses the command's output to determine which SDK components are missing and installs\n  them.\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-10-11T14:49:43.584014034+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: c59062639b1579f935f7ede8a75bf87c34a6dc44\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.4/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: \"This step makes sure that required Android SDK components (platforms\n  and build-tools) are installed.\\n\\nThe step runs the `gradlew dependencies` command.\\n\\nIf\n  the Plugin version is 2.2.0 or later, the plugin will download and install the missing\n  components during the Gradle command.   \\nOtherwise the command will fail, the step\n  parses the command's output to determine which SDK components are missing and installs\n  them.\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-10-27T14:26:16.243158105+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: bf0c1eec16bd5685bcaf276bdc1b138af2acd782\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.5/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: \"This step makes sure that required Android SDK components (platforms\n  and build-tools) are installed.\\n\\nThe step runs the `gradlew dependencies` command.\\n\\nIf\n  the Plugin version is 2.2.0 or later, the plugin will download and install the missing\n  components during the Gradle command.   \\nOtherwise the command will fail, the step\n  parses the command's output to determine which SDK components are missing and installs\n  them.\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-11-08T13:45:51.591821541+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: d03513f4341eb728753f9e459eeb0eda085cd4f3\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.0.6/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2017-12-04T10:23:28.924874355+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 151f6b2fb969e385132fdb7a6692b3f0031d4374\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: Path to the root build.gradle file.\n    is_required: true\n    summary: \"\"\n    title: Path to the root build.gradle file\n  root_build_gradle_file: $GRADLE_BUILD_FILE_PATH\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.1.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-01-16T11:45:10.029964+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: bf7df2c0d53ce07bd4a2d72c6e4e93426bbb71fa\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.1.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-01-26T15:35:43.397186491+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 78845f47c52e5a3321239b33460df7aa4d032ae3\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.2.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-06-04T12:28:12.882357879+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: b7c204200cc406d514a51efca9096d857f859f54\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-10-19T13:36:44.611829609Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 710a27a20326121721a02a75b233281a07bda005\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-10-24T08:37:18.891549583Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 05e4844db51a4d0b8029136a4015718e91dfbda9\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.2/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-10-24T09:14:50.66943263Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 539b018395b2aaa1bb9aa806f00f636a011a0451\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.3/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-11-07T14:05:15.666676416Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: e06fc61f8657ed0df9b756b7a6046d12ede0d3f1\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.4/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2018-12-19T12:46:53.00776847Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: d0c37b18567d083c2ab74263877dcb8e32f38560\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.5/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2019-01-23T15:03:44.549285887Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 459d4ac2745b3b10ec383bff32eca8214cd816b8\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.6/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2019-06-28T14:33:08.592879324Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 983c641f551cc473ed3db28b90eb186a3e47c533\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.7/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install missing Android SDK components\ndescription: |-\n  This step makes sure that required Android SDK components (platforms and build-tools) are installed.\n\n  The step runs the `gradlew dependencies` command.\n\n  If the _Android Plugin for Gradle_ version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n\n  Otherwise the command will fail, the step parses the command's output to determine which SDK components are missing and installs them.\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2019-07-04T10:00:55.957138678Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: ae54ed077860d8dbb3fb93633bc7365b5ce58d9b\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.8/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: \"\\nThis Step makes sure that required Android SDK components (platforms\n  and build-tools) are installed. To do so, the Step runs the `gradlew dependencies`\n  command. \\n\\nIf the Android Plugin for Gradle version is 2.2.0 or higher, the plugin\n  will download and install the missing components during the Gradle command.  \\nOtherwise\n  the command fails and the Step parses the command's output to determine which SDK\n  components are missing and installs them.\\n\\n### Configuring the Step\\n\\n1. Set\n  the path of the `gradlew` file.\\n\\n   The default value is that of the $PROJECT_LOCATION\n  Environment Variable.\\n\\n1. If you use an Android NDK in your app, set its revision\n  in the **NDK Revision** input.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check\n  that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this\n  Step won't work.\\n\\n### Useful links\\n\\n[Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\\n\\n###\n  Related Steps\\n\\n* [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\\n*\n  [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2020-01-13T14:10:54.673288882Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 6892cca8316ee5fc90bd549449af3f059b8cde5f\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.3.9/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: \"\\nThis Step makes sure that required Android SDK components (platforms\n  and build-tools) are installed. To do so, the Step runs the `gradlew dependencies`\n  command. \\n\\nIf the Android Plugin for Gradle version is 2.2.0 or higher, the plugin\n  will download and install the missing components during the Gradle command.  \\nOtherwise\n  the command fails and the Step parses the command's output to determine which SDK\n  components are missing and installs them.\\n\\n### Configuring the Step\\n\\n1. Set\n  the path of the `gradlew` file.\\n\\n   The default value is that of the $PROJECT_LOCATION\n  Environment Variable.\\n\\n1. If you use an Android NDK in your app, set its revision\n  in the **NDK Revision** input.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check\n  that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this\n  Step won't work.\\n\\n### Useful links\\n\\n[Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\\n\\n###\n  Related Steps\\n\\n* [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\\n*\n  [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2021-06-24T13:51:58.654264618Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 6ed845c7b6d8b14d4496a33d543b4614d95d0ae9\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.4.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: \"\\nThis Step makes sure that required Android SDK components (platforms\n  and build-tools) are installed. To do so, the Step runs the `gradlew dependencies`\n  command. \\n\\nIf the Android Plugin for Gradle version is 2.2.0 or higher, the plugin\n  will download and install the missing components during the Gradle command.  \\nOtherwise\n  the command fails and the Step parses the command's output to determine which SDK\n  components are missing and installs them.\\n\\n### Configuring the Step\\n\\n1. Set\n  the path of the `gradlew` file.\\n\\n   The default value is that of the $PROJECT_LOCATION\n  Environment Variable.\\n\\n1. If you use an Android NDK in your app, set its revision\n  in the **NDK Revision** input.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check\n  that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this\n  Step won't work.\\n\\n### Useful links\\n\\n[Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\\n\\n###\n  Related Steps\\n\\n* [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\\n*\n  [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2021-07-28T07:29:59.34034586Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 34ea2538067d28a5607ff3d43e491e64d676bde6\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/2.4.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: \"\\nThis Step makes sure that required Android SDK components (platforms\n  and build-tools) are installed. To do so, the Step runs the `gradlew dependencies`\n  command. \\n\\nIf the Android Plugin for Gradle version is 2.2.0 or higher, the plugin\n  will download and install the missing components during the Gradle command.  \\nOtherwise\n  the command fails and the Step parses the command's output to determine which SDK\n  components are missing and installs them.\\n\\n### Configuring the Step\\n\\n1. Set\n  the path of the `gradlew` file.\\n\\n   The default value is that of the $PROJECT_LOCATION\n  Environment Variable.\\n\\n1. If you use an Android NDK in your app, set its revision\n  in the **NDK Revision** input.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check\n  that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this\n  Step won't work.\\n\\n### Useful links\\n\\n[Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\\n\\n###\n  Related Steps\\n\\n* [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\\n*\n  [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2021-08-04T09:01:46.28656917Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 15f4b8be5626764a9d9068e5ed447b3330c2159a\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_revision: null\n  opts:\n    description: 'The step will install the given revision of the Android NDK.(eg.:\n      18) Leave this input empty if you are not using NDK in your project.'\n    summary: 'The step will install the given revision of the Android NDK.(eg.: 18)\n      Leave this input empty if you are not using NDK in your project.'\n    title: NDK Revision\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.0.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: \"\\nThis Step makes sure that required Android SDK components (platforms\n  and build-tools) are installed. To do so, the Step runs the `gradlew dependencies`\n  command. \\n\\nIf the Android Plugin for Gradle version is 2.2.0 or higher, the plugin\n  will download and install the missing components during the Gradle command.  \\nOtherwise\n  the command fails and the Step parses the command's output to determine which SDK\n  components are missing and installs them.\\n\\n### Configuring the Step\\n\\n1. Set\n  the path of the `gradlew` file.\\n\\n   The default value is that of the $PROJECT_LOCATION\n  Environment Variable.\\n\\n1. If you use an Android NDK in your app, set its revision\n  in the **NDK Revision** input.\\n\\n### Troubleshooting\\n\\nIf the Step fails, check\n  that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this\n  Step won't work.\\n\\n### Useful links\\n\\n[Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\\n\\n###\n  Related Steps\\n\\n* [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\\n*\n  [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\"\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2021-09-20T15:01:52.135348833Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: adccaaa6d14883b3be40ce1144d387d0511ebb59\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.0.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |2-\n\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2022-02-23T08:18:27.196562934Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: b8edd9291245860d62c964947442e848dd08ef2c\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.1.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |2-\n\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2022-07-25T13:50:52.609644163Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: b77cfa8b0d02648e20a8487e93034842242ac35a\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.2.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |2-\n\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2023-07-04T08:40:38.580668611Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 2d89aef238597ebd5ca0fa478dab15c47a3b804f\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.2.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |2-\n\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2024-04-25T14:04:58.668923896Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 6f93547388b7144fd33e535683dc54875a6d0adb\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.2.2/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |2-\n\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2025-11-13T08:27:02.283123045Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 6dbc486e7e90dda9c1051144a329174dab075392\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.2.3/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-02-18T16:20:38.560293148Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 1d42e3c111ad286bb427fc381ff18c9e4ed0eb10\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.2.3/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-64d89a0b5015b238638bc3a403ff858ededf7a5cc1304bfc22a64e4c31886d55\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.2.3/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-ddbcc95e0a97b747496dcce1a194749b86fd852166ce7ca4470548d0a7e193ef\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.2.3/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-fe7c7d4a8e5961dad181f8ac9884da26e7bf20d39ce52ab78c80e66106587dfc\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.2.3/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-fdb3e794779dd1cc07be22ef1d169913e8b40a91bd1fca105729f9181eedc039\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.3.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-03-24T09:20:23.678533868Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 2d57999c09e7ea22b352e79a694d104db0aeb004\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.3.0/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-6ff9e2eaff8038bcca651224a43eb84dcfad9c6cd20efa5a8f73220a67a72568\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.3.0/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-0ffbe017aaefea67c21f8db843b5b23fe7a077b5cf3bed81aca3c3e486bea479\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.3.0/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-c150d619c683181c882dce1690eb59f4bf39d461e8557832e8dedf52966f0518\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.3.0/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-4a8016a268ade460769533a1c3440a66636da7273207b039ffa720ceb42a1811\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_maven_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the MavenCentral mirror\n      available, Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise MavenCentral mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-21T11:26:09.4238179Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 54c1b1b69c5418af6ec867c5088056724b85bce2\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.0/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-78d56072f3374758400bd7053dd0e10cee23bc5d8497dfd186f7b504e9043cc3\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.0/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-17e4568ac03fe15d77ec90b5ce4028cfa04b4b5772d4e580fb2fdab85556b145\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.0/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-774ad794f4bbca1f8a552cf1a096feb05ce56ff1f77799359cdde0d12dff2897\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.0/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-937dc9b3bcecd59665960c8a4cba8b4ddcee66c150172dacd4ab7cc02ac45e5e\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-28T16:50:13.943795491Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 3920300918631633ae5341dae17579c0e062660d\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.1/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-6f7773c6c52091ea620e4a930101a7c7fa1da893227a68c681e9a014f9c2743f\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.1/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-449008d80adfecb592744deff6c13a5da2cd25206e1f3cdc2167b7e22a7926a4\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.1/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-c152e0ffe6518dad80f811a694e53f3e269873cca3197c2ba319bc13b5280322\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.1/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-e2e0bf892b4f3e4169e2b06d3faec1ffceb4df9a508e9b8e1cdb5afbe560c55c\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.2/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-28T18:45:47.767816011Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: e8e3514b2bbd43cbbc083e3bfd88150c032f855a\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.2/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-e8375b3409131bb4fd941895fe0fdf60ff887bd817eee42061092fa7d45eb76d\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.2/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-6989556ab8084020a98babeeafae131a219a2a6279b3c855c54ed4626a17df4d\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.2/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-609f37ad7e808c0f4f9926f9679548f1417cb8be03e87eebd0e92879dc0649de\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.2/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-c88d5c6b2cb81b4e1aa6c8c0f3b64f4b7709aec5f7394af81e7ac7328347a2db\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.3/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-29T13:21:59.196755276Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 6c910efde36358b9985966999227f0b6302edef3\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.3/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-aa4c8844176e8dc43240c12e695a8d919e06fbf0e7c25fa096bc34ae4d5fb477\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.3/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-223808562091d6873643e68d99aa80ca0ba35eb24ea0602e7f9946da62f9c4fb\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.3/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-9136a78446fe8bd8be5265a3233c8b839e595bbe6a1e69d728185d53b1c6f16c\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.3/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-c2792f40488e890fd53aa497642286308b9a3264da0e9286717a6c9489ef8ebb\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.4/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-30T07:24:49.466676857Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: bbe6e33815c6740e3581b609a5586e626498272d\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.4/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-7af65d380ba16858dc36c87fd65de6653f0e280ac644244f1a6e446cb1ad92cc\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.4/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-d6d17de07abc2947ffcbd4a0321d5fcf5190186c40f8b702e3b7771c00cb8485\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.4/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-9018ec76e9f519738d00d138c03b16beecf2e1bde832576ddba215c8eff4b5d8\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.4/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-9c510d1cc1b4f50eecb94f26612bf960d91bcfa2429034bf0aa900c78c245a87\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.5/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-30T10:43:20.895119998Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 50add7e1e94ec83324152e8651508e65e0a3d739\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.5/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-c8e5318cb089f1228a4b01b1baba0b8d16fa3378b763a49e3014e22d9a92070a\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.5/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-273bc13ddad29fcd9daaf96687c2a2618994dc0e7213e4cc81670a15a5e15e44\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.5/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-8f5b5f488ac01d4e07cdc32c51a22eaef8c6112d617a63892acaff765cc51409\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.5/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-ca2b0dfe2d3122d8c4b5f3a52bbea98c049dd067ee020396f572a77cf7fc90cf\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.6/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-30T12:21:47.705956428Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 828a0e3e59b8a0971a7f704352515d44d4ef93ca\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.6/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-f1f5edd990d54b57ff15887764ff7ef8f884fd9c24a54aa9dba6114c50c3ec68\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.6/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-f72ad27c4a02c70a1ebead7a946e202c878f9451bcc57407bc1052383ee90743\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.6/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-105e2cb3a89b8fdde0c67ea1494f713e2c9ebc51f61c61f32269c39ce23a25a5\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.6/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-28b93345ee590bbc5af3ffb1431e6703614aeb6e40be1f15323f6a14af698993\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.4.7/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-04-30T15:58:02.401614422Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 38c028a3681693ca28514b6c664163137bd951dd\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.7/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-ad4b09af0218b9b3c2a957a66e47f4b50410054bccf47177976d0e62d2d49db1\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.7/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-ebc93860b88f16dc8c9cdf4f26b2114cf990f525acec231501a5dc7dcafaece4\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.4.7/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-c20608900d5c65073baecdf7ac26a1704fc2563566ecd9f569bdccf430de0cba\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.4.7/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-a1dc24060eae2d593d8c63d21ac5bd22bfed387feaff2a0b10270da0b6b9d957\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.5.0/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-05-05T13:52:10.119909183Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: e8ee17aef9a7285d47cae1f26d910b84462c9aef\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.5.0/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-8fcf765abbc9d7a72df783d980a617dedc9aa4555b8fb1c6dba1dc8d5acb78c8\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.5.0/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-534082d7f0aeb189bf5b74b85ae2adab3818681218c1b6118a35be2c3f57fa91\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.5.0/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-8e4d46b9f1584abfc823521a05d353081681ed2d47823df9d17314b87796d774\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.5.0/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-1f7c1c7ba0770afcb9eaef4711761db5709eeb2b92d33c0feccb2a3cbf60990e\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n- enable_repo_mirror: \"true\"\n  opts:\n    is_required: false\n    summary: When enabled and the build runs on Bitrise with the repo mirror available,\n      Gradle will be configured to download dependencies from the mirror.\n    title: Use Bitrise repo mirror for dependencies\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/install-missing-android-tools/3.5.1/step.yml",
    "content": "title: Install missing Android SDK components\nsummary: Install Android SDK components that are required for the app.\ndescription: |-\n  This Step makes sure that required Android SDK components (platforms and build-tools) are installed. To do so, the Step runs the `gradlew dependencies` command.\n\n  If the Android Plugin for Gradle version is 2.2.0 or higher, the plugin will download and install the missing components during the Gradle command.\n  Otherwise the command fails and the Step parses the command's output to determine which SDK components are missing and installs them.\n\n  ### Configuring the Step\n\n  1. Set the path of the `gradlew` file.\n\n     The default value is that of the $PROJECT_LOCATION Environment Variable.\n\n  1. If you use an Android NDK in your app, set its revision in the **NDK Revision** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check that your repo actually contains a `gradlew` file. Without the Gradle wrapper, this Step won't work.\n\n  ### Useful links\n\n  [Installing an additional Android SDK package](https://devcenter.bitrise.io/tips-and-tricks/android-tips-and-tricks/#how-to-install-an-additional-android-sdk-package)\n\n  ### Related Steps\n\n  * [Android SDK Update](https://www.bitrise.io/integrations/steps/android-sdk-update)\n  * [Install React Native](https://www.bitrise.io/integrations/steps/install-react-native)\nwebsite: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsource_code_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools\nsupport_url: https://github.com/bitrise-steplib/steps-install-missing-android-tools/issues\npublished_at: 2026-05-12T08:59:39.473720664Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-missing-android-tools.git\n  commit: 6193d2ef7da3a1169746062145111d0829bd9616\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/install-missing-android-tools/3.5.1/bin/install-missing-android-tools-darwin-amd64\n    hash: sha256-2916dfd3b9448e4e511bc73801da1b91ab6446709a83166ce659a4e1b739d852\n  darwin-arm64:\n    storage_uri: steps/install-missing-android-tools/3.5.1/bin/install-missing-android-tools-darwin-arm64\n    hash: sha256-20a2934eefb8f7fad6f8a820675d0cfaacd0ac31b5ec8acb338504a22e9adb13\n  linux-amd64:\n    storage_uri: steps/install-missing-android-tools/3.5.1/bin/install-missing-android-tools-linux-amd64\n    hash: sha256-06754ae0f0523d1ff048c67a0084433c21440dd83fb7d0902d21a8773dc777cc\n  linux-arm64:\n    storage_uri: steps/install-missing-android-tools/3.5.1/bin/install-missing-android-tools-linux-arm64\n    hash: sha256-ed23e03dea3857776edcd3042be01f81abad7b945e74a153f619cc94ab59e744\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- installer\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-install-missing-android-tools\nis_always_run: false\nis_skippable: false\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper is what makes sure\n      that the right Gradle version is installed and used for the build.\n      __You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one (if you would not have one already)__\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n\n      **The path should be relative** to the repository root, for example: `./gradlew`,\n      or if it's in a sub directory: `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- ndk_version: null\n  opts:\n    description: NDK version to install, for example `23.0.7599858`. Run `sdkmanager\n      --list` on your machine to see all available versions. Leave this input empty\n      if you are not using the Native Development Kit in your project.\n    summary: NDK version to install. Leave this input empty if you are not using the\n      Native Development Kit in your project.\n    title: NDK version\n- gradlew_dependencies_options: null\n  opts:\n    description: |-\n      Additional options to be added to the executed `gradlew dependencies` command.\n\n      The step runs `gradlew dependencies --stacktrace` to list and install the missing project dependencies.\n\n      Additional options will be appended to the end of this command.\n\n      Example: `--configuration-cache-problems=warn`.\n    summary: Additional options to be added to the executed `gradlew dependencies`\n      command.\n    title: Additional options for the `gradlew dependencies` command\n"
  },
  {
    "path": "steps/install-missing-android-tools/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/install-react-native/0.1.0/step.yml",
    "content": "title: Install React Native\nsummary: Installs the `react-native-cli` command line tools.\ndescription: Installs the [React Native CLI npm package](https://www.npmjs.com/package/react-native-cli).\nwebsite: https://github.com/bitrise-steplib/steps-install-react-native\nsource_code_url: https://github.com/bitrise-steplib/steps-install-react-native\nsupport_url: https://github.com/bitrise-steplib/steps-install-react-native/issues\npublished_at: 2016-03-09T13:31:32.035939753+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-react-native.git\n  commit: 7d57bef9ff458a85701a3cfe24955664386db171\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\n  - name: watchman\n  - name: flow\ninputs:\n- opts:\n    description: |-\n      Version of the `react-native-cli` package to install.\n      If not specified, the latest version will be selected.\n      Check the logs for the available versions from this\n      package and specify the desired verion as `0.1.9` for example.\n    title: Version of the `react-native-cli` package to install\n  version: null\n- npm_options: null\n  opts:\n    description: |-\n      Options are added to `npm install`. `-g` (global) option is set by default.\n      You can use multiple options, separated by a space\n      character, for example `-dd -ll`\n    title: Additional options when installing React Native CLI with `npm install`\n"
  },
  {
    "path": "steps/install-react-native/0.10.0/step.yml",
    "content": "title: Install React Native\nsummary: Installs the React Native CLI tools.\ndescription: \"The Step installs the React Native command line tools with npm. \\nIt\n  exposes the `react-native` binary, so you can call `yarn react-native` or `npx react-native`\n  directly from your project.\\n  \\n### Configuring the Step\\n\\nYou can set which version\n  of the CLI you want to use, and add any additional options to the `npm install`\n  command.\\n\\n1. In the **Version of the `@react-native-community/cli` package to\n  install**, set the version you need.\\n  \\n   For example, set it to `0.9.1`. If\n  you leave the input empty, the Step will use the latest version.\\n   \\n2. In the\n  **Additional options when installing React Native CLI with `npm install`** input,\n  set any additional flags you want to use with the `npm-install` command.\\n\\n   The\n  default is set to `global`. You can use multiple options, separated by a space.\n  \\n  \\n### Useful links\\n\\n- [Getting started with React Native apps](https://devcenter.bitrise.io/getting-started/getting-started-with-react-native-apps/)\\n-\n  [React Native CLI](https://github.com/react-native-community/cli)\\n  \\n### Related\n  Steps \\n\\n- [React Native Bundle](https://www.bitrise.io/integrations/steps/react-native-bundle)\\n-\n  [Expo Eject](https://www.bitrise.io/integrations/steps/expo-detach)\"\nwebsite: https://github.com/bitrise-steplib/steps-install-react-native\nsource_code_url: https://github.com/bitrise-steplib/steps-install-react-native\nsupport_url: https://github.com/bitrise-steplib/steps-install-react-native/issues\npublished_at: 2020-12-01T07:47:21.198469049Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-react-native.git\n  commit: e455baf35c16185ad3169da93059e365a739c42f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- installer\ndeps:\n  brew:\n  - name: node\n  - name: watchman\n  - name: flow\ninputs:\n- opts:\n    description: |-\n      Version of the `@react-native-community/cli` package to install.\n      If not specified, the latest version will be selected.\n      Check the logs for the available versions from this\n      package and specify the desired version. For example, `0.1.9`.\n    title: Version of the `@react-native-community/cli` package to install\n  version: null\n- npm_options: null\n  opts:\n    description: |-\n      Options are added to `npm install`. `-g` (global) option is set by default.\n      You can use multiple options, separated by a space\n      character, for example `-dd -ll`\n    title: Additional options when installing React Native CLI with `npm install`\n"
  },
  {
    "path": "steps/install-react-native/0.9.1/step.yml",
    "content": "title: Install React Native\nsummary: Installs the `react-native-cli` command line tools.\ndescription: Installs the [React Native CLI npm package](https://www.npmjs.com/package/react-native-cli).\nwebsite: https://github.com/bitrise-steplib/steps-install-react-native\nsource_code_url: https://github.com/bitrise-steplib/steps-install-react-native\nsupport_url: https://github.com/bitrise-steplib/steps-install-react-native/issues\npublished_at: 2016-12-16T12:02:27.822712571+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-react-native.git\n  commit: 81093defde3990049cb8fd58b3b53edbefb7d067\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- installer\ndeps:\n  brew:\n  - name: node\n  - name: watchman\n  - name: flow\ninputs:\n- opts:\n    description: |-\n      Version of the `react-native-cli` package to install.\n      If not specified, the latest version will be selected.\n      Check the logs for the available versions from this\n      package and specify the desired verion as `0.1.9` for example.\n    title: Version of the `react-native-cli` package to install\n  version: null\n- npm_options: null\n  opts:\n    description: |-\n      Options are added to `npm install`. `-g` (global) option is set by default.\n      You can use multiple options, separated by a space\n      character, for example `-dd -ll`\n    title: Additional options when installing React Native CLI with `npm install`\n"
  },
  {
    "path": "steps/install-react-native/0.9.2/step.yml",
    "content": "title: Install React Native\nsummary: Installs the `react-native-cli` command line tools.\ndescription: Installs the [React Native CLI npm package](https://www.npmjs.com/package/react-native-cli).\nwebsite: https://github.com/bitrise-steplib/steps-install-react-native\nsource_code_url: https://github.com/bitrise-steplib/steps-install-react-native\nsupport_url: https://github.com/bitrise-steplib/steps-install-react-native/issues\npublished_at: 2019-10-11T13:37:50.107626531Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-install-react-native.git\n  commit: a2bda02c15d8b288ea9f7cc1f4ea0c8ce1c18fa6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- ios\n- android\ntype_tags:\n- installer\ndeps:\n  brew:\n  - name: node\n  - name: watchman\n  - name: flow\ninputs:\n- opts:\n    description: |-\n      Version of the `react-native-cli` package to install.\n      If not specified, the latest version will be selected.\n      Check the logs for the available versions from this\n      package and specify the desired verion as `0.1.9` for example.\n    title: Version of the `react-native-cli` package to install\n  version: null\n- npm_options: null\n  opts:\n    description: |-\n      Options are added to `npm install`. `-g` (global) option is set by default.\n      You can use multiple options, separated by a space\n      character, for example `-dd -ll`\n    title: Additional options when installing React Native CLI with `npm install`\n"
  },
  {
    "path": "steps/install-react-native/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/installrapp-deploy/1.0.1/step.yml",
    "content": "title: InstallrApp iOS Deploy\nsummary: Deploy your awesome iOS Application to InstallrApp.\ndescription: |-\n  Deploy an iOS application to [InstallrApp](http://installrapp.com),\n  add notes, add testers, notify testers.\n\n  Register an InstallrApp account at [http://installrapp.com/](http://installrapp.com)\n  to utilize this step.\n  You also need to create an *InstallrApp API Token* for your app.\nwebsite: https://github.com/Redth/bitrise-steps-installrapp-deploy\nsource_code_url: https://github.com/Redth/bitrise-steps-installrapp-deploy\nsupport_url: https://github.com/Redth/bitrise-steps-installrapp-deploy/issues\npublished_at: 2016-03-29T09:08:50.558446576-04:00\nsource:\n  git: https://github.com/Redth/bitrise-steps-installrapp-deploy.git\n  commit: c032bf1dd837e89001fcf97427c7383796f0e535\nhost_os_tags:\n- osx-10.9\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    is_required: true\n    title: IPA file path\n- api_token: \"\"\n  opts:\n    description: |-\n      ## Where to get the InstallrApp API Token?\n\n      Sign in to your [http://installrapp.com/](http://installrapp.com) account,\n      click on *My Account* at the top right corner to get to the\n      *My Account* page. Under the *API Tokens* heading, click *Create New Token*.\n\n      You can see your registered API Tokens at the bottom of this page\n      at the *API Tokens* section. Copy and paste here the API Token\n      you want to use.\n    is_required: true\n    title: API Token\n- notes: \"\"\n  opts:\n    description: Additional notes to the deploy.\n    title: Notes attached to the deploy\n- notify: \"\"\n  opts:\n    description: \"Sets Tester Teams who should be notified on deployment.\\n\\nTester\n      Team names should be specified in a comma separated list.\\n\\n*NOTE:* You can\n      also enter *true* to notify all the same users \\nof the previous build\"\n    is_required: false\n    title: Notify Tester Teams\n- add: \"\"\n  opts:\n    description: \"Sets Tester Teams who should be added to access the deployment.\\n\\nTester\n      Team names should be specified in a comma separated list.\\n\\n*NOTE:* You can\n      also enter *true* to add all the same users \\nof the previous build\"\n    is_required: false\n    title: Add Tester Teams\noutputs:\n- INSTALLRAPP_DEPLOY_STATUS: \"\"\n  opts:\n    title: 'Deployment result: ''success'' or ''failed'''\n- INSTALLRAPP_DEPLOY_BUILD_URL: \"\"\n  opts:\n    title: URL of the InstallrApp build\n- INSTALLRAPP_DEPLOY_JSON: \"\"\n  opts:\n    title: Raw JSON response of the InstallrApp deploy\n"
  },
  {
    "path": "steps/installrapp-deploy/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/ionic-archive/0.10.0/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-09-21T16:56:12.435888009+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 705694e775884508000a1b41d319534fa9c75181\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: |-\n      From ionic-cli version 3.10.0 you need to login with the ioni-cli to run a build.\n      Use `Ionic username` and `Ionic password` to provide your credentials.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: |-\n      From ionic-cli version 3.10.0 you need to login with the ioni-cli to run a build.\n      Use `Ionic username` and `Ionic password` to provide your credentials.\n    title: Ionic password\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/0.9.1/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-05-25T16:59:30.473151686+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: eca1ea54a13402275f2505b18d60ee380d297d02\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/0.9.3/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-05-31T12:46:56.543246386+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 95f4825413266da5d19d78d899d534078f9c69c6\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/0.9.4/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-08-09T15:05:06.738353801+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: a2b755b3d53001f7d32751f6134d3b4df2d3f92a\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/0.9.5/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-09-06T14:39:36.505243023+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 55dead4d60b490ed224bcc072dde63b5c4267ccb\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/1.0.0/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-09-26T11:16:13.854317746+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 20cb453dfc2a0300ef5e8bd2d42c67f0cc8e71ab\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic password\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/1.1.0/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-10-18T15:57:01.227685853+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 748504561db76725fac865745a215b642b32fa21\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n"
  },
  {
    "path": "steps/ionic-archive/1.2.1/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2017-11-16T13:01:39.143467813+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 3a8d3a421c87541afca14df4b4f9e433e1b315d7\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/1.2.2/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2018-03-12T13:05:42.73413966+01:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 364cf6dd20c7c14d1f31bca9d2f4e536477bf57e\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/1.2.3/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2018-04-13T17:33:52.089706557+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: b1af92025b35866fffb636405d90a09a1ac45c14\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/1.2.4/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  For first the step prepare your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  then it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: !!timestamp 2018-05-07T13:09:08.176257883+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: a71a080f751f6878af757ff5d1bb0e04db14865a\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ioni-cli.\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/1.2.5/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  First, the step prepares your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  After, it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2018-08-22T14:57:43.346626126Z\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 9e995b5fb97a3002fbe2915cd300ee86c67fdf2a\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/1.2.6/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  First, the step prepares your Ionic project by calling:\n\n  - `ionic cordova \"platform\" \"rm\" \"<platform>\"`\n  - `ionic cordova \"platform\" \"add\" \"<platform>\"`\n\n  After, it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2018-10-24T12:25:14.300009485Z\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: f619ec94c5121d332e645cfa1920c7fff78e0fe1\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/2.0.0/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  First, the step prepares your Ionic project by calling:\n\n  - `ionic cordova \"prepare\" \"--no-build\"`\n\n  After, it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2018-12-14T10:56:27.323161782Z\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-archive.git\n  commit: 42a4fa1cd6b4d67cf659f3f92afea4ed4615bb55\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: -- --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova does not yet support the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/2.1.0/step.yml",
    "content": "title: Ionic archive\nsummary: Archives your Ionic project\ndescription: |-\n  Archives your Ionic project.\n\n  First, the step prepares your Ionic project by calling:\n\n  - `ionic cordova \"prepare\" \"--no-build\"`\n\n  After, it archives the project by calling:\n\n  - `ionic cordova \"build\" \"--debug|--release\" \"--device|--emulator\" \"<platform>\" \"--buildConfig=$BITRISE_CORDOVA_BUILD_CONFIGURATION\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2019-09-20T11:58:50.869087592Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: 2f199bec4463b23944cb8d8fd874662faf3064a2\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: -- --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova does not yet support the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/2.1.1/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-community/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-community/steps-ionic-archive\nsupport_url: https://github.com/bitrise-community/steps-ionic-archive/issues\npublished_at: 2020-01-13T14:35:50.546863221Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: ed12f36cf4c511270ad54eb8f69a0ea9c0a98523\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: -- --buildFlag=\"-UseModernBuildSystem=0\"\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova does not yet support the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/2.2.0/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-archive\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-archive/issues\npublished_at: 2020-07-03T09:22:04.079113176Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: fab48be8d571904c48ab2f2147711d9b5cd71a12\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova now supports the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/2.2.1/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-archive\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-archive/issues\npublished_at: 2021-04-19T11:54:24.914804843Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: e0929986bdeeb635040e465b9c28f401b9cac58c\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova now supports the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n"
  },
  {
    "path": "steps/ionic-archive/2.3.0/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-archive\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-archive/issues\npublished_at: 2021-08-02T12:56:02.365709272Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: 4545ca69dc3ec35dfd9504259b6e231f3e56036e\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova now supports the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- android_app_type: apk\n  opts:\n    category: Android\n    description: |\n      Set the distribution type that you want to build for your Android app.\n    is_required: true\n    summary: |\n      Set the distribution type that you want to build for your Android app.\n    title: Android app type\n    value_options:\n    - apk\n    - aab\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB.\n      If the build generates more than one AAB this output\n      will contain the last one's path.\n    summary: Path of the generated (and copied) AAB.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths.\n    title: List of the generated AAB paths\n"
  },
  {
    "path": "steps/ionic-archive/2.3.1/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-archive\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-archive/issues\npublished_at: 2021-08-23T11:49:56.156118868Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: 00ec8df1ee1241a456d641d871adbf2e5d0daded\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova now supports the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- android_app_type: apk\n  opts:\n    category: Android\n    description: |\n      Set the distribution type that you want to build for your Android app.\n    is_required: true\n    summary: |\n      Set the distribution type that you want to build for your Android app.\n    title: Android app type\n    value_options:\n    - apk\n    - aab\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB.\n      If the build generates more than one AAB this output\n      will contain the last one's path.\n    summary: Path of the generated (and copied) AAB.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths.\n    title: List of the generated AAB paths\n"
  },
  {
    "path": "steps/ionic-archive/2.3.2/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-archive\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-archive/issues\npublished_at: 2024-02-27T08:39:27.187715801Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: 97289aeec10d288e952cbadc4164983fc53b7f88\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova now supports the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- android_app_type: apk\n  opts:\n    category: Android\n    description: |\n      Set the distribution type that you want to build for your Android app.\n    is_required: true\n    summary: |\n      Set the distribution type that you want to build for your Android app.\n    title: Android app type\n    value_options:\n    - apk\n    - aab\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB.\n      If the build generates more than one AAB this output\n      will contain the last one's path.\n    summary: Path of the generated (and copied) AAB.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths.\n    title: List of the generated AAB paths\n"
  },
  {
    "path": "steps/ionic-archive/2.3.3/step.yml",
    "content": "title: Ionic archive\nsummary: Generates builds for the requested platforms.\ndescription: |-\n  Generates an iOS, Android or an iOS and Android build based on your Step settings and a `build.json` file which is inherited from the **Generate cordova build configuration** Step.\n\n  ### Configuring the Step\n  1. In the **Platform to use in ionic-cli commands** input, select the platform you wish to build for from the drop-down menu.\n  2. In the **Build command configuration** input, select either `debug` or `release` mode from the drop-down menu. If you set `release` to generate a release build, then you should select `device` instead of `emulator` in the **Build command target**.\n  3. Select either `emulator` or `device` in the **Build command target** field.\n  4. Make sure the file path set in the **Working directory** is pointing to the path where your project's code got downloaded to.\n  If you're using any services of the Ionic framework which requires login credentials, you have to provide those in the **Ionic username** and **Ionic password** inputs. Don't worry, these are stored as secret Environment Variables.\n  If you wish to to modify your native projects by inserting the **Ionic Prepare** Step before the **Ionic Archive** Step, then make sure you set the **Should `ionic cordova prepare` be executed before `ionic cordova build`?** input to `false` in the **Ionic Archive** Step.\n  The **Build configuration path to describe code signing properties** input is automatically filled out with the output Environment Variable of the **Generate cordova build configuation** Step. You do not need to modify this input.\n\n  ### Troubleshooting\n  Make sure you add the **Ionic Archive** Step AFTER the **Generate cordova build configuration** Step as the latter generates the build config file which the **Ionic Archive** Step uses to successfully build an iOS and/or Android project.\n  Make sure you insert the **Ionic Archive** Step BEFORE any deploy Step.\n  Note that if you’re building for both iOS and Android in one workflow, and either of your apps fails, the whole **Ionic Archive** Step will fail.\n  If you set the **Build configuration** input in the **Generate Cordova Build Configuration** Step to `release`, then you need to use the release configuration in the **Ionic Archive** Step as well.\n\n  ### Useful links\n  - [Getting started with Ionic/Cordova apps on Bitrise](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Secret Environment Variables on Bitrise](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/)\n  - [Ionic framework](https://ionicframework.com/)\n\n  ### Related Steps\n  - [Generate Cordova Build Configuration](https://www.bitrise.io/integrations/steps/android-build)\n  - [Run npm command](https://www.bitrise.io/integrations/steps/npm)\n  - [Cordova Archive](https://www.bitrise.io/integrations/steps/cordova-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ionic-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-archive\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-archive/issues\npublished_at: 2024-03-06T12:24:11.602145033Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-archive.git\n  commit: 6d42875c2624fc63dcff236f25c70a6524c3a27c\nproject_type_tags:\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-archive\ndeps:\n  brew:\n  - name: go\n  - name: gradle\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic cordova build [OTHER_PARAMS] <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- configuration: release\n  opts:\n    description: |-\n      Specify build command configuration.\n\n      `ionic cordova build [OTHER_PARAMS] [--release | --debug]`\n    is_required: true\n    title: Build command configuration\n    value_options:\n    - release\n    - debug\n- opts:\n    description: |-\n      Specify build command target.\n\n      `ionic cordova build [OTHER_PARAMS] [--device | --emulator]`\n    is_required: true\n    title: Build command target\n    value_options:\n    - device\n    - emulator\n  target: device\n- build_config: $BITRISE_CORDOVA_BUILD_CONFIGURATION\n  opts:\n    description: Path to the build configuration file (build.json), which describes\n      code signing properties.\n    title: Build configuration path, to describe code signing properties\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the ionic-cli build command.\n\n      Cordova now supports the new build system made default in XCode 10 (https://github.com/apache/cordova-ios/issues/407).\n      To use the legacy build system add `-- --buildFlag=\"-UseModernBuildSystem=0\"` to the options string.\n\n      Example:\n      - `--browserify`\n\n      `ionic cordova build [OTHER_PARAMS] [options]`\n    title: Options to append to the ionic-cli build command\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- opts:\n    description: |-\n      It should be set to false if ionic-prepare step is used.\n\n      - false: `ionic cordova build`\n      - true: `ionic cordova prepare --no-build` followed by `ionic cordova build`\n    title: Should `ionic cordova prepare` be executed before `ionic cordova build`?\n  run_ionic_prepare: \"true\"\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- android_app_type: apk\n  opts:\n    category: Android\n    description: |\n      Set the distribution type that you want to build for your Android app.\n    is_required: true\n    summary: |\n      Set the distribution type that you want to build for your Android app.\n    title: Android app type\n    value_options:\n    - apk\n    - aab\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created ios .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The created ios .app dir's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created ios .app.zip file's path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    title: The created ios .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created ios .dSYM.zip file's path\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_APK_PATH_LIST: \"\"\n  opts:\n    title: The created android .apk file paths (separated via |)\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the generated AAB.\n      If the build generates more than one AAB this output\n      will contain the last one's path.\n    summary: Path of the generated (and copied) AAB.\n    title: Path of the generated AAB\n- BITRISE_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      The paths are separated with `|` character, for example, `app--debug.aab|app-mips-debug.aab`\n    summary: List of the generated (and copied) AAB paths.\n    title: List of the generated AAB paths\n"
  },
  {
    "path": "steps/ionic-archive/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/ionic-prepare/0.9.0/step.yml",
    "content": "title: Ionic prepare\nsummary: Prepares your Ionic project\ndescription: |-\n  Prepares your Ionic project.\n\n  The step prepares your Ionic project by calling:\n\n  - `ionic [cordova] platform rm <platform>`\n  - `ionic [cordova] platform add <platform>`\nwebsite: https://github.com/bitrise-community/steps-ionic-prepare\nsource_code_url: https://github.com/bitrise-community/steps-ionic-prepare\nsupport_url: https://github.com/bitrise-community/steps-ionic-prepare/issues\npublished_at: 2018-05-22T12:12:58.48287491+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-prepare.git\n  commit: 91023129e015be118079292b184447f2f35b8218\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-prepare\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- opts:\n    description: |-\n      Specify whether to remove platforms and then re-add (overwrites some config.xml values).\n\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Should remove platforms as prepare step?\n    value_options:\n    - \"true\"\n    - \"false\"\n  readd_platform: \"true\"\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- cordova_ios_version: null\n  opts:\n    description: |-\n      The version of cordova-ios plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-ios/releases) equivalent to doing `ionic cordova platform add ios@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-ios.git`\n\n      - latest - The step will update to the latest cordova-ios version `ionic cordova platform add ios@latest`.\n\n      - empty - Uses the pinned cordova-ios version.\n    title: iOS version\n- cordova_android_version: null\n  opts:\n    description: |-\n      The version of cordova-android plugin you want to use.\n\n      Should be one of the following:\n\n      - x.x.x - [A specific release](https://github.com/apache/cordova-android/releases) equivalent to doing `ionic cordova platform add android@x.x.x`\n\n      - master - will use the master branch of the repo, equivalent to doing `ionic cordova platform add https://github.com/apache/cordova-android.git`\n\n      - latest - The step will update to the latest cordova-android version `ionic cordova platform add android@latest`.\n\n      - empty - Uses the pinned cordova-android version.\n    title: Android version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/ionic-prepare/1.0.0/step.yml",
    "content": "title: Ionic prepare\nsummary: Prepares your Ionic project\ndescription: |-\n  Prepares your Ionic project.\n\n  The step prepares your Ionic project by calling:\n\n  - `ionic cordova \"prepare\" \"--no-build\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-prepare\nsource_code_url: https://github.com/bitrise-community/steps-ionic-prepare\nsupport_url: https://github.com/bitrise-community/steps-ionic-prepare/issues\npublished_at: 2018-12-14T10:58:35.811761205Z\nsource:\n  git: https://github.com/bitrise-community/steps-ionic-prepare.git\n  commit: 154e15bab9f06cb95aa548e47cae7096c0dfba02\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-prepare\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n"
  },
  {
    "path": "steps/ionic-prepare/1.1.0/step.yml",
    "content": "title: Ionic prepare\nsummary: Prepares your Ionic project\ndescription: |-\n  Prepares your Ionic project.\n\n  The step prepares your Ionic project by calling:\n\n  - `ionic cordova \"prepare\" \"--no-build\"`\nwebsite: https://github.com/bitrise-community/steps-ionic-prepare\nsource_code_url: https://github.com/bitrise-community/steps-ionic-prepare\nsupport_url: https://github.com/bitrise-community/steps-ionic-prepare/issues\npublished_at: 2019-09-20T11:59:11.184621073Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-prepare.git\n  commit: 095f2c50124b74e7f9b9efa92fd2f47fb490cf6a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-ionic-prepare\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    title: Platform to use in ionic-cli commands\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    title: Ionic password\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n      `true`: Mark local dependencies to be cached.\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ionic-prepare/1.2.0/step.yml",
    "content": "title: Ionic prepare\nsummary: Prepares your Ionic project\ndescription: |-\n  Prepares your Ionic project.\n\n  The step prepares your Ionic project by calling:\n\n  - `ionic cordova \"prepare\" \"--no-build\"`\nwebsite: https://github.com/bitrise-steplib/steps-ionic-prepare\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-prepare\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-prepare/issues\npublished_at: 2020-11-11T09:25:29.396625735Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-prepare.git\n  commit: 9b052841f20befb15fa9344043e37fae703c3d17\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-prepare\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    summary: Platform to use in ionic-cli commands\n    title: Platform\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    summary: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    summary: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: Root directory of the Ionic project.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    summary: Username to login with in ionic-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    summary: Password to login with in ionic-cli.\n    title: Ionic password\n- cache_local_deps: \"false\"\n  opts:\n    description: |-\n      Selects if the contents of node_modules directory is cached.\n      - `true`: Mark local dependencies to be cached.\n      - `false`: Do not use cache.\n    is_required: true\n    summary: Enable caching node_modules.\n    title: Cache enabled\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ionic-prepare/1.2.1/step.yml",
    "content": "title: Ionic prepare\nsummary: Prepares your Ionic project\ndescription: |-\n  Prepares your Ionic project.\n\n  The step prepares your Ionic project by calling:\n\n  - `ionic cordova \"prepare\" \"--no-build\"`\nwebsite: https://github.com/bitrise-steplib/steps-ionic-prepare\nsource_code_url: https://github.com/bitrise-steplib/steps-ionic-prepare\nsupport_url: https://github.com/bitrise-steplib/steps-ionic-prepare/issues\npublished_at: 2023-09-28T14:11:32.115749443Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ionic-prepare.git\n  commit: 60c0fe279161292dfe3d22285d870418f9196130\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ionic-prepare\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Specify this input to apply ionic-cli commands to desired platforms only.\n\n      `ionic [cordova] platform rm <platform>`\n    is_required: true\n    summary: Platform to use in ionic-cli commands\n    title: Platform\n    value_options:\n    - ios,android\n    - ios\n    - android\n  platform: ios,android\n- ionic_version: null\n  opts:\n    description: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    summary: |-\n      The version of ionic you want to use.\n\n      If value is set to `latest`, the step will update to the latest ionic version.\n      Leave this input empty to use the preinstalled ionic version.\n    title: Ionic version\n- cordova_version: null\n  opts:\n    description: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    summary: |-\n      The version of cordova you want to use.\n\n      If value is set to `latest`, the step will update to the latest cordova version.\n      Leave this input empty to use the preinstalled cordova version.\n    title: Cordova version\n- opts:\n    description: Root directory of your Ionic project, where your Ionic config.xml\n      exists.\n    is_required: true\n    summary: Root directory of the Ionic project.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- ionic_username: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    summary: Username to login with in ionic-cli.\n    title: Ionic username\n- ionic_password: null\n  opts:\n    description: Use `Ionic username` and `Ionic password` to login with ionic-cli.\n    is_sensitive: true\n    summary: Password to login with in ionic-cli.\n    title: Ionic password\n- cache_local_deps: \"false\"\n  opts:\n    description: |-\n      Selects if the contents of node_modules directory is cached.\n      - `true`: Mark local dependencies to be cached.\n      - `false`: Do not use cache.\n    is_required: true\n    summary: Enable caching node_modules.\n    title: Cache enabled\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/ionic-prepare/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2017-11-14T18:15:31.902098022+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: ea726dfd8f21ea2e28bce6f321a49a45a16d1ac6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code singing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- distributon_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.1/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2017-11-14T22:49:43.680154751+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 2d650fa7471bca560d313f4e52b8f1bcf4fc7136\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code singing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- distributon_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2017-11-15T16:23:58.099983823+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: b0ef24a6f316a97943403b635d5124be5b689d94\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code singing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- distributon_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.3/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2017-12-06T16:32:05.41316264+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 9afd01f474794a989d9286358fee29deb08b204a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.4/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2017-12-06T23:22:09.470107235+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: c2c2cc21f47ee9d977c2c3f77679ebad3139a40a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.5/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2017-12-22T11:48:32.011076+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: ee95fae93f9b0372dd1f13e295ef9e4d52b3d0cd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.6/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-01-11T17:01:40.035101+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: ef827768ba17ace25f0d358aa1fc179b22d6d120\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/0.9.7/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-01-24T14:47:42.793369+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 4eeaa92055cc48dc0b3041e52ce17ffa4758bb7d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/1.0.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: !!timestamp 2018-03-21T17:36:39.573215634+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 8f8503e36afa9ab238a62544492b45b3c16c2ba5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/1.0.1/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: !!timestamp 2018-03-29T17:18:16.444931239+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: a2a3cd76f20931a85de1363e61f6bf1a82c8865f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/1.0.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-04-23T17:48:22.032881087+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 8d5f7369dade91be647dcb4444765f0928366ac8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/1.0.3/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  Automatically manages your iOS Provisioning Profiles for your Xcode project:\n\n  - it ensures that the Application Identifier exists on the Apple Developer Portal\n  - it ensures that the project's Capabilities are set correctly in the Application Identifier\n  - it ensures that the Provisioning Profiles exists on the Apple Developer Portal\n  - it ensure that all the available Test Devices exists on the Apple Developer Portal and are included in the Provisioning Profile as well\n  - it installs all the Codesigning Certificates into the Keychain\n\n  Setup guide: https://blog.bitrise.io/ios-auto-provision-step\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: !!timestamp 2018-05-08T12:11:21.643181181+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: a7ed3b45420cbfde7b552865ae93b6fab440e485\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__ Otherwise specify this input if you want to manage the Profiles with different team, then one set in your project.\n\n      If you leave it empty the project defined team will be used.\n\n      Example: `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character.\\n\\nYou can specify a local path as well,\n      using the `file://` scheme.\\n\\nProvide a development certificate url, to ensure\n      development code sign files for the project and also provide a distribution\n      certificate url, to ensure distribution code sign files for your project.\\n\\nExample:\n      \\n\\n`file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      Specified certificate passphrase count should match the count of the certificate urls.\n\n      example: development certificate with empty passphrase, distribution certificate with non-empty passphrase\n\n      ```\n      passphrases: \"|distribution-passphrase\"\n      ```\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Config\n    description: The Keychain path\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Config\n    description: The Keychain's password\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/1.1.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [https://blog.bitrise.io/ios-auto-provision-step](https://blog.bitrise.io/ios-auto-provision-step)\n\n  In case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exists on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exists on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-05-10T16:20:50.637924056+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 68713fa6d3d5e0ff92b959ddd498cc00078868b6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's codesigning files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with different team, then the one set in your project.\\n\\nIf you leave\n      it empty the project defined team will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In case of __Xcode managed codesigning__ projects, by default the\n      step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf this\n      input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in case of Manual codesigning projects__),  \\nthe step will\n      fall back to use the Xcode managed Provisioning Profiles in case of an issue.\\n\\n__This\n      input has no effect in case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code sign files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code sign files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    title: Bitrise build api token\n"
  },
  {
    "path": "steps/ios-auto-provision/1.1.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [https://blog.bitrise.io/ios-auto-provision-step](https://blog.bitrise.io/ios-auto-provision-step)\n\n  In case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exists on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exists on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-05-28T17:09:52.758419314+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 5e1c6fd90881c2d969cbe4ac7bc2cd42a6f3e787\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's codesigning files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with different team, then the one set in your project.\\n\\nIf you leave\n      it empty the project defined team will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In case of __Xcode managed codesigning__ projects, by default the\n      step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf this\n      input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in case of Manual codesigning projects__),  \\nthe step will\n      fall back to use the Xcode managed Provisioning Profiles in case of an issue.\\n\\n__This\n      input has no effect in case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code sign files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code sign files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.1.3/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [https://blog.bitrise.io/ios-auto-provision-step](https://blog.bitrise.io/ios-auto-provision-step)\n\n  In case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exists on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exists on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-06-27T08:52:30.471125787+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 4469129de6e71403950615a5f326726dd62bc808\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's codesigning files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with different team, then the one set in your project.\\n\\nIf you leave\n      it empty the project defined team will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In case of __Xcode managed codesigning__ projects, by default the\n      step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf this\n      input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in case of Manual codesigning projects__),  \\nthe step will\n      fall back to use the Xcode managed Provisioning Profiles in case of an issue.\\n\\n__This\n      input has no effect in case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code sign files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code sign files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.1.4/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-08-27T11:07:41.103243763Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: b72dc71a215939e5f997c831305211975cc5d4bd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's code signing files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with a different team than the one set in your project.\\n\\nIf you leave\n      it empty the team defined by the project will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In the case of __Xcode managed code signing__ projects, by default\n      the step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf\n      this input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in the case of Manual code signing projects__),  \\nthe step\n      will fall back to use the Xcode managed Provisioning Profiles if there is an\n      issue.\\n\\n__This input has no effect in the case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code signing files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code signing files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.1.5/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-09-13T11:02:18.593738587Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 4512ff062e2af5a1ec6eafd93d9994ea7ddd5d65\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's code signing files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with a different team than the one set in your project.\\n\\nIf you leave\n      it empty the team defined by the project will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In the case of __Xcode managed code signing__ projects, by default\n      the step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf\n      this input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in the case of Manual code signing projects__),  \\nthe step\n      will fall back to use the Xcode managed Provisioning Profiles if there is an\n      issue.\\n\\n__This input has no effect in the case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code signing files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code signing files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.2.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-09-18T08:53:56.832594931Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: df35c7f42a0250b259fd0d2586c9855cb6bb4de1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's code signing files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with a different team than the one set in your project.\\n\\nIf you leave\n      it empty the team defined by the project will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In the case of __Xcode managed code signing__ projects, by default\n      the step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf\n      this input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in the case of Manual code signing projects__),  \\nthe step\n      will fall back to use the Xcode managed Provisioning Profiles if there is an\n      issue.\\n\\n__This input has no effect in the case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code signing files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code signing files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.2.1/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-11-08T11:40:59.442992666Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: c5fe2719bfef0e8a9dab0243f4e9d68d96d98e57\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's code signing files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with a different team than the one set in your project.\\n\\nIf you leave\n      it empty the team defined by the project will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In the case of __Xcode managed code signing__ projects, by default\n      the step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf\n      this input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in the case of Manual code signing projects__),  \\nthe step\n      will fall back to use the Xcode managed Provisioning Profiles if there is an\n      issue.\\n\\n__This input has no effect in the case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code signing files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code signing files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.2.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-12-06T18:50:29.589451157Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 59db2eac177feae103d9a098e9e4cb329f5d4bea\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's code signing files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with a different team than the one set in your project.\\n\\nIf you leave\n      it empty the team defined by the project will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In the case of __Xcode managed code signing__ projects, by default\n      the step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf\n      this input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in the case of Manual code signing projects__),  \\nthe step\n      will fall back to use the Xcode managed Provisioning Profiles if there is an\n      issue.\\n\\n__This input has no effect in the case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code signing files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code signing files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.2.3/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2018-12-19T16:21:08.279967089Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 007c37de89e83585a444c2d847aa3c54fc8ed83c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: \"The Developer Portal team to manage the project's code signing files.\\n\\n__If\n      your Developer Portal Account belongs to multiple development team, this input\n      is required!__   \\nOtherwise specify this input if you want to manage the Provisioning\n      Profiles with a different team than the one set in your project.\\n\\nIf you leave\n      it empty the team defined by the project will be used.\\n\\n__Example:__ `1MZX23ABCD4`\"\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: \"The Xcode Configuration to use. \\n\\nBy default your Scheme defines\n      which Configuration (Debug, Release, ...) should be used,\\nbut you can overwrite\n      it with this option.\"\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: \"In the case of __Xcode managed code signing__ projects, by default\n      the step downloads and installs the Xcode managed Provisioning Profiles.\\n\\nIf\n      this input is set to: `yes`, the step will try to manage the Provisioning Profiles\n      by itself (__like in the case of Manual code signing projects__),  \\nthe step\n      will fall back to use the Xcode managed Provisioning Profiles if there is an\n      issue.\\n\\n__This input has no effect in the case of Manual codesigning projects.__\"\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: \"URLs of the certificates to download.\\n\\nMultiple URLs can be specified,\n      separated by a pipe (`|`) character,  \\nyou can specify a local path as well,\n      using the `file://` scheme.\\n\\n__Provide a development certificate__ url, to\n      ensure development code signing files for the project and __also provide a distribution\n      certificate__ url, to ensure distribution code signing files for your project.\\n\\n__Example:__\n      `file://./development/certificate/path|https://distribution/certificate/url`\\n\"\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.3.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-01-11T08:39:47.622466823Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 536ba20a7a7be313686958dfae58f0e660f16e47\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.3.1/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-02-22T13:44:24.508501662Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 88e22472b0f75e159900f856b2dde1c78cafe2c6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team id\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.3.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-09-27T13:00:00.508501662Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 37af3aabad8a6a62fe3e6a4d4270dd4c3bebaf93\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.4.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-10-02T11:14:53.553763994Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: bdc059f6a98903c166f3f2d733a2d51609a3cde0\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.4.1/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-10-15T09:17:29.766225166Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: aeea88a3fec20fd0538e135443d36701dd041cbd\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.4.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-11-22T12:55:21.080127157Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: f2f36ef6a6accdfdc9950b0d121bcedaa7169e62\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.4.3/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-12-16T12:14:37.801960987Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: f6b15758d827c72e18ed901889e56e93635cc68a\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.0/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2019-12-19T14:09:02.386785459Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 6d6b7be47791e3bebfac285a6692fd748e524216\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.1/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2020-01-15T15:15:15.731395176Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: d67ead35dbdfae316b088a627fbee3816f35a213\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.10/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-07-28T11:51:08.522967362Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: d4431a5af941f06e79f13e636d1c88501a10850c\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.2/step.yml",
    "content": "title: iOS Auto Provision\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2020-01-16T09:50:07.347893998Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 4c504c6c690b55902c4d0981a9acc3afd068bbfb\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.3/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  In the case of __Xcode managed codesigning__ projects:\n\n  - downloads the __Xcode managed Provisioning Profiles__ and installs them for the build\n  - installs the provided __Codesigning Certificates__ into the Keychain\n\n  In the case of __Manual codesigning__ projects:\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2020-06-23T08:45:08.945729049Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: e6443be1b37f1f708d26848ba2d904e4d97eb783\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n\n      If you leave it empty the team defined by the project will be used.\n\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build url.\n    is_required: true\n    title: Bitrise build url\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build api token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build api token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.4/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2020-10-16T12:29:39.408212419Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: ff0350e080c95e50fb99d6f83c63ba169ddd814e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.5/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-02-09T09:06:54.681178874Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 12b58e2059b903166ff67ad3a3ea4e137dde8e1b\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.6/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-02-24T13:52:02.570475092Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 9633ba5702532f5819fbc377dce08017cdb6f2ea\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.7/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-02-24T17:50:00.685936108Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 13ead42899f12a92557d80244c61d0fe2845d877\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.8/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-02-25T08:24:10.56046817Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 00801c97e43d3520ca5027712c0a8473084f85cb\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/1.5.9/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-05-10T09:40:50.69639139Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 34ca8eaa103c7a7b01ba9b60ee74610028655cda\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/2.0.0/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-08-04T08:48:39.476009575Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: c31ae375a4e9988d5685f4dd39c06ea818c7db89\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices on Bitrise from team members with the Apple Developer Portal.\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/2.0.1/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-08-13T09:07:20.432185061Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 49a9950ed0b43912ae5bd8bc964fccf51074a594\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices on Bitrise from team members with the Apple Developer Portal.\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/2.0.2/step.yml",
    "content": "title: iOS Auto Provision with Apple ID\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2021-08-24T12:01:17.046180343Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 77e4e4405180bc5de67cd87b9688fa260969e9d6\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices on Bitrise from team members with the Apple Developer Portal.\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/2.0.3/step.yml",
    "content": "title: iOS Auto Provision with Apple ID (Deprecated)\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"### This Step has been deprecated in favour of the new automatic code\n  signing options on Bitrise.\\nYou can read more about these changes in our blog post:\n  [https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise](https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise).\\n\\n####\n  Option A)\\nThe latest versions of the [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive),\n  [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test),\n  and the [Export iOS and tvOS Xcode archive](https://www.bitrise.io/integrations/steps/xcode-archive)\n  Steps have built-in automatic code signing.\\nWe recommend removing this Step from\n  your Workflow and using the automatic code signing feature in the Steps mentioned\n  above.\\n\\n#### Option B)\\nIf you are not using any of the mentioned Xcode Steps,\n  then you can replace\\nthis iOS Auto Provision Step with the [Manage iOS Code signing](https://www.bitrise.io/integrations/steps/manage-ios-code-signing)\n  Step.\\n\\n### Description\\nThe [Step](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#ios-auto-provision-with-apple-id-step)\n  uses session-based authentication to connect to an Apple Developer account. In addition\n  to an Apple ID and password, it also stores the 2-factor authentication (2FA) code\n  you provide.\\n\\nPlease note that the [iOS Auto Provision with App Store Connect\n  API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\n  Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests)\n  instead of the old session-based method.\\n\\nThe **iOS Auto Provision with Apple\n  ID** Step supports in Xcode managed and manual code signing in the following ways:\\n\\nIn\n  the case of Xcode managed code signing projects, the Step:\\n- Downloads the Xcode\n  managed Provisioning Profiles and installs them for the build.\\n- Installs the provided\n  code signing certificates into the Keychain.\\nIn the case of manual code signing\n  projects, the Step:\\n- Ensures that the Application Identifier exists on the Apple\n  Developer Portal.\\n- Ensures that the project's Capabilities are set correctly in\n  the Application Identifier.\\n- Ensures that the Provisioning Profiles exist on the\n  Apple Developer Portal and are installed for the build.\\n- Ensures that all the\n  available Test Devices exist on the Apple Developer Portal and are included in the\n  Provisioning Profiles.\\n- Installs the provided code signing certificates into the\n  Keychain.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the Step,\n  make sure you've completed the following requirements:\\n- You've [defining your\n  Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise-1).\\n-\n  You've [assigned an Apple Developer Account for your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app-1).\\n\\nTo\n  configure the Step:\\nOnce you've completed the above requirements, there is very\n  little configuration needed to this Step.\\n1. Add the **iOS Auto Provision with\n  Apple ID** Step after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Distribution type**, **Xcode Project (or Workspace) path**,\n  and the **Scheme name** inputs are automatically filled out for you.\\n3. If your\n  Developer Portal Account belongs to multiple development teams, add the **Developer\n  Portal team ID** to manage the project's code signing files, for example '1MZX23ABCD4'.\n  If that's not the case, you can still add it to manage the Provisioning Profiles\n  with a different team than the one set in your project. If you leave it empty, the\n  team defined by the project will be used.\\n4. If you wish to overwrite the configuration\n  defined in your Scheme (for example, Debug, Release), you can do so in the **Configuration\n  name** input.\\n5. If Xcode managed signing is enabled in the iOS app, check the\n  value of the **Should the step try to generate Provisioning Profiles even if Xcode\n  managed signing is enabled in the Xcode project?** input.\\n- If it’s set to 'no',\n  the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer\n  Portal.\\n- If it’s set to 'yes', the Step will generate a new manual provisioning\n  profile on the Apple Developer portal for the project.\\nThis input has no effect\n  in the case of Manual code signing projects.\\n6. **The minimum days the Provisioning\n  Profile should be valid** lets you specify how long a Provisioning Profile should\n  be valid to sign an iOS app. By default it will only renew the Provisioning Profile\n  when it expires.\\n\\n### Troubleshooting\\nPlease note that the 2FA code is only valid\n  for 30 days. \\nWhen the 2FA code expires, you will need to re-authenticate to provide\n  a new code. \\nGo to the Apple Developer Account of the **Account settings** page,\n  it will automatically ask for the 2FA code to authenticate again. \\nThere will be\n  a list of the Apple Developer accounts that you have defined. To the far right of\n  each, there are 3 dots. \\nClick the dots and select **Re-authenticate (2SA/2FA)**.\\n\\n###\n  Useful links\\n- [Managing code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/#configuring-ios-auto-provisioning)\\n-\n  [iOS code signing troubleshooting](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-code-signing-troubleshooting/)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with App Store Connect API](https://app.bitrise.io/integrations/steps/ios-auto-provision-appstoreconnect)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues\npublished_at: 2022-01-14T16:26:36.435848951Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision.git\n  commit: 4f51fd6877888de878a852ac31fa1c8b37ddcc82\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: |-\n      The Developer Portal team to manage the project's code signing files.\n      __If your Developer Portal Account belongs to multiple development team, this input is required!__\n      Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.\n      If you leave it empty the team defined by the project will be used.\n      __Example:__ `1MZX23ABCD4`\n    title: The Developer Portal team ID\n  team_id: null\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- generate_profiles: \"no\"\n  opts:\n    description: |-\n      In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.\n      If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself (__like in the case of Manual code signing projects__),\n      the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.\n      __This input has no effect in the case of Manual codesigning projects.__\n    title: Should the step try to generate Provisioning Profiles even if Xcode managed\n      signing is enabled in the Xcode project?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices on Bitrise from team members with the Apple Developer Portal.\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate URLs.__\n      For example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase) `|distribution-passphrase`.\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Debug\n    description: Bitrise build URL.\n    is_required: true\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Debug\n    description: Bitrise build API token.\n    is_required: true\n    is_sensitive: true\n    title: Bitrise build API token\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n      One of these: `development`, `app-store`, `ad-hoc` or `enterprise`.\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development code signing identity's name.\n      For example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`.\n    title: The development code signing identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production code signing identity's name.\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production code signing identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile UUID.\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2022-09-15\"\ndeprecate_notes: |\n  This Step has been deprecated in favour of the new automatic code signing options on Bitrise.\n\n  Option A)\n  The latest versions of the [Xcode Archive & Export for iOS](https://github.com/bitrise-steplib/steps-xcode-archive), [Xcode Build for testing for iOS](https://github.com/bitrise-steplib/steps-xcode-build-for-test), and the [Export iOS and tvOS Xcode archive](https://github.com/bitrise-steplib/steps-export-xcarchive) Steps have built-in automatic code signing.\n  We recommend removing this Step from your Workflow and using the automatic code signing feature in the Steps mentioned above.\n\n  Option B)\n  If you are not using any of the mentioned Xcode steps, then you can replace this iOS Auto Provision Step with the [Manage iOS Code signing](https://www.bitrise.io/integrations/steps/manage-ios-code-signing) Step.\n\n  You can [read more](https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise) about these changes in our blog post.\n\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.0/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  How does it work?\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-05-28T10:57:29.517494113Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: c1d53fc60d082f8e32efaa0ea43231d25c1be772\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise API token\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.1/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  How does it work?\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-09-29T09:02:33.456290583Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: f140e29521253cfd0502606040c76a47b8189ccc\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise API token\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.2/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  How does it work?\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-12-01T15:56:42.607680257Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 44d35658e682568492057024f10dd75810cd2708\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise API token\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.3/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  How does it work?\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-12-02T12:16:21.475178082Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 6d5850231dd76df47377bee6121efb4ab505e6a6\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise API token\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.4/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project\ndescription: |-\n  ### Automatically manages your iOS Provisioning Profiles for your Xcode project.\n\n  __Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n\n  How does it work?\n\n  - ensures that the __Application Identifier__ exists on the Apple Developer Portal\n  - ensures that the __project's Capabilities__ are set correctly in the Application Identifier\n  - ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build\n  - ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles\n  - installs the provided __Codesigning Certificates__ into the Keychain\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-12-03T16:22:37.633036597Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 50af00e297f72ca8e250df1af772f635e045ea0d\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Bitrise API token\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n\n      By default your Scheme defines which Configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n\n      By default (0) it just renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n\n      __Provide a development certificate__ url, to ensure development code signing files for the project and __also provide a distribution certificate__ url, to ensure distribution code signing files for your project.\n\n      __Example:__ `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n\n      __Specified certificate passphrase count should match the count of the certificate urls.__\n\n      __Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: |-\n      The selected distribution type.\n\n      One of: `development`, `app-store`, `ad-hoc` or `enterprise`\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: |-\n      The development team's ID.\n\n      Example: `1MZX23ABCD4`\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The development codesign identity's name.\n\n      Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: |-\n      The production codesign identity's name.\n\n      Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: |-\n      The main target's development provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's development provisioning profile's UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: |-\n      The main target's production provisioning profile's UUID.\n\n      Example: `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: The main target's production provisioning profile's UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.5/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-12-09T15:46:17.322915052Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 24a26ed85f5fcb1bc89e401c8711f2ad7d56d10a\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.6/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2020-12-17T08:57:58.267862848Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: fa70b441073f4d69487d7fe78a40df381f4eb091\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/0.1.7/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-01-13T12:10:15.080428478Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: e175864cd4d36ed49383aa05ffffe5ea7f8b587c\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_required: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_required: true\n    title: Build URL\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.0.0/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-02-04T08:32:55.181760145Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 2f8484733d293df6c193984c9591e99742b9089f\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.0.1/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-02-24T11:28:03.895278215Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 73b28e45b669f2135978f3ab027c1e5e339957d3\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.0.2/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-03-02T12:47:51.798675708Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: cd61d18c5f1f2b13cd44079e017b6efd46edaa88\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.0.3/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-03-05T11:59:20.984666103Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: d322784b71828ad627455464da7f847689d3c872\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_something.p8` or `file:///PATH/TO/AuthKey_something.p8`\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.0.4/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-05-10T11:38:33.940062901Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: a312f1bde768432e0f80b25ed50a44253328ac3e\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Xcode Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      The Xcode Configuration to use.\n      By default your Scheme defines which Configuration (for example, Debug, Release) should be used,\n      but you can overwrite it with this option.\n    title: Configuration name\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.1.0/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n\\n- **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n\\n- **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n\\n- **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-06-03T08:09:33.559456434Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 307f5891eee0070a7765d3ed6cb64b7ccff2cdc8\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.1.1/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n    - **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n    - **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n    - **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-07-08T16:46:24.435260579Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: cee2bafe0af51d83ff7601688b595d5b44abbacc\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.1.2/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n    - **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n    - **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n    - **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-07-26T11:23:20.862425941Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: b4db99bc74a45a5d6908dfe9ad0a66c04f4f0301\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/1.1.3/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n    - **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n    - **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n    - **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-07-29T15:15:43.123591168Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 9423c90c50d7f0ba56f5923c278b6c37777eb526\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.0.0/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n    - **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n    - **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n    - **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-07-30T09:15:16.936826629Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: c6797b6a0cde7cd40ba39744fcce9c346963dfec\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.0.1/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n    - **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n    - **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n    - **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-08-04T11:55:46.281893838Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 91298aba3892e5fbdd93f0388db45b4f6fcde583\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.0.2/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: \"The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests).\n  \\nThe Steps performs the following:\\n- It generates, updates and downloads the provisioning\n  profiles needed for your iOS project.\\n- It verifies if your project is registered\n  with the App Store Connect. If it was not, the Step registers your project.\\n- It\n  registers the iOS devices connected to your Bitrise account with the App Store Connect.\\n-\n  It modifies the iOS project to use manual code signing if the project uses automatically\n  managed signing.\\n\\n### Configuring the Step\\n\\nBefore you start configuring the\n  Step, make sure you've completed the following requirements:\\n1. You've generated\n  an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)\n  and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\\n2. You've [defined\n  your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\\n3.\n  You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\\n\\nOnce\n  these are done, most of the required Step input fields are already populated for\n  you.\\n\\nTo configure the Step:\\n\\n1. Add the **iOS Auto Provision with App Store\n  Connect API** after any dependency installer Step in your Workflow, such as **Run\n  CocoaPods install** or **Carthage**.\\n2. Click the Step to edit its input fields.\n  You can see that the **Build API token**, **Build URL**, and the **Xcode Project\n  (or Workspace) path** inputs are automatically filled out for you.\\n    - **Build\n  API token**: Every running build has a temporary API token on a Bitrise virtual\n  machine. This token is only available while the build is running. The Step downloads\n  the connected API key with the help of this API token and Bitrise saves it in a\n  JSON file.\\n    - **Build URL**: URL of the current build or local path URL to your\n  `apple_developer_portal_data.json`.\\n    - **Xcode Project path**: The path where\n  the `.xcodeproj` / `.xcworkspace` is located.\\n3. **Distribution type** input's\n  value has to match with the value of the **Select method for export** input in the\n  **Xcode Archive & Export for iOS** Step.\\n4. With the **Scheme name** input you\n  can restrict which targets to process.\\n\\n### Troubleshooting\\nMake sure you do\n  not have the **Certificate and Profile Installer** Step in your Workflow.\\nMake\n  sure that you do NOT modify your Xcode project between the **iOS Auto Provision\n  with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For\n  example, do not change the **bundle ID** after the **iOS Auto Provision with App\n  Store Connect API** Step.\\n\\n### Useful links\\n- [Managing iOS code signing files\n  - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\\n-\n  [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\\n\\n###\n  Related Steps\\n- [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\"\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-08-27T04:42:21.230468736Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: fa40eed93971cce97c68af509af9643549bddee7\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      The input determines the method used for Apple Service authentication. By default, the Bitrise Apple Developer connection based on API key is used and other authentication-related Step inputs are ignored.\n\n      You can either use the established Bitrise Apple Developer connection or you can tell the Step to only use the Step inputs for authentication.\n      - `automatic`: Use the Apple Developer connection based on API key. Step inputs are only used as a fallback.\n      - `api_key`: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.\n      - `off`: Do not use any already configured Apple Developer Connection. Only authentication-related Step inputs are considered.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.0.3/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-09-10T09:08:52.320652315Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: a5efb7298e1358139603b76f8671de673896310d\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.1.0/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-09-20T13:25:48.927864373Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 0c3bda4f8c2e7a2f8b19f72595b24583977a33a8\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise-with-apple-id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise-with-apple-id\n    - apple-id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Needed if the are multiple Developer Portal teams active when using\n      Bitrise Apple Service connection with Apple ID.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.1.1/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-10-01T10:09:36.873743567Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 293a592243b2bb5eac0cf6fa6129bc0930cc9b3b\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise-with-apple-id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise-with-apple-id\n    - apple-id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Needed if the are multiple Developer Portal teams active when using\n      Bitrise Apple Service connection with Apple ID.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.1.2/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-10-08T10:58:47.021184918Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: cc93e58e951a04f72c4425d02c419d462afbf81b\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Needed if the are multiple Developer Portal teams active when using\n      Bitrise Apple Service connection with Apple ID.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.1.3/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-10-13T11:08:07.436952775Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 906b5add3d448b389eb2a07ae3e982a322a56af9\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Needed if the are multiple Developer Portal teams active when using\n      Bitrise Apple Service connection with Apple ID.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.0/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-10-20T07:37:12.132754217Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 52f54734f0a0468088da85fdfb539a1914aa621b\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Needed if the are multiple Developer Portal teams active when using\n      Bitrise Apple Service connection with Apple ID.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.1/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-10-21T08:40:33.0882978Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 8b91bea34d4bac92da5b98cff5b4487ef645ba18\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Needed if the are multiple Developer Portal teams active when using\n      Bitrise Apple Service connection with Apple ID.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.2/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-12-13T14:26:26.449092271Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 508096f5c17319dbb8b1919164fd2d26431c91f6\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.3/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-12-17T00:56:48.79441844Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: c34b2e332d1cfbb8d9faba3556c0efd61af6fa7a\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.4/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2021-12-17T16:06:51.839201502Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: ba1ed3ebdeafebb01f38fac8711ab0da19febe96\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.5/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2022-01-05T17:01:09.743479953Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 06e023dfa790e6c2025988dbef0ed13ebf34c087\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.6/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API (Deprecated)\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  ### This Step has been deprecated in favour of the new automatic code signing options on Bitrise.\n  You can read more about these changes in our blog post: [https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise](https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise).\n\n  #### Option A)\n  The latest versions of the [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive), [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test), and the [Export iOS and tvOS Xcode archive](https://www.bitrise.io/integrations/steps/xcode-archive) Steps have built-in automatic code signing.\n  We recommend removing this Step from your Workflow and using the automatic code signing feature in the Steps mentioned above.\n\n  #### Option B)\n  If you are not using any of the mentioned Xcode Steps, then you can replace\n  this iOS Auto Provision Step with the [Manage iOS Code signing](https://www.bitrise.io/integrations/steps/manage-ios-code-signing) Step.\n\n  ### Description\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2022-01-14T16:28:43.257481889Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: d15916233b9c90a55b031034c83e6385ac2cff62\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.7/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API (Deprecated)\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  ### This Step has been deprecated in favour of the new automatic code signing options on Bitrise.\n  You can read more about these changes in our blog post: [https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise](https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise).\n\n  #### Option A)\n  The latest versions of the [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive), [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test), and the [Export iOS and tvOS Xcode archive](https://www.bitrise.io/integrations/steps/xcode-archive) Steps have built-in automatic code signing.\n  We recommend removing this Step from your Workflow and using the automatic code signing feature in the Steps mentioned above.\n\n  #### Option B)\n  If you are not using any of the mentioned Xcode Steps, then you can replace\n  this iOS Auto Provision Step with the [Manage iOS Code signing](https://www.bitrise.io/integrations/steps/manage-ios-code-signing) Step.\n\n  ### Description\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2022-01-28T11:07:54.544502411Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: 66e3d21f557bcb7ad5fe764977c3d45c7c2d0706\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/2.2.8/step.yml",
    "content": "title: iOS Auto Provision with App Store Connect API (Deprecated)\nsummary: Automatically manages your iOS Provisioning Profiles for your Xcode project.\ndescription: |-\n  ### This Step has been deprecated in favour of the new automatic code signing options on Bitrise.\n  You can read more about these changes in our blog post: [https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise](https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise).\n\n  #### Option A)\n  The latest versions of the [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive), [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test), and the [Export iOS and tvOS Xcode archive](https://www.bitrise.io/integrations/steps/xcode-archive) Steps have built-in automatic code signing.\n  We recommend removing this Step from your Workflow and using the automatic code signing feature in the Steps mentioned above.\n\n  #### Option B)\n  If you are not using any of the mentioned Xcode Steps, then you can replace\n  this iOS Auto Provision Step with the [Manage iOS Code signing](https://www.bitrise.io/integrations/steps/manage-ios-code-signing) Step.\n\n  ### Description\n  The Step uses the official [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests). The Step can obtain the API connection information in 2 ways:\n  It can use either the Bitrise Apple Developer connection selected under the **Team** tab for the application, or you can provide the information to the Step using Step's input variables.\n  The Steps performs the following:\n  - It generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - It verifies if your project is registered with the App Store Connect. If it was not, the Step registers your project.\n  - It registers the iOS devices connected to your Bitrise account with the App Store Connect.\n  - It modifies the iOS project to use manual code signing if the project uses automatically managed signing.\n\n  ### Configuring the Step\n\n  Before you start configuring the Step, make sure you've completed the following requirements:\n  1. You've generated an [API key](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api) and obtained an **Issuer ID**, **Key ID** and a **Private Key**.\n  2. You've [defined your Apple Developer Account to Bitrise](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#defining-your-apple-developer-account-to-bitrise).\n  3. You've [assigned an Apple Developer Account to your app](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-app).\n\n  Once these are done, most of the required Step input fields are already populated for you.\n\n  To configure the Step:\n\n  1. Add the **iOS Auto Provision with App Store Connect API** after any dependency installer Step in your Workflow, such as **Run CocoaPods install** or **Carthage**.\n  2. Click the Step to edit its input fields. You can see that the **Build API token**, **Build URL**, and the **Xcode Project (or Workspace) path** inputs are automatically filled out for you.\n      - **Build API token**: Every running build has a temporary API token on a Bitrise virtual machine. This token is only available while the build is running. The Step downloads the connected API key with the help of this API token and Bitrise saves it in a JSON file.\n      - **Build URL**: URL of the current build or local path URL to your `apple_developer_portal_data.json`.\n      - **Xcode Project path**: The path where the `.xcodeproj` / `.xcworkspace` is located.\n  3. **Distribution type** input's value has to match with the value of the **Select method for export** input in the **Xcode Archive & Export for iOS** Step.\n  4. With the **Scheme name** input you can restrict which targets to process.\n\n  ### Troubleshooting\n  Make sure you do not have the **Certificate and Profile Installer** Step in your Workflow.\n  Make sure that you do NOT modify your Xcode project between the **iOS Auto Provision with App Store Connect API** and the **Xcode Archive & Export for iOS** Steps. For example, do not change the **bundle ID** after the **iOS Auto Provision with App Store Connect API** Step.\n\n  ### Useful links\n  - [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)\n  - [About iOS Auto Provision with Apple ID](https://devcenter.bitrise.io/getting-started/configuring-bitrise-steps-that-require-apple-developer-account-data/#assigning-an-apple-developer-account-for-your-appv)\n\n  ### Related Steps\n  - [iOS Auto Provision with Apple ID](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Xcode Archive & Export](https://www.bitrise.io/integrations/steps/xcode-archive)\nwebsite: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsource_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nsupport_url: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues\npublished_at: 2022-02-23T21:19:58.526787013Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect.git\n  commit: cd013bba55b78f8e5745c5fe088f4317f0aed39d\nproject_type_tags:\n- ios\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- connection: automatic\n  opts:\n    description: |-\n      This input variable allows you to specify how the Step determines the API connection to use.\n      - `automatic`: The Step can use either method: It will attempt to use the Bitrise Apple Developer connection first. If this is not available, it will use the Step input variables.\n      - `api_key`: The Step will only use the Bitrise Apple Developer connection. It will not use the Step input variables.\n      - `off`: The Step will only use the Step input variables. It will not use the Bitrise Apple Developer connection.\n      - `enterprise_with_apple_id`: [Bitrise Apple Service connection with an Apple Developer Enterpsie account.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n      - `apple_id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: The Apple Service authentication method the Step uses. By default, the\n      Bitrise Apple Developer connection based on API key is used and other authentication-related\n      Step inputs are ignored.\n    title: Bitrise Apple Developer Connection\n    value_options:\n    - automatic\n    - api_key\n    - \"off\"\n    - enterprise_with_apple_id\n    - apple_id\n- api_key_path: \"\"\n  opts:\n    description: |-\n      Specify the path in an URL format where your API key is stored.\n\n      For example: `https://URL/TO/AuthKey_[KEY_ID].p8` or `file:///PATH/TO/AuthKey_[KEY_ID].p8`.\n      **NOTE:** The Step will only recognize the API key if the filename includes the  `KEY_ID` value as shown on the examples above.\n\n      You can upload your key on the **Generic File Storage** tab in the Workflow Editor and set the Environment Variable for the file here.\n\n      For example: `$BITRISEIO_MYKEY_URL`\n    is_sensitive: true\n    summary: Path to local or remote file\n    title: API Key URL\n- api_issuer: \"\"\n  opts:\n    description: Issuer ID. Required if **API Key URL** (`api_key_path`) is specified.\n    title: API Key Issuer ID\n- apple_id_team_id: \"\"\n  opts:\n    category: Apple ID\n    description: Defining this is required when Bitrise Apple Developer Connection\n      is set to `apple-id` and the connected account belongs to multiple teams.\n    title: Team ID\n- distribution_type: development\n  opts:\n    description: Describes how Xcode should sign your project.\n    is_required: true\n    title: Distribution type\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    description: The path where the `.xcodeproj` / `.xcworkspace` is located.\n    is_required: true\n    title: Xcode Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The scheme selects the main Application Target of the project.\n\n      The step will manage the codesign settings of the main Application and related executable (Application and App Extension) targets.\n    is_required: true\n    summary: The scheme name you want to use to archive your project later.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Configuration (for example, Debug, Release) selects the Build Settings describing the managed executable targets' Signing (Code Signing Style, Development Team, Code Signing Identity, Provisioning Profile).\n\n      If not set the step will use the provided Scheme's Archive Action's Build Configuration.\n    title: Configuration name\n- opts:\n    description: |-\n      If set the step will manage the codesign settings of the UITest targets of the main Application.\n      The UITest targets' bundle id will be set to the main Application's bundle id, so that the same Signing can be used for both the main Application and related UITest targets.\n    title: Should the step manage UITest target's codesigning?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    description: |-\n      If set the step will register known test devices from team members with the Apple Developer Portal.\n\n      Note that setting this to \"yes\" may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    title: Should the step register test devices with the Apple Developer Portal?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_days_valid: 0\n  opts:\n    description: |-\n      Sometimes you want to sign an app with a Provisioning Profile that is valid for at least 'x' days.\n      For example, an enterprise app won't open if your Provisioning Profile is expired. With this parameter, you can have a Provisioning Profile that's at least valid for 'x' days.\n      By default it is set to `0` and renews the Provisioning Profile when expired.\n    is_required: false\n    title: The minimum days the Provisioning Profile should be valid\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- certificate_urls: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Debug\n    description: |\n      URLs of the certificates to download.\n      Multiple URLs can be specified, separated by a pipe (`|`) character,\n      you can specify a local path as well, using the `file://` scheme.\n      __Provide a development certificate__ URL, to ensure development code signing files for the project and __also provide a distribution certificate__ URL, to ensure distribution code signing files for your project, for example, `file://./development/certificate/path|https://distribution/certificate/url`\n    is_required: true\n    is_sensitive: true\n    title: Certificate URL\n- opts:\n    category: Debug\n    description: |\n      Certificate passphrases.\n      Multiple passphrases can be specified, separated by a pipe (`|`) character.\n      __Specified certificate passphrase count should match the count of the certificate urls__,for example, (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`\n    is_required: true\n    is_sensitive: true\n    title: Certificate passphrase\n  passphrases: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Debug\n    description: The Keychain path.\n    is_required: true\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Debug\n    description: The Keychain's password.\n    is_required: true\n    is_sensitive: true\n    title: Keychain's password\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    description: Every build gets a temporary Bitrise API token to download the connected\n      API key in a JSON file.\n    is_dont_change_value: true\n    title: Build API token\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: URL of the current build or local path URL to your apple_developer_portal_data.json.\n    is_dont_change_value: true\n    title: Build URL\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    description: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    description: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The development codesign identity''s name, for example, `iPhone\n      Developer: Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    description: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    description: The development provisioning profile's UUID which belongs to the\n      main target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    description: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/ios-auto-provision-appstoreconnect/step-info.yml",
    "content": "maintainer: bitrise\nremoval_date: \"2022-09-15\"\ndeprecate_notes: |\n  This Step has been deprecated in favour of the new automatic code signing options on Bitrise.\n\n  Option A)\n  The latest versions of the [Xcode Archive & Export for iOS](https://github.com/bitrise-steplib/steps-xcode-archive), [Xcode Build for testing for iOS](https://github.com/bitrise-steplib/steps-xcode-build-for-test), and the [Export iOS and tvOS Xcode archive](https://github.com/bitrise-steplib/steps-export-xcarchive) Steps have built-in automatic code signing.\n  We recommend removing this Step from your Workflow and using the automatic code signing feature in the Steps mentioned above.\n\n  Option B)\n  If you are not using any of the mentioned Xcode steps, then you can replace this iOS Auto Provision Step with the [Manage iOS Code signing](https://www.bitrise.io/integrations/steps/manage-ios-code-signing) Step.\n\n  You can [read more](https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise) about these changes in our blog post.\n"
  },
  {
    "path": "steps/ipa-info/1.0.0/step.yml",
    "content": "title: IPA info\nsummary: IPA iOS info provider\ndescription: Provides all possible iOS IPA information as package name, version name\n  or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-ipa-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-ipa-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-ipa-info/issues\npublished_at: 2016-11-09T14:19:02.621919082+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-ipa-info.git\n  commit: e7f1991eaa23e68c2c772ec390f701f0f06c0c87\nproject_type_tags:\n- ios\ntype_tags:\n- ios\n- ipa\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      File path to IPA file to get info from.\n    is_required: true\n    title: IPA file path\noutputs:\n- IOS_IPA_PACKAGE_NAME: null\n  opts:\n    description: iOS application package name, ex. com.package.my\n    title: iOS application package name\n- IOS_IPA_FILE_SIZE: null\n  opts:\n    description: iOS IPA file size, in bytes\n    title: iOS IPA file size\n- IOS_APP_NAME: null\n  opts:\n    description: iOS application name from IPA\n    title: iOS application name\n- IOS_APP_VERSION_NAME: null\n  opts:\n    description: iOS application version name from IPA, ex. 1.0.0\n    title: iOS application version name\n- IOS_APP_VERSION_CODE: null\n  opts:\n    description: iOS application version code from IPA, ex. 10\n    title: iOS application version code\n- IOS_ICON_PATH: null\n  opts:\n    description: File path to iOS application icon\n    title: File path to icon\n- IOS_APP_PROFILE_NAME: null\n  opts:\n    description: iOS application profile name\n    title: iOS application profile name\n"
  },
  {
    "path": "steps/ipa-info/1.0.1/step.yml",
    "content": "title: IPA info\nsummary: IPA iOS info provider\ndescription: Provides all possible iOS IPA information as package name, version name\n  or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-ipa-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-ipa-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-ipa-info/issues\npublished_at: 2016-12-14T18:13:48.89429679+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-ipa-info.git\n  commit: c3dabeb442c18410520baad4301ade8e81666a96\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- \"artifact info\"\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      File path to IPA file to get info from.\n    is_required: true\n    title: IPA file path\noutputs:\n- IOS_IPA_PACKAGE_NAME: null\n  opts:\n    description: iOS application package name, ex. com.package.my\n    title: iOS application package name\n- IOS_IPA_FILE_SIZE: null\n  opts:\n    description: iOS IPA file size, in bytes\n    title: iOS IPA file size\n- IOS_APP_NAME: null\n  opts:\n    description: iOS application name from IPA\n    title: iOS application name\n- IOS_APP_VERSION_NAME: null\n  opts:\n    description: iOS application version name from IPA, ex. 1.0.0\n    title: iOS application version name\n- IOS_APP_VERSION_CODE: null\n  opts:\n    description: iOS application version code from IPA, ex. 10\n    title: iOS application version code\n- IOS_ICON_PATH: null\n  opts:\n    description: File path to iOS application icon\n    title: File path to icon\n- IOS_APP_PROFILE_NAME: null\n  opts:\n    description: iOS application profile name\n    title: iOS application profile name\n"
  },
  {
    "path": "steps/ipa-info/1.1.0/step.yml",
    "content": "title: IPA info\nsummary: IPA iOS info provider\ndescription: Provides all possible iOS IPA information as package name, version name\n  or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-ipa-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-ipa-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-ipa-info/issues\npublished_at: 2018-01-17T12:27:12.106338+01:00\nsource:\n  git: https://github.com/thefuntasty/bitrise-step-ipa-info.git\n  commit: 9131a67b7d0e17bb84f2c537dd2bea1a2afac02e\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      File path to IPA file to get info from.\n    is_required: true\n    title: IPA file path\noutputs:\n- IOS_IPA_PACKAGE_NAME: null\n  opts:\n    description: iOS application package name, ex. com.package.my\n    title: iOS application package name\n- IOS_IPA_FILE_SIZE: null\n  opts:\n    description: iOS IPA file size, in bytes\n    title: iOS IPA file size\n- IOS_APP_NAME: null\n  opts:\n    description: iOS application name from IPA\n    title: iOS application name\n- IOS_APP_DISPLAY_NAME: null\n  opts:\n    description: iOS application display name from IPA's Info.plist\n    title: iOS application display name\n- IOS_APP_VERSION_NAME: null\n  opts:\n    description: iOS application version name from IPA, ex. 1.0.0\n    title: iOS application version name\n- IOS_APP_VERSION_CODE: null\n  opts:\n    description: iOS application version code from IPA, ex. 10\n    title: iOS application version code\n- IOS_ICON_PATH: null\n  opts:\n    description: File path to iOS application icon\n    title: File path to icon\n- IOS_APP_PROFILE_NAME: null\n  opts:\n    description: iOS application profile name\n    title: iOS application profile name\n"
  },
  {
    "path": "steps/ipa-info/1.1.1/step.yml",
    "content": "title: IPA info\nsummary: IPA iOS info provider\ndescription: Provides all possible iOS IPA information as package name, version name\n  or version code.\nwebsite: https://github.com/thefuntasty/bitrise-step-ipa-info\nsource_code_url: https://github.com/thefuntasty/bitrise-step-ipa-info\nsupport_url: https://github.com/thefuntasty/bitrise-step-ipa-info/issues\npublished_at: 2025-12-01T11:34:06.688007+01:00\nsource:\n  git: https://github.com/futuredapp/bitrise-step-ipa-info.git\n  commit: 8031e4f02d88c294f8336e850fca2889a50bb70f\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- artifact-info\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      File path to IPA file to get info from.\n    is_required: true\n    title: IPA file path\noutputs:\n- IOS_IPA_PACKAGE_NAME: null\n  opts:\n    description: iOS application package name, ex. com.package.my\n    title: iOS application package name\n- IOS_IPA_FILE_SIZE: null\n  opts:\n    description: iOS IPA file size, in bytes\n    title: iOS IPA file size\n- IOS_APP_NAME: null\n  opts:\n    description: iOS application name from IPA\n    title: iOS application name\n- IOS_APP_DISPLAY_NAME: null\n  opts:\n    description: iOS application display name from IPA's Info.plist\n    title: iOS application display name\n- IOS_APP_VERSION_NAME: null\n  opts:\n    description: iOS application version name from IPA, ex. 1.0.0\n    title: iOS application version name\n- IOS_APP_VERSION_CODE: null\n  opts:\n    description: iOS application version code from IPA, ex. 10\n    title: iOS application version code\n- IOS_ICON_PATH: null\n  opts:\n    description: File path to iOS application icon\n    title: File path to icon\n- IOS_APP_PROFILE_NAME: null\n  opts:\n    description: iOS application profile name\n    title: iOS application profile name\n"
  },
  {
    "path": "steps/ipa-info/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/jandi-message/0.1.0/step.yml",
    "content": "title: Send a Jandi message\nsummary: Send a [Jandi](http://bit.ly/2FiXoc5) message to a topic.\ndescription: |\n  Send a [Jandi](http://bit.ly/2FiXoc5) message to a topic.\n  You can setup **Incoming WebHook integration**.\n  To register an **Incoming WebHook integration** visit http://bit.ly/31Bxeeh\nwebsite: https://github.com/kimjunil/bitrise-step-jandi-message\nsource_code_url: https://github.com/kimjunil/bitrise-step-jandi-message\nsupport_url: https://github.com/kimjunil/bitrise-step-jandi-message/issues\npublished_at: 2019-06-20T11:01:49.447064+09:00\nsource:\n  git: https://github.com/kimjunil/bitrise-step-jandi-message.git\n  commit: c5432abe0f57a24de5b540ac7eaf0a489af2127d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/kimjunil/bitrise-step-jandi-message\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- jandi_webhook_url: null\n  opts:\n    description: |\n      To register an **Incoming WebHook integration** visit http://bit.ly/31Bxeeh\n    is_required: true\n    is_sensitive: true\n    title: Jandi Webhook URL (Webhook URL is required)\n- message_body: null\n  opts:\n    description: |\n      Text of the message to send.\n      This field is required and will not generate a message if there is no content in this field.\n    is_required: true\n    title: Text of the message to send.\n- message_body_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      You can specify the color value of the attachment area, which is divided into separate areas at the bottom of the body message.\n      Can be any hex color code (eg. #439FE0).\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- attachment_area_title: null\n  opts:\n    description: |\n      Title of the attachment area, displayed in bold by default.\n    title: Title of the attachment area.\n- attachment_area_title_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Title of the attachment area if the build failed\n- attachment_area_description: null\n  opts:\n    description: |\n      Description of the attachment area.\n    title: Description of the attachment area.\n- attachment_area_description_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Description of the attachment area if the build failed\n- attachment_area_image_url: null\n  opts:\n    description: \"If you have an image file attached to that webhook message, you\n      can attach it as a URL. \\nWe will provide a thumbnail of the image corresponding\n      to the URL later with the message.\\n\"\n    title: A URL to an image file that will be displayed as a thumbnail\n- attachment_area_image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n"
  },
  {
    "path": "steps/jandi-message/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/jasmine-runner/0.9.0/step.yml",
    "content": "title: Jasmine Test Runner\nsummary: Runs Jasmine Tests\ndescription: Runs Jasmine Tests\nwebsite: https://github.com/bitrise-community/steps-jasmine-runner\nsource_code_url: https://github.com/bitrise-community/steps-jasmine-runner\nsupport_url: https://github.com/bitrise-community/steps-jasmine-runner/issues\npublished_at: 2017-04-27T18:05:14.038292257+02:00\nsource:\n  git: https://github.com/bitrise-community/steps-jasmine-runner.git\n  commit: 7a15c2cb20443dd0a844e8814315bf6e99347cda\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-jasmine-runner\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: Working directory.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the jasmine command.\n\n      `jasmine [options]`\n    title: Options to append to the jasmine command\n"
  },
  {
    "path": "steps/jasmine-runner/0.9.1/step.yml",
    "content": "title: Jasmine Test Runner\nsummary: Runs Jasmine tests.\ndescription: \"Perform unit testing with our **Jasmine Test Runner** Step. \\nIf your\n  Cordova/Ionic project has Jasmine dependency in its package.json file, the **Jasmine\n  Test Runner** Step will get automatically inserted in your Workflow. \\nIf the dependency\n  is missing from your project, you can manually insert the **Jasmine Test Runner**\n  Step from our StepLib.\\n\\n### Configuring the Step\\n1. Provide your project's working\n  directory in the **Working directory** input.\\n3. Add custom options in `jasmine\n  [options]` in the **Options to append to the jasmine command** input.\\n\\n### Troubleshooting\\nMake\n  sure you insert the **Jasmine Test Runner** Step right after **Run npm command**\n  or **Run yarn command package manager** Step.\\n\\n\\n### Useful links\\n- [Getting\n  started with Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n-\n  [Testing on Bitrise](https://devcenter.bitrise.io/testing/testing-index/)\\n\\n###\n  Related Steps\\n- [Karma Jasmine Test Runner](https://www.bitrise.io/integrations/steps/karma-jasmine-runner)\\n-\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-community/steps-jasmine-runner\nsource_code_url: https://github.com/bitrise-community/steps-jasmine-runner\nsupport_url: https://github.com/bitrise-community/steps-jasmine-runner/issues\npublished_at: 2021-02-10T15:18:41.896891286Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-jasmine-runner.git\n  commit: a92e1d18b9f0ac9f3e6861e39a6d1ff5429a6c3a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-jasmine-runner\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    description: Working directory.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- options: null\n  opts:\n    description: |-\n      Use this input to specify custom options, to append to the end of the jasmine command.\n\n      `jasmine [options]`\n    title: Options to append to the jasmine command\n"
  },
  {
    "path": "steps/jasmine-runner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/jira-comments/0.0.1/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2018-09-04T13:02:24.540780402+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: 339ada3adc9a2ea263856e8131ede51bc5a33cdc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.2/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2018-09-07T11:04:37.807268948+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: 10f6e99a7022ff34dcf082af18bf82e7ee89e80d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.3/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2018-09-07T14:00:35.428893879+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: b6d7cae09e4544b7ec39c8126524804311b5dd7e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.4/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2018-09-10T11:20:32.070663565+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: c091d9cccbcc8f462a842036dab9aa55d8e7fcd3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.5/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2020-08-25T17:13:59.438684+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: 2c700b411dd1a5879cae25c2a49c488af6e847f8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_sensitive: true\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_sensitive: true\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.6/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2020-11-05T17:09:06.73242+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: 40e3d878188d0ac9a181aae88f17616aeb15ebde\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_sensitive: true\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_sensitive: true\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.7/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2021-08-05T17:18:45.841643+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: 024cf135b1e9db111ef90e79a8be573e8283c186\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_sensitive: true\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_sensitive: true\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/0.0.8/step.yml",
    "content": "title: Jira Comments\nsummary: |\n  Creates comments for all tasks from pull request merge commits. It uses the commit message to determine which tasks should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira tasks names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and posts a comment for each found task.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsource_code_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment\nsupport_url: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment/issues\npublished_at: 2023-04-25T00:25:16.990416+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise_step_build_info_jira_comment.git\n  commit: f33edd53dd029eb2cf6afaa63c90735ccbb6efa8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    title: Jira project prefix\n    value_options: []\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_sensitive: true\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_sensitive: true\n    title: Jira user token\n- jira_comment: null\n  opts:\n    description: Comment that will be posted for each found Jira task\n    title: Comment\n"
  },
  {
    "path": "steps/jira-comments/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/jira-issue-field-add-or-update/0.0.2/step.yml",
    "content": "title: Jira Issue Field Add Or Update\nsummary: |\n  Adds or updates field value for all issues from pull request merge commits. It uses the commit message to determine which issues should be commented.\ndescription: |\n  This steps scans last merge commits or last commit if it is not a merge commit, and gathers all Jira issues names found in commit messages.\n  Once the tasks are found it uses the credentials provided to use Jira API and update each found issue field with specified value.\n  Value can be added as an array element or the whole field can be updated.\n\n  The regex pattern to look for Jira tasks is \"<project_prefix>[0-9]{1,5}\"\n\n  This step is using Jira API v2.\nwebsite: https://github.com/maqoo/bitrise-step-jira-issue-field-update\nsource_code_url: https://github.com/maqoo/bitrise-step-jira-issue-field-update\nsupport_url: https://github.com/maqoo/bitrise-step-jira-issue-field-update/issues\npublished_at: 2020-11-09T14:41:49.00993+01:00\nsource:\n  git: https://github.com/maqoo/bitrise-step-jira-issue-field-update.git\n  commit: 461fdf70387fd9a1f87bdf5b0b0233395a11354d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: true\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Jira project prefix to search for tasks.\n\n      e.g. \"PROJ-\"\n    is_expand: true\n    is_required: true\n    summary: Jira project prefix to search for tasks.\n    title: Jira project prefix\n  project_prefix: null\n- backlog_default_url: null\n  opts:\n    description: |\n      Jira company domain.\n\n      e.g. \"example.atlassian.net\"\n    is_expand: true\n    is_required: true\n    summary: Jira company domain\n    title: Jira domain\n- jira_user: null\n  opts:\n    description: |\n      Jira user used to authenticate with Jira API\n\n      e.g. \"someone@example.pl\"\n    is_sensitive: true\n    summary: Jira user used to authenticate with Jira API\n    title: Jira user\n- jira_token: null\n  opts:\n    description: |\n      Jira user token used to authenticate with Jira API\n\n      24 character string\n    is_sensitive: true\n    summary: Jira user token used to authenticate with Jira API\n    title: Jira user token\n- jira_issue_field_name: null\n  opts:\n    description: |\n      The name of the field you want to update. This is the field name NOT field description.\n\n      To find the name of the field you need admin access to \"Screens\" page for your Jira project.\n    is_required: true\n    summary: The name of the field you want to update\n    title: Jira issue field name\n- jira_issue_field_type: single\n  opts:\n    description: |\n      Type of issue field.\n\n      Can be a single value or an array.\n    is_required: true\n    summary: Type of issue field.\n    title: Jira issue field type\n    value_options:\n    - single\n    - array\n- jira_issue_field_value: null\n  opts:\n    description: |\n      Value to update the issue field with.\n\n      If you want to add array of values or replace array with another array, you need to specify values as strings divided by `|` delimeter.\n    is_required: true\n    summary: Value to update the issue field with.\n    title: Jira issue field value to update or add\n- jira_should_array_add_or_set: add\n  opts:\n    description: |\n      If you specify the field type as \"array\", you can append (\"add\") values to the array or you can replace whole array with new values.\n\n      If you want to add array of values or replace array with another array, you need to specify values as strings divided by `|` delimeter.\n    is_required: true\n    summary: If the type is array, you can specify if the values are set or added.\n    title: If field type is array, should add or set values?\n    value_options:\n    - add\n    - set\n"
  },
  {
    "path": "steps/jira-issue-field-add-or-update/step-info.yml",
    "content": "maintainer: community"
  },
  {
    "path": "steps/jira-issue-status-update/0.1.0/step.yml",
    "content": "title: Update JIRA Issue Status\nsummary: Change status of JIRA issues.\ndescription: Automate process of moving issues from 'In Progress' to 'Code Review'\n  or 'In Test'.\nwebsite: https://github.com/MiSikora/bitrise-step-update-jira-issue-status\nsource_code_url: https://github.com/MiSikora/bitrise-step-update-jira-issue-status\nsupport_url: https://github.com/MiSikora/bitrise-step-update-jira-issue-status/issues\npublished_at: 2020-02-09T16:41:09.656336+01:00\nsource:\n  git: https://github.com/MiSikora/bitrise-step-jira-issue-status-update.git\n  commit: 78638095c0de6562b4e8b5e6e11878eec36f7889\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/MiSikora/bitrise-step-update-jira-issue-status\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- base_url: null\n  opts:\n    description: URL of the presonal JIRA software.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: URL of the presonal JIRA software.\n    title: JIRA base URL.\n- opts:\n    description: User name on JIRA (user's email).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User name on JIRA (user's email).\n    title: JIRA user name\n  user_name: null\n- api_token: null\n  opts:\n    description: Api token generated on JIRA.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Api token generated on JIRA.\n    title: JIRA api token\n- issue_keys: null\n  opts:\n    description: JIRA issue keys separatad with `|`\n    is_required: true\n    summary: JIRA issue keys separatad with `|`\n    title: JIRA issue keys\n- opts:\n    description: Status ID in which JIRA issues should be after this step\n    is_required: true\n    summary: Status ID in which JIRA issues should be after this step\n    title: To status\n  to_status_id: null\n"
  },
  {
    "path": "steps/jira-issue-status-update/0.1.2/step.yml",
    "content": "title: Update JIRA Issue Status\nsummary: Change status of JIRA issues.\ndescription: Automate process of moving issues from 'In Progress' to 'Code Review'\n  or 'In Test'.\nwebsite: https://github.com/MiSikora/bitrise-step-jira-issue-status-update\nsource_code_url: https://github.com/MiSikora/bitrise-step-jira-issue-status-update\nsupport_url: https://github.com/MiSikora/bitrise-step-jira-issue-status-update/issues\npublished_at: 2020-02-27T18:29:40.088096+01:00\nsource:\n  git: https://github.com/MiSikora/bitrise-step-jira-issue-status-update.git\n  commit: a3f5802582341759f5e2f4664642dda29beca988\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/MiSikora/bitrise-step-update-jira-issue-status\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- base_url: null\n  opts:\n    description: URL of the presonal JIRA software.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: URL of the presonal JIRA software.\n    title: JIRA base URL.\n- opts:\n    description: User name on JIRA (user's email).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User name on JIRA (user's email).\n    title: JIRA user name\n  user_name: null\n- api_token: null\n  opts:\n    description: Api token generated on JIRA.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Api token generated on JIRA.\n    title: JIRA api token\n- issue_keys: null\n  opts:\n    description: JIRA issue keys separatad with `|`\n    is_expand: true\n    is_required: true\n    summary: JIRA issue keys separatad with `|`\n    title: JIRA issue keys\n- opts:\n    description: Status ID in which JIRA issues should be after this step\n    is_expand: true\n    is_required: true\n    summary: Status ID in which JIRA issues should be after this step\n    title: To status\n  to_status_id: null\n"
  },
  {
    "path": "steps/jira-issue-status-update/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/jira-issue-update-build/0.1.4/step.yml",
    "content": "title: Update JIRA issues with build number\nsummary: Update fields of JIRA issues with build number.\ndescription: \"Update fields of JIRA issues associated with current MR/PR, with the\n  current build number.\\n\\n### How does it work?\\n\\nFirst, the step needs to know\n  tasks associated with the build, so it examines Git history of the merge that it\n  was triggered by. \\nEach merge request can have multiple tasks related to it. So\n  step extracts all the messages of commits involved from the merge commit, \\nand\n  it looks for task keys using a predefined format (for example, [ABCD-1234]). Then\n  using JIRA API, it updates custom fields of these tasks with current build number.\n  \\n\\nAdditionally step can keep ticket history from failed/aborted builds. It uses\n  Bitrise API to gather information about the commits \\nfrom all aborted or failed\n  builds preceding the current one.\\n\\n### Useful links\\n- [About this step](https://www.holdapp.com/blog/bitrise-tests-made-easier-with-jira-build-step)\"\nwebsite: https://github.com/Holdapp/bitrise-step-jira-build\nsource_code_url: https://github.com/Holdapp/bitrise-step-jira-build\nsupport_url: https://github.com/Holdapp/bitrise-step-jira-build/issues\npublished_at: 2021-02-02T17:08:57.274627+01:00\nsource:\n  git: https://github.com/Holdapp/bitrise-step-jira-build.git\n  commit: b24f886c00c324dfb79a921bea68575bc9b9ecc5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ndeps:\n  brew:\n  - name: pkg-config\n  - name: libgit2\n  - name: go\n  apt_get:\n  - name: pkg-config\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: true\ninputs:\n- app_version: null\n  opts:\n    description: \"If you develop an iOS project, you can extract the version number\n      from Info.plist of the main target. It’s called `CFBundleShortVersionString`.\n      \\nAlternatively, you may use a custom step that can do it for you: [bitrise-step-xcode-build-version](https://github.com/nodes-ios/bitrise-step-xcode-build-version)\"\n    is_required: true\n    summary: App version (for example 1.0.0)\n    title: App version\n- jira_host: null\n  opts:\n    is_required: true\n    summary: Your JIRA instance URL (e.g. https://company.atlassian.net)\n    title: JIRA host\n- jira_custom_field_id: null\n  opts:\n    description: \"You can read how to find it [here](https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html).\n      \\nAnd if you don’t have a custom field yet, check out this [guide](https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html)\n      that explains how to create it.\"\n    is_required: true\n    summary: Custom field id for the build number (integer)\n    title: JIRA Custom Field ID\n- jira_username: null\n  opts:\n    is_required: true\n    summary: User (or bot) username\n    title: JIRA username\n- jira_access_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: User (or bot) password or API token (you can generate it [here](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)).\n    title: JIRA access token\n- jira_issue_pattern: ([A-Z]{1,10}-[0-9]+)\n  opts:\n    is_required: true\n    summary: A regular expression for matching issue keys in commit messages. For\n      example, ([A-Z]{1,10}-[0-9]+)\n    title: Regex pattern used to identify issue keys from commit messages\n- bitrise_api_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Access token for bitrise.io API, you can find your API token [here](https://discuss.bitrise.io/t/personal-access-tokens-beta/1383)\n    title: Token for bitrise.io API\n"
  },
  {
    "path": "steps/jira-issue-update-build/0.2.3/step.yml",
    "content": "title: Update JIRA issues with build number\nsummary: Update fields of JIRA issues with build number.\ndescription: \"Update fields of JIRA issues associated with current MR/PR, with the\n  current build number.\\n\\n### How does it work?\\n\\nFirst, the step needs to know\n  tasks associated with the build, so it examines Git history of the merge that it\n  was triggered by. \\nEach merge request can have multiple tasks related to it. So\n  step extracts all the messages of commits involved from the merge commit, \\nand\n  it looks for task keys using a predefined format (for example, [ABCD-1234]). Then\n  using JIRA API, it updates custom fields of these tasks with current build number.\n  \\n\\nAdditionally step can keep ticket history from failed/aborted builds. It uses\n  Bitrise API to gather information about the commits \\nfrom all aborted or failed\n  builds preceding the current one.\\n\\n### Useful links\\n- [About this step](https://www.holdapp.com/blog/bitrise-tests-made-easier-with-jira-build-step)\"\nwebsite: https://github.com/Holdapp/bitrise-step-jira-build\nsource_code_url: https://github.com/Holdapp/bitrise-step-jira-build\nsupport_url: https://github.com/Holdapp/bitrise-step-jira-build/issues\npublished_at: 2022-09-23T14:42:18.502245+02:00\nsource:\n  git: https://github.com/Holdapp/bitrise-step-jira-build.git\n  commit: 63f82b7a95e3b6f20a284ea7b31111e37aa519dc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ndeps:\n  brew:\n  - name: pkg-config\n  - name: go\n  apt_get:\n  - name: pkg-config\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: true\ninputs:\n- app_version: null\n  opts:\n    description: \"If you develop an iOS project, you can extract the version number\n      from Info.plist of the main target. It’s called `CFBundleShortVersionString`.\n      \\nAlternatively, you may use a custom step that can do it for you: [bitrise-step-xcode-build-version](https://github.com/nodes-ios/bitrise-step-xcode-build-version)\"\n    is_required: true\n    summary: App version (for example 1.0.0)\n    title: App version\n- jira_host: null\n  opts:\n    is_required: true\n    summary: Your JIRA instance URL (e.g. https://company.atlassian.net)\n    title: JIRA host\n- jira_custom_field_id: null\n  opts:\n    description: \"You can read how to find it [here](https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html).\n      \\nAnd if you don’t have a custom field yet, check out this [guide](https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html)\n      that explains how to create it.\"\n    is_required: true\n    summary: Custom field id for the build number (integer)\n    title: JIRA Custom Field ID\n- jira_username: null\n  opts:\n    is_required: true\n    summary: User (or bot) username\n    title: JIRA username\n- jira_access_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: User (or bot) password or API token (you can generate it [here](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)).\n    title: JIRA access token\n- jira_issue_pattern: ([A-Z]{1,10}-[0-9]+)\n  opts:\n    is_required: true\n    summary: A regular expression for matching issue keys in commit messages. For\n      example, ([A-Z]{1,10}-[0-9]+)\n    title: Regex pattern used to identify issue keys from commit messages\n- bitrise_api_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Access token for bitrise.io API, you can find your API token [here](https://discuss.bitrise.io/t/personal-access-tokens-beta/1383)\n    title: Token for bitrise.io API\n- opts:\n    is_expand: true\n    is_required: true\n    summary: If false, existing content will be modified, by replacing any previous\n      builds with matching version\n    title: Should overwrite content of custom field\n    value_options:\n    - \"true\"\n    - \"false\"\n  overwrite_field: \"true\"\n"
  },
  {
    "path": "steps/jira-issue-update-build/0.2.4/step.yml",
    "content": "title: Update JIRA issues with build number\nsummary: Update fields of JIRA issues with build number.\ndescription: \"Update fields of JIRA issues associated with current MR/PR, with the\n  current build number.\\n\\n### How does it work?\\n\\nFirst, the step needs to know\n  tasks associated with the build, so it examines Git history of the merge that it\n  was triggered by. \\nEach merge request can have multiple tasks related to it. So\n  step extracts all the messages of commits involved from the merge commit, \\nand\n  it looks for task keys using a predefined format (for example, [ABCD-1234]). Then\n  using JIRA API, it updates custom fields of these tasks with current build number.\n  \\n\\nAdditionally step can keep ticket history from failed/aborted builds. It uses\n  Bitrise API to gather information about the commits \\nfrom all aborted or failed\n  builds preceding the current one.\\n\\n### Useful links\\n- [About this step](https://www.holdapp.com/blog/bitrise-tests-made-easier-with-jira-build-step)\"\nwebsite: https://github.com/Holdapp/bitrise-step-jira-build\nsource_code_url: https://github.com/Holdapp/bitrise-step-jira-build\nsupport_url: https://github.com/Holdapp/bitrise-step-jira-build/issues\npublished_at: 2022-10-19T11:57:38.49501+02:00\nsource:\n  git: https://github.com/Holdapp/bitrise-step-jira-build.git\n  commit: 051233c08277085b6047c96e46a8d87609d2e3be\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ndeps:\n  brew:\n  - name: pkg-config\n  - name: go\n  apt_get:\n  - name: pkg-config\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: true\ninputs:\n- app_version: null\n  opts:\n    description: \"If you develop an iOS project, you can extract the version number\n      from Info.plist of the main target. It’s called `CFBundleShortVersionString`.\n      \\nAlternatively, you may use a custom step that can do it for you: [bitrise-step-xcode-build-version](https://github.com/nodes-ios/bitrise-step-xcode-build-version)\"\n    is_required: true\n    summary: App version (for example 1.0.0)\n    title: App version\n- jira_host: null\n  opts:\n    is_required: true\n    summary: Your JIRA instance URL (e.g. https://company.atlassian.net)\n    title: JIRA host\n- jira_custom_field_id: null\n  opts:\n    description: \"You can read how to find it [here](https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html).\n      \\nAnd if you don’t have a custom field yet, check out this [guide](https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html)\n      that explains how to create it.\"\n    is_required: true\n    summary: Custom field id for the build number (integer)\n    title: JIRA Custom Field ID\n- jira_username: null\n  opts:\n    is_required: true\n    summary: User (or bot) username\n    title: JIRA username\n- jira_access_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: User (or bot) password or API token (you can generate it [here](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)).\n    title: JIRA access token\n- jira_issue_pattern: ([A-Z]{1,10}-[0-9]+)\n  opts:\n    is_required: true\n    summary: A regular expression for matching issue keys in commit messages. For\n      example, ([A-Z]{1,10}-[0-9]+)\n    title: Regex pattern used to identify issue keys from commit messages\n- bitrise_api_token: null\n  opts:\n    is_required: false\n    is_sensitive: true\n    summary: Access token for bitrise.io API, you can find your API token [here](https://discuss.bitrise.io/t/personal-access-tokens-beta/1383)\n    title: Token for bitrise.io API\n- opts:\n    is_expand: true\n    is_required: true\n    summary: If false, existing content will be modified, by replacing any previous\n      builds with matching version\n    title: Should overwrite content of custom field\n    value_options:\n    - \"true\"\n    - \"false\"\n  overwrite_field: \"true\"\n"
  },
  {
    "path": "steps/jira-issue-update-build/0.2.5/step.yml",
    "content": "title: Update JIRA issues with build number\nsummary: Update fields of JIRA issues with build number.\ndescription: \"Update fields of JIRA issues associated with current MR/PR, with the\n  current build number.\\n\\n### How does it work?\\n\\nFirst, the step needs to know\n  tasks associated with the build, so it examines Git history of the merge that it\n  was triggered by. \\nEach merge request can have multiple tasks related to it. So\n  step extracts all the messages of commits involved from the merge commit, \\nand\n  it looks for task keys using a predefined format (for example, [ABCD-1234]). Then\n  using JIRA API, it updates custom fields of these tasks with current build number.\n  \\n\\nAdditionally step can keep ticket history from failed/aborted builds. It uses\n  Bitrise API to gather information about the commits \\nfrom all aborted or failed\n  builds preceding the current one.\\n\\nThe step does not clone git repository by itself,\n  instead it is using the one located at `$BITRISE_SOURCE_DIR`. \\nMake sure repository\n  is cloned before using it ([guide](https://devcenter.bitrise.io/en/steps-and-workflows/generic-workflow-recipes/cloning-a-git-repository.html)).\\n\\n###\n  Useful links\\n- [About this step](https://www.holdapp.com/blog/bitrise-tests-made-easier-with-jira-build-step)\"\nwebsite: https://github.com/Holdapp/bitrise-step-jira-build\nsource_code_url: https://github.com/Holdapp/bitrise-step-jira-build\nsupport_url: https://github.com/Holdapp/bitrise-step-jira-build/issues\npublished_at: 2022-11-29T11:33:52.04197+01:00\nsource:\n  git: https://github.com/Holdapp/bitrise-step-jira-build.git\n  commit: a35a437e687635007493e37892eee6f72d1083dc\ntype_tags:\n- notification\ndeps:\n  brew:\n  - name: pkg-config\n  apt_get:\n  - name: pkg-config\nis_always_run: false\nis_skippable: true\ninputs:\n- app_version: null\n  opts:\n    description: \"If you develop an iOS project, you can extract the version number\n      from Info.plist of the main target. It’s called `CFBundleShortVersionString`.\n      \\nAlternatively, you may use a custom step that can do it for you: [bitrise-step-xcode-build-version](https://github.com/nodes-ios/bitrise-step-xcode-build-version)\"\n    is_required: true\n    summary: App version (for example 1.0.0)\n    title: App version\n- jira_host: null\n  opts:\n    is_required: true\n    summary: Your JIRA instance URL (e.g. https://company.atlassian.net)\n    title: JIRA host\n- jira_custom_field_id: null\n  opts:\n    description: \"You can read how to find it [here](https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html).\n      \\nAnd if you don’t have a custom field yet, check out this [guide](https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html)\n      that explains how to create it.\"\n    is_required: true\n    summary: Custom field id for the build number (integer)\n    title: JIRA Custom Field ID\n- jira_username: null\n  opts:\n    is_required: true\n    summary: User (or bot) username\n    title: JIRA username\n- jira_access_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: User (or bot) password or API token (you can generate it [here](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)).\n    title: JIRA access token\n- jira_issue_pattern: ([A-Z]{1,10}-[0-9]+)\n  opts:\n    is_required: true\n    summary: A regular expression for matching issue keys in commit messages. For\n      example, ([A-Z]{1,10}-[0-9]+)\n    title: Regex pattern used to identify issue keys from commit messages\n- bitrise_api_token: null\n  opts:\n    is_required: false\n    is_sensitive: true\n    summary: Access token for bitrise.io API, you can find your API token [here](https://discuss.bitrise.io/t/personal-access-tokens-beta/1383)\n    title: Token for bitrise.io API\n- opts:\n    is_expand: true\n    is_required: true\n    summary: If true, existing field content will be overridden. If false, a new version\n      will try to replace the old version in the currently set field content\n    title: Should overwrite content of custom field\n    value_options:\n    - \"true\"\n    - \"false\"\n  overwrite_field: \"true\"\n"
  },
  {
    "path": "steps/jira-issue-update-build/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/karma-jasmine-runner/0.9.0/step.yml",
    "content": "title: Karma Jasmine Test Runner\nsummary: Karma Jasmine Test Runner\ndescription: Karma Jasmine Test Runner\nwebsite: https://github.com/bitrise-community/steps-karma-jasmine-runner\nsource_code_url: https://github.com/bitrise-community/steps-karma-jasmine-runner\nsupport_url: https://github.com/bitrise-community/steps-karma-jasmine-runner/issues\npublished_at: 2017-04-27T17:15:00.375064985+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-karma-jasmine-runner.git\n  commit: 6853e7fba38826e968bf650bb88aedf44046db77\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-karma-jasmine-runner\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- browsers: Safary\n  opts:\n    description: |-\n      Use this input to specify which browser to use by karma start command.\n      Comma separated list of browsers (eg. `Safari,Chrome,Firefox`).\n    is_required: true\n    title: List of browsers to start\n- options: null\n  opts:\n    description: Use this input to specify custom options, to append to the end of\n      the karma start command.\n    title: Options to append to the karma start command\n"
  },
  {
    "path": "steps/karma-jasmine-runner/0.9.1/step.yml",
    "content": "title: Karma Jasmine Test Runner\nsummary: Karma Jasmine Test Runner\ndescription: Karma Jasmine Test Runner\nwebsite: https://github.com/bitrise-community/steps-karma-jasmine-runner\nsource_code_url: https://github.com/bitrise-community/steps-karma-jasmine-runner\nsupport_url: https://github.com/bitrise-community/steps-karma-jasmine-runner/issues\npublished_at: 2017-04-28T15:30:49.260119785+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-karma-jasmine-runner.git\n  commit: 15e8e7bd55624d70041334c05766e220446c060c\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-karma-jasmine-runner\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- browsers: Safari\n  opts:\n    description: |-\n      Use this input to specify which browser to use by karma start command.\n      Comma separated list of browsers (eg. `Safari,Chrome,Firefox`).\n    is_required: true\n    title: List of browsers to start\n- options: null\n  opts:\n    description: Use this input to specify custom options, to append to the end of\n      the karma start command.\n    title: Options to append to the karma start command\n"
  },
  {
    "path": "steps/karma-jasmine-runner/0.9.2/step.yml",
    "content": "title: Karma Jasmine Test Runner\nsummary: Run your Jasmine tests with the Karma tool on Bitrise.\ndescription: \"The Step allows you to run Jasmine tests using the Karma tool in your\n  build. Karma lets you spawn different browsers and re-run the tests within each\n  browser. \\n\\n### Configuring the Step \\n\\nThe Step runs the `karma start` command\n  to run your Jasmine tests. To set this up:\\n\\n1. Choose the browsers in which you\n  want to run tests. Separate each browser with a comma. \\n1. In the **Options to\n  append to the karma start command**, add custom options to the `karma start` command.\n  For the available options, run `karma start --help` in a command line. \\n\\n### Useful\n  links \\n\\n[Testing on Bitrise](devcenter.bitrise.io/testing/)\\n\\n### Related Steps\n  \\n\\n[Jasmine Test Runner](https://www.bitrise.io/integrations/steps/jasmine-runner)\"\nwebsite: https://github.com/bitrise-community/steps-karma-jasmine-runner\nsource_code_url: https://github.com/bitrise-community/steps-karma-jasmine-runner\nsupport_url: https://github.com/bitrise-community/steps-karma-jasmine-runner/issues\npublished_at: 2021-03-17T15:25:34.634029494Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-karma-jasmine-runner.git\n  commit: 93ff7ea9a0a78b99df08f0040ce36c99fa70b122\nproject_type_tags:\n- cordova\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-community/steps-karma-jasmine-runner\ndeps:\n  brew:\n  - name: go\ninputs:\n- opts:\n    is_required: true\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- browsers: Safari\n  opts:\n    description: |-\n      Use this input to specify which browser to use by karma start command.\n      Comma separated list of browsers (eg. `Safari,Chrome,Firefox`).\n    is_required: true\n    title: List of browsers to start\n- options: null\n  opts:\n    description: Use this input to specify custom options, to append to the end of\n      the karma start command.\n    title: Options to append to the karma start command\n"
  },
  {
    "path": "steps/karma-jasmine-runner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/kobiton-app-upload/1.0.0/step.yml",
    "content": "title: Upload application to Kobiton\nsummary: |\n  Uploads an application to Kobiton App Repo\ndescription: |\n  This step will take an .apk or .ipa file and upload it to the Kobiton App Repository. You can find your API key at [Kobiton](https://portal.kobiton.com/settings/keys)\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo/issues\npublished_at: 2021-12-06T11:33:55.037205+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo.git\n  commit: 40b4eb88a03863221445abf852429e0bd024a879\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: ack\n  apt_get:\n  - name: curl\n  - name: ack\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobiton_app_name: $BITRISE_APP_TITLE\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Title of the app beign built\n    title: App Name\n- kobiton_app_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk or .ipa file\n    title: App Path\n- kobiton_app_id:\n  opts:\n    is_expand: true\n    is_required: false\n    summary: App ID in Kobiton - use this in case you want to upload new version of\n      an existing app in Kobiton\n    title: App ID\n- kobiton_app_type: apk\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Select ipa for iOS app or apk for Android app\n    title: App Type\n    value_options:\n    - \"apk\"\n    - \"ipa\"\n- kobiton_app_access: public\n  opts:\n    summary: You can either to make this app private or available for everyone in\n      the organization\n    title: App Privacy\n    value_options:\n    - \"public\"\n    - \"private\"\n- kobiton_username:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The user to upload to Kobiton\n    title: Kobiton Username\n- kobiton_api_key:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API key to access Kobiton API\n    title: Kobiton API Key/Secret\noutputs:\n- KOBITON_APP_ID:\n  opts:\n    description: |\n      The App ID that the app has been uploaded to Kobiton Repo.\n    summary: Kobiton App ID\n    title: App ID\n- KOBITON_UPLOAD_URL:\n  opts:\n    description: |\n      The URL the app has been uploaded to.\n    summary: Amazon S3 Upload URL\n    title: Upload URL\n- KOBITON_APP_PATH:\n  opts:\n    description: |\n      Path to the app binary on Kobiton\n    summary: Path to the app binary on Kobiton\n    title: App Path\n"
  },
  {
    "path": "steps/kobiton-app-upload/1.0.1/step.yml",
    "content": "title: Upload application to Kobiton\nsummary: |\n  Uploads an application to Kobiton App Repo\ndescription: |\n  This step will take an .apk or .ipa file and upload it to the Kobiton App Repository. You can find your API key at [Kobiton](https://portal.kobiton.com/settings/keys)\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo/issues\npublished_at: 2021-12-09T14:03:01.283014+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo.git\n  commit: d69b2a45f0560174fac348f47fe6254d62a6ff90\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: ack\n  apt_get:\n  - name: curl\n  - name: ack\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobiton_app_name: $BITRISE_APP_TITLE\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Title of the app beign built\n    title: App Name\n- kobiton_app_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk or .ipa file\n    title: App Path\n- kobiton_app_id:\n  opts:\n    is_expand: true\n    is_required: false\n    summary: App ID in Kobiton - use this in case you want to upload new version of\n      an existing app in Kobiton\n    title: App ID\n- kobiton_app_type: apk\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Select ipa for iOS app or apk for Android app\n    title: App Type\n    value_options:\n    - \"apk\"\n    - \"ipa\"\n- kobiton_app_access: public\n  opts:\n    summary: You can either to make this app private or available for everyone in\n      the organization\n    title: App Privacy\n    value_options:\n    - \"public\"\n    - \"private\"\n- kobiton_username:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The user to upload to Kobiton\n    title: Kobiton Username\n- kobiton_api_key:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API key to access Kobiton API\n    title: Kobiton API Key/Secret\noutputs:\n- KOBITON_APP_ID:\n  opts:\n    description: |\n      The App ID that the app has been uploaded to Kobiton Repo.\n    summary: Kobiton App ID\n    title: App ID\n- KOBITON_UPLOAD_URL:\n  opts:\n    description: |\n      The URL the app has been uploaded to.\n    summary: Amazon S3 Upload URL\n    title: Upload URL\n- KOBITON_APP_PATH:\n  opts:\n    description: |\n      Path to the app binary on Kobiton\n    summary: Path to the app binary on Kobiton\n    title: App Path"
  },
  {
    "path": "steps/kobiton-app-upload/1.0.2/step.yml",
    "content": "title: Upload application to Kobiton\nsummary: |\n  Uploads an application to Kobiton App Repo\ndescription: |\n  This step will take an .apk or .ipa file and upload it to the Kobiton App Repository. You can find your API key at [Kobiton](https://portal.kobiton.com/settings/keys)\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo/issues\npublished_at: 2022-01-06T10:35:05.69699+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo.git\n  commit: 6430e0fa5b3aab680aee3f3158b165f7c8b2b0c6\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: ack\n  apt_get:\n  - name: curl\n  - name: ack\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobiton_app_name: $BITRISE_APP_TITLE\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Title of the app being built\n    title: App Name\n- kobiton_app_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk or .ipa file\n    title: App Path\n- kobiton_app_id:\n  opts:\n    is_expand: true\n    is_required: false\n    summary: App ID in Kobiton - use this in case you want to upload new version of\n      an existing app in Kobiton\n    title: App ID\n- kobiton_app_type: apk\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Select ipa for iOS app or apk for Android app\n    title: App Type\n    value_options:\n    - \"apk\"\n    - \"ipa\"\n- kobiton_app_access: public\n  opts:\n    summary: You can either to make this app private or available for everyone in\n      the organization\n    title: App Privacy\n    value_options:\n    - \"public\"\n    - \"private\"\n- kobiton_username:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The user to upload to Kobiton\n    title: Kobiton Username\n- kobiton_api_key:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API key to access Kobiton API\n    title: Kobiton API Key/Secret\noutputs:\n- KOBITON_APP_ID:\n  opts:\n    description: |\n      The App ID that the app has been uploaded to Kobiton Repo.\n    summary: Kobiton App ID\n    title: App ID\n- KOBITON_UPLOAD_URL:\n  opts:\n    description: |\n      The URL the app has been uploaded to.\n    summary: Amazon S3 Upload URL\n    title: Upload URL\n- KOBITON_APP_PATH:\n  opts:\n    description: |\n      Path to the app binary on Kobiton\n    summary: Path to the app binary on Kobiton\n    title: App Path\n    "
  },
  {
    "path": "steps/kobiton-app-upload/1.0.3/step.yml",
    "content": "title: Upload application to Kobiton\nsummary: |\n  Uploads your application to the Kobiton Platform for seamless interactive app testing\ndescription: |\n  This step will take an .apk or .ipa file and upload it to the Kobiton App Repository. You can find your API key at [Kobiton](https://portal.kobiton.com/settings/keys)\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo/issues\npublished_at: 2023-10-02T15:46:42.395256+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-upload-apps-repo.git\n  commit: f5dc9fcd4520c95a834e5081abf40a20d24c161d\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: ack\n  apt_get:\n  - name: curl\n  - name: ack\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobiton_app_name: $BITRISE_APP_TITLE\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Title of the app being built\n    title: App Name\n- kobiton_app_path: $BITRISE_SIGNED_APK_PATH\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk or .ipa file\n    title: App Path\n- kobiton_app_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: App ID in Kobiton - use this in case you want to upload new version of\n      an existing app in Kobiton\n    title: App ID\n- kobiton_app_type: apk\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Select ipa for iOS app or apk for Android app\n    title: App Type\n    value_options:\n    - apk\n    - ipa\n- kobiton_app_access: public\n  opts:\n    summary: You can either to make this app private or available for everyone in\n      the organization\n    title: App Privacy\n    value_options:\n    - public\n    - private\n- kobiton_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The user to upload to Kobiton\n    title: Kobiton Username\n- kobiton_api_key: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API key to access Kobiton API\n    title: Kobiton API Key/Secret\noutputs:\n- KOBITON_APP_ID: null\n  opts:\n    description: |\n      The App ID that the app has been uploaded to Kobiton Repo.\n    summary: Kobiton App ID\n    title: App ID\n- KOBITON_UPLOAD_URL: null\n  opts:\n    description: |\n      The URL the app has been uploaded to.\n    summary: Amazon S3 Upload URL\n    title: Upload URL\n- KOBITON_APP_PATH: null\n  opts:\n    description: |\n      Path to the app binary on Kobiton\n    summary: Path to the app binary on Kobiton\n    title: App Path\n"
  },
  {
    "path": "steps/kobiton-app-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/kobiton-execute-test/1.0.0/step.yml",
    "content": "title: Execute Automation Test in Kobiton\nsummary: |\n  Execute an automation test script\ndescription: |\n  A Bitrise step to (synchronously) execute an automated test script on Kobiton service\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-execute-test\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-execute-test/issues\npublished_at: 2021-12-15T13:12:54.382493+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-execute-test.git\n  commit: 490c780611cd02325c5c95f943ae6114129754b5\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/kobiton/bitrise-step-kobiton-execute-test\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobi_username_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Your username in Kobiton.\n    title: Kobiton Username\n- kobi_apikey_input:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API key in Kobiton.\n    title: Kobiton API Key\n- executor_url_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Kobiton Automation Test Executor URL.\n    title: Executor Server URL\n- executor_username_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The Username for Kobiton Automation Test Executor.\n    title: Kobiton Executor Username\n- executor_password_input:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Password Kobiton Automation Test Executor.\n    title: Kobiton Executor Password\n- git_repo_url_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Link to your Git repository.\n    title: Git repository URL\n- git_repo_branch_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The branch of your Git repository you want to execute automation test\n      with.\n    title: Git repository branch\n- git_repo_ssh_key_input:\n  opts:\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: This is required if your Git Repository is private.\n    title: Git repository SSH key\n- app_id_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The App ID or App URL to use in your test script.\n    title: App ID\n- use_custom_device_input: \"false\"\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: Check if you want to execute one or some test cases with a specific Kobiton\n      Cloud Device. If you already set your device information in your test script,\n      leave this field unchecked.\n    title: Use Custom Device\n    value_options:\n    - \"true\"\n    - \"false\"\n- device_name_input:\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_DEVICE_NAME` environment\n      variable in your test script.\n    title: Kobiton Cloud Device Name\n- device_platform_version_input:\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_SESSION_PLATFORM_VERSION`\n      environment variable in your test script.\n    title: Device platform version\n- device_platform_input: android\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_DEVICE_PLATFORM_NAME` environment\n      variable in your test script.\n    title: Device platform\n    value_options:\n    - \"android\"\n    - \"ios\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Input the root directory of your Git repository.\n    title: Root directory\n  root_directory_input: /\n- command_input: mvn test\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Command lines to install dependencies and execute your automation test\n      script. These commands will run from the root directory of your Git repository.\n    title: Commands\n- wait_for_execution_input: \"true\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Check if your want the release pipeline to wait until your automation\n      testing is completed or failed, then print out the console log and test result.\n    title: Wait for execution\n    value_options:\n    - \"true\"\n    - \"false\"\n  \n- log_type_input: combined\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Your desired log type to be showed. Choose Combined to show logs in chronological\n      order, or Separated for single type of log (Ouput or Error).\n    title: Log type\n    value_options:\n    - \"combined\"\n    - \"output\"\n    - \"error\"\noutputs:\n- JOB_ID:\n  opts:\n    summary: The Job ID that runs the job in Kobiton Executor Server.\n    title: Executor Job ID\n- REPORT_URL:\n  opts:\n    summary: The link to access TestNG Report in Kobiton Executor Server.\n    title: TestNG Report URL\n"
  },
  {
    "path": "steps/kobiton-execute-test/1.0.1/step.yml",
    "content": "title: Execute Automation Test in Kobiton\nsummary: |\n  Execute an automation test script\ndescription: |\n  A Bitrise step to (synchronously) execute an automated test script on Kobiton service\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-execute-test\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-execute-test/issues\npublished_at: 2022-03-08T13:35:34.197337+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-execute-test.git\n  commit: f4cd236781a361610745e37cc2ac49291888abe1\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/kobiton/bitrise-step-kobiton-execute-test\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobi_username_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Your username in Kobiton.\n    title: Kobiton Username\n- kobi_apikey_input:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API key in Kobiton.\n    title: Kobiton API Key\n- executor_url_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Kobiton Automation Test Executor URL.\n    title: Executor Server URL\n- executor_username_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The Username for Kobiton Automation Test Executor.\n    title: Kobiton Executor Username\n- executor_password_input:\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Password Kobiton Automation Test Executor.\n    title: Kobiton Executor Password\n- git_repo_url_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Link to your Git repository.\n    title: Git repository URL\n- git_repo_branch_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The branch of your Git repository you want to execute automation test\n      with.\n    title: Git repository branch\n- git_repo_ssh_key_input:\n  opts:\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: This is required if your Git Repository is private.\n    title: Git repository SSH key\n- app_id_input:\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The App ID or App URL to use in your test script.\n    title: App ID\n- use_custom_device_input: \"false\"\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: Check if you want to execute one or some test cases with a specific Kobiton\n      Cloud Device. If you already set your device information in your test script,\n      leave this field unchecked.\n    title: Use Custom Device\n    value_options:\n    - \"true\"\n    - \"false\"\n- device_name_input:\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_DEVICE_NAME` environment\n      variable in your test script.\n    title: Kobiton Cloud Device Name\n- device_platform_version_input:\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_SESSION_PLATFORM_VERSION`\n      environment variable in your test script.\n    title: Device platform version\n- device_platform_input: android\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_DEVICE_PLATFORM_NAME` environment\n      variable in your test script.\n    title: Device platform\n    value_options:\n    - \"android\"\n    - \"ios\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Input the root directory of your Git repository.\n    title: Root directory\n  root_directory_input: /\n- command_input: mvn test\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Command lines to install dependencies and execute your automation test\n      script. These commands will run from the root directory of your Git repository.\n    title: Commands\n- wait_for_execution_input: \"true\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Check if your want the release pipeline to wait until your automation\n      testing is completed or failed, then print out the console log and test result.\n    title: Wait for execution\n    value_options:\n    - \"true\"\n    - \"false\"\n  \n- log_type_input: combined\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Your desired log type to be showed. Choose Combined to show logs in chronological\n      order, or Separated for single type of log (Ouput or Error).\n    title: Log type\n    value_options:\n    - \"combined\"\n    - \"output\"\n    - \"error\"\noutputs:\n- JOB_ID:\n  opts:\n    summary: The Job ID that runs the job in Kobiton Executor Server.\n    title: Executor Job ID\n- REPORT_URL:\n  opts:\n    summary: The link to access TestNG Report in Kobiton Executor Server.\n    title: TestNG Report URL\n"
  },
  {
    "path": "steps/kobiton-execute-test/2.0.0/step.yml",
    "content": "title: Execute Automation Test on Kobiton\nsummary: |\n  Executes automation tests on the Kobiton Platform and seamlessly triggers Scriptless Automation across multiple devices, harnessing the power of AI without the need for additional scripting\ndescription: |\n  A Bitrise step to (synchronously) execute an automated test script on Kobiton service\nwebsite: https://kobiton.com\nsource_code_url: https://github.com/kobiton/bitrise-step-kobiton-execute-test\nsupport_url: https://github.com/kobiton/bitrise-step-kobiton-execute-test/issues\npublished_at: 2023-10-02T15:43:45.238325+07:00\nsource:\n  git: https://github.com/kobiton/bitrise-step-kobiton-execute-test.git\n  commit: e8efdd6d9abb4b5976baca2f4287b366416d47cc\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/kobiton/bitrise-step-kobiton-execute-test\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- kobi_username_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Your username in Kobiton.\n    title: Kobiton Username\n- kobi_apikey_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API key in Kobiton.\n    title: Kobiton API Key\n- executor_url_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Kobiton Automation Test Executor URL.\n    title: Executor Server URL\n- executor_username_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The Username for Kobiton Automation Test Executor.\n    title: Kobiton Executor Username\n- executor_password_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Password Kobiton Automation Test Executor.\n    title: Kobiton Executor Password\n- git_repo_url_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Link to your Git repository.\n    title: Git repository URL\n- git_repo_branch_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The branch of your Git repository you want to execute automation test\n      with.\n    title: Git repository branch\n- git_repo_ssh_key_input: null\n  opts:\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: This is required if your Git Repository is private.\n    title: Git repository SSH key\n- app_input: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: The App Path or App URL to use in your test script.\n    title: App\n- opts:\n    category: Custom device\n    is_expand: true\n    summary: Check if you want to execute one or some test cases with a specific Kobiton\n      Cloud Device. If you already set your device information in your test script,\n      leave this field unchecked.\n    title: Use Custom Device\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_custom_device_input: \"false\"\n- device_name_input: null\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_DEVICE_NAME` environment\n      variable in your test script.\n    title: Kobiton Cloud Device Name\n- device_platform_version_input: null\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_SESSION_PLATFORM_VERSION`\n      environment variable in your test script.\n    title: Device platform version\n- device_platform_input: android\n  opts:\n    category: Custom device\n    is_expand: true\n    summary: This value will be consumed by the `KOBITON_DEVICE_PLATFORM_NAME` environment\n      variable in your test script.\n    title: Device platform\n    value_options:\n    - android\n    - ios\n- opts:\n    category: Scriptless Automation\n    is_expand: true\n    summary: Check whether you wish to initiate Scriptless execution of your test\n      case across multiple devices by specifying a particular device bundle.\n    title: Trigger Scriptless on multiple devices\n    value_options:\n    - \"true\"\n    - \"false\"\n  scriptless_automation: \"false\"\n- device_bundle: null\n  opts:\n    category: Scriptless Automation\n    is_expand: true\n    summary: Specify the Kobiton Device Bundle ID.\n    title: Kobiton Device Bundle\n- opts:\n    category: Scriptless Automation\n    is_expand: true\n    summary: Specify the Kobiton Timeout in seconds.\n    title: Kobiton Scriptless Timeout\n  scriptless_timeout: null\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Input the root directory of your Git repository.\n    title: Root directory\n  root_directory_input: /\n- command_input: mvn test\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Command lines to install dependencies and execute your automation test\n      script. These commands will run from the root directory of your Git repository.\n    title: Commands\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Check if your want the release pipeline to wait until your automation\n      testing is completed or failed, then print out the console log and test result.\n    title: Wait for execution\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_execution_input: \"true\"\n- log_type_input: combined\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Your desired log type to be showed. Choose Combined to show logs in chronological\n      order, or Separated for single type of log (Ouput or Error).\n    title: Log type\n    value_options:\n    - combined\n    - output\n    - error\noutputs:\n- JOB_ID: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Executor Job ID\n- REPORT_URL: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: TestNG Report URL\n- SCRIPTLESS_AUTOMATION_PASSED: null\n  opts:\n    description: |\n      Description of this output.\n\n      Can be Markdown formatted text.\n    summary: Summary. No more than 2-3 sentences.\n    title: Scriptless automation testing is passed or not\n"
  },
  {
    "path": "steps/kobiton-execute-test/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/kotlin-script/1.0.2/step.yml",
    "content": "title: Kotlin Script\nsummary: |\n  Step to execute a kotlin script\ndescription: |\n  Step to execute a kotlin script\nwebsite: https://github.com/jakob-grabner/bitrise-step-kotlin-script\nsource_code_url: https://github.com/jakob-grabner/bitrise-step-kotlin-script\nsupport_url: https://github.com/jakob-grabner/bitrise-step-kotlin-script/issues\npublished_at: 2023-12-19T10:48:46.074443+01:00\nsource:\n  git: https://github.com/jakob-grabner/bitrise-step-kotlin-script.git\n  commit: c01edc21378f029dcd2e11fa98c604b74397dd44\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- kotlin_content: |\n    println(\"Hello World!\")\n  opts:\n    description: The Kotlin script to run\n    is_expand: false\n    is_required: true\n    summary: The Kotlin script to run\n    title: The Kotlin script\n- opts:\n    description: |\n      Specify a directory - this will be set as the\n      current working directory for the script\n    is_required: false\n    summary: |\n      Specify a directory - this will be set as the\n      current working directory for the script\n    title: Run in directory\n  working_dir: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/kotlin-script/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/lambdatest-espresso-app-automate/1.0.0/step.yml",
    "content": "title: LambdaTest App Automate - Espresso\nsummary: |\n  Upload an app apk and an Espresso test apk to LambdaTest and run tests with App Automate. For more information, please check out this [document](https://www.lambdatest.com/support/docs/getting-started-with-espresso-testing/)\ndescription: |\n  This step uploads a provided app apk and test apk to LambdaTest. It then will execute the Espresso Tests for the provided apks in LambdaTest's app automate.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-espresso-app-automate\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-espresso-app-automate\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-espresso-app-automate/issues\npublished_at: 2022-07-28T11:31:05.022295+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-espresso-app-automate.git\n  commit: 8c691c312b226e097fee68e40aeab72ab8bec57f\nproject_type_tags:\n- android\n- xamarin\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  - name: sed\n  apt_get:\n  - name: curl\n  - name: jq\n  - name: sed\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: null\n  opts:\n    description: |\n      The .apk file for your app.\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app.\n    is_expand: true\n    is_required: true\n    summary: Path to the test .apk file\n    title: Test suite apk path\n  test_apk_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to run your automation tests. Your access key can be found on the Automation Dashboard by clicking [here](https://appautomation.lambdatest.com/build).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- lambdatest_device_list: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Provide a comma separated list of Device and OS version you want to run your tests on, with quotes. Acceptable format example: \"Galaxy S10-9\", \"OnePlus 6T-10\".\n      A list of available device and OS combinations can be found [here](https://www.lambdatest.com/capabilities-generator/).\n    is_expand: true\n    is_required: true\n    summary: A comma separated list of desired test devices\n    title: Device list\n- lambdatest_build_name: null\n  opts:\n    category: Automated Test Options\n    description: |\n      The name of your build.\n    is_required: false\n    summary: Your build name\n    title: Build Name\n- lambdatest_queue_timeout: 600\n  opts:\n    category: Automated Test Options\n    description: |\n      The time in seconds after which you want your build to timeout from queue. The default value of Queue Timeout is 600 seconds.\n    is_required: false\n    summary: The time in seconds after which you want your build to timeout from queue\n    title: Queue Timeout\n- lambdatest_idle_timeout: 120\n  opts:\n    category: Automated Test Options\n    description: |\n      The maximum time in seconds during which the device will stay idle without any commands being executed. The default value of Idle Timeout is 120 seconds.\n    is_required: false\n    summary: The maximum time in seconds during which the device will stay idle without\n      any commands being executed\n    title: Idle Timeout\n- lambdatest_tunnel: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter if you want to enable local testing. By default\n      it's set to false.\n    is_required: false\n    summary: Set this parameter if you want to enable local testing\n    title: Tunnel\n    value_options:\n    - \"true\"\n    - \"false\"\n- lambdatest_tunnel_name: null\n  opts:\n    category: Automated Test Options\n    description: Name of the tunnel .\n    is_required: false\n    summary: Your Tunnel Name\n    title: Tunnel Name\n- lambdatest_device_logs: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter to true if you want to enable the device logs.\n      By default it's set to false.\n    is_required: false\n    summary: Set this parameter to true if you want to enable the device logs\n    title: Device Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- lambdatest_network_logs: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter to true if you want to enable the network logs.\n      By default it's set to false.\n    is_required: false\n    summary: Set this parameter to true if you want to enable the network logs\n    title: Network Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- lambdatest_video: \"true\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter to true if you want to enable the video of the\n      test run. By default it's set to true.\n    is_required: false\n    summary: Set this parameter to true if you want to enable the video of the test\n      run\n    title: Video\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- LAMBDATEST_BUILD_ID: null\n  opts:\n    summary: The Build ID for this test run in LambdaTest\n    title: Build ID\n"
  },
  {
    "path": "steps/lambdatest-espresso-app-automate/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/lambdatest-upload/1.0.0/step.yml",
    "content": "title: LambdaTest Upload\nsummary: |\n  Upload APK/IPA files to LambdaTest's App Automate\ndescription: |\n  Upload your build files to LambdaTest for remote device testing. Upload your IPA/APK file to LambdaTest App Automation and get back the app's url for your remote device tests\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload/issues\npublished_at: 2022-04-01T11:46:49.57948+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-upload.git\n  commit: 150c91cc2a8daaf2741c912e2f70ab29ef4ec21d\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  - name: ack\n  apt_get:\n  - name: curl\n  - name: jq\n  - name: ack\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- upload_path:\n  opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to LambdaTest, usually `$BITRISE\\_APK\\_PATH`\n      or `$BITRISE\\_IPA\\_PATH`\n    title: A Bitrise generated APK or IPA path\n- lambdatest_username:\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key:\n  opts:\n    description: |\n      The access key you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- custom_id:\n  opts:\n    summary: Custom Id to run your automation on the same app instead of remembering app_url\n    title: Custom Id\noutputs:\n- LAMBDATEST_APP_URL:\n  opts:\n    description: \"The app url returned by LambdaTest App Automate with the following\n      format \\\"lt://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: LambdaTest App Automate App URL\n"
  },
  {
    "path": "steps/lambdatest-upload/2.0.0/step.yml",
    "content": "title: LambdaTest Upload\nsummary: |\n  Upload APK/IPA files to LambdaTest's App Automate\ndescription: |\n  Upload your build files to LambdaTest for remote device testing on Real Devices. Upload your IPA/APK file to LambdaTest App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload/issues\npublished_at: 2022-04-21T23:40:48.586584+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-upload.git\n  commit: c9ac1ea850b3e5ac0817c9180281aabe1816edb3\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  - name: ack\n  apt_get:\n  - name: curl\n  - name: jq\n  - name: ack\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to LambdaTest, usually `$BITRISE\\_APK\\_PATH`\n      or `$BITRISE\\_IPA\\_PATH`\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- app_name: \"Untitled\"\n  opts:\n    description: |\n      The name of your application\n    is_required: true\n    summary: Your application name\n    title: Application Name\n- custom_id: \"\"\n  opts:\n    is_required: false\n    summary: Custom Id to run your automation on the same app instead of remembering\n      app_url\n    title: Custom Id\noutputs:\n- LAMBDATEST_APP_URL: null\n  opts:\n    description: \"The app url returned by LambdaTest App Automate with the following\n      format \\\"lt://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: LambdaTest App Automate App URL\n"
  },
  {
    "path": "steps/lambdatest-upload/3.0.0/step.yml",
    "content": "title: LambdaTest Upload\nsummary: |\n  Upload APK/IPA files to LambdaTest's App Automate\ndescription: |\n  Upload your build files to LambdaTest for remote device testing on Real Devices. Upload your IPA/APK file to LambdaTest App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload/issues\npublished_at: 2022-05-05T20:57:08.812422+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-upload.git\n  commit: c0a39a58646cc3d79aaa25a1e1fb3a72355d94af\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to LambdaTest, usually `$BITRISE\\_APK\\_PATH`\n      or `$BITRISE\\_IPA\\_PATH`\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- app_name: Untitled\n  opts:\n    description: |\n      The name of your application\n    is_required: true\n    summary: Your application name\n    title: Application Name\n- custom_id: \"\"\n  opts:\n    is_required: false\n    summary: Custom Id to run your automation on the same app instead of remembering\n      app_url\n    title: Custom Id\noutputs:\n- LAMBDATEST_APP_URL: null\n  opts:\n    description: \"The app url returned by LambdaTest App Automate with the following\n      format \\\"lt://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: LambdaTest App Automate App URL\n"
  },
  {
    "path": "steps/lambdatest-upload/4.0.0/step.yml",
    "content": "title: LambdaTest Upload\nsummary: |\n  Upload APK/IPA files to LambdaTest's App Automate\ndescription: |\n  Upload your build files to LambdaTest for remote device testing on Real Devices. Upload your IPA/APK file to LambdaTest App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload/issues\npublished_at: 2022-05-17T23:30:59.350736+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-upload.git\n  commit: 661b2d495a669cab235a2d11ee8400c5bd1c297a\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to LambdaTest, usually `$BITRISE\\_APK\\_PATH`\n      or `$BITRISE\\_IPA\\_PATH`\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- app_name: Untitled\n  opts:\n    description: |\n      The name of your application\n    is_required: true\n    summary: Your application name\n    title: Application Name\n- custom_id: \"\"\n  opts:\n    is_required: false\n    summary: Custom Id to run your automation on the same app instead of remembering\n      app_url\n    title: Custom Id\noutputs:\n- LAMBDATEST_APP_URL: null\n  opts:\n    description: \"The app url returned by LambdaTest App Automate with the following\n      format \\\"lt://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: LambdaTest App Automate App URL\n"
  },
  {
    "path": "steps/lambdatest-upload/4.1.0/step.yml",
    "content": "title: LambdaTest Upload\nsummary: |\n  Upload APK/IPA files to LambdaTest's App Automate\ndescription: |\n  Upload your build files to LambdaTest for remote device testing on Real Devices. Upload your IPA/APK file to LambdaTest App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload/issues\npublished_at: 2024-06-04T23:30:59.350736+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-upload.git\n  commit: d67468c78d40a94cb1c03606be1f0bf163a618cd\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to LambdaTest, usually `$BITRISE\\_APK\\_PATH`\n      or `$BITRISE\\_IPA\\_PATH`\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- app_name: Untitled\n  opts:\n    description: |\n      The name of your application\n    is_required: true\n    summary: Your application name\n    title: Application Name\n- custom_id: \"\"\n  opts:\n    is_required: false\n    summary: Custom Id to run your automation on the same app instead of remembering\n      app_url\n    title: Custom Id\n- app_visibility: individual\n  opts:\n    is_required: false\n    summary: Whether to display the app to just the account that uploaded the file (\"individual\") or to everyone (\"team\")\n    title: App Visibility\noutputs:\n- LAMBDATEST_APP_URL: null\n  opts:\n    description: \"The app url returned by LambdaTest App Automate with the following\n      format \\\"lt://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: LambdaTest App Automate App URL\n"
  },
  {
    "path": "steps/lambdatest-upload/4.2.0/step.yml",
    "content": "title: LambdaTest Upload\nsummary: |\n  Upload APK/IPA files to LambdaTest's App Automate\ndescription: |\n  Upload your build files to LambdaTest for remote device testing on Real Devices. Upload your IPA/APK file to LambdaTest App Automation and get back the app's url for your remote device tests.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-upload/issues\npublished_at: 2025-08-30T00:45:00.57948+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-upload.git\n  commit: fd43524ba189f6698b2a1f0bb63850c9426691d9\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to LambdaTest, usually `$BITRISE\\_APK\\_PATH`\n      or `$BITRISE\\_IPA\\_PATH`\n    title: A Bitrise generated APK or IPA path\n  upload_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to log into your LambdaTest account\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- app_name: Untitled\n  opts:\n    description: |\n      The name of your application\n    is_required: true\n    summary: Your application name\n    title: Application Name\n- custom_id: \"\"\n  opts:\n    is_required: false\n    summary: Custom Id to run your automation on the same app instead of remembering\n      app_url\n    title: Custom Id\n- app_visibility: individual\n  opts:\n    is_required: false\n    summary: Whether to display the app to just the account that uploaded the file (\"individual\") or to everyone (\"team\")\n    title: App Visibility\n- show_debug_logs: \"false\"\n  opts:\n    description: |\n      When enabled, prints detailed debug information for troubleshooting upload issues.\n    title: Show debug logs\n    value_options:\n      - \"false\"\n      - \"true\"\noutputs:\n- LAMBDATEST_APP_URL: null\n  opts:\n    description: \"The app url returned by LambdaTest App Automate with the following\n      format \\\"lt://...\\\"\\\". \\nUse this in your remote device tests, usually through\n      your capabilities configuration\\n\"\n    summary: The app URL used in your App Automate's remote device tests\n    title: LambdaTest App Automate App URL\n"
  },
  {
    "path": "steps/lambdatest-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/lambdatest-xcuitest-app-automate/1.0.0/step.yml",
    "content": "title: LambdaTest App Automate - XCUITest\nsummary: |\n  Upload an app ipa and an XCUITest test ipa to LambdaTest and run tests with App Automate. For more information, please check out this [document](https://www.lambdatest.com/support/docs/getting-started-with-xcuitest/)\ndescription: |\n  This step uploads a provided app ipa and test ipa to LambdaTest. It then will execute the XCUI Tests for the provided apps in LambdaTest's app automate.\nwebsite: https://github.com/LambdaTest/bitrise-step-lambdatest-xcuitest-app-automate\nsource_code_url: https://github.com/LambdaTest/bitrise-step-lambdatest-xcuitest-app-automate\nsupport_url: https://github.com/LambdaTest/bitrise-step-lambdatest-xcuitest-app-automate/issues\npublished_at: 2022-07-28T11:38:07.831606+05:30\nsource:\n  git: https://github.com/LambdaTest/bitrise-step-lambdatest-xcuitest-app-automate.git\n  commit: 4071eb4bddcf33c41e04d5779198a87cde141b28\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  - name: sed\n  apt_get:\n  - name: curl\n  - name: jq\n  - name: sed\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_ipa_path: null\n  opts:\n    description: |\n      The .ipa file for your app.\n    is_expand: true\n    is_required: true\n    summary: Path to the app .ipa file\n    title: App ipa path\n- opts:\n    description: |\n      The test .ipa file for your app.\n    is_expand: true\n    is_required: true\n    summary: Path to the test .ipa file\n    title: Test suite ipa path\n  test_ipa_path: null\n- lambdatest_username: null\n  opts:\n    description: |\n      The username you use to log into your LambdaTest account.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest username\n    title: LambdaTest username\n- lambdatest_access_key: null\n  opts:\n    description: |\n      The access key you use to run your automation tests. Your access key can be found on the Automation Dashboard by clicking [here](https://appautomation.lambdatest.com/build).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your LambdaTest access key\n    title: LambdaTest access key\n- lambdatest_device_list: null\n  opts:\n    category: Automated Test Options\n    description: |\n      Provide a comma separated list of Device and OS version you want to run your tests on, with quotes. Acceptable format example: \"iPhone 12-14\", \"iPhone 6S-13\".\n      A list of available device and OS combinations can be found [here](https://www.lambdatest.com/list-of-real-devices).\n    is_expand: true\n    is_required: true\n    summary: A comma separated list of desired test devices\n    title: Device list\n- lambdatest_build_name: null\n  opts:\n    category: Automated Test Options\n    description: |\n      The name of your build.\n    is_required: false\n    summary: Your build name\n    title: Build Name\n- lambdatest_queue_timeout: 600\n  opts:\n    category: Automated Test Options\n    description: |\n      The time in seconds after which you want your build to timeout from queue. The default value of Queue Timeout is 600 seconds.\n    is_required: false\n    summary: The time in seconds after which you want your build to timeout from queue\n    title: Queue Timeout\n- lambdatest_idle_timeout: 120\n  opts:\n    category: Automated Test Options\n    description: |\n      The maximum time in seconds during which the device will stay idle without any commands being executed. The default value of Idle Timeout is 120 seconds.\n    is_required: false\n    summary: The maximum time in seconds during which the device will stay idle without\n      any commands being executed\n    title: Idle Timeout\n- lambdatest_tunnel: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter if you want to enable local testing. By default\n      it's set to false.\n    is_required: false\n    summary: Set this parameter if you want to enable local testing.\n    title: Tunnel\n    value_options:\n    - \"true\"\n    - \"false\"\n- lambdatest_tunnel_name: null\n  opts:\n    category: Automated Test Options\n    description: Name of the tunnel\n    is_required: false\n    summary: Your Tunnel Name\n    title: Tunnel Name\n- lambdatest_device_logs: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter to true if you want to enable the device logs.\n      By default it's set to false.\n    is_required: false\n    summary: Set this parameter to true if you want to enable the device logs\n    title: Device Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- lambdatest_network_logs: \"false\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter to true if you want to enable the network logs.\n      By default it's set to false.\n    is_required: false\n    summary: Set this parameter to true if you want to enable the network logs\n    title: Network Logs\n    value_options:\n    - \"true\"\n    - \"false\"\n- lambdatest_video: \"true\"\n  opts:\n    category: Automated Test Options\n    description: Set this parameter to true if you want to enable the video of the\n      test run. By default it's set to true.\n    is_required: false\n    summary: Set this parameter to true if you want to enable the video of the test\n      run.\n    title: Video\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- LAMBDATEST_BUILD_ID: null\n  opts:\n    summary: The Build ID for this test run in LambdaTest\n    title: Build ID\n"
  },
  {
    "path": "steps/lambdatest-xcuitest-app-automate/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/lifx-notifier/1.0.0/step.yml",
    "content": "title: LIFX Notifier\nsummary: Sends signals to your LIFX bulb during builds.\ndescription: |-\n  Add this step to your workflow when color change is required.\n\n  This step can be used at the start (notify build start) and at the end (notify success/failure) of your workflow.\n  If there's no need to notify about workflow start than adding step to the end of the workflow will be enough.\n\n  If all colors fields will be empty, default colors will be used:\n  \"build start\" - yellow, \"build success\" - green, \"build failure\" - red.\nwebsite: https://github.com/vgaidarji/steps-lifx-notifier\nsource_code_url: https://github.com/vgaidarji/steps-lifx-notifier\nsupport_url: https://github.com/vgaidarji/steps-lifx-notifier/issues\npublished_at: 2016-10-08T18:06:20.182318893+03:00\nsource:\n  git: https://github.com/vgaidarji/steps-lifx-notifier.git\n  commit: 52ea2c3561022d0664e6f6af1ce7460a14009698\nhost_os_tags:\n- osx-10.8\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- utilities\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- auth_token: null\n  opts:\n    description: |\n      This step uses official LIFX API,\n      which requires OAuth2 Access token (https://api.developer.lifx.com/docs/authentication).\n    is_required: true\n    title: Authentication token\n- bulb_label: null\n  opts:\n    description: |\n      This is the name of the LIFX bulb, eg. \"Bedroom\", \"Office\".\n    is_required: true\n    title: LIFX bulb label\n- opts:\n    description: |\n      Identifies if this step used at the start of the workflow or not.\n    is_required: true\n    title: Workflow start identifier\n    value_options:\n    - \"yes\"\n    - \"no\"\n  workflow_start: \"no\"\n- color_build_started: yellow\n  opts:\n    description: |\n      This color will be used to notify about workflow start,\n      if no custom color provided.\n    title: Build started color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_started_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: ffff00 (yellow).\n    title: Build started color (custom)\n- color_build_success: green\n  opts:\n    description: |\n      This color will be used to notify about successfully completed workflow,\n      if no custom color provided.\n    title: Build success color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_success_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: 00ff00 (green).\n    title: Build success color (custom)\n- color_build_failure: red\n  opts:\n    description: |\n      This color will be used to notify about failure,\n      if no custom color provided.\n    title: Build failure color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_failure_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: ff0000 (red).\n    title: Build failure color (custom)\n"
  },
  {
    "path": "steps/lifx-notifier/1.0.1/step.yml",
    "content": "title: LIFX Notifier\nsummary: Sends signals to your LIFX bulb during builds.\ndescription: |-\n  Add this step to your workflow when color change is required.\n\n  This step can be used at the start (notify build start) and at the end (notify success/failure) of your workflow.\n  If there's no need to notify about workflow start than adding step to the end of the workflow will be enough.\n\n  If all colors fields will be empty, default colors will be used:\n  \"build start\" - yellow, \"build success\" - green, \"build failure\" - red.\nwebsite: https://github.com/vgaidarji/steps-lifx-notifier\nsource_code_url: https://github.com/vgaidarji/steps-lifx-notifier\nsupport_url: https://github.com/vgaidarji/steps-lifx-notifier/issues\npublished_at: 2016-10-09T14:00:35.390617484+03:00\nsource:\n  git: https://github.com/vgaidarji/steps-lifx-notifier.git\n  commit: 3899544d14f75f3fcbaf81259d147a71f5c39777\nhost_os_tags:\n- osx-10.8\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- auth_token: null\n  opts:\n    description: |\n      This step uses official LIFX API,\n      which requires OAuth2 Access token (https://api.developer.lifx.com/docs/authentication).\n    is_required: true\n    title: Authentication token\n- bulb_label: null\n  opts:\n    description: |\n      This is the name of the LIFX bulb, eg. \"Bedroom\", \"Office\".\n    is_required: true\n    title: LIFX bulb label\n- color_build_success: green\n  opts:\n    description: |\n      It can be used after any step in the workflow to notify about current state.\n      e.g.: use \"yellow\" color to indicate that workflow started\n    title: Build success color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_success_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: 00ff00 (green).\n    title: Build success color (custom)\n- color_build_failure: red\n  opts:\n    description: |\n      This color will be used to notify about failure,\n      if no custom color provided.\n    title: Build failure color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_failure_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: ff0000 (red).\n    title: Build failure color (custom)\n"
  },
  {
    "path": "steps/lifx-notifier/1.0.3/step.yml",
    "content": "title: LIFX Notifier\nsummary: Sends signals to your LIFX bulb during builds.\ndescription: |-\n  Add this step to your workflow when color change is required.\n\n  This step can be used at the start (notify build start) and at the end (notify success/failure) of your workflow.\n  If there's no need to notify about workflow start than adding step to the end of the workflow will be enough.\n\n  If all colors fields will be empty, default colors will be used:\n  \"build start\" - yellow, \"build success\" - green, \"build failure\" - red.\nwebsite: https://github.com/vgaidarji/steps-lifx-notifier\nsource_code_url: https://github.com/vgaidarji/steps-lifx-notifier\nsupport_url: https://github.com/vgaidarji/steps-lifx-notifier/issues\npublished_at: 2017-08-17T16:04:25.018497066+03:00\nsource:\n  git: https://github.com/vgaidarji/steps-lifx-notifier.git\n  commit: f815e5dc14a75acdd3266e9c43baf3dbb96f0d38\nhost_os_tags:\n- osx-10.8\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- auth_token: null\n  opts:\n    description: |\n      This step uses official LIFX API,\n      which requires OAuth2 Access token (https://api.developer.lifx.com/docs/authentication).\n    is_required: true\n    title: Authentication token\n- bulb_label: null\n  opts:\n    description: |\n      This is the name of the LIFX bulb, eg. \"Bedroom\", \"Office\".\n    is_required: true\n    title: LIFX bulb label\n- color_build_success: green\n  opts:\n    description: |\n      It can be used after any step in the workflow to notify about current state.\n      e.g.: use \"yellow\" color to indicate that workflow started\n    title: Build success color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_success_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: 00ff00 (green).\n    title: Build success color (custom)\n- color_build_failure: red\n  opts:\n    description: |\n      This color will be used to notify about failure,\n      if no custom color provided.\n    title: Build failure color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_failure_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: ff0000 (red).\n    title: Build failure color (custom)\n- effect: none\n  opts:\n    description: |\n      Instead of setting a solid color, do you want to e.g. pulse the light?\n    title: Effect\n    value_options:\n    - none\n    - pulse\n    - breathe\n"
  },
  {
    "path": "steps/lifx-notifier/1.1.1/step.yml",
    "content": "title: LIFX Notifier\nsummary: Sends signals to your LIFX bulb during builds.\ndescription: |-\n  Add this step to your workflow when color change is required.\n\n  This step can be used at the start (notify build start) and at the end (notify success/failure) of your workflow.\n  If there's no need to notify about workflow start than adding step to the end of the workflow will be enough.\n\n  If all colors fields will be empty, default colors will be used:\n  \"build start\" - yellow, \"build success\" - green, \"build failure\" - red.\nwebsite: https://github.com/ShotSkydiver/steps-lifx-notifier\nsource_code_url: https://github.com/ShotSkydiver/steps-lifx-notifier\nsupport_url: https://github.com/ShotSkydiver/steps-lifx-notifier/issues\npublished_at: 2020-07-17T14:09:25.627659-06:00\nsource:\n  git: https://github.com/ShotSkydiver/steps-lifx-notifier.git\n  commit: 299d9f8466296c6462d02f374d6240fbc9f56fb5\nhost_os_tags:\n- osx-10.8\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- auth_token: null\n  opts:\n    description: |\n      This step uses official LIFX API,\n      which requires OAuth2 Access token (https://api.developer.lifx.com/docs/authentication).\n    is_required: true\n    title: Authentication token\n- opts:\n    description: |\n      By default, only the name of a single light will be triggered. You can change this to specify a group instead.\n    title: Selector type\n    value_options:\n    - label\n    - group\n    - location\n  selector_type: label\n- bulb_label: null\n  opts:\n    description: |\n      This is the name of the LIFX light or group, eg. \"Bedroom\", \"Office\".\n    is_required: true\n    title: LIFX light(s) selector label\n- color_build_success: green\n  opts:\n    description: |\n      It can be used after any step in the workflow to notify about current state.\n      e.g.: use \"yellow\" color to indicate that workflow started\n    title: Build success color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_success_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: 00ff00 (green).\n    title: Build success color (custom)\n- color_build_failure: red\n  opts:\n    description: |\n      This color will be used to notify about failure,\n      if no custom color provided.\n    title: Build failure color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_failure_custom: null\n  opts:\n    description: |\n      If custom color provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: ff0000 (red).\n    title: Build failure color (custom)\n- effect: none\n  opts:\n    description: |\n      Instead of setting a solid color, do you want to e.g. pulse the light?\n    title: Effect\n    value_options:\n    - none\n    - pulse\n    - breathe\n"
  },
  {
    "path": "steps/lifx-notifier/1.2.1/step.yml",
    "content": "title: LIFX Notifier\nsummary: Sends signals to your LIFX bulb during builds.\ndescription: |-\n  Add this step to your workflow when color change is required.\n\n  This step can be used at the start (notify build start) and at the end (notify success/failure) of your workflow.\n  If there's no need to notify about workflow start than adding step to the end of the workflow will be enough.\nwebsite: https://github.com/ShotSkydiver/steps-lifx-notifier\nsource_code_url: https://github.com/ShotSkydiver/steps-lifx-notifier\nsupport_url: https://github.com/ShotSkydiver/steps-lifx-notifier/issues\npublished_at: 2021-05-21T16:03:58.500425-06:00\nsource:\n  git: https://github.com/ShotSkydiver/steps-lifx-notifier.git\n  commit: 472646e717257221e3eba2bad03f7f6d5af0a00f\nhost_os_tags:\n- osx-10.8\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- auth_token: null\n  opts:\n    description: |\n      This step uses official LIFX API,\n      which requires OAuth2 Access token (https://api.developer.lifx.com/docs/authentication).\n    is_required: true\n    title: Authentication token\n- opts:\n    description: |\n      By default, all lights associated with your LIFX account will be triggered. You can change this to specify a group name, or a single light name instead.\n    title: Selector type\n    value_options:\n    - all\n    - label\n    - group\n    - location\n  selector_type: all\n- bulb_label: null\n  opts:\n    description: |\n      This is the name of the LIFX light, group (eg. \"Bedroom\", \"Office\"), or location (eg. \"Home\"). This value will be ignored if \"all\" is chosen as the selector type above.\n    is_required: false\n    title: LIFX light(s) selector label\n- color_build_success: green\n  opts:\n    description: |\n      Choose the color you want the lights to change to upon a successful build.\n    title: Build success color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_success_custom: null\n  opts:\n    description: |\n      If a custom color is provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: 00ff00 (green).\n    title: Build success color (custom)\n- color_build_failure: red\n  opts:\n    description: |\n      Choose the color you want the lights to change to upon a failed build.\n    title: Build failure color (LIFX default)\n    value_options:\n    - blue\n    - cyan\n    - green\n    - orange\n    - pink\n    - purple\n    - red\n    - yellow\n    - white\n- color_build_failure_custom: null\n  opts:\n    description: |\n      If a custom color is provided, it will be used instead of LIFX default.\n      Format RRGGBB, e.g: ff0000 (red).\n    title: Build failure color (custom)\n- effect: none\n  opts:\n    description: |\n      Instead of setting a solid color, do you want to e.g. pulse the light?\n    title: Effect\n    value_options:\n    - none\n    - pulse\n    - breathe\n- cycles: null\n  opts:\n    description: |\n      If an effect is chosen, this option will set the number of times the effect is repeated.\n    title: Number of Effect Cycles\n"
  },
  {
    "path": "steps/lifx-notifier/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/localazy/1.0.0/step.yml",
    "content": "title: Localazy CLI\nsummary: Install Localazy CLI and download updated translations\ndescription: This step runs a `wti pull` after installing the web translate it gem.\n  You need an account on https://webtranslateit.com to be able to run this step.\nwebsite: https://localazy.com\nsource_code_url: https://github.com/localazy/bitrise-step-localazy\nsupport_url: https://github.com/localazy/bitrise-step-localazy/issues\npublished_at: 2020-11-26T13:45:32.173355644+01:00\nsource:\n  git: https://github.com/localazy/bitrise-step-localazy.git\n  commit: 2b16ead33fd5ec89d24a69e2af2dee0b804ebad3\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: java\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- config_file: localazy.json\n  opts:\n    description: |-\n      If you use different filename for the configuration file (not `localazy.json`), please specify the filename here.\n\n      For more information, visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\n    is_required: false\n    summary: The filename of the configuration file. Default is `localazy.json`.\n    title: Configuration file\n- key_file: null\n  opts:\n    description: |-\n      If you provide read and write keys in the key file, please specify its filename here.\n\n      For more information, visit [Localazy CLI - Authorization](https://localazy.com/docs/cli/authorization).\n    is_required: false\n    summary: The filename of the key file\n    title: Key file\n- opts:\n    description: \"If you don't provide read and write keys in the configuration or\n      key file, please provide it here.\\n\\nFor more information, visit [Localazy CLI\n      - Authorization](https://localazy.com/docs/cli/authorization) \\nand [Localazy\n      CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: The custom read key\n    title: Read Key\n  read_key: null\n- opts:\n    description: \"If you don't provide read and write keys in the configuration or\n      key file, please provide it here.\\n\\nFor more information, visit [Localazy CLI\n      - Authorization](https://localazy.com/docs/cli/authorization) \\nand [Localazy\n      CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: The custom write key\n    title: Write Key\n  write_key: null\n- groups_list: null\n  opts:\n    description: |-\n      Groups allow for running only selected rules from the configuration file.\n\n      For more information, visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options#groups).\n    is_required: false\n    summary: The list of download groups separated by space\n    title: Groups\n- opts:\n    description: 'You should invoke Localazy CLI in the directory containing the configuration\n      file `localazy.json`.      '\n    is_required: false\n    summary: Change the working directory\n    title: Working directory\n  working_directory: null\n- custom_command: null\n  opts:\n    description: \"Provide parameters that you would normally use after the `localazy`\n      command.\\nExample: `download -r read-key -w write-key -s` \\n\\nNote: Providing\n      custom parameters override other options defined above.    \\n\\nFor more information,\n      visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_required: false\n    summary: Invoke Localazy CLI with custom parameters\n    title: Custom parameters\n"
  },
  {
    "path": "steps/localazy/1.0.2/step.yml",
    "content": "title: Localazy CLI\nsummary: Runs Localazy CLI and download updated translations\ndescription: \"This step runs [Localazy CLI](https://localazy.com/docs/cli) and download\n  updated translations.\\n[Localazy](https://localazy.com) is a translation management\n  platform built by developers for developers \\nto localize apps in the modern way. \"\nwebsite: https://localazy.com\nsource_code_url: https://github.com/localazy/bitrise-step-localazy\nsupport_url: https://github.com/localazy/bitrise-step-localazy/issues\npublished_at: 2020-11-27T11:28:48.095620718+01:00\nsource:\n  git: https://github.com/localazy/bitrise-step-localazy.git\n  commit: bd3931c466ca793a3bb567b7577dd9e5dcc9aa35\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: java\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- config_file: localazy.json\n  opts:\n    description: |-\n      If you use different filename for the configuration file (not `localazy.json`), please specify the filename here.\n\n      For more information, visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\n    is_required: false\n    summary: The filename of the configuration file. Default is `localazy.json`.\n    title: Configuration file\n- key_file: null\n  opts:\n    description: |-\n      If you provide read and write keys in the key file, please specify its filename here.\n\n      For more information, visit [Localazy CLI - Authorization](https://localazy.com/docs/cli/authorization).\n    is_required: false\n    summary: The filename of the key file\n    title: Key file\n- opts:\n    description: \"If you don't provide read and write keys in the configuration or\n      key file, please provide it here.\\n\\nFor more information, visit [Localazy CLI\n      - Authorization](https://localazy.com/docs/cli/authorization) \\nand [Localazy\n      CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: The custom read key\n    title: Read Key\n  read_key: null\n- opts:\n    description: \"If you don't provide read and write keys in the configuration or\n      key file, please provide it here.\\n\\nFor more information, visit [Localazy CLI\n      - Authorization](https://localazy.com/docs/cli/authorization) \\nand [Localazy\n      CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: The custom write key\n    title: Write Key\n  write_key: null\n- groups_list: null\n  opts:\n    description: |-\n      Groups allow for running only selected rules from the configuration file.\n\n      For more information, visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options#groups).\n    is_required: false\n    summary: The list of download groups separated by space\n    title: Groups\n- opts:\n    description: 'You should invoke Localazy CLI in the directory containing the configuration\n      file `localazy.json`.      '\n    is_required: false\n    summary: Change the working directory\n    title: Working directory\n  working_directory: null\n- custom_command: null\n  opts:\n    description: \"Provide parameters that you would normally use after the `localazy`\n      command.\\nExample: `download -r read-key -w write-key -s` \\n\\nNote: Providing\n      custom parameters override other options defined above.    \\n\\nFor more information,\n      visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_required: false\n    summary: Invoke Localazy CLI with custom parameters\n    title: Custom parameters\n"
  },
  {
    "path": "steps/localazy/1.0.5/step.yml",
    "content": "title: Localazy CLI\nsummary: Runs Localazy CLI and download updated translations\ndescription: \"This step runs [Localazy CLI](https://localazy.com/docs/cli) and download\n  updated translations.\\n[Localazy](https://localazy.com) is a translation management\n  platform built by developers for developers \\nto localize apps in the modern way. \"\nwebsite: https://localazy.com\nsource_code_url: https://github.com/localazy/bitrise-step-localazy\nsupport_url: https://github.com/localazy/bitrise-step-localazy/issues\npublished_at: 2021-08-27T10:46:27.924269874+02:00\nsource:\n  git: https://github.com/localazy/bitrise-step-localazy.git\n  commit: 33819490a1282ad92b12408016d11b1bc40be874\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: java\n  apt_get:\n  - name: openjdk-11-jre\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- config_file: localazy.json\n  opts:\n    description: |-\n      If you use different filename for the configuration file (not `localazy.json`), please specify the filename here.\n\n      For more information, visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\n    is_required: false\n    summary: The filename of the configuration file. Default is `localazy.json`.\n    title: Configuration file\n- key_file: null\n  opts:\n    description: |-\n      If you provide read and write keys in the key file, please specify its filename here.\n\n      For more information, visit [Localazy CLI - Authorization](https://localazy.com/docs/cli/authorization).\n    is_required: false\n    summary: The filename of the key file\n    title: Key file\n- opts:\n    description: \"If you don't provide read and write keys in the configuration or\n      key file, please provide it here.\\n\\nFor more information, visit [Localazy CLI\n      - Authorization](https://localazy.com/docs/cli/authorization) \\nand [Localazy\n      CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: The custom read key\n    title: Read Key\n  read_key: null\n- opts:\n    description: \"If you don't provide read and write keys in the configuration or\n      key file, please provide it here.\\n\\nFor more information, visit [Localazy CLI\n      - Authorization](https://localazy.com/docs/cli/authorization) \\nand [Localazy\n      CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: The custom write key\n    title: Write Key\n  write_key: null\n- groups_list: null\n  opts:\n    description: |-\n      Groups allow for running only selected rules from the configuration file.\n\n      For more information, visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options#groups).\n    is_required: false\n    summary: The list of download groups separated by space\n    title: Groups\n- opts:\n    description: 'You should invoke Localazy CLI in the directory containing the configuration\n      file `localazy.json`.      '\n    is_required: false\n    summary: Change the working directory\n    title: Working directory\n  working_directory: null\n- custom_command: null\n  opts:\n    description: \"Provide parameters that you would normally use after the `localazy`\n      command.\\nExample: `download -r read-key -w write-key -s` \\n\\nNote: Providing\n      custom parameters override other options defined above.    \\n\\nFor more information,\n      visit [Localazy CLI - Command-Line Options](https://localazy.com/docs/cli/command-line-options).\"\n    is_required: false\n    summary: Invoke Localazy CLI with custom parameters\n    title: Custom parameters\n"
  },
  {
    "path": "steps/localazy/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/loco/0.0.3/step.yml",
    "content": "title: loco\nsummary: Upload or download translations from Loco\ndescription: This step can upload your new assets to Loco and download updated assets\n  from Loco. Importing (upload) is always done before exporting (download).\nwebsite: https://github.com/3factr/bitrise-step-loco\nsource_code_url: https://github.com/3factr/bitrise-step-loco\nsupport_url: https://github.com/3factr/bitrise-step-loco/issues\npublished_at: 2019-07-28T12:40:52.545291+02:00\nsource:\n  git: https://github.com/3factr/bitrise-step-loco.git\n  commit: 58f56d9bbf55255643dfd22be2585a1ab8c9c16c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- loco_api_key: null\n  opts:\n    description: Your Loco export key if you only want to download translations, or\n      your Loco Full access key if you want to upload new assets. You can get your\n      API key under _Developer Tools > API keys_.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your Loco export key if you only want to download translations, or your\n      Loco Full access key if you want to upload new assets.\n    title: Loco API key\n- import_file_ext: csv\n  opts:\n    category: Import\n    summary: File extension for the type of data you're importing. Required if you\n      are importing assets.\n    title: File extension\n    value_options:\n    - arb\n    - bplist\n    - csv\n    - ini\n    - json\n    - mo\n    - php\n    - plist\n    - po\n    - pot\n    - properties\n    - res\n    - resx\n    - strings\n    - tmx\n    - ts\n    - txt\n    - xlf\n    - xml\n    - yml\n- import_file_path: null\n  opts:\n    category: Import\n    summary: Path to the file that has to be imported in Loco. Required if you are\n      importing assets.\n    title: Path to imported translations\n- import_index: id\n  opts:\n    category: Import\n    summary: Specify whether translations in your file are indexed by generic IDs\n      or human-readable source text\n    title: import_index\n    value_options:\n    - id\n    - text\n- import_locale: null\n  opts:\n    category: Import\n    summary: Specify target locale if importing translations\n    title: Locale\n- import_async: \"false\"\n  opts:\n    category: Import\n    summary: Specify that import should be done asynchronously (recommended for large\n      files)\n    title: Async\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_source_path: null\n  opts:\n    category: Import\n    summary: Specify original file path for source code references (excluding line\n      number)\n    title: Path\n- import_ignore_new: \"false\"\n  opts:\n    category: Import\n    summary: Specify that new assets will **NOT** be added to the project\n    title: Ignore new\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_ignore_existing: \"false\"\n  opts:\n    category: Import\n    summary: Specify that existing assets encountered in the file will NOT be updated\n    title: Ignore existing\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_delete_absent: \"false\"\n  opts:\n    category: Import\n    summary: Permanently **DELETES** project assets NOT found in the file (use with\n      extreme caution)\n    title: Delete absent\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_tag_new: null\n  opts:\n    category: Import\n    summary: Tag any NEW assets added during the import with the given tags (comma\n      separated)\n    title: Tag new\n- import_tag_all: null\n  opts:\n    category: Import\n    summary: Tag ALL assets in the file with the given tags (comma separated)\n    title: Tag all\n- import_untag_all: null\n  opts:\n    category: Import\n    summary: Remove existing tags from any assets matched in the imported file (comma\n      separated)\n    title: Untag all\n- import_tag_updated: null\n  opts:\n    category: Import\n    summary: Tag existing assets that are MODIFIED by this import\n    title: Tag updated\n- opts:\n    category: Import\n    summary: Remove existing tags from assets that are MODIFIED during import\n    title: Untag updated\n  untag_updated: null\n- import_tag_absent: null\n  opts:\n    category: Import\n    summary: Tag existing assets in the project that are NOT found in the imported\n      file\n    title: Tag absent\n- import_untag_absent: null\n  opts:\n    category: Import\n    summary: Remove existing tags from assets NOT found in the imported file\n    title: Untag absent\n- export_file_ext: all|csv\n  opts:\n    category: Export\n    description: |\n      Target file type specified as a file extension. Required if you are exporting assets.\n      * The options prepended with `all` export all your locales into a single file.\n      * The options prepended with `archive` export all your locales into a zip file that will be extracted.\n      * The options prepended with `locale` export a single locale into a single file.\n    summary: Target file type specified as a file extension. Required if you are exporting\n      assets.\n    title: File extension\n    value_options:\n    - all|json\n    - all|csv\n    - all|html\n    - all|sql\n    - all|tmx\n    - all|xlf\n    - all|yml\n    - archive|arb\n    - archive|csv\n    - archive|html\n    - archive|ini\n    - archive|json\n    - archive|mo\n    - archive|php\n    - archive|po\n    - archive|pot\n    - archive|plist\n    - archive|bplist\n    - archive|properties\n    - archive|res\n    - archive|resx\n    - archive|sql\n    - archive|strings\n    - archive|stringsdict\n    - archive|tmx\n    - archive|ts\n    - archive|txt\n    - archive|xlf\n    - archive|xliff\n    - archive|xml\n    - archive|yml\n    - locale|arb\n    - locale|csv\n    - locale|html\n    - locale|ini\n    - locale|json\n    - locale|mo\n    - locale|php\n    - locale|po\n    - locale|pot\n    - locale|plist\n    - locale|bplist\n    - locale|properties\n    - locale|res\n    - locale|resx\n    - locale|sql\n    - locale|strings\n    - locale|stringsdict\n    - locale|tmx\n    - locale|ts\n    - locale|txt\n    - locale|xlf\n    - locale|xliff\n    - locale|xml\n    - locale|yml\n- export_locale: null\n  opts:\n    category: Export\n    summary: Locale to export, specified as short code or language tag. e.g. `en`\n      or `en_GB`. Required and only valid if you selected an extension prepended with\n      `locale`.\n    title: Locale\n- export_file_path: null\n  opts:\n    category: Export\n    summary: Where the exported file should be stored. This is required when you are\n      exporting. This should be a path to a file when you are exporting a multi-locale\n      or a single-locale file. This should be a path to a directory when you are exporting\n      an archive.\n    title: File path\n- export_format: default\n  opts:\n    category: Export\n    summary: More specific format of file type. e.g. `rails` applies to `yml` and\n      `symfony` applies to `php`, `xlf` & `yml`\n    title: Format\n    value_options:\n    - default\n    - rails\n    - i18next\n    - i18next3\n    - symfony\n    - zend\n    - codeigniter\n    - constants\n    - chrome\n    - nested\n    - rails\n    - java\n    - tizen\n    - jed\n    - gettext\n    - ng-gettext\n    - xcode\n    - script\n- export_filter: null\n  opts:\n    category: Export\n    summary: Filter assets by comma-separated tag names. Match any tag with * and\n      negate tags by prefixing with !\n    title: Filter\n- export_index: id\n  opts:\n    category: Export\n    summary: Override default lookup key for the file format; `id`, `text` or a custom\n      alias\n    title: Index\n- export_source: null\n  opts:\n    category: Export\n    summary: Specify alternative source locale instead of project default\n    title: Source\n- export_fallback: null\n  opts:\n    category: Export\n    summary: Fallback locale for untranslated assets, specified as short code. e.g.\n      `en` or `en_GB`\n    title: Fallback\n- export_order: created\n  opts:\n    category: Export\n    summary: Export translations according to asset order\n    title: Order\n    value_options:\n    - created\n    - id\n- export_printf: default\n  opts:\n    category: Export\n    summary: Force alternative \"printf\" style. [See string formatting](https://localise.biz/help/developers/printf)\n    title: printf style\n    value_options:\n    - default\n    - php\n    - java\n    - objc\n    - icu\n- export_charset: UTF-8\n  opts:\n    category: Export\n    summary: Specify preferred character encoding.\n    title: Encoding\n- export_breaks: Unix\n  opts:\n    category: Export\n    summary: Force platform-specific line-endings. Default is Unix (LF) breaks.\n    title: Line-endings\n    value_options:\n    - Unix\n    - DOS\n    - Mac\n- export_no_comments: \"false\"\n  opts:\n    category: Export\n    summary: Disable rendering of redundant inline comments including the Loco banner.\n    title: No comments\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_no_folding: \"false\"\n  opts:\n    category: Export\n    summary: Protect [dot-separated](https://localise.biz/help/developers/asset-ids#folding)\n      keys so that `foo.bar` is not folded into object properties.\n    title: No folding\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_namespace: null\n  opts:\n    category: Export\n    summary: Override the project name for some language packs that use it as a key\n      prefix\n    title: Namespace\n- export_status: null\n  opts:\n    category: Export\n    summary: Export translations with a specific status or flag. Negate values by\n      prefixing with !. e.g. `translated`, or `!fuzzy`.\n    title: Status\n- export_path: null\n  opts:\n    category: Export\n    summary: Custom pattern for file paths. [See syntax](https://localise.biz/help/developers/locales/export-paths)\n    title: Path\n"
  },
  {
    "path": "steps/loco/0.1.1/step.yml",
    "content": "title: loco\nsummary: Upload or download translations from Loco\ndescription: This step can upload your new assets to Loco and download updated assets\n  from Loco. Importing (upload) is always done before exporting (download).\nwebsite: https://github.com/3factr/bitrise-step-loco\nsource_code_url: https://github.com/3factr/bitrise-step-loco\nsupport_url: https://github.com/3factr/bitrise-step-loco/issues\npublished_at: 2019-10-31T14:12:23.665+01:00\nsource:\n  git: https://github.com/3factr/bitrise-step-loco.git\n  commit: af7fbde7f086dc1b8e8ffd9fc906018f00b9668a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- loco_api_key: null\n  opts:\n    description: Your Loco export key if you only want to download translations, or\n      your Loco Full access key if you want to upload new assets. You can get your\n      API key under _Developer Tools > API keys_.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your Loco export key if you only want to download translations, or your\n      Loco Full access key if you want to upload new assets.\n    title: Loco API key\n- import_file_ext: csv\n  opts:\n    category: Import\n    summary: File extension for the type of data you're importing. Required if you\n      are importing assets.\n    title: File extension\n    value_options:\n    - arb\n    - bplist\n    - csv\n    - ini\n    - json\n    - mo\n    - php\n    - plist\n    - po\n    - pot\n    - properties\n    - res\n    - resx\n    - strings\n    - tmx\n    - ts\n    - txt\n    - xlf\n    - xml\n    - yml\n- import_file_path: null\n  opts:\n    category: Import\n    summary: Path to the file that has to be imported in Loco. Required if you are\n      importing assets.\n    title: Path to imported translations\n- import_index: id\n  opts:\n    category: Import\n    summary: Specify whether translations in your file are indexed by generic IDs\n      or human-readable source text\n    title: Index type\n    value_options:\n    - id\n    - text\n- import_locale: null\n  opts:\n    category: Import\n    summary: Specify target locale if importing translations (e.g. en_US or en)\n    title: Locale\n- import_async: \"false\"\n  opts:\n    category: Import\n    summary: Specify that import should be done asynchronously (recommended for large\n      files)\n    title: Async\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_source_path: null\n  opts:\n    category: Import\n    summary: Specify original file path for source code references (excluding line\n      number)\n    title: Path\n- import_ignore_new: \"false\"\n  opts:\n    category: Import\n    summary: Specify that new assets will **NOT** be added to the project\n    title: Ignore new\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_ignore_existing: \"false\"\n  opts:\n    category: Import\n    summary: Specify that existing assets encountered in the file will NOT be updated\n    title: Ignore existing\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_delete_absent: \"false\"\n  opts:\n    category: Import\n    summary: Permanently **DELETES** project assets NOT found in the file (use with\n      extreme caution)\n    title: Delete absent\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_tag_new: null\n  opts:\n    category: Import\n    summary: Tag any NEW assets added during the import with the given tags (comma\n      separated)\n    title: Tag new\n- import_tag_all: null\n  opts:\n    category: Import\n    summary: Tag ALL assets in the file with the given tags (comma separated)\n    title: Tag all\n- import_untag_all: null\n  opts:\n    category: Import\n    summary: Remove existing tags from any assets matched in the imported file (comma\n      separated)\n    title: Untag all\n- import_tag_updated: null\n  opts:\n    category: Import\n    summary: Tag existing assets that are MODIFIED by this import\n    title: Tag updated\n- opts:\n    category: Import\n    summary: Remove existing tags from assets that are MODIFIED during import\n    title: Untag updated\n  untag_updated: null\n- import_tag_absent: null\n  opts:\n    category: Import\n    summary: Tag existing assets in the project that are NOT found in the imported\n      file\n    title: Tag absent\n- import_untag_absent: null\n  opts:\n    category: Import\n    summary: Remove existing tags from assets NOT found in the imported file\n    title: Untag absent\n- export_file_ext: all|csv\n  opts:\n    category: Export\n    description: |\n      Target file type specified as a file extension. Required if you are exporting assets.\n      * The options prepended with `all` export all your locales into a single file.\n      * The options prepended with `archive` export all your locales into a zip file that will be extracted.\n      * The options prepended with `locale` export a single locale into a single file.\n    summary: Target file type specified as a file extension. Required if you are exporting\n      assets.\n    title: File extension\n    value_options:\n    - all|json\n    - all|csv\n    - all|html\n    - all|sql\n    - all|tmx\n    - all|xlf\n    - all|yml\n    - archive|arb\n    - archive|csv\n    - archive|html\n    - archive|ini\n    - archive|json\n    - archive|mo\n    - archive|php\n    - archive|po\n    - archive|pot\n    - archive|plist\n    - archive|bplist\n    - archive|properties\n    - archive|res\n    - archive|resx\n    - archive|sql\n    - archive|strings\n    - archive|stringsdict\n    - archive|tmx\n    - archive|ts\n    - archive|txt\n    - archive|xlf\n    - archive|xliff\n    - archive|xml\n    - archive|yml\n    - locale|arb\n    - locale|csv\n    - locale|html\n    - locale|ini\n    - locale|json\n    - locale|mo\n    - locale|php\n    - locale|po\n    - locale|pot\n    - locale|plist\n    - locale|bplist\n    - locale|properties\n    - locale|res\n    - locale|resx\n    - locale|sql\n    - locale|strings\n    - locale|stringsdict\n    - locale|tmx\n    - locale|ts\n    - locale|txt\n    - locale|xlf\n    - locale|xliff\n    - locale|xml\n    - locale|yml\n- export_locale: null\n  opts:\n    category: Export\n    summary: Locale to export, specified as short code or language tag. e.g. `en`\n      or `en_GB`. Required and only valid if you selected an extension prepended with\n      `locale`.\n    title: Locale\n- export_file_path: null\n  opts:\n    category: Export\n    summary: Where the exported file should be stored. This is required when you are\n      exporting. This should be a path to a file when you are exporting a multi-locale\n      or a single-locale file. This should be a path to a directory when you are exporting\n      an archive.\n    title: File path\n- export_format: default\n  opts:\n    category: Export\n    description: |\n      More specific format of file type. E.g. `rails` applies to `yml` and `symfony` applies to `php`, `xlf` & `yml`.\n      The default format picks the most commonly used format for the file type.\n      * `json` defaults to simple JSON structure\n      * `xml` defaults to Android string resources\n      * `yml` defaults to Symfony-style flat structure\n      * `php` defaults to Zend-style array\n    summary: More specific format of file type. e.g. `rails` applies to `yml` and\n      `symfony` applies to `php`, `xlf` & `yml`.\n    title: Format\n    value_options:\n    - default\n    - rails\n    - i18next\n    - i18next3\n    - symfony\n    - zend\n    - codeigniter\n    - constants\n    - chrome\n    - nested\n    - rails\n    - java\n    - tizen\n    - jed\n    - gettext\n    - ng-gettext\n    - xcode\n    - script\n    - android\n- export_filter: null\n  opts:\n    category: Export\n    summary: Filter assets by comma-separated tag names. Match any tag with * and\n      negate tags by prefixing with !\n    title: Filter\n- export_index: id\n  opts:\n    category: Export\n    summary: Override default lookup key for the file format; `id`, `text` or a custom\n      alias\n    title: Index\n- export_source: null\n  opts:\n    category: Export\n    summary: Specify alternative source locale instead of project default\n    title: Source\n- export_fallback: null\n  opts:\n    category: Export\n    summary: Fallback locale for untranslated assets, specified as short code. e.g.\n      `en` or `en_GB`\n    title: Fallback\n- export_order: created\n  opts:\n    category: Export\n    summary: Export translations according to asset order\n    title: Order\n    value_options:\n    - created\n    - id\n- export_printf: default\n  opts:\n    category: Export\n    summary: Force alternative \"printf\" style. [See string formatting](https://localise.biz/help/developers/printf)\n    title: printf style\n    value_options:\n    - default\n    - php\n    - java\n    - objc\n    - icu\n- export_charset: UTF-8\n  opts:\n    category: Export\n    summary: Specify preferred character encoding.\n    title: Encoding\n- export_breaks: Unix\n  opts:\n    category: Export\n    summary: Force platform-specific line-endings. Default is Unix (LF) breaks.\n    title: Line-endings\n    value_options:\n    - Unix\n    - DOS\n    - Mac\n- export_no_comments: \"false\"\n  opts:\n    category: Export\n    summary: Disable rendering of redundant inline comments including the Loco banner.\n    title: No comments\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_no_folding: \"false\"\n  opts:\n    category: Export\n    summary: Protect [dot-separated](https://localise.biz/help/developers/asset-ids#folding)\n      keys so that `foo.bar` is not folded into object properties.\n    title: No folding\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_namespace: null\n  opts:\n    category: Export\n    summary: Override the project name for some language packs that use it as a key\n      prefix\n    title: Namespace\n- export_status: null\n  opts:\n    category: Export\n    summary: Export translations with a specific status or flag. Negate values by\n      prefixing with !. e.g. `translated`, or `!fuzzy`.\n    title: Status\n- export_path: null\n  opts:\n    category: Export\n    summary: Custom pattern for file paths. [See syntax](https://localise.biz/help/developers/locales/export-paths)\n    title: Path\n"
  },
  {
    "path": "steps/loco/0.1.2/step.yml",
    "content": "title: loco\nsummary: Upload or download translations from Loco\ndescription: This step can upload your new assets to Loco and download updated assets\n  from Loco. Importing (upload) is always done before exporting (download).\nwebsite: https://github.com/3factr/bitrise-step-loco\nsource_code_url: https://github.com/3factr/bitrise-step-loco\nsupport_url: https://github.com/3factr/bitrise-step-loco/issues\npublished_at: 2019-12-13T14:51:03.466166+01:00\nsource:\n  git: https://github.com/3factr/bitrise-step-loco.git\n  commit: ed074d7b9d25f343afb0e46a64516bf774340384\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- loco_api_key: null\n  opts:\n    description: Your Loco export key if you only want to download translations, or\n      your Loco Full access key if you want to upload new assets. You can get your\n      API key under _Developer Tools > API keys_.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your Loco export key if you only want to download translations, or your\n      Loco Full access key if you want to upload new assets.\n    title: Loco API key\n- import_file_ext: csv\n  opts:\n    category: Import\n    summary: File extension for the type of data you're importing. Required if you\n      are importing assets.\n    title: File extension\n    value_options:\n    - arb\n    - bplist\n    - csv\n    - ini\n    - json\n    - mo\n    - php\n    - plist\n    - po\n    - pot\n    - properties\n    - res\n    - resx\n    - strings\n    - tmx\n    - ts\n    - txt\n    - xlf\n    - xml\n    - yml\n- import_file_path: null\n  opts:\n    category: Import\n    summary: Path to the file that has to be imported in Loco. Required if you are\n      importing assets.\n    title: Path to imported translations\n- import_index: id\n  opts:\n    category: Import\n    summary: Specify whether translations in your file are indexed by generic IDs\n      or human-readable source text\n    title: Index type\n    value_options:\n    - id\n    - text\n- import_locale: null\n  opts:\n    category: Import\n    summary: Specify target locale if importing translations (e.g. en_US or en)\n    title: Locale\n- import_async: \"false\"\n  opts:\n    category: Import\n    summary: Specify that import should be done asynchronously (recommended for large\n      files)\n    title: Async\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_source_path: null\n  opts:\n    category: Import\n    summary: Specify original file path for source code references (excluding line\n      number)\n    title: Path\n- import_ignore_new: \"false\"\n  opts:\n    category: Import\n    summary: Specify that new assets will **NOT** be added to the project\n    title: Ignore new\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_ignore_existing: \"false\"\n  opts:\n    category: Import\n    summary: Specify that existing assets encountered in the file will NOT be updated\n    title: Ignore existing\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_delete_absent: \"false\"\n  opts:\n    category: Import\n    summary: Permanently **DELETES** project assets NOT found in the file (use with\n      extreme caution)\n    title: Delete absent\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_tag_new: null\n  opts:\n    category: Import\n    summary: Tag any NEW assets added during the import with the given tags (comma\n      separated)\n    title: Tag new\n- import_tag_all: null\n  opts:\n    category: Import\n    summary: Tag ALL assets in the file with the given tags (comma separated)\n    title: Tag all\n- import_untag_all: null\n  opts:\n    category: Import\n    summary: Remove existing tags from any assets matched in the imported file (comma\n      separated)\n    title: Untag all\n- import_tag_updated: null\n  opts:\n    category: Import\n    summary: Tag existing assets that are MODIFIED by this import\n    title: Tag updated\n- opts:\n    category: Import\n    summary: Remove existing tags from assets that are MODIFIED during import\n    title: Untag updated\n  untag_updated: null\n- import_tag_absent: null\n  opts:\n    category: Import\n    summary: Tag existing assets in the project that are NOT found in the imported\n      file\n    title: Tag absent\n- import_untag_absent: null\n  opts:\n    category: Import\n    summary: Remove existing tags from assets NOT found in the imported file\n    title: Untag absent\n- export_file_ext: all|csv\n  opts:\n    category: Export\n    description: |\n      Target file type specified as a file extension. Required if you are exporting assets.\n      * The options prepended with `all` export all your locales into a single file.\n      * The options prepended with `archive` export all your locales into a zip file that will be extracted.\n      * The options prepended with `locale` export a single locale into a single file.\n    summary: Target file type specified as a file extension. Required if you are exporting\n      assets.\n    title: File extension\n    value_options:\n    - all|json\n    - all|csv\n    - all|html\n    - all|sql\n    - all|tmx\n    - all|xlf\n    - all|yml\n    - archive|arb\n    - archive|csv\n    - archive|html\n    - archive|ini\n    - archive|json\n    - archive|mo\n    - archive|php\n    - archive|po\n    - archive|pot\n    - archive|plist\n    - archive|bplist\n    - archive|properties\n    - archive|res\n    - archive|resx\n    - archive|sql\n    - archive|strings\n    - archive|stringsdict\n    - archive|tmx\n    - archive|ts\n    - archive|txt\n    - archive|xlf\n    - archive|xliff\n    - archive|xml\n    - archive|yml\n    - locale|arb\n    - locale|csv\n    - locale|html\n    - locale|ini\n    - locale|json\n    - locale|mo\n    - locale|php\n    - locale|po\n    - locale|pot\n    - locale|plist\n    - locale|bplist\n    - locale|properties\n    - locale|res\n    - locale|resx\n    - locale|sql\n    - locale|strings\n    - locale|stringsdict\n    - locale|tmx\n    - locale|ts\n    - locale|txt\n    - locale|xlf\n    - locale|xliff\n    - locale|xml\n    - locale|yml\n- export_locale: null\n  opts:\n    category: Export\n    summary: Locale to export, specified as short code or language tag. e.g. `en`\n      or `en_GB`. Required and only valid if you selected an extension prepended with\n      `locale`.\n    title: Locale\n- export_file_path: null\n  opts:\n    category: Export\n    summary: Where the exported file should be stored. This is required when you are\n      exporting. This should be a path to a file when you are exporting a multi-locale\n      or a single-locale file. This should be a path to a directory when you are exporting\n      an archive.\n    title: File path\n- export_format: default\n  opts:\n    category: Export\n    description: |\n      More specific format of file type. E.g. `rails` applies to `yml` and `symfony` applies to `php`, `xlf` & `yml`.\n      The default format picks the most commonly used format for the file type.\n      * `json` defaults to simple JSON structure\n      * `xml` defaults to Android string resources\n      * `yml` defaults to Symfony-style flat structure\n      * `php` defaults to Zend-style array\n    summary: More specific format of file type. e.g. `rails` applies to `yml` and\n      `symfony` applies to `php`, `xlf` & `yml`.\n    title: Format\n    value_options:\n    - default\n    - rails\n    - i18next\n    - i18next3\n    - symfony\n    - zend\n    - codeigniter\n    - constants\n    - chrome\n    - nested\n    - rails\n    - java\n    - tizen\n    - jed\n    - gettext\n    - ng-gettext\n    - xcode\n    - script\n    - android\n- export_filter: null\n  opts:\n    category: Export\n    summary: Filter assets by comma-separated tag names. Match any tag with * and\n      negate tags by prefixing with !\n    title: Filter\n- export_index: id\n  opts:\n    category: Export\n    summary: Override default lookup key for the file format; `id`, `text` or a custom\n      alias\n    title: Index\n- export_source: null\n  opts:\n    category: Export\n    summary: Specify alternative source locale instead of project default\n    title: Source\n- export_fallback: null\n  opts:\n    category: Export\n    summary: Fallback locale for untranslated assets, specified as short code. e.g.\n      `en` or `en_GB`\n    title: Fallback\n- export_order: created\n  opts:\n    category: Export\n    summary: Export translations according to asset order\n    title: Order\n    value_options:\n    - created\n    - id\n- export_printf: default\n  opts:\n    category: Export\n    summary: Force alternative \"printf\" style. [See string formatting](https://localise.biz/help/developers/printf)\n    title: printf style\n    value_options:\n    - default\n    - php\n    - java\n    - objc\n    - icu\n- export_charset: UTF-8\n  opts:\n    category: Export\n    summary: Specify preferred character encoding.\n    title: Encoding\n- export_breaks: Unix\n  opts:\n    category: Export\n    summary: Force platform-specific line-endings. Default is Unix (LF) breaks.\n    title: Line-endings\n    value_options:\n    - Unix\n    - DOS\n    - Mac\n- export_no_comments: \"false\"\n  opts:\n    category: Export\n    summary: Disable rendering of redundant inline comments including the Loco banner.\n    title: No comments\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_no_folding: \"false\"\n  opts:\n    category: Export\n    summary: Protect [dot-separated](https://localise.biz/help/developers/asset-ids#folding)\n      keys so that `foo.bar` is not folded into object properties.\n    title: No folding\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_namespace: null\n  opts:\n    category: Export\n    summary: Override the project name for some language packs that use it as a key\n      prefix\n    title: Namespace\n- export_status: null\n  opts:\n    category: Export\n    summary: Export translations with a specific status or flag. Negate values by\n      prefixing with !. e.g. `translated`, or `!fuzzy`.\n    title: Status\n- export_path: null\n  opts:\n    category: Export\n    summary: Custom pattern for file paths. [See syntax](https://localise.biz/help/developers/locales/export-paths)\n    title: Path\n"
  },
  {
    "path": "steps/loco/0.1.3/step.yml",
    "content": "title: loco\nsummary: Upload or download translations from Loco\ndescription: This step can upload your new assets to Loco and download updated assets\n  from Loco. Importing (upload) is always done before exporting (download).\nwebsite: https://github.com/3factr/bitrise-step-loco\nsource_code_url: https://github.com/3factr/bitrise-step-loco\nsupport_url: https://github.com/3factr/bitrise-step-loco/issues\npublished_at: 2020-01-31T10:21:01.184659+01:00\nsource:\n  git: https://github.com/digitalrmdy/bitrise-step-loco.git\n  commit: a3a17ec35f66a026277f2cb6acd2e5185991e942\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- loco_api_key: null\n  opts:\n    description: Your Loco export key if you only want to download translations, or\n      your Loco Full access key if you want to upload new assets. You can get your\n      API key under _Developer Tools > API keys_.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your Loco export key if you only want to download translations, or your\n      Loco Full access key if you want to upload new assets.\n    title: Loco API key\n- import_file_ext: csv\n  opts:\n    category: Import\n    summary: File extension for the type of data you're importing. Required if you\n      are importing assets.\n    title: File extension\n    value_options:\n    - arb\n    - bplist\n    - csv\n    - ini\n    - json\n    - mo\n    - php\n    - plist\n    - po\n    - pot\n    - properties\n    - res\n    - resx\n    - strings\n    - tmx\n    - ts\n    - txt\n    - xlf\n    - xml\n    - yml\n- import_file_path: null\n  opts:\n    category: Import\n    summary: Path to the file that has to be imported in Loco. Required if you are\n      importing assets.\n    title: Path to imported translations\n- import_index: id\n  opts:\n    category: Import\n    summary: Specify whether translations in your file are indexed by generic IDs\n      or human-readable source text\n    title: Index type\n    value_options:\n    - id\n    - text\n- import_locale: null\n  opts:\n    category: Import\n    summary: Specify target locale if importing translations (e.g. en_US or en)\n    title: Locale\n- import_async: \"false\"\n  opts:\n    category: Import\n    summary: Specify that import should be done asynchronously (recommended for large\n      files)\n    title: Async\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_source_path: null\n  opts:\n    category: Import\n    summary: Specify original file path for source code references (excluding line\n      number)\n    title: Path\n- import_ignore_new: \"false\"\n  opts:\n    category: Import\n    summary: Specify that new assets will **NOT** be added to the project\n    title: Ignore new\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_ignore_existing: \"false\"\n  opts:\n    category: Import\n    summary: Specify that existing assets encountered in the file will NOT be updated\n    title: Ignore existing\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_delete_absent: \"false\"\n  opts:\n    category: Import\n    summary: Permanently **DELETES** project assets NOT found in the file (use with\n      extreme caution)\n    title: Delete absent\n    value_options:\n    - \"true\"\n    - \"false\"\n- import_tag_new: null\n  opts:\n    category: Import\n    summary: Tag any NEW assets added during the import with the given tags (comma\n      separated)\n    title: Tag new\n- import_tag_all: null\n  opts:\n    category: Import\n    summary: Tag ALL assets in the file with the given tags (comma separated)\n    title: Tag all\n- import_untag_all: null\n  opts:\n    category: Import\n    summary: Remove existing tags from any assets matched in the imported file (comma\n      separated)\n    title: Untag all\n- import_tag_updated: null\n  opts:\n    category: Import\n    summary: Tag existing assets that are MODIFIED by this import\n    title: Tag updated\n- opts:\n    category: Import\n    summary: Remove existing tags from assets that are MODIFIED during import\n    title: Untag updated\n  untag_updated: null\n- import_tag_absent: null\n  opts:\n    category: Import\n    summary: Tag existing assets in the project that are NOT found in the imported\n      file\n    title: Tag absent\n- import_untag_absent: null\n  opts:\n    category: Import\n    summary: Remove existing tags from assets NOT found in the imported file\n    title: Untag absent\n- export_file_ext: all|csv\n  opts:\n    category: Export\n    description: |\n      Target file type specified as a file extension. Required if you are exporting assets.\n      * The options prepended with `all` export all your locales into a single file.\n      * The options prepended with `archive` export all your locales into a zip file that will be extracted.\n      * The options prepended with `locale` export a single locale into a single file.\n    summary: Target file type specified as a file extension. Required if you are exporting\n      assets.\n    title: File extension\n    value_options:\n    - all|json\n    - all|csv\n    - all|html\n    - all|sql\n    - all|tmx\n    - all|xlf\n    - all|yml\n    - archive|arb\n    - archive|csv\n    - archive|html\n    - archive|ini\n    - archive|json\n    - archive|mo\n    - archive|php\n    - archive|po\n    - archive|pot\n    - archive|plist\n    - archive|bplist\n    - archive|properties\n    - archive|res\n    - archive|resx\n    - archive|sql\n    - archive|strings\n    - archive|stringsdict\n    - archive|tmx\n    - archive|ts\n    - archive|txt\n    - archive|xlf\n    - archive|xliff\n    - archive|xml\n    - archive|yml\n    - locale|arb\n    - locale|csv\n    - locale|html\n    - locale|ini\n    - locale|json\n    - locale|mo\n    - locale|php\n    - locale|po\n    - locale|pot\n    - locale|plist\n    - locale|bplist\n    - locale|properties\n    - locale|res\n    - locale|resx\n    - locale|sql\n    - locale|strings\n    - locale|stringsdict\n    - locale|tmx\n    - locale|ts\n    - locale|txt\n    - locale|xlf\n    - locale|xliff\n    - locale|xml\n    - locale|yml\n- export_locale: null\n  opts:\n    category: Export\n    summary: Locale to export, specified as short code or language tag. e.g. `en`\n      or `en_GB`. Required and only valid if you selected an extension prepended with\n      `locale`.\n    title: Locale\n- export_file_path: null\n  opts:\n    category: Export\n    summary: Where the exported file should be stored. This is required when you are\n      exporting. This should be a path to a file when you are exporting a multi-locale\n      or a single-locale file. This should be a path to a directory when you are exporting\n      an archive.\n    title: File path\n- export_format: default\n  opts:\n    category: Export\n    description: |\n      More specific format of file type. E.g. `rails` applies to `yml` and `symfony` applies to `php`, `xlf` & `yml`.\n      The default format picks the most commonly used format for the file type.\n      * `json` defaults to simple JSON structure\n      * `xml` defaults to Android string resources\n      * `yml` defaults to Symfony-style flat structure\n      * `php` defaults to Zend-style array\n    summary: More specific format of file type. e.g. `rails` applies to `yml` and\n      `symfony` applies to `php`, `xlf` & `yml`.\n    title: Format\n    value_options:\n    - default\n    - rails\n    - i18next\n    - i18next3\n    - symfony\n    - zend\n    - codeigniter\n    - constants\n    - chrome\n    - nested\n    - rails\n    - java\n    - tizen\n    - jed\n    - gettext\n    - ng-gettext\n    - xcode\n    - script\n    - android\n- export_filter: null\n  opts:\n    category: Export\n    summary: Filter assets by comma-separated tag names. Match any tag with * and\n      negate tags by prefixing with !\n    title: Filter\n- export_index: id\n  opts:\n    category: Export\n    summary: Override default lookup key for the file format; `id`, `text` or a custom\n      alias\n    title: Index\n- export_source: null\n  opts:\n    category: Export\n    summary: Specify alternative source locale instead of project default\n    title: Source\n- export_fallback: null\n  opts:\n    category: Export\n    summary: Fallback locale for untranslated assets, specified as short code. e.g.\n      `en` or `en_GB`\n    title: Fallback\n- export_order: created\n  opts:\n    category: Export\n    summary: Export translations according to asset order\n    title: Order\n    value_options:\n    - created\n    - id\n- export_printf: default\n  opts:\n    category: Export\n    summary: Force alternative \"printf\" style. [See string formatting](https://localise.biz/help/developers/printf)\n    title: printf style\n    value_options:\n    - default\n    - php\n    - java\n    - objc\n    - icu\n- export_charset: UTF-8\n  opts:\n    category: Export\n    summary: Specify preferred character encoding.\n    title: Encoding\n- export_breaks: Unix\n  opts:\n    category: Export\n    summary: Force platform-specific line-endings. Default is Unix (LF) breaks.\n    title: Line-endings\n    value_options:\n    - Unix\n    - DOS\n    - Mac\n- export_no_comments: \"false\"\n  opts:\n    category: Export\n    summary: Disable rendering of redundant inline comments including the Loco banner.\n    title: No comments\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_no_folding: \"false\"\n  opts:\n    category: Export\n    summary: Protect [dot-separated](https://localise.biz/help/developers/asset-ids#folding)\n      keys so that `foo.bar` is not folded into object properties.\n    title: No folding\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_namespace: null\n  opts:\n    category: Export\n    summary: Override the project name for some language packs that use it as a key\n      prefix\n    title: Namespace\n- export_status: null\n  opts:\n    category: Export\n    summary: Export translations with a specific status or flag. Negate values by\n      prefixing with !. e.g. `translated`, or `!fuzzy`.\n    title: Status\n- export_path: null\n  opts:\n    category: Export\n    summary: Custom pattern for file paths. [See syntax](https://localise.biz/help/developers/locales/export-paths)\n    title: Path\n"
  },
  {
    "path": "steps/loco/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.0.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2022-11-24T12:57:12.923142+01:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: eb77a380cdb47a3b03d4deb7373cd11f6c29bfc8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: \"\"\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: false\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: false\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.0.1/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2022-11-28T19:39:14.004128+01:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: 3f3280bf918c362f11c136559f424f678381a125\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: \"\"\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.1.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2023-01-25T22:06:55.504814+04:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: 89ca79c54c7bf8c4ea52eb4474175cdf3c6842bc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android api level the devices should run (Default: 30)'\n    title: Android api level\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated) i.e\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated)\n      i.e pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.2.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2023-06-23T13:54:22.832257+04:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: 0254bf84c0820a4fa1bd959cdc24b64bcc919ba6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android api level the devices should run on (Default: 30)'\n    title: Android api level\n- ios_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the iOS version the devices should run on (Default: 15)'\n    title: iOS version\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated) i.e\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated)\n      i.e pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.3.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2023-10-24T00:12:41.636401+02:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: c216e37aff7080969876b0c1112f8a655e08670d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android api level the devices should run on (Default: 30)'\n    title: Android api level\n- ios_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the iOS version the devices should run on (Default: 15)'\n    title: iOS version\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, i.e. de_DE for Germany.\n    is_expand: true\n    is_required: false\n    summary: 'Set the device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated) i.e\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated)\n      i.e pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.3.2/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2023-10-27T16:22:06.398227+02:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: b953a2155b704151aeb2c96bcefbe84e3284cb31\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android api level the devices should run on (Default: 30)'\n    title: Android api level\n- ios_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the iOS version the devices should run on (Default: 15)'\n    title: iOS version\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, i.e. de_DE for Germany.\n    is_expand: true\n    is_required: false\n    summary: 'Set the device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated) i.e\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated)\n      i.e pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.4.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2023-12-08T13:04:45.536326+01:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: dee3bad37edc5d02cff732d9f375bc9aa6286f1a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android api level the devices should run on (Default: 30)'\n    title: Android api level\n- ios_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the iOS version the devices should run on (Default: 15)'\n    title: iOS version\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, i.e. de_DE for Germany.\n    is_expand: true\n    is_required: false\n    summary: 'Set the device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated) i.e\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated)\n      i.e pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Minutes to timeout while waiting for results\n    title: Timeout\n  timeout: \"\"\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.5.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |\n  This steps uploads both your app binary and flows to Maestro Cloud.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2024-10-07T10:36:06.813114+02:00\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: e1a8cb12d4d669d386b27040bdc54d831f761e5a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      Maestro Cloud / Robin API key\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud / Robin API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to an x86 compatible Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android api level the devices should run on (Default: 30)'\n    title: Android api level\n- ios_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the iOS version the devices should run on (Default: 15)'\n    title: iOS version\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, i.e. de_DE for Germany.\n    is_expand: true\n    is_required: false\n    summary: 'Set the device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated) i.e\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated)\n      i.e pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository name (ie: GitHub repo slug)'\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Repository owner (ie: GitHub organization or user slug)'\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Minutes to timeout while waiting for results\n    title: Timeout\n  timeout: \"\"\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Robin Project ID\n    title: Robin Project ID\n  project_id: \"\"\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.6.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |-\n  Run your flows on [Maestro Cloud](https://app.maestro.dev/).\n\n  ## Configuration\n\n  The minimum required configuration is to provide an API key, Project ID and an app binary (an x86 compatible APK for Android, or a Simulator build packaged in a zip archive for iOS).\n\n  If your tests are anywhere but the default `.maestro` folder in the root of your project, you should set the Flow Workspace.\n\n  Full list of step options:\n\n  | Option.                   | Required | Description                                                                                                                                                   |\n  | -------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n  | API Key                    | Yes      | Maestro Cloud API key, available in [Maestro Cloud](https://app.maestro.dev)                                                                                 |\n  | Maestro Cloud Project ID   | Yes      | Which project to run the tests against                                                                                                                       |\n  | App File                   | Yes      | Path to the app file to upload.                                                                                                                              |\n  | Flow workspace             | No       | Path to Maestro flows (default: `.maestro`)                                                                                                                  |\n  | Upload Name                | No       | Friendly name of the run                                                                                                                                     |\n  | Async Mode                 | No       | Whether to start the flow and exit the action (defaults to `false`)                                                                                          |\n  | Environment variables      | No       | Environment variables to pass to the run                                                                                                                     |\n  | Android api level          | No       | The Android API level to use when running the flows                                                                                                          |\n  | Device OS                  | No       | The [device OS](https://docs.maestro.dev/cloud/reference/configuring-os-version) to use when running iOS flows (eg iOS-16-2)                                 |\n  | Device model               | No       | The [device model](https://docs.maestro.dev/cloud/reference/configuring-os-version#using-a-specific-ios-minor-version-and-device-recommended) (eg iPhone-11) |\n  | Device locale              | No       | The [device locale](https://docs.maestro.dev/cloud/reference/configuring-device-locale) to use when running the flows (eg en_US)                             |\n  | Include tags               | No       | Comma-separated list of tags to include in the run                                                                                                           |\n  | Exclude tags               | No       | Comma-separated list of tags to exclude from the run                                                                                                         |\n  | Export test report (JUnit) | No       | Generate test suite report (JUnit)                                                                                                                           |\n  | Export test output         | No       | Export test file output (Default: report.xml)                                                                                                                |\n  | Mapping File               | No       | Path to the ProGuard map (Android) or dSYM (iOS)                                                                                                             |\n  | Build branch               | No       | The branch this upload originated from                                                                                                                       |\n  | Repository name            | No       | Repository name (ie: GitHub repo slug)                                                                                                                       |\n  | Repository owner           | No       | Repository owner (ie: GitHub organization or user slug)                                                                                                      |\n  | Pull request id            | No       | The ID of the pull request this upload originated from                                                                                                       |\n  | Maestro CLI version        | No       | Maestro CLI version to be downloaded in your CI (Default: latest)                                                                                            |\n  | Timeout                    | No       | How long to wait for the run to complete when not async (defaults to 30 minutes)                                                                             |\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2025-11-18T10:44:10.269617Z\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: 9a3aa72f21142d55c8e4a406718d7fccadabfaa4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      API Key found in the Maestro Cloud web console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to a Simulator build packaged in a zip archive.\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      By default, the action is looking for a .maestro folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      \"A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed (as is the default behaviour), set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      i.e VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the Android API level the devices should run on (Default: 33)'\n    title: Android API level\n- device_os: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the device OS for iOS runs (Default: iOS-16-2)'\n    title: Device OS\n- device_model: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Set the device model for iOS runs (Default: iPhone-11)'\n    title: Device model\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, i.e. de_DE for Germany.\n    is_expand: true\n    is_required: false\n    summary: 'Set the device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated), e.g.\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated),\n      e.g. pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository name (e.g. GitHub repo slug)\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository owner (e.g. GitHub organization or user slug)\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Minutes to timeout while waiting for results\n    title: Timeout\n  timeout: \"\"\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Maestro Cloud Project ID\n    title: Maestro Cloud Project ID\n  project_id: \"\"\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.7.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |-\n  Run your flows on [Maestro Cloud](https://app.maestro.dev/).\n\n  ## Configuration\n\n  The minimum required configuration is to provide an API key, Project ID and an app binary (an x86 compatible APK for Android, or a Simulator build packaged in a zip archive for iOS).\n\n  If your tests are anywhere but the default `.maestro` folder in the root of your project, you should set the Flow Workspace.\n\n  Full list of step options:\n\n  | Name                       | Key                   | Required | Description                                                                                                                                                  |\n  | -------------------------- | --------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n  | API Key                    | `api_key`             | Yes      | Maestro Cloud API key, available in [Maestro Cloud](https://app.maestro.dev)                                                                                 |\n  | Maestro Cloud Project ID   | `project_id`          | Yes      | Which project to run the tests against                                                                                                                       |\n  | App File                   | `app_file`            | No       | Path to the app file to upload. This, or App Binary ID, must be provided.                                                                                    |\n  | App Binary ID              | `app_binary_id`.      | No       | The unique identifier of the app binary in Maestro Cloud. This, or App File, must be provided.                                                               |\n  | Flow workspace             | `workspace`           | No       | Path to Maestro flows (default: `.maestro`)                                                                                                                  |\n  | Upload Name                | `upload_name`         | No       | Friendly name of the run                                                                                                                                     |\n  | Async Mode                 | `async`               | No       | Whether to start the flow and exit the action (defaults to `false`)                                                                                          |\n  | Environment variables      | `env`                 | No       | Environment variables to pass to the run                                                                                                                     |\n  | Android API level          | `android_api_level`   | No       | The Android API level to use when running the flows                                                                                                          |\n  | Device OS                  | `device_os`           | No       | The [device OS](https://docs.maestro.dev/cloud/reference/configuring-os-version) to use when running iOS flows (eg iOS-16-2)                                 |\n  | Device model               | `device_model`        | No       | The [device model](https://docs.maestro.dev/cloud/reference/configuring-os-version#using-a-specific-ios-minor-version-and-device-recommended) (eg iPhone-11) |\n  | Device locale              | `device_locale`       | No       | The [device locale](https://docs.maestro.dev/cloud/reference/configuring-device-locale) to use when running the flows (eg en_US)                             |\n  | Include tags               | `include_tags`        | No       | Comma-separated list of tags to include in the run                                                                                                           |\n  | Exclude tags               | `exclude_tags`        | No       | Comma-separated list of tags to exclude from the run                                                                                                         |\n  | Export test report (JUnit) | `export_test_report`  | No       | Generate test suite report (JUnit)                                                                                                                           |\n  | Export test output         | `export_output`       | No       | Export test file output (Default: report.xml)                                                                                                                |\n  | Mapping File               | `mapping_file`        | No       | Path to the ProGuard map (Android) or dSYM (iOS)                                                                                                             |\n  | Build branch               | `branch`              | No       | The branch this upload originated from                                                                                                                       |\n  | Repository name            | `repo_name`           | No       | Repository name (ie: GitHub repo slug)                                                                                                                       |\n  | Repository owner           | `repo_owner`          | No       | Repository owner (ie: GitHub organization or user slug)                                                                                                      |\n  | Pull request ID            | `pull_request_id`     | No       | The ID of the pull request this upload originated from                                                                                                       |\n  | Maestro CLI version        | `maestro_cli_version` | No       | Maestro CLI version to be downloaded in your CI (Default: latest)                                                                                            |\n  | Timeout                    | `timeout`             | No       | How long to wait for the run to complete when not async (defaults to 30 minutes)                                                                             |\n  | Debug Mode                 | `debug_mode`          | No       | Prints shell commands as they execute. Set to any non-blank value to enable.                                                                                 |\n\n  See the [Changelog](https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/blob/main/CHANGELOG.md) for recent updates.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2025-11-26T15:01:25.842627Z\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: abebcd2049f6c9fbbd36300ac72a124b5ba0c26f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      API Key found in the Maestro Cloud web console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- opts:\n    description: Project ID found in the Maestro Cloud console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    summary: Maestro Cloud Project ID\n    title: Maestro Cloud Project ID\n  project_id: \"\"\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to a Simulator build packaged in a zip archive. An App File or App Binary ID must be provided.\n    is_expand: true\n    is_required: false\n    summary: App binary to run your Flows against\n    title: App File\n- app_binary_id: \"\"\n  opts:\n    description: |\n      The unique identifier of a previously uploaded app binary in Maestro Cloud. An App File or App Binary ID must be provided.\n    is_expand: true\n    is_required: false\n    summary: The unique identifier of the app binary in Maestro Cloud\n    title: App Binary ID\n- opts:\n    description: |\n      By default, the action is looking for a `.maestro` folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed (as is the default behaviour), set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      e.g. VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'The Android API level the devices should run (Default: 33)'\n    title: Android API level\n- device_os: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'The device OS for iOS runs (Default: iOS-16-2)'\n    title: Device OS\n- device_model: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'The device model for iOS runs (Default: iPhone-11)'\n    title: Device model\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, e.g. de_DE for Germany. Note that this sets locale, but\n      not location.\n    is_expand: true\n    is_required: false\n    summary: 'The device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated), e.g.\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated),\n      e.g. pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository name (e.g. GitHub repo slug)\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository owner (e.g. GitHub organization or user slug)\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be used in executing your Bitrise workflow (Default:\n      latest)'\n    title: Maestro CLI version\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Minutes to timeout while waiting for results\n    title: Timeout\n  timeout: \"\"\n- debug_mode: \"\"\n  opts:\n    description: \"\"\n    is_expand: false\n    is_required: false\n    summary: Print shell commands as they execute, for debugging purposes\n    title: Debug Mode\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.8.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |-\n  Run your flows on [Maestro Cloud](https://app.maestro.dev/).\n\n  ## Configuration\n\n  The minimum required configuration is to provide an API key, Project ID and an app binary (an x86 compatible APK for Android, or a Simulator build packaged in a zip archive for iOS).\n\n  If your tests are anywhere but the default `.maestro` folder in the root of your project, you should set the Flow Workspace.\n\n  Full list of step options:\n\n  | Name                       | Key                   | Required | Description                                                                                                                                                  |\n  | -------------------------- | --------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n  | API Key                    | `api_key`             | Yes      | Maestro Cloud API key, available in [Maestro Cloud](https://app.maestro.dev)                                                                                 |\n  | Maestro Cloud Project ID   | `project_id`          | Yes      | Which project to run the tests against                                                                                                                       |\n  | App File                   | `app_file`            | No       | Path to the app file to upload. This, or App Binary ID, must be provided.                                                                                    |\n  | App Binary ID              | `app_binary_id`.      | No       | The unique identifier of the app binary in Maestro Cloud. This, or App File, must be provided.                                                               |\n  | Flow workspace             | `workspace`           | No       | Path to Maestro flows (default: `.maestro`)                                                                                                                  |\n  | Upload Name                | `upload_name`         | No       | Friendly name of the run                                                                                                                                     |\n  | Async Mode                 | `async`               | No       | Whether to start the flow and exit the action (defaults to `false`)                                                                                          |\n  | Environment variables      | `env`                 | No       | Environment variables to pass to the run                                                                                                                     |\n  | Android API level          | `android_api_level`   | No       | The Android API level to use when running the flows                                                                                                          |\n  | Device OS                  | `device_os`           | No       | The [device OS](https://docs.maestro.dev/cloud/reference/configuring-os-version) to use when running iOS flows (eg iOS-16-2)                                 |\n  | Device model               | `device_model`        | No       | The [device model](https://docs.maestro.dev/cloud/reference/configuring-os-version#using-a-specific-ios-minor-version-and-device-recommended) (eg iPhone-11) |\n  | Device locale              | `device_locale`       | No       | The [device locale](https://docs.maestro.dev/cloud/reference/configuring-device-locale) to use when running the flows (eg en_US)                             |\n  | Include tags               | `include_tags`        | No       | Comma-separated list of tags to include in the run                                                                                                           |\n  | Exclude tags               | `exclude_tags`        | No       | Comma-separated list of tags to exclude from the run                                                                                                         |\n  | Export test report (JUnit) | `export_test_report`  | No       | Generate test suite report (JUnit)                                                                                                                           |\n  | Export test output         | `export_output`       | No       | Export test file output (Default: report.xml)                                                                                                                |\n  | Mapping File               | `mapping_file`        | No       | Path to the ProGuard map (Android) or dSYM (iOS)                                                                                                             |\n  | Build branch               | `branch`              | No       | The branch this upload originated from                                                                                                                       |\n  | Repository name            | `repo_name`           | No       | Repository name (ie: GitHub repo slug)                                                                                                                       |\n  | Repository owner           | `repo_owner`          | No       | Repository owner (ie: GitHub organization or user slug)                                                                                                      |\n  | Pull request ID            | `pull_request_id`     | No       | The ID of the pull request this upload originated from                                                                                                       |\n  | Maestro CLI version        | `maestro_cli_version` | No       | Maestro CLI version to be downloaded in your CI (Default: latest)                                                                                            |\n  | Timeout                    | `timeout`             | No       | How long to wait for the run to complete when not async (defaults to 30 minutes)                                                                             |\n  | Debug Mode                 | `debug_mode`          | No       | Prints shell commands as they execute. Set to any non-blank value to enable.                                                                                 |\n\n  ## Outputs\n\n  | Name                        | Key                            | Description                                                                                               |\n  | --------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------- |\n  | Maestro Cloud App Binary ID | `MAESTRO_CLOUD_APP_BINARY_ID`  | The unique identifier of the uploaded app binary — can be reused in future uploads to skip re-uploading.  |\n  | Maestro Cloud Run URL       | `MAESTRO_CLOUD_RUN_URL`        | The URL to view this test run in Maestro Cloud.                                                           |\n\n  See the [Changelog](https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/blob/main/CHANGELOG.md) for recent updates.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2026-03-18T11:57:50.465915Z\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: e57b5d91518f7a1477dd0e7acd4db2e88a78456c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      API Key found in the Maestro Cloud web console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- opts:\n    description: Project ID found in the Maestro Cloud console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    summary: Maestro Cloud Project ID\n    title: Maestro Cloud Project ID\n  project_id: \"\"\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to a Simulator build packaged in a zip archive. An App File or App Binary ID must be provided.\n    is_expand: true\n    is_required: false\n    summary: App binary to run your Flows against\n    title: App File\n- app_binary_id: \"\"\n  opts:\n    description: |\n      The unique identifier of a previously uploaded app binary in Maestro Cloud. An App File or App Binary ID must be provided.\n    is_expand: true\n    is_required: false\n    summary: The unique identifier of the app binary in Maestro Cloud\n    title: App Binary ID\n- opts:\n    description: |\n      By default, the action is looking for a `.maestro` folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed (as is the default behaviour), set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      e.g. VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'The Android API level the devices should run (Default: 33)'\n    title: Android API level\n- device_os: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'The device OS for iOS runs (Default: iOS-16-2)'\n    title: Device OS\n- device_model: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'The device model for iOS runs (Default: iPhone-11)'\n    title: Device model\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, e.g. de_DE for Germany. Note that this sets locale, but\n      not location.\n    is_expand: true\n    is_required: false\n    summary: 'The device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated), e.g.\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated),\n      e.g. pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository name (e.g. GitHub repo slug)\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository owner (e.g. GitHub organization or user slug)\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be used in executing your Bitrise workflow (Default:\n      latest)'\n    title: Maestro CLI version\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Minutes to timeout while waiting for results\n    title: Timeout\n  timeout: \"\"\n- debug_mode: \"\"\n  opts:\n    description: \"\"\n    is_expand: false\n    is_required: false\n    summary: Print shell commands as they execute, for debugging purposes\n    title: Debug Mode\noutputs:\n- MAESTRO_CLOUD_APP_BINARY_ID: \"\"\n  opts:\n    description: |\n      The unique identifier of the uploaded app binary - can be used in future uploads to avoid reuploading.\n    is_expand: false\n    summary: The App Binary ID reported by Maestro Cloud after upload\n    title: Maestro Cloud App Binary ID\n- MAESTRO_CLOUD_RUN_URL: \"\"\n  opts:\n    description: |\n      The URL to view this test run in Maestro Cloud.\n    is_expand: false\n    summary: The Maestro Cloud URL for this upload\n    title: Maestro Cloud Run URL\n"
  },
  {
    "path": "steps/maestro-cloud-upload/1.9.0/step.yml",
    "content": "title: Upload to Maestro Cloud\nsummary: |\n  Upload your app binary to Maestro Cloud and run your flows\ndescription: |-\n  Run your flows on [Maestro Cloud](https://app.maestro.dev/).\n\n  ## Configuration\n\n  The minimum required configuration is to provide an API key, Project ID and an app binary (an x86 compatible APK for Android, or a Simulator build packaged in a zip archive for iOS).\n\n  If your tests are anywhere but the default `.maestro` folder in the root of your project, you should set the Flow Workspace.\n\n  Full list of step options:\n\n  | Name                       | Key                   | Required | Description                                                                                                                                                  |\n  | -------------------------- | --------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n  | API Key                    | `api_key`             | Yes      | Maestro Cloud API key, available in [Maestro Cloud](https://app.maestro.dev)                                                                                 |\n  | Maestro Cloud Project ID   | `project_id`          | Yes      | Which project to run the tests against                                                                                                                       |\n  | App File                   | `app_file`            | No       | Path to the app file to upload. This, or App Binary ID, must be provided.                                                                                    |\n  | App Binary ID              | `app_binary_id`.      | No       | The unique identifier of the app binary in Maestro Cloud. This, or App File, must be provided.                                                               |\n  | Flow workspace             | `workspace`           | No       | Path to Maestro flows (default: `.maestro`)                                                                                                                  |\n  | Upload Name                | `upload_name`         | No       | Friendly name of the run                                                                                                                                     |\n  | Async Mode                 | `async`               | No       | Whether to start the flow and exit the action (defaults to `false`)                                                                                          |\n  | Environment variables      | `env`                 | No       | Environment variables to pass to the run                                                                                                                     |\n  | Android API level          | `android_api_level`   | No       | **Deprecated.** Use `device_os` instead (e.g. `android-33`).                                                                                                 |\n  | Device OS                  | `device_os`           | No       | The [device OS version](https://docs.maestro.dev/cloud/reference/configuring-os-version) to use. iOS: `iOS-18-2`, `iOS-26-2`, etc. Android: `android-33`, `android-34`, etc. |\n  | Device model               | `device_model`        | No       | The [device model](https://docs.maestro.dev/cloud/reference/configuring-os-version#using-a-specific-ios-minor-version-and-device-recommended). iOS: `iPhone-11`, `iPhone-17-Pro`, etc. Android: `pixel_6`, `pixel_7`, etc. |\n  | Device locale              | `device_locale`       | No       | The [device locale](https://docs.maestro.dev/cloud/reference/configuring-device-locale) to use when running the flows (eg en_US)                             |\n  | Include tags               | `include_tags`        | No       | Comma-separated list of tags to include in the run                                                                                                           |\n  | Exclude tags               | `exclude_tags`        | No       | Comma-separated list of tags to exclude from the run                                                                                                         |\n  | Export test report (JUnit) | `export_test_report`  | No       | Generate test suite report (JUnit)                                                                                                                           |\n  | Export test output         | `export_output`       | No       | Export test file output (Default: report.xml)                                                                                                                |\n  | Mapping File               | `mapping_file`        | No       | Path to the ProGuard map (Android) or dSYM (iOS)                                                                                                             |\n  | Build branch               | `branch`              | No       | The branch this upload originated from                                                                                                                       |\n  | Repository name            | `repo_name`           | No       | Repository name (ie: GitHub repo slug)                                                                                                                       |\n  | Repository owner           | `repo_owner`          | No       | Repository owner (ie: GitHub organization or user slug)                                                                                                      |\n  | Pull request ID            | `pull_request_id`     | No       | The ID of the pull request this upload originated from                                                                                                       |\n  | Maestro CLI version        | `maestro_cli_version` | No       | Maestro CLI version to be downloaded in your CI (Default: latest)                                                                                            |\n  | Timeout                    | `timeout`             | No       | How long to wait for the run to complete when not async (defaults to 30 minutes)                                                                             |\n  | Debug Mode                 | `debug_mode`          | No       | Prints shell commands as they execute. Set to any non-blank value to enable.                                                                                 |\n\n  ## Outputs\n\n  | Name                        | Key                            | Description                                                                                               |\n  | --------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------- |\n  | Maestro Cloud App Binary ID | `MAESTRO_CLOUD_APP_BINARY_ID`  | The unique identifier of the uploaded app binary — can be reused in future uploads to skip re-uploading.  |\n  | Maestro Cloud Run URL       | `MAESTRO_CLOUD_RUN_URL`        | The URL to view this test run in Maestro Cloud.                                                           |\n\n  See the [Changelog](https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/blob/main/CHANGELOG.md) for recent updates.\nwebsite: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsource_code_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload\nsupport_url: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload/issues\npublished_at: 2026-05-01T17:24:16.180138+05:30\nsource:\n  git: https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-upload.git\n  commit: b9673786ac74535f540b61cfbb17dcf39429e5bd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |\n      API Key found in the Maestro Cloud web console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Maestro Cloud API key\n    title: API Key\n- opts:\n    description: Project ID found in the Maestro Cloud console (https://app.maestro.dev/)\n    is_expand: true\n    is_required: true\n    summary: Maestro Cloud Project ID\n    title: Maestro Cloud Project ID\n  project_id: \"\"\n- app_file: \"\"\n  opts:\n    description: |\n      **Android**: `app_file` should point to an x86 compatible APK file. **iOS**: `app_file` should point to a Simulator build packaged in a zip archive. An App File or App Binary ID must be provided.\n    is_expand: true\n    is_required: false\n    summary: App binary to run your Flows against\n    title: App File\n- app_binary_id: \"\"\n  opts:\n    description: |\n      The unique identifier of a previously uploaded app binary in Maestro Cloud. An App File or App Binary ID must be provided.\n    is_expand: true\n    is_required: false\n    summary: The unique identifier of the app binary in Maestro Cloud\n    title: App Binary ID\n- opts:\n    description: |\n      By default, the action is looking for a `.maestro` folder with Maestro flows in the root directory of the project.\n       If you would like to customize this behaviour, you can override it with a workspace argument\"\n    is_expand: true\n    is_required: false\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- opts:\n    description: |\n      A name will automatically be provided according to the following order:\n        - If it is a Pull Request, use Pull Request title as name\n        - If it is a normal push, use commit message as name\n        - If for some reason the commit message is not available, use the commit SHA as name\n        - If you want to override this behaviour and specify your own name, you can do so by setting the name argument\n    is_expand: true\n    is_required: false\n    summary: Custom upload name\n    title: Upload Name\n  upload_name: $BITRISE_GIT_MESSAGE\n- async: false\n  opts:\n    description: |\n      If you don't want the action to wait until the Upload has been completed (as is the default behaviour), set the async argument to true\n    is_expand: true\n    is_required: false\n    summary: Run in async mode\n    title: Async Mode\n- env: \"\"\n  opts:\n    description: |\n      If you want to pass environment variables along with your upload, add variables separated by a new line or **\\n**.\n      e.g. VAR1=1\\nVAR2=2 ...\n    is_expand: true\n    is_required: false\n    summary: Pass environment variables to your flows\n    title: Environment variables\n- android_api_level: \"\"\n  opts:\n    description: |\n      **Deprecated.** This input will be removed in a future release. Use `device_os` instead (e.g. `android-33`).\n    is_expand: true\n    is_required: false\n    summary: Deprecated. Use `device_os` instead (e.g. android-33).\n    title: Android API level (Deprecated)\n- device_os: \"\"\n  opts:\n    description: |\n      OS version to run your flows on.\n      - iOS examples: `iOS-16-2`, `iOS-18-2`, `iOS-26-2`\n      - Android examples: `android-33`, `android-34`\n    is_expand: true\n    is_required: false\n    summary: 'OS version to run on. iOS: iOS-16-2, iOS-18-2, iOS-26-2 etc. Android:\n      android-33, android-34, etc.'\n    title: Device OS\n- device_model: \"\"\n  opts:\n    description: |\n      Device model to run your flows on.\n      - iOS examples: `iPhone-11`, `iPhone-17-Pro`\n      - Android examples: `pixel_6`, `pixel_7`\n    is_expand: true\n    is_required: false\n    summary: 'Device model. iOS: iPhone-11, iPhone-17-Pro, etc. Android: pixel_6,\n      pixel_7, etc.'\n    title: Device model\n- device_locale: \"\"\n  opts:\n    description: A combination of lowercase ISO-639-1 code and uppercase ISO-3166-1\n      code should be used, e.g. de_DE for Germany. Note that this sets locale, but\n      not location.\n    is_expand: true\n    is_required: false\n    summary: 'The device locale (Default: en_US)'\n    title: Device locale\n- include_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Run only flows that contain the specified tags (comma separated), e.g.\n      dev,pull-request\n    title: Include tags\n- exclude_tags: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Exclude flows from running with the specified tags (comma separated),\n      e.g. pull-request,experimental\n    title: Exclude tags\n- export_test_report: \"false\"\n  opts:\n    description: \"\"\n    is_required: false\n    summary: Generate test suite report (JUnit)\n    title: Export test report (JUnit)\n    value_options:\n    - \"true\"\n    - \"false\"\n- export_output: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Export test file output (Default: report.xml)'\n    title: Export test output\n- mapping_file: \"\"\n  opts:\n    description: |\n      **Android**: Include the Proguard mapping file to deobfuscate Android performance traces.\n      **iOS**: Include the generated .dSYM file (unique per build)\n    is_expand: true\n    is_required: false\n    summary: dSYM file (iOS) or Proguard mapping file (Android)\n    title: Mapping File\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The branch this upload originated from\n    title: Build branch\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository name (e.g. GitHub repo slug)\n    title: Repository name\n  repo_name: $BITRISEIO_GIT_REPOSITORY_SLUG\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Repository owner (e.g. GitHub organization or user slug)\n    title: Repository owner\n  repo_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: The ID of the pull request this upload originated from\n    title: Pull request id\n  pull_request_id: $BITRISE_PULL_REQUEST\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be used in executing your Bitrise workflow (Default:\n      latest)'\n    title: Maestro CLI version\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Minutes to timeout while waiting for results\n    title: Timeout\n  timeout: \"\"\n- debug_mode: \"\"\n  opts:\n    description: \"\"\n    is_expand: false\n    is_required: false\n    summary: Print shell commands as they execute, for debugging purposes\n    title: Debug Mode\noutputs:\n- MAESTRO_CLOUD_APP_BINARY_ID: \"\"\n  opts:\n    description: |\n      The unique identifier of the uploaded app binary - can be used in future uploads to avoid reuploading.\n    is_expand: false\n    summary: The App Binary ID reported by Maestro Cloud after upload\n    title: Maestro Cloud App Binary ID\n- MAESTRO_CLOUD_RUN_URL: \"\"\n  opts:\n    description: |\n      The URL to view this test run in Maestro Cloud.\n    is_expand: false\n    summary: The Maestro Cloud URL for this upload\n    title: Maestro Cloud Run URL\n"
  },
  {
    "path": "steps/maestro-cloud-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/maestro-ios-test-run/0.0.1/step.yml",
    "content": "title: Run iOS Maestro Flows\nsummary: |\n  Runs Maestro Flows on iOS Simulator\ndescription: |\n  This steps runs your Maestro Flows on iOS Simulator and exports a test report and a video recording.\n    This step does not give any output but puts test results in deploy folder if requested.\nwebsite: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git\nsource_code_url: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git\nsupport_url: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git/issues\npublished_at: 2023-02-28T09:14:44.333686+03:00\nsource:\n  git: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git\n  commit: 108f1f012ff913206206c6282c3e60a93604cd39\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_file: \"\"\n  opts:\n    description: \"**iOS**: `app_file` should point to an x86 compatible Simulator\n      build packaged as an **.app**. \\n  **Hint:** Output Varaible `$BITRISE_APP_DIR_PATH`\n      from **Xcode Build for Simulator** step can be used. \\n\"\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      A single maestro flow file or directroy that includes Maestro Flows.\n    is_expand: true\n    is_required: true\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- additional_params: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Additional parameters of Maestro CLI command i.e --include-tags=dev,pull-request\n    title: Additional Maestro Parameters\n- export_test_report: \"true\"\n  opts:\n    description: Exports Test Report to Bitrise Test Result Page and Deploy Dir. Report\n      and video will be available for download as artifacts.\n    is_required: false\n    summary: Generate test suite report (JUnit) and video(mp4)\n    title: Export test report (JUnit) and Video(mp4) to Deploy Directory\n    value_options:\n    - \"true\"\n    - \"false\"\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n"
  },
  {
    "path": "steps/maestro-ios-test-run/0.0.2/step.yml",
    "content": "title: Run iOS Maestro Flows\nsummary: |\n  Runs Maestro Flows on iOS Simulator\ndescription: |\n  This steps runs your Maestro Flows on iOS Simulator and exports a test report and a video recording.\n    This step does not give any output but puts test results in deploy folder if requested.\nwebsite: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git\nsource_code_url: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git\nsupport_url: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git/issues\npublished_at: 2025-05-26T13:31:18.035246+03:00\nsource:\n  git: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run.git\n  commit: 3d3e50c9c5a2ae4de6571df270f957ea5ff35e90\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_file: \"\"\n  opts:\n    description: \"**iOS**: `app_file` should point to an x86 compatible Simulator\n      build packaged as an **.app**. \\n  **Hint:** Output Varaible `$BITRISE_APP_DIR_PATH`\n      from **Xcode Build for Simulator** step can be used. \\n\"\n    is_expand: true\n    is_required: true\n    summary: App binary to run your Flows against\n    title: App File\n- opts:\n    description: |\n      A single maestro flow file or directroy that includes Maestro Flows.\n    is_expand: true\n    is_required: true\n    summary: Flow file or directory\n    title: Flow workspace\n  workspace: .maestro\n- additional_params: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: Additional parameters of Maestro CLI command i.e --include-tags=dev,pull-request\n    title: Additional Maestro Parameters\n- export_test_report: \"true\"\n  opts:\n    description: Exports Test Report to Bitrise Test Result Page and Deploy Dir. Report\n      and video will be available for download as artifacts.\n    is_required: false\n    summary: Generate test suite report (JUnit) and video(mp4)\n    title: Export test report (JUnit) and Video(mp4) to Deploy Directory\n    value_options:\n    - \"true\"\n    - \"false\"\n- maestro_cli_version: \"\"\n  opts:\n    description: \"\"\n    is_expand: true\n    is_required: false\n    summary: 'Maestro CLI version to be downloaded in your CI (Default: latest)'\n    title: Maestro CLI version\n"
  },
  {
    "path": "steps/maestro-ios-test-run/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/magic-pod/0.54.1/step.yml",
    "content": "title: Magic Pod\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on Magic Pod (https://magic-pod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2020-06-02T22:24:46.286263+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: 3503680420460bbd2ab75446c2f6da2767e19df3\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on Magic Pod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magic-pod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on Magic Pod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to Magic\n      Pod cloud and can be seen by project members.*\\n* For iOS simulator testing,\n      specify the directory _xx.app_ so that included files are automatically ziped\n      into one file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://magic-pod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGIC_POD_TEST_SUCCEEDED\n- MAGIC_POD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://magic-pod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGIC_POD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/0.65.1/step.yml",
    "content": "title: Magic Pod\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on Magic Pod (https://magic-pod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2020-11-05T16:48:29.202842+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: 447853bb7409859be9db3f0ad0ce232753c6e9ed\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on Magic Pod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magic-pod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on Magic Pod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to Magic\n      Pod cloud and can be seen by project members.*\\n* For iOS simulator testing,\n      specify the directory _xx.app_ so that included files are automatically ziped\n      into one file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://magic-pod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGIC_POD_TEST_SUCCEEDED\n- MAGIC_POD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://magic-pod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGIC_POD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/0.95.1/step.yml",
    "content": "title: MagicPod\nsummary: |\n  MagicPod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on MagicPod (https://magic-pod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2022-01-27T13:38:45.94827+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: 5d9c87ba5cc94d12e078b99a91d042387f5528fa\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use MagicPod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: MagicPod API token\n- opts:\n    description: |-\n      Organization name in MagicPod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in MagicPod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on MagicPod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magicpod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on MagicPod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to MagicPod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until MagicPod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://magic-pod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: MagicPod web API URL\noutputs:\n- MAGIC_POD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGIC_POD_TEST_SUCCEEDED\n- MAGIC_POD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://magic-pod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGIC_POD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/0.99.24/step.yml",
    "content": "title: MagicPod\nsummary: |\n  MagicPod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on MagicPod (https://magicpod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2023-03-01T11:46:59.864159+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: 125741337df7e46a825dd9a5228ff1bf4217590b\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use MagicPod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://app.magicpod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: MagicPod API token\n- opts:\n    description: |-\n      Organization name in MagicPod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in MagicPod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on MagicPod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magicpod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on MagicPod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to MagicPod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until MagicPod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://app.magicpod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: MagicPod web API URL\noutputs:\n- MAGIC_POD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGIC_POD_TEST_SUCCEEDED\n- MAGIC_POD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://app.magicpod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGIC_POD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/0.99.40/step.yml",
    "content": "title: MagicPod\nsummary: |\n  MagicPod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on MagicPod (https://magicpod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2023-11-14T16:39:09.605837+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: 55bda535880980724521cb8a123040e189072ad6\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use MagicPod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://app.magicpod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: MagicPod API token\n- opts:\n    description: |-\n      Organization name in MagicPod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in MagicPod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on MagicPod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magicpod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on MagicPod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to MagicPod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until MagicPod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://app.magicpod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: MagicPod web API URL\noutputs:\n- MAGIC_POD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGIC_POD_TEST_SUCCEEDED\n- MAGIC_POD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://app.magicpod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGIC_POD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/0.99.7/step.yml",
    "content": "title: MagicPod\nsummary: |\n  MagicPod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on MagicPod (https://magicpod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2022-08-04T18:30:13.177708+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: 0ba52cb6c77f9ac9dee2298f4d9ed0cebf55da92\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use MagicPod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://app.magicpod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: MagicPod API token\n- opts:\n    description: |-\n      Organization name in MagicPod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in MagicPod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on MagicPod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magicpod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on MagicPod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to MagicPod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until MagicPod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://app.magicpod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: MagicPod web API URL\noutputs:\n- MAGIC_POD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGIC_POD_TEST_SUCCEEDED\n- MAGIC_POD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://app.magicpod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGIC_POD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/1.38.0/step.yml",
    "content": "title: MagicPod\nsummary: |\n  MagicPod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on MagicPod (https://magicpod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2025-05-21T10:31:57.827362+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: a16c6c0fe7535b29ffff8b51439157ca27a46d51\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magicpod_api_token: null\n  opts:\n    description: \"Access token to use MagicPod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGICPOD_API_TOKEN`\\n* Value: API token copied from https://app.magicpod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: MagicPod API token\n- opts:\n    description: |-\n      Organization name in MagicPod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in MagicPod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on MagicPod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magicpod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on MagicPod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to MagicPod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until MagicPod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://app.magicpod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: MagicPod web API URL\noutputs:\n- MAGICPOD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGICPOD_TEST_SUCCEEDED\n- MAGICPOD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://app.magicpod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGICPOD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/1.60.0/step.yml",
    "content": "title: MagicPod\nsummary: |\n  MagicPod UI test step\ndescription: |\n  You can execute E2E testing of iOS/Android apps on MagicPod (https://magicpod.com).\nwebsite: https://github.com/magic-Pod/bitrise-step-magic-pod\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magic-pod\nsupport_url: https://github.com/magic-Pod/bitrise-step-magic-pod/issues\npublished_at: 2026-04-01T16:20:15.368352+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magic-pod.git\n  commit: c7488c255c0a7ec6a8414a409ca200310b279450\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magic-pod\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magicpod_api_token: null\n  opts:\n    description: \"Access token to use MagicPod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGICPOD_API_TOKEN`\\n* Value: API token copied from https://app.magicpod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: MagicPod API token\n- opts:\n    description: |-\n      Organization name in MagicPod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in MagicPod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- opts:\n    description: Test settings number specified on MagicPod project batch run page.\n    is_required: false\n    title: Test settings number\n  test_settings_number: \"1\"\n- opts:\n    category: detail\n    description: |-\n      If you would like to define test settings from scratch or overwrite pre-defined test settings, please specify this parameter.\n      You can generate an example JSON on your project's batch run page (Setting -> menu -> Advanced -> Copy as magicpod-api-client (detailed settings))\n    is_required: false\n    title: Test settings\n  test_settings: null\n- branch_name: null\n  opts:\n    description: Branch name to be specified when executing batch run on a branch.\n      This is optional.\n    is_expand: true\n    is_required: false\n    title: Branch name\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Path to app (apk/app/ipa) file you want to test.\\nNote that you\n      need to select _App file (cloud upload)_ for _App Type_ on MagicPod project\n      batch run page.\\n* *Warning: The file of the specified path is uploaded to MagicPod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- opts:\n    description: |-\n      If set to true, this step waits until MagicPod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: Wait limit in seconds. If 0 is specified, the value is test count\n      x 10 minutes.\n    title: Wait limit\n  wait_limit: \"0\"\n- delete_app_after_test: Not delete\n  opts:\n    description: |-\n      Define how to treat the uploaded app file after the test.\n      This option is valid only when you specify _App path_.\n    title: Delete app after test\n    value_options:\n    - Not delete\n    - Always delete\n    - Delete only when tests succeeded\n- base_url: https://app.magicpod.com\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: MagicPod web API URL\noutputs:\n- MAGICPOD_TEST_SUCCEEDED: null\n  opts:\n    summary: This variable becomes 'true' only when all batch runs succeeded, otherwise\n      'false'.\n    title: MAGICPOD_TEST_SUCCEEDED\n- MAGICPOD_TEST_RESULT: null\n  opts:\n    summary: |-\n      Array which contains status/URL information of all batch runs.  The format is like\n      [{\"Url\":\"https://app.magicpod.com/ORG_NAME/PRJ_NAME/batch-run/10/\",\"Status\":\"failed\",\"Batch_Run_Number\":10,\"Test_Cases\":{\"Succeeded\":3,\"Failed\":1,\"Aborted\":0,\"Unresolved\":0,\"Total\":4}}]\n    title: MAGICPOD_TEST_RESULT\n"
  },
  {
    "path": "steps/magic-pod/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/magicpod-ui-test/0.1.0/step.yml",
    "content": "title: Magic Pod UI test\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  Magic Pod UI test step\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2019-03-07T09:28:43.872845+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magicpod-uitest.git\n  commit: cf970756d28be9a6ecad5e6a1867a8696170f967\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: |-\n      Access token to use Magic Pod Web API.\n\n      Please refer to https://magic-pod.com/accounts/api-token/ for detail.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sured to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sured to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- environment: Magic Pod\n  opts:\n    description: |-\n      Environment (cloud service) on which you want to execute your tests.\n      Each environment has its own limitation of OS/devices.  Please refer to project batch runs page for available choices.\n    is_expand: true\n    is_required: true\n    title: Environment\n    value_options:\n    - Magic Pod\n    - Remote TestKit\n- external_service_token: null\n  opts:\n    description: |-\n      Access token to use external cloud services (ex. Remote TestKit) for testing.\n      Required when you have selected **other than Magic Pod** for _Environment_.\n    is_expand: true\n    is_sensitive: true\n    title: External service token\n- opts:\n    description: \"Currently you can select only \\n\\n* _iOS_ for Magic Pod cloud service.\\n*\n      _Android_ for Remote TestKit.\"\n    is_expand: true\n    is_required: true\n    title: OS\n    value_options:\n    - iOS\n    - Android\n  os: iOS\n- device_type: Simulator\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _Simulator_ for Magic Pod cloud service.\n      * _Real Device_ for Remote TestKit.\n    is_expand: true\n    is_required: true\n    title: Device type\n    value_options:\n    - Simulator\n    - Emulator\n    - Real Device\n- opts:\n    description: \"Currently you can select only \\n\\n* _12.1_ for Magic Pod cloud service.\"\n    is_expand: true\n    is_required: true\n    title: Version\n  version: \"12.1\"\n- model: iPhone 8\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _iPhone 8_ for Magic Pod cloud service.\n      * For Remote TestKit, please refer to model list on https://appkitbox.com/testkit/devicelist/.\n    is_expand: true\n    is_required: true\n    title: Model\n- app_type: App file (cloud upload)\n  opts:\n    description: |-\n      Specify how you submit your app to the cloud.\n\n      * When you select _App file (cloud upload)_, then fill in _App path_ field below.\n      * When you select _App file (URL)_, then fill in _App URL_ field below.\n      * When you select _Installed app_, then fill in _Bundle ID_ field for iOS, or _App package_ and _App activity_ for Android.\n    is_expand: true\n    is_required: true\n    title: App type\n    value_options:\n    - App file (cloud upload)\n    - App file (URL)\n    - Installed app\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Required when you have selected _App file (cloud upload)_ for _App\n      type_.\\n\\n* *Warning: The file of the specified path is uploaded to Magic Pod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- app_url: null\n  opts:\n    description: Required when you have selected _App file (URL)_ for _App type_.\n    is_expand: true\n    title: App URL\n- bundle_id: null\n  opts:\n    description: |-\n      Required when you have selected _iOS_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.apple.Preferences`\n    is_expand: true\n    title: Bundle ID\n- app_package: null\n  opts:\n    description: |-\n      Required when you have selected _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.android.settings`\n    is_expand: true\n    title: App package\n- app_activity: null\n  opts:\n    description: |-\n      Required when you have selected _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `.Settings`\n    is_expand: true\n    title: App activity\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: If _true_, the test result is sent to all project members by Magic\n      Pod.\n    is_required: true\n    title: Send mail\n    value_options:\n    - \"true\"\n    - \"false\"\n  send_mail: \"true\"\n- opts:\n    category: detail\n    description: |-\n      Each test in the project is executed at most the specified number of times when it failed.\n      Please set to 0 for no retry.\n    title: Retry count\n  retry_count: \"0\"\n- capture_type: Failure capture only\n  opts:\n    category: detail\n    description: |-\n      Specify how often you want to save captures of your app screen.\n\n      _Every step_ is only for enterprise users.\n    is_expand: true\n    is_required: true\n    title: Capture type\n    value_options:\n    - Failure capture only\n    - Every UI transit\n    - Every step\n- device_language: English\n  opts:\n    category: detail\n    is_expand: true\n    title: Device language\n    value_options:\n    - English\n    - Japanese\n- multi_lang_data: null\n  opts:\n    category: detail\n    description: |-\n      Required when you have Multi-lang data patterns for the project.\n      This feature is only for enterprise users.\n    is_expand: true\n    title: Multi-lang data pattern\n- base_url: https:/magic-pod.com/api/v1.0/\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magid Pod web API URL\noutputs:\n- MAGIC_POD_TEST_STATUS: null\n  opts:\n    summary: Status of batch test run. The value is either of 'succeeded', 'failed',\n      'aborted', 'running'.\n    title: MAGIC_POD_TEST_STATUS\n- MAGIC_POD_TEST_PASSED_COUNT: null\n  opts:\n    summary: The number of succeeded test cases in the batch run.\n    title: MAGIC_POD_TEST_PASSED_COUNT\n- MAGIC_POD_TEST_FAILED_COUNT: null\n  opts:\n    summary: The number of failed test cases in the batch run.\n    title: MAGIC_POD_TEST_FAILED_COUNT\n- MAGIC_POD_TEST_TOTAL_COUNT: null\n  opts:\n    summary: The number of total test cases in the batch run.\n    title: MAGIC_POD_TEST_TOTAL_COUNT\n- MAGIC_POD_TEST_URL: null\n  opts:\n    summary: URL of Magic Pod batch run page\n    title: MAGIC_POD_TEST_URL\n"
  },
  {
    "path": "steps/magicpod-ui-test/0.1.1/step.yml",
    "content": "title: Magic Pod UI test\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  Magic Pod UI test step\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2019-03-12T16:10:09.954708+09:00\nsource:\n  git: https://github.com/magic-Pod/bitrise-step-magicpod-uitest.git\n  commit: 0e4d24b2900588e51c261d755050a2fa6c187f35\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\nKey: Arbitrary new Secret\n      Env name like MAGIC_POD_API_TOKEN\\nValue: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sured to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sured to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- environment: Magic Pod\n  opts:\n    description: |-\n      Environment (cloud service) on which you want to execute your tests.\n      Each environment has its own limitation of OS/devices.  Please refer to project batch runs page for available choices.\n    is_expand: true\n    is_required: true\n    title: Environment\n    value_options:\n    - Magic Pod\n    - Remote TestKit\n- external_service_token: null\n  opts:\n    description: |-\n      Access token to use external cloud services (ex. Remote TestKit) for testing.\n      Required when you have selected **other than Magic Pod** for _Environment_.\n    is_expand: true\n    is_sensitive: true\n    title: External service token\n- opts:\n    description: \"Currently you can select only \\n\\n* _iOS_ for Magic Pod cloud service.\\n*\n      _Android_ for Remote TestKit.\"\n    is_expand: true\n    is_required: true\n    title: OS\n    value_options:\n    - iOS\n    - Android\n  os: iOS\n- device_type: Simulator\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _Simulator_ for Magic Pod cloud service.\n      * _Real Device_ for Remote TestKit.\n    is_expand: true\n    is_required: true\n    title: Device type\n    value_options:\n    - Simulator\n    - Emulator\n    - Real Device\n- opts:\n    description: \"Currently you can select only \\n\\n* _12.1_ for Magic Pod cloud service.\"\n    is_expand: true\n    is_required: true\n    title: Version\n  version: \"12.1\"\n- model: iPhone 8\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _iPhone 8_ for Magic Pod cloud service.\n      * For Remote TestKit, please refer to model list on https://appkitbox.com/testkit/devicelist/.\n    is_expand: true\n    is_required: true\n    title: Model\n- app_type: App file (cloud upload)\n  opts:\n    description: |-\n      Specify how you submit your app to the cloud.\n\n      * When you select _App file (cloud upload)_, then fill in _App path_ field below.\n      * When you select _App file (URL)_, then fill in _App URL_ field below.\n      * When you select _Installed app_, then fill in _Bundle ID_ field for iOS, or _App package_ and _App activity_ for Android.\n    is_expand: true\n    is_required: true\n    title: App type\n    value_options:\n    - App file (cloud upload)\n    - App file (URL)\n    - Installed app\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Required when you have selected _App file (cloud upload)_ for _App\n      type_.\\n\\n* *Warning: The file of the specified path is uploaded to Magic Pod\n      cloud and can be seen by project members.*\\n* For iOS simulator testing, specify\n      the directory _xx.app_ so that included files are automatically ziped into one\n      file before uploading. \"\n    is_expand: true\n    title: App path\n- app_url: null\n  opts:\n    description: Required when you have selected _App file (URL)_ for _App type_.\n    is_expand: true\n    title: App URL\n- bundle_id: null\n  opts:\n    description: |-\n      Required when you have selected _iOS_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.apple.Preferences`\n    is_expand: true\n    title: Bundle ID\n- app_package: null\n  opts:\n    description: |-\n      Required when you have selected _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.android.settings`\n    is_expand: true\n    title: App package\n- app_activity: null\n  opts:\n    description: |-\n      Required when you have selected _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `.Settings`\n    is_expand: true\n    title: App activity\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: If _true_, the test result is sent to all project members by Magic\n      Pod.\n    is_required: true\n    title: Send mail\n    value_options:\n    - \"true\"\n    - \"false\"\n  send_mail: \"true\"\n- opts:\n    category: detail\n    description: |-\n      Each test in the project is executed at most the specified number of times when it failed.\n      Please set to 0 for no retry.\n    title: Retry count\n  retry_count: \"0\"\n- capture_type: Every step\n  opts:\n    category: detail\n    description: Specify how often you want to save captures of your app screen.\n    is_expand: true\n    is_required: true\n    title: Capture type\n    value_options:\n    - Every step\n    - Every UI transit\n    - Failure capture only\n- device_language: English\n  opts:\n    category: detail\n    is_expand: true\n    title: Device language\n    value_options:\n    - English\n    - Japanese\n- multi_lang_data: null\n  opts:\n    category: detail\n    description: |-\n      Required when you have Multi-lang data patterns for the project.\n      This feature is only for enterprise users.\n    is_expand: true\n    title: Multi-lang data pattern\n- base_url: https://magic-pod.com/api/v1.0\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_STATUS: null\n  opts:\n    summary: Status of batch test run. The value is either of 'succeeded', 'failed',\n      'aborted', 'running'.\n    title: MAGIC_POD_TEST_STATUS\n- MAGIC_POD_TEST_PASSED_COUNT: null\n  opts:\n    summary: The number of succeeded test cases in the batch run.\n    title: MAGIC_POD_TEST_PASSED_COUNT\n- MAGIC_POD_TEST_FAILED_COUNT: null\n  opts:\n    summary: The number of failed test cases in the batch run.\n    title: MAGIC_POD_TEST_FAILED_COUNT\n- MAGIC_POD_TEST_TOTAL_COUNT: null\n  opts:\n    summary: The number of total test cases in the batch run.\n    title: MAGIC_POD_TEST_TOTAL_COUNT\n- MAGIC_POD_TEST_URL: null\n  opts:\n    summary: URL of Magic Pod batch run page\n    title: MAGIC_POD_TEST_URL\n"
  },
  {
    "path": "steps/magicpod-ui-test/0.26.0/step.yml",
    "content": "title: Magic Pod UI test\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  Magic Pod UI test step\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2019-05-13T17:29:17.850893+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magicpod-uitest.git\n  commit: 19281ea938537a518a6f2fa016d7820dc9fdb9d0\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- environment: Magic Pod\n  opts:\n    description: |-\n      Environment (cloud service) on which you want to execute your tests.\n      Each environment has its own limitation of OS/devices.  Please refer to project batch runs page for available choices.\n    is_expand: true\n    is_required: true\n    title: Environment\n    value_options:\n    - Magic Pod\n    - Remote TestKit\n    - Remote TestKit Onpremise\n- external_service_token: null\n  opts:\n    description: |-\n      Access token to use external cloud services (ex. Remote TestKit) for testing.\n      Required when you select _Remote Testkit_ for _Environment_.\n    is_expand: true\n    is_sensitive: true\n    title: External service token\n- external_service_user_name: null\n  opts:\n    description: User name which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service user name\n- external_service_password: null\n  opts:\n    description: Password which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    is_sensitive: true\n    title: External service password\n- external_service_server_url: null\n  opts:\n    description: Server url which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service server url\n- opts:\n    description: \"Currently you can select only \\n\\n* _iOS_ for Magic Pod cloud service.\"\n    is_expand: true\n    is_required: true\n    title: OS\n    value_options:\n    - iOS\n    - Android\n  os: iOS\n- device_type: Simulator\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _Simulator_ for Magic Pod cloud service.\n      * _Real Device_ for Remote TestKit and Remote TestKit Onpremise.\n    is_expand: true\n    is_required: true\n    title: Device type\n    value_options:\n    - Simulator\n    - Emulator\n    - Real Device\n- opts:\n    description: \"Currently you can select only \\n\\n* _12.1_ for Magic Pod cloud service.\"\n    is_expand: true\n    is_required: true\n    title: Version\n  version: \"12.1\"\n- model: iPhone 8\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _iPhone 8_ for Magic Pod cloud service.\n      * For Remote TestKit and Remote TestKit Onpremise, please refer to model list on https://appkitbox.com/testkit/devicelist/.\n    is_expand: true\n    is_required: true\n    title: Model\n- app_type: App file (cloud upload)\n  opts:\n    description: |-\n      Specify how you submit your app to the cloud.\n\n      * When you select _App file (cloud upload)_, then fill in _App path_ field below.\n      * When you select _App file (URL)_, then fill in _App URL_ field below.\n      * When you select _Installed app_, then fill in _Bundle ID_ field for iOS, or _App package_ and _App activity_ for Android.\n    is_expand: true\n    is_required: true\n    title: App type\n    value_options:\n    - App file (cloud upload)\n    - App file (URL)\n    - Installed app\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Required when you select _App file (cloud upload)_ for _App type_.\\nNote\n      that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote\n      TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\\n*\n      *Warning: The file of the specified path is uploaded to Magic Pod cloud and\n      can be seen by project members.*\\n* For iOS simulator testing, specify the directory\n      _xx.app_ so that included files are automatically ziped into one file before\n      uploading. \"\n    is_expand: true\n    title: App path\n- app_url: null\n  opts:\n    description: |-\n      Required when you select _App file (URL)_ for _App type_.\n      Note that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\n    is_expand: true\n    title: App URL\n- bundle_id: null\n  opts:\n    description: \"Specify the unique ID for the iOS app under test. \\n* ex) `com.apple.Preferences`\\n\\nThis\n      field is required in one of the following conditions.\\n1. When you select _iOS_\n      for _OS_ and _Installed_ for _App type_.\\n2. When you select _iOS_ for _OS_\n      and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_.\"\n    is_expand: true\n    title: Bundle ID\n- app_package: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.android.settings`\n    is_expand: true\n    title: App package\n- app_activity: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `.Settings`\n    is_expand: true\n    title: App activity\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: If _true_, the test result is sent to all project members by Magic\n      Pod.\n    is_required: true\n    title: Send mail\n    value_options:\n    - \"true\"\n    - \"false\"\n  send_mail: \"true\"\n- opts:\n    category: detail\n    description: |-\n      Each test in the project is executed at most the specified number of times when it failed.\n      Please set to 0 for no retry.\n    title: Retry count\n  retry_count: \"0\"\n- capture_type: Every step\n  opts:\n    category: detail\n    description: Specify how often you want to save captures of your app screen.\n    is_expand: true\n    is_required: true\n    title: Capture type\n    value_options:\n    - Every step\n    - Every UI transit\n    - Failure capture only\n- device_language: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device language\n    value_options:\n    - Default\n    - English\n    - Japanese\n    - Korean\n- device_region: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device region\n    value_options:\n    - Default\n    - Australia\n    - Brazil\n    - Canada\n    - China mainland\n    - France\n    - Germany\n    - India\n    - Indonesia\n    - Italy\n    - Japan\n    - Mexico\n    - Netherlands\n    - Russia\n    - Saudi Arabia\n    - South Korea\n    - Spain\n    - Switzerland\n    - Taiwan\n    - Turkey\n    - United Kingdom\n    - United States\n- multi_lang_data: null\n  opts:\n    category: detail\n    description: |-\n      Required when you have Multi-lang data patterns for the project.\n      This feature is only for enterprise users.\n    is_expand: true\n    title: Multi-lang data pattern\n- base_url: https://magic-pod.com/api/v1.0\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_STATUS: null\n  opts:\n    summary: Status of batch test run. The value is either of 'succeeded', 'failed',\n      'aborted', 'running'.\n    title: MAGIC_POD_TEST_STATUS\n- MAGIC_POD_TEST_PASSED_COUNT: null\n  opts:\n    summary: The number of succeeded test cases in the batch run.\n    title: MAGIC_POD_TEST_PASSED_COUNT\n- MAGIC_POD_TEST_FAILED_COUNT: null\n  opts:\n    summary: The number of failed test cases in the batch run.\n    title: MAGIC_POD_TEST_FAILED_COUNT\n- MAGIC_POD_TEST_TOTAL_COUNT: null\n  opts:\n    summary: The number of total test cases in the batch run.\n    title: MAGIC_POD_TEST_TOTAL_COUNT\n- MAGIC_POD_TEST_URL: null\n  opts:\n    summary: URL of Magic Pod batch run page\n    title: MAGIC_POD_TEST_URL\n"
  },
  {
    "path": "steps/magicpod-ui-test/0.47.0/step.yml",
    "content": "title: Magic Pod UI test\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  Magic Pod UI test step\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2020-02-13T13:29:09.814995+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magicpod-uitest.git\n  commit: e2b9e5eb3f8083ac238eb56099e989a2de265261\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- environment: Magic Pod\n  opts:\n    description: |-\n      Environment (cloud service) on which you want to execute your tests.\n      Each environment has its own limitation of OS/devices.  Please refer to project batch runs page for available choices.\n    is_expand: true\n    is_required: true\n    title: Environment\n    value_options:\n    - Magic Pod\n    - Remote TestKit\n    - Remote TestKit Onpremise\n- external_service_token: null\n  opts:\n    description: |-\n      Access token to use external cloud services (ex. Remote TestKit) for testing.\n      Required when you select _Remote Testkit_ for _Environment_.\n    is_expand: true\n    is_sensitive: true\n    title: External service token\n- external_service_user_name: null\n  opts:\n    description: User name which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service user name\n- external_service_password: null\n  opts:\n    description: Password which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    is_sensitive: true\n    title: External service password\n- external_service_server_url: null\n  opts:\n    description: Server url which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service server url\n- opts:\n    is_expand: true\n    is_required: true\n    title: OS\n    value_options:\n    - iOS\n    - Android\n  os: iOS\n- device_type: Simulator\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _Simulator_ or _Emulator_ for Magic Pod cloud service.\n      * _Real Device_ for Remote TestKit and Remote TestKit Onpremise.\n    is_expand: true\n    is_required: true\n    title: Device type\n    value_options:\n    - Simulator\n    - Emulator\n    - Real Device\n- opts:\n    description: |-\n      When you use Magic Pod cloud environment, you don't care about this field.\n      Version is automatically replaced with the one currently supported by Magic Pod.\n    is_expand: true\n    is_required: true\n    title: Version\n  version: \"13.1\"\n- model: iPhone 8\n  opts:\n    description: |-\n      * For Magic Pod cloud environment, please see available model list on your project's batch run page.\n      * For Remote TestKit and Remote TestKit Onpremise, please refer to model list on https://appkitbox.com/testkit/devicelist/.\n    is_expand: true\n    is_required: true\n    title: Model\n- app_type: App file (cloud upload)\n  opts:\n    description: |-\n      Specify how you submit your app to the cloud.\n\n      * When you select _App file (cloud upload)_, then fill in _App path_ field below.\n      * When you select _App file (URL)_, then fill in _App URL_ field below.\n      * When you select _Installed app_, then fill in _Bundle ID_ field for iOS, or _App package_ and _App activity_ for Android.\n    is_expand: true\n    is_required: true\n    title: App type\n    value_options:\n    - App file (cloud upload)\n    - App file (URL)\n    - Installed app\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Required when you select _App file (cloud upload)_ for _App type_.\\nNote\n      that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote\n      TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\\n*\n      *Warning: The file of the specified path is uploaded to Magic Pod cloud and\n      can be seen by project members.*\\n* For iOS simulator testing, specify the directory\n      _xx.app_ so that included files are automatically ziped into one file before\n      uploading. \"\n    is_expand: true\n    title: App path\n- app_url: null\n  opts:\n    description: |-\n      Required when you select _App file (URL)_ for _App type_.\n      Note that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\n    is_expand: true\n    title: App URL\n- bundle_id: null\n  opts:\n    description: \"Specify the unique ID for the iOS app under test. \\n* ex) `com.apple.Preferences`\\n\\nThis\n      field is required in one of the following conditions.\\n1. When you select _iOS_\n      for _OS_ and _Installed_ for _App type_.\\n2. When you select _iOS_ for _OS_\n      and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_.\"\n    is_expand: true\n    title: Bundle ID\n- app_package: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.android.settings`\n    is_expand: true\n    title: App package\n- app_activity: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `.Settings`\n    is_expand: true\n    title: App activity\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: If _true_, the test result is sent to all project members by Magic\n      Pod.\n    is_required: true\n    title: Send mail\n    value_options:\n    - \"true\"\n    - \"false\"\n  send_mail: \"true\"\n- opts:\n    category: detail\n    description: |-\n      Each test in the project is executed at most the specified number of times when it failed.\n      Please set to 0 for no retry.\n    title: Retry count\n  retry_count: \"0\"\n- capture_type: Every step\n  opts:\n    category: detail\n    description: Specify how often you want to save captures of your app screen.\n    is_expand: true\n    is_required: true\n    title: Capture type\n    value_options:\n    - Every step\n    - Every UI transit\n    - Failure capture only\n- device_language: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device language\n    value_options:\n    - Default\n    - English\n    - Japanese\n    - Korean\n- device_region: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device region\n    value_options:\n    - Default\n    - Australia\n    - Brazil\n    - Canada\n    - China mainland\n    - France\n    - Germany\n    - India\n    - Indonesia\n    - Italy\n    - Japan\n    - Mexico\n    - Netherlands\n    - Russia\n    - Saudi Arabia\n    - South Korea\n    - Spain\n    - Switzerland\n    - Taiwan\n    - Turkey\n    - United Kingdom\n    - United States\n- multi_lang_data: null\n  opts:\n    category: detail\n    description: |-\n      Required when you have Multi-lang data patterns for the project.\n      This feature is only for enterprise users.\n    is_expand: true\n    title: Multi-lang data pattern\n- base_url: https://magic-pod.com/api/v1.0\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_STATUS: null\n  opts:\n    summary: Status of batch test run. The value is either of 'succeeded', 'failed',\n      'aborted', 'running'.\n    title: MAGIC_POD_TEST_STATUS\n- MAGIC_POD_TEST_PASSED_COUNT: null\n  opts:\n    summary: The number of succeeded test cases in the batch run.\n    title: MAGIC_POD_TEST_PASSED_COUNT\n- MAGIC_POD_TEST_FAILED_COUNT: null\n  opts:\n    summary: The number of failed test cases in the batch run.\n    title: MAGIC_POD_TEST_FAILED_COUNT\n- MAGIC_POD_TEST_UNRESOLVED_COUNT: null\n  opts:\n    summary: The number of unresolved test cases in the batch run.\n    title: MAGIC_POD_TEST_UNRESOLVED_COUNT\n- MAGIC_POD_TEST_TOTAL_COUNT: null\n  opts:\n    summary: The number of total test cases in the batch run.\n    title: MAGIC_POD_TEST_TOTAL_COUNT\n- MAGIC_POD_TEST_URL: null\n  opts:\n    summary: URL of Magic Pod batch run page\n    title: MAGIC_POD_TEST_URL\n"
  },
  {
    "path": "steps/magicpod-ui-test/0.47.1/step.yml",
    "content": "title: Magic Pod UI test\nsummary: |\n  Magic Pod UI test step\ndescription: |\n  Magic Pod UI test step\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2020-02-25T12:52:15.605771+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magicpod-uitest.git\n  commit: 8e3fd8652d15a66fbf8e3c69bfa836739fc5090a\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- environment: Magic Pod\n  opts:\n    description: |-\n      Environment (cloud service) on which you want to execute your tests.\n      Each environment has its own limitation of OS/devices.  Please refer to project batch runs page for available choices.\n    is_expand: true\n    is_required: true\n    title: Environment\n    value_options:\n    - Magic Pod\n    - Remote TestKit\n    - Remote TestKit Onpremise\n- external_service_token: null\n  opts:\n    description: |-\n      Access token to use external cloud services (ex. Remote TestKit) for testing.\n      Required when you select _Remote Testkit_ for _Environment_.\n    is_expand: true\n    is_sensitive: true\n    title: External service token\n- external_service_user_name: null\n  opts:\n    description: User name which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service user name\n- external_service_password: null\n  opts:\n    description: Password which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    is_sensitive: true\n    title: External service password\n- external_service_server_url: null\n  opts:\n    description: Server url which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service server url\n- opts:\n    is_expand: true\n    is_required: true\n    title: OS\n    value_options:\n    - iOS\n    - Android\n  os: iOS\n- device_type: Simulator\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _Simulator_ or _Emulator_ for Magic Pod cloud service.\n      * _Real Device_ for Remote TestKit and Remote TestKit Onpremise.\n    is_expand: true\n    is_required: true\n    title: Device type\n    value_options:\n    - Simulator\n    - Emulator\n    - Real Device\n- opts:\n    description: |-\n      When you use Magic Pod cloud environment, you don't care about this field.\n      Version is automatically replaced with the one currently supported by Magic Pod.\n    is_expand: true\n    is_required: true\n    title: Version\n  version: \"13.1\"\n- model: iPhone 8\n  opts:\n    description: |-\n      * For Magic Pod cloud environment, please see available model list on your project's batch run page.\n      * For Remote TestKit and Remote TestKit Onpremise, please refer to model list on https://appkitbox.com/testkit/devicelist/.\n    is_expand: true\n    is_required: true\n    title: Model\n- app_type: App file (cloud upload)\n  opts:\n    description: |-\n      Specify how you submit your app to the cloud.\n\n      * When you select _App file (cloud upload)_, then fill in _App path_ field below.\n      * When you select _App file (URL)_, then fill in _App URL_ field below.\n      * When you select _Installed app_, then fill in _Bundle ID_ field for iOS, or _App package_ and _App activity_ for Android.\n    is_expand: true\n    is_required: true\n    title: App type\n    value_options:\n    - App file (cloud upload)\n    - App file (URL)\n    - Installed app\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Required when you select _App file (cloud upload)_ for _App type_.\\nNote\n      that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote\n      TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\\n*\n      *Warning: The file of the specified path is uploaded to Magic Pod cloud and\n      can be seen by project members.*\\n* For iOS simulator testing, specify the directory\n      _xx.app_ so that included files are automatically ziped into one file before\n      uploading. \"\n    is_expand: true\n    title: App path\n- app_url: null\n  opts:\n    description: |-\n      Required when you select _App file (URL)_ for _App type_.\n      Note that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\n    is_expand: true\n    title: App URL\n- bundle_id: null\n  opts:\n    description: \"Specify the unique ID for the iOS app under test. \\n* ex) `com.apple.Preferences`\\n\\nThis\n      field is required in one of the following conditions.\\n1. When you select _iOS_\n      for _OS_ and _Installed_ for _App type_.\\n2. When you select _iOS_ for _OS_\n      and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_.\"\n    is_expand: true\n    title: Bundle ID\n- app_package: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.android.settings`\n    is_expand: true\n    title: App package\n- app_activity: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `.Settings`\n    is_expand: true\n    title: App activity\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: If _true_, the test result is sent to all project members by Magic\n      Pod.\n    is_required: true\n    title: Send mail\n    value_options:\n    - \"true\"\n    - \"false\"\n  send_mail: \"true\"\n- opts:\n    category: detail\n    description: Specify which test cases to be executed by command-separated test\n      case numbers. If no number is specified, all test cases will be executed.\n    title: Test case numbers\n  test_case_numbers: \"\"\n- opts:\n    category: detail\n    description: |-\n      Each test in the project is executed at most the specified number of times when it failed.\n      Please set to 0 for no retry.\n    title: Retry count\n  retry_count: \"0\"\n- capture_type: Every step\n  opts:\n    category: detail\n    description: Specify how often you want to save captures of your app screen.\n    is_expand: true\n    is_required: true\n    title: Capture type\n    value_options:\n    - Every step\n    - Every UI transit\n    - Failure capture only\n- device_language: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device language\n    value_options:\n    - Default\n    - English\n    - Japanese\n    - Korean\n- device_region: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device region\n    value_options:\n    - Default\n    - Australia\n    - Brazil\n    - Canada\n    - China mainland\n    - France\n    - Germany\n    - India\n    - Indonesia\n    - Italy\n    - Japan\n    - Mexico\n    - Netherlands\n    - Russia\n    - Saudi Arabia\n    - South Korea\n    - Spain\n    - Switzerland\n    - Taiwan\n    - Turkey\n    - United Kingdom\n    - United States\n- multi_lang_data: null\n  opts:\n    category: detail\n    description: |-\n      Required when you have Multi-lang data patterns for the project.\n      This feature is only for enterprise users.\n    is_expand: true\n    title: Multi-lang data pattern\n- base_url: https://magic-pod.com/api/v1.0\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_STATUS: null\n  opts:\n    summary: Status of batch test run. The value is either of 'succeeded', 'failed',\n      'aborted', 'running'.\n    title: MAGIC_POD_TEST_STATUS\n- MAGIC_POD_TEST_PASSED_COUNT: null\n  opts:\n    summary: The number of succeeded test cases in the batch run.\n    title: MAGIC_POD_TEST_PASSED_COUNT\n- MAGIC_POD_TEST_FAILED_COUNT: null\n  opts:\n    summary: The number of failed test cases in the batch run.\n    title: MAGIC_POD_TEST_FAILED_COUNT\n- MAGIC_POD_TEST_UNRESOLVED_COUNT: null\n  opts:\n    summary: The number of unresolved test cases in the batch run.\n    title: MAGIC_POD_TEST_UNRESOLVED_COUNT\n- MAGIC_POD_TEST_TOTAL_COUNT: null\n  opts:\n    summary: The number of total test cases in the batch run.\n    title: MAGIC_POD_TEST_TOTAL_COUNT\n- MAGIC_POD_TEST_URL: null\n  opts:\n    summary: URL of Magic Pod batch run page\n    title: MAGIC_POD_TEST_URL\n"
  },
  {
    "path": "steps/magicpod-ui-test/0.54.1/step.yml",
    "content": "title: Magic Pod UI test (Deprecated)\nsummary: |\n  This step is deprecated. Please use the new step \"Magic Pod\" instead.\ndescription: |\n  This step is deprecated. Please use the new step \"Magic Pod\" instead.\nwebsite: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsource_code_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest\nsupport_url: https://github.com/magic-Pod/bitrise-step-magicpod-uitest/issues\npublished_at: 2020-06-02T22:33:41.701818+09:00\nsource:\n  git: https://github.com/Magic-Pod/bitrise-step-magicpod-uitest.git\n  commit: fd3b8a41ffa13ce68a3b63112b05b6d706863960\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/magic-Pod/bitrise-step-magicpod-uitest\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- magic_pod_api_token: null\n  opts:\n    description: \"Access token to use Magic Pod Web API.\\n\\n* Key: Arbitrary new Secret\n      Env name like `MAGIC_POD_API_TOKEN`\\n* Value: API token copied from https://magic-pod.com/accounts/api-token/. \"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Magic Pod API token\n- opts:\n    description: |-\n      Organization name in Magic Pod.\n      Please be sure to use **organization name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Organization name\n  organization_name: null\n- opts:\n    description: |-\n      Project name in Magic Pod.\n      Please be sure to use **project name**, not **display name**.\n    is_expand: true\n    is_required: true\n    title: Project name\n  project_name: null\n- environment: Magic Pod\n  opts:\n    description: |-\n      Environment (cloud service) on which you want to execute your tests.\n      Each environment has its own limitation of OS/devices.  Please refer to project batch runs page for available choices.\n    is_expand: true\n    is_required: true\n    title: Environment\n    value_options:\n    - Magic Pod\n    - Remote TestKit\n    - Remote TestKit Onpremise\n- external_service_token: null\n  opts:\n    description: |-\n      Access token to use external cloud services (ex. Remote TestKit) for testing.\n      Required when you select _Remote Testkit_ for _Environment_.\n    is_expand: true\n    is_sensitive: true\n    title: External service token\n- external_service_user_name: null\n  opts:\n    description: User name which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service user name\n- external_service_password: null\n  opts:\n    description: Password which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    is_sensitive: true\n    title: External service password\n- external_service_server_url: null\n  opts:\n    description: Server url which is required when you select _Remote TestKit Onpremise_.\n    is_expand: true\n    title: External service server url\n- opts:\n    is_expand: true\n    is_required: true\n    title: OS\n    value_options:\n    - iOS\n    - Android\n  os: iOS\n- device_type: Simulator\n  opts:\n    description: |-\n      Currently you can select only\n\n      * _Simulator_ or _Emulator_ for Magic Pod cloud service.\n      * _Real Device_ for Remote TestKit and Remote TestKit Onpremise.\n    is_expand: true\n    is_required: true\n    title: Device type\n    value_options:\n    - Simulator\n    - Emulator\n    - Real Device\n- opts:\n    description: |-\n      When you use Magic Pod cloud environment, you don't care about this field.\n      Version is automatically replaced with the one currently supported by Magic Pod.\n    is_expand: true\n    is_required: true\n    title: Version\n  version: \"13.1\"\n- model: iPhone 8\n  opts:\n    description: |-\n      * For Magic Pod cloud environment, please see available model list on your project's batch run page.\n      * For Remote TestKit and Remote TestKit Onpremise, please refer to model list on https://appkitbox.com/testkit/devicelist/.\n    is_expand: true\n    is_required: true\n    title: Model\n- app_type: App file (cloud upload)\n  opts:\n    description: |-\n      Specify how you submit your app to the cloud.\n\n      * When you select _App file (cloud upload)_, then fill in _App path_ field below.\n      * When you select _App file (URL)_, then fill in _App URL_ field below.\n      * When you select _Installed app_, then fill in _Bundle ID_ field for iOS, or _App package_ and _App activity_ for Android.\n    is_expand: true\n    is_required: true\n    title: App type\n    value_options:\n    - App file (cloud upload)\n    - App file (URL)\n    - Installed app\n- app_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: \"Required when you select _App file (cloud upload)_ for _App type_.\\nNote\n      that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote\n      TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\\n*\n      *Warning: The file of the specified path is uploaded to Magic Pod cloud and\n      can be seen by project members.*\\n* For iOS simulator testing, specify the directory\n      _xx.app_ so that included files are automatically ziped into one file before\n      uploading. \"\n    is_expand: true\n    title: App path\n- app_url: null\n  opts:\n    description: |-\n      Required when you select _App file (URL)_ for _App type_.\n      Note that _Bundle ID_ is also required when you select _iOS_ for _OS_ and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_ due to their restriction.\n    is_expand: true\n    title: App URL\n- bundle_id: null\n  opts:\n    description: \"Specify the unique ID for the iOS app under test. \\n* ex) `com.apple.Preferences`\\n\\nThis\n      field is required in one of the following conditions.\\n1. When you select _iOS_\n      for _OS_ and _Installed_ for _App type_.\\n2. When you select _iOS_ for _OS_\n      and _Remote TestKit_ or _Remote TestKit Onpremise_ for _Environment_.\"\n    is_expand: true\n    title: Bundle ID\n- app_package: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `com.android.settings`\n    is_expand: true\n    title: App package\n- app_activity: null\n  opts:\n    description: |-\n      Required when you select _Android_ for _OS_ and _Installed_ for _App type_.\n\n      * ex) `.Settings`\n    is_expand: true\n    title: App activity\n- opts:\n    description: |-\n      If set to true, this step waits until Magic Pod testing is completed and succeeds only when the test is successful.\n      Otherwise this step immediately exits with success.\n    title: Wait for result\n  wait_for_result: \"true\"\n- opts:\n    description: If _true_, the test result is sent to all project members by Magic\n      Pod.\n    is_required: true\n    title: Send mail\n    value_options:\n    - \"true\"\n    - \"false\"\n  send_mail: \"true\"\n- opts:\n    category: detail\n    description: Specify which test cases to be executed by command-separated test\n      case numbers. If no number is specified, all test cases will be executed.\n    title: Test case numbers\n  test_case_numbers: \"\"\n- opts:\n    category: detail\n    description: |-\n      Each test in the project is executed at most the specified number of times when it failed.\n      Please set to 0 for no retry.\n    title: Retry count\n  retry_count: \"0\"\n- capture_type: Every step\n  opts:\n    category: detail\n    description: Specify how often you want to save captures of your app screen.\n    is_expand: true\n    is_required: true\n    title: Capture type\n    value_options:\n    - Every step\n    - Every UI transit\n    - Failure capture only\n- device_language: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device language\n    value_options:\n    - Default\n    - English\n    - Japanese\n    - Korean\n- device_region: Default\n  opts:\n    category: detail\n    is_expand: true\n    title: Device region\n    value_options:\n    - Default\n    - Australia\n    - Brazil\n    - Canada\n    - China mainland\n    - France\n    - Germany\n    - India\n    - Indonesia\n    - Italy\n    - Japan\n    - Mexico\n    - Netherlands\n    - Russia\n    - Saudi Arabia\n    - South Korea\n    - Spain\n    - Switzerland\n    - Taiwan\n    - Turkey\n    - United Kingdom\n    - United States\n- multi_lang_data: null\n  opts:\n    category: detail\n    description: |-\n      Required when you have Multi-lang data patterns for the project.\n      This feature is only for enterprise users.\n    is_expand: true\n    title: Multi-lang data pattern\n- base_url: https://magic-pod.com/api/v1.0\n  opts:\n    category: debug\n    description: Cannot be changed\n    is_dont_change_value: true\n    title: Magic Pod web API URL\noutputs:\n- MAGIC_POD_TEST_STATUS: null\n  opts:\n    summary: Status of batch test run. The value is either of 'succeeded', 'failed',\n      'aborted', 'running'.\n    title: MAGIC_POD_TEST_STATUS\n- MAGIC_POD_TEST_PASSED_COUNT: null\n  opts:\n    summary: The number of succeeded test cases in the batch run.\n    title: MAGIC_POD_TEST_PASSED_COUNT\n- MAGIC_POD_TEST_FAILED_COUNT: null\n  opts:\n    summary: The number of failed test cases in the batch run.\n    title: MAGIC_POD_TEST_FAILED_COUNT\n- MAGIC_POD_TEST_UNRESOLVED_COUNT: null\n  opts:\n    summary: The number of unresolved test cases in the batch run.\n    title: MAGIC_POD_TEST_UNRESOLVED_COUNT\n- MAGIC_POD_TEST_TOTAL_COUNT: null\n  opts:\n    summary: The number of total test cases in the batch run.\n    title: MAGIC_POD_TEST_TOTAL_COUNT\n- MAGIC_POD_TEST_URL: null\n  opts:\n    summary: URL of Magic Pod batch run page\n    title: MAGIC_POD_TEST_URL\n"
  },
  {
    "path": "steps/magicpod-ui-test/step-info.yml",
    "content": "deprecate_notes: This step is deprecated. Please use magic-pod step instead.\nmaintainer: community\nremoval_date: \"2020-09-01\"\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.0.0/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2021-12-13T15:41:59.442247+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 73eaf3ee436d99a60ca016044493a19d12e46b74\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.0.1/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2021-12-17T16:13:42.786052073Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 2e7fdd76fe88c4a6b1ec46a6b889b46d1529f5ff\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.0.2/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-01-06T08:50:37.790235285Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 269eef956bdef1378125817bfc7ee49767c96fb1\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.0.3/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-01-20T13:49:25.755154448Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: e281713ef2f3069486c3157bea891a096b03f058\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.0.4/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-01-28T11:05:43.156761447Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: beb2fb4ffbfb19744d0387a3197f5054f418ffdf\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.0.5/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-02-23T21:20:28.54926794Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 1b2435c3a630ad6f5189b2f537222df2b9a28f4a\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.1.0/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-03-08T14:30:37.992785875Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 8d19896ab100fa420d4323411cc68a9b5759df6a\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.1.1/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-03-21T10:19:40.321513453Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: a7c77ab18ead348e00f0391197dd35c87d2d824f\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.1.2/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-04-14T14:29:57.391378948Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: e3569f79a10de8a3852a1da927d2965d92ea55d2\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.2.0/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2022-08-10T13:28:56.663637149Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 8cdddea01d086235096ad2cba80f9b2f9a603ee1\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/1.2.1/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2023-03-01T10:14:49.49824168Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: e9f11b3d688ada6259dc51f01e98ea6991601ed2\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.0.0/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2023-08-30T06:20:24.98228393Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 60e41ea0227a0c6ce2a8cd0b17f5301452f46f32\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.0.1/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2024-10-22T13:47:19.843455599Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 04c4ff917b274cfb72296a5b8c0b08ebe1251275\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.0/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2024-11-21T12:45:02.767211139Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 761d6e24c739d8f33c54d5acea2655c1766067fc\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.1/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-01-14T09:58:52.305073596Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: b770620c2182a830a7932fdc56973ab8c9af6aaf\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.2/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-03-21T15:53:42.122367692Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: d1c7690b30a32c4dde58679fb3aa6633e2121905\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.3/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-04-08T13:21:12.054788013Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: fccd542468cb99ca9d01fe067ab2556bcf97a524\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.4/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-05-16T09:30:34.682828151Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 507ecca8f6dd8ef4239ba6f0d8965af663ba0daf\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.5/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-06-17T14:35:59.88975116Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: dd570d947f381fa1db47cabec90650fb4a6afdc5\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.1.6/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-06-18T13:56:08.166104478Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: c70513c6e89ffd64c4d84330dbf760eef2aff6d3\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.2.0/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-06-25T14:08:21.973613574Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 958a781b642d4b02af88e92edc41039c1fd6b6e4\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Options\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.2.1/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-08-27T07:35:51.259816791Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 06f66233525c7e386badc479f310f00ca9cef526\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Options\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.2.2/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-09-02T11:08:05.225777161Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: bd47505d4a5a1b58a9ff76aded43081ea4fff99f\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Options\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/2.2.3/step.yml",
    "content": "title: Manage iOS Code Signing\nsummary: Automatically manage code signing assets before a build.\ndescription: |-\n  The **Manage iOS Code Signing** Step takes care of setting up the required code signing assets before the project is built on Bitrise.\n  The Step:\n  - Downloads and installs certificates uploaded to Bitrise.\n  - Generates, updates and downloads the provisioning profiles needed for your iOS project.\n  - Verifies and registers the project's Bundle IDs on the Apple Developer Site.\n  - Registers the iOS or tvOS devices connected to your Bitrise account with the Apple Developer Site.\n\n  Use the **Manage iOS Code Signing** Step if, for example:\n  - You use Fastlane for your project.\n  - You use the **Ionic Archive** or the **Cordova Archive** build Steps in your project.\n  - You use a **Script** Step because your project has its own build scripts.\n  The **Manage iOS Code Signing** Step takes care of automatically code signing your project before it's built on Bitrise.\n\n  ### Configuring the Step\n  Before you start, make sure:\n  - You've defined your Apple Developer Account to Bitrise.\n  - You've assigned an Apple Developer Account to your app.\n  - Make sure the Step is followed by another Step that needs iOS code signing.\n\n  1. **Apple services connection method**: Select the Apple service connection method you provided earlier on Bitrise; which is either the API Key or the Apple ID.\n  2. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n  3. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  4. **Scheme**: Add the scheme name you wish to archive your project later.\n  5. **Build configuration**:Specify Xcode Build Configuration. The Step will use the provided Build Configuration's Build Settings, to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Options**:\n  1. **Ensure code signing assets for UITest targets too**: If this input is set, the Step will manage the codesign settings of the UITest targets of the main Application.\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register known test devices from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n\n  Under **Build environment**:\n  You do not have to change any sensitive Environment Variable if all your certificates are already uploaded to Bitrise. Should you store your code signing files somewhere else (for example, in a private repository), then you can set these inputs in the `bitrise.yml` file.\n\n  Under **Debugging**:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  ### Troubleshooting:\n  - The **Manage iOS Code Signing** Step will fail if the correct Apple Developer Account is not connected to Bitrise or the right connection method is not selected in the **Apple service connection method** input within the Step.\n  - The **Manage iOS Code Signing** Step will also fail if the right code signing certificates are not uploaded to Bitrise. A Development type certificate is needed if the **Distribution method** input is set to `development`, otherwise a Distribution type certificate is needed. We recommend you upload one Development and one Distribution certificate, so that the Step can ensure code signing files for all the distribution methods.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing/issues\npublished_at: 2025-11-13T08:26:12.276412119Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing.git\n  commit: 532f48abf2bff9794dbaaa4ca0d6f6fab1334d6c\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-manage-ios-code-signing\nrun_if: .IsCI\ninputs:\n- apple_service_connection: api-key\n  opts:\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n      Available values:\n      - `api-key`: [Bitrise Apple Service connection with API Key.](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/)\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID.](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/)\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Apple service connection method\n    value_options:\n    - api-key\n    - apple-id\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- opts:\n    is_required: true\n    summary: Xcode Project (.xcodeproj) or Workspace (.xcworkspace) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: Options\n    is_required: true\n    summary: If this input is set, the Step will manage the codesign assets of the\n      UITest targets (of the main Application) among with the main Application codesign\n      assets.\n    title: Ensure code signing assets for UITest targets too\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sign_uitest_targets: \"no\"\n- opts:\n    category: Options\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Options\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Options\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Apple Service Connection method is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Options\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Build environment\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (|) character.\n\n      Local file path can be specified, using the file:// URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Build environment\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (|) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Build environment\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Build environment\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    summary: URL of the current Bitrise build.\n    title: Bitrise build URL\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    category: Build environment\n    is_dont_change_value: true\n    is_sensitive: true\n    summary: API token to access Bitrise resources during the current build.\n    title: Bitrise build API token\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will produce verbose level log messages.\n    title: Verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORT_METHOD: null\n  opts:\n    summary: 'Distribution type can be one of the following: `development`, `app-store`,\n      `ad-hoc` or `enterprise`.'\n    title: The selected distribution type\n- BITRISE_DEVELOPER_TEAM: null\n  opts:\n    summary: The development team's ID, for example, `1MZX23ABCD4`.\n    title: The development team's ID\n- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The development codesign identity''s name, for example, `iPhone Developer:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The development codesign identity's name\n- BITRISE_PRODUCTION_CODESIGN_IDENTITY: null\n  opts:\n    summary: 'The production codesign identity''s name, for example, `iPhone Distribution:\n      Bitrise Bot (VV2J4SV8V4)`.'\n    title: The production codesign identity's name\n- BITRISE_DEVELOPMENT_PROFILE: null\n  opts:\n    summary: The development provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's development provisioning profile UUID\n- BITRISE_PRODUCTION_PROFILE: null\n  opts:\n    summary: The production provisioning profile's UUID which belongs to the main\n      target, for example, `c5be4123-1234-4f9d-9843-0d9be985a068`.\n    title: The main target's production provisioning profile UUID\n"
  },
  {
    "path": "steps/manage-ios-code-signing/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/microsoft-teams-adaptive-card/1.0.4/step.yml",
    "content": "title: Microsoft Teams Adaptive Card Integration\nsummary: |\n  Send Microsoft Teams message to a channel\ndescription: |\n  Send Microsoft Teams message as adaptive card\nwebsite: https://github.com/HUK-COBURG/bitrise-step-microsoft-teams-adaptive-card\nsource_code_url: https://github.com/HUK-COBURG/bitrise-step-microsoft-teams-adaptive-card\nsupport_url: https://github.com/HUK-COBURG/bitrise-step-microsoft-teams-adaptive-card/issues\npublished_at: 2025-01-31T12:19:02.662532+01:00\nsource:\n  git: https://github.com/HUK-COBURG/bitrise-step-microsoft-teams-adaptive-card.git\n  commit: 85309d120949de3079a73509c9aa7b0afb3bfab3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/HUK-COBURG/bitrise-step-microsoft-teams-adaptive-card\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Microsoft Teams Webhook URL\n    is_required: true\n    is_sensitive: true\n    title: Microsoft Teams Webhook URL\n  webhook_url: null\n- card_headline: Success\n  opts:\n    description: |\n      Text of the header container.\n    title: Adaptive Card Header Container text\n- card_headline_on_error: Failed\n  opts:\n    category: If Build Failed\n    description: |\n      Text of the header container.\n    title: Adaptive Card Header Container text\n- card_style: good\n  opts:\n    description: \"Specifies the color of the header container. \\nFor preview see:\\n[documentation\n      of Adaptive Cards](https://adaptivecards.io/designer/).\\n\"\n    title: Adaptive Card Style\n    value_options:\n    - default\n    - good\n    - attention\n    - warning\n    - accent\n    - emphasis\n- card_style_on_error: attention\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.**\n    title: Message card theme color if the build failed\n    value_options:\n    - default\n    - good\n    - attention\n    - warning\n    - accent\n    - emphasis\n- opts:\n    description: |\n      The `title` property is meant to be rendered in a prominent way, at the very top of the card.\n      Use it to introduce the content of the card in such a way users will immediately know what to expect.\n    title: Message card title\n  title: Build Succeeded!\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.**\n    title: Message card title if the build failed\n  title_on_error: Build Failed!\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: A small text used to display the subject.\n    title: A small text used to display the subject.\n  subject: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n    Branch|${BITRISE_GIT_BRANCH}\n    Tag|${BITRISE_GIT_TAG}\n    Message|${BITRISE_GIT_MESSAGE}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a section\n- images: null\n  opts:\n    description: |\n      Fields separated by newlines and each image contains a `title` and a `url`.\n      The `title` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *image url* is shown.\n    title: A list of images to be displayed in a section\n- images_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      Fields separated by newlines and each image contains a `title` and a `url`.\n      The `title` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *image url* is shown.\n    title: A list of images to be displayed in a section if the build failed\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 4 buttons.\n    title: A list of buttons attached to the message as link buttons\n- buttons_on_error: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    category: If Build Failed\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 4 buttons.\n    title: A list of buttons attached to the message as link buttons if the build\n      failed\n"
  },
  {
    "path": "steps/microsoft-teams-adaptive-card/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/microsoft-teams-integration/1.0.1/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to recieve build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2018-03-16T17:53:15.852209088Z\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: ac3283b9034e50161a0da2ff919058df1a3e0d04\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n"
  },
  {
    "path": "steps/microsoft-teams-integration/1.0.2/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to recieve build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2021-01-12T14:20:19.001764+11:00\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: 1a0c88e72ee3d6c22026d75bdc097b20ad51cf9c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n"
  },
  {
    "path": "steps/microsoft-teams-integration/1.1.0/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to recieve build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2021-01-13T00:06:30.918935+11:00\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: 9bb15c9c9d3e331b7f7cf00ab0ba4ff654cbe5df\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |\n      If no value is given, the step automatically uses the `$GIT_REPOSITORY_URL` var.\n\n      If a Bitrise project is configured via SSH, `$GIT_REPOSITORY_URL` is not a useable\n      URI Target for the MessageCard, so this allows for overriding this value if SSH is configured.\n    subtitle: Defines a custom repository location\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n"
  },
  {
    "path": "steps/microsoft-teams-integration/1.2.0/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to recieve build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2021-01-24T14:25:13.9664+11:00\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: 1c771e34efe52d9647f7f4692ff9bdd3db424db4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- card_title: null\n  opts:\n    description: |\n      Primary MessageCard title text.\n\n      If no value is given, the default value will be the `BITRISE_APP_TITLE`.\n    subtitle: The heading text at the top of the MessageCard\n    title: Card Title\n- enable_debug: false\n  opts:\n    description: |\n      Enables debug logging to the Bitrise console.\n\n      WARNING: This will output the JSON value of the Teams Webhook body, be mindful of what is output here.\n    subtitle: Toggles whether to log debug info to the build output\n    title: Enable debug logging\n- opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `359914` if not overridden.\n    subtitle: Sets the cards theme color to the given hex value for successful builds\n    title: Theme Color - Build Success\n  success_theme_color: 359914\n- failed_theme_color: E04504\n  opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `E04504` if not overridden.\n    subtitle: Sets the cards theme color to the given hex value for failed builds\n    title: Theme Color - Build Failed\n- enable_primary_section_markdown: true\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the each field of the first section of the MessageCard.\n\n      User input fields affected:\n      * section_title\n      * section_subtitle\n      * section_text\n    subtitle: Sets whether the text fields within the MessageCard's first section\n      should render Markdown text\n    title: Primary Section Markdown\n- enable_build_status_facts_markdown: false\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the default Facts within the MessageCard.\n\n      Fact fields affected:\n      * Build Status\n      * Build Number\n      * Git Branch\n      * Build Triggered\n      * Workflow\n    subtitle: Sets whether each of the facts should render their values as Markdown\n      text\n    title: Build Status Facts Markdown\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activityTitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit authors' name that triggered the build.\n    subtitle: Text that is displayed within the MessageCard Section `activityTitle`\n    title: Section Title\n  section_title: $GIT_CLONE_COMMIT_AUTHOR_NAME\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activitySubtitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit message subject that triggered the build.\n    subtitle: Text that is displayed within the MessageCard Section `activitySubtitle`\n    title: Section Subtitle\n  section_subtitle: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `text` within the primary Section of the MessageCard. By default,\n      this will be set to the commit message body that triggered the build.\n\n      If desired, this is the perfect place to include release notes via the `generate-changelog` Bitrise step, however\n      setting `enable_primary_section_markdown` to `true` may be necessary to properly format the changelog content.\n    subtitle: Text that is displayed within the MessageCard Section `text`\n    title: Section Text\n  section_text: $GIT_CLONE_COMMIT_MESSAGE_BODY\n- opts:\n    category: MessageCard Content\n    subtitle: Image that is displayed within the MessageCard Section `activityImage`\n    title: Section Image\n  section_header_image: null\n- opts:\n    description: |\n      If no value is given, the step automatically uses the `$GIT_REPOSITORY_URL` var.\n\n      If a Bitrise project is configured via SSH, `$GIT_REPOSITORY_URL` is not a useable\n      URI Target for the MessageCard, so this allows for overriding this value if SSH is configured.\n    subtitle: Defines a custom repository location\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n"
  },
  {
    "path": "steps/microsoft-teams-integration/1.2.2/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to recieve build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2021-02-18T21:28:22.072847+11:00\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: 83a518dc014f7bfcbfff1104aaafd7fca0600824\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- card_title: $BITRISE_APP_TITLE\n  opts:\n    description: |\n      Primary MessageCard title text.\n\n      If no value is given, the default value will be the `BITRISE_APP_TITLE`.\n    summary: The heading text at the top of the MessageCard\n    title: Card Title\n- enable_debug: false\n  opts:\n    description: |\n      Enables debug logging to the Bitrise console.\n\n      WARNING: This will output the JSON value of the Teams Webhook body, be mindful of what is output here.\n    summary: Toggles whether to log debug info to the build output\n    title: Enable debug logging\n- opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `359914` if not overridden.\n    summary: Sets the cards theme color to the given hex value for successful builds\n    title: Theme Color - Build Success\n  success_theme_color: 359914\n- failed_theme_color: E04504\n  opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `E04504` if not overridden.\n    summary: Sets the cards theme color to the given hex value for failed builds\n    title: Theme Color - Build Failed\n- enable_primary_section_markdown: true\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the each field of the first section of the MessageCard.\n\n      User input fields affected:\n      * section_title\n      * section_subtitle\n      * section_text\n    summary: Sets whether the text fields within the MessageCard's first section should\n      render Markdown text\n    title: Primary Section Markdown\n- enable_build_status_facts_markdown: false\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the default Facts within the MessageCard.\n\n      Fact fields affected:\n      * Build Status\n      * Build Number\n      * Git Branch\n      * Build Triggered\n      * Workflow\n    summary: Sets whether each of the facts should render their values as Markdown\n      text\n    title: Build Status Facts Markdown\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activityTitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit authors' name that triggered the build.\n    summary: Text that is displayed within the MessageCard Section `activityTitle`\n    title: Section Title\n  section_title: $GIT_CLONE_COMMIT_AUTHOR_NAME\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activitySubtitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit message subject that triggered the build.\n    summary: Text that is displayed within the MessageCard Section `activitySubtitle`\n    title: Section Subtitle\n  section_subtitle: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `text` within the primary Section of the MessageCard. By default,\n      this will be set to the commit message body that triggered the build.\n\n      If desired, this is the perfect place to include release notes via the `generate-changelog` Bitrise step, however\n      setting `enable_primary_section_markdown` to `true` may be necessary to properly format the changelog content.\n    summary: Text that is displayed within the MessageCard Section `text`\n    title: Section Text\n  section_text: $GIT_CLONE_COMMIT_MESSAGE_BODY\n- opts:\n    category: MessageCard Content\n    summary: Image that is displayed within the MessageCard Section `activityImage`\n    title: Section Image\n  section_header_image: null\n- opts:\n    description: |\n      If no value is given, the step automatically uses the `$GIT_REPOSITORY_URL` var.\n\n      If a Bitrise project is configured via SSH, `$GIT_REPOSITORY_URL` is not a useable\n      URI Target for the MessageCard, so this allows for overriding this value if SSH is configured.\n    summary: Define a custom repository location\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n"
  },
  {
    "path": "steps/microsoft-teams-integration/2.0.0/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to receive build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2021-02-28T12:36:53.583905+11:00\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: e885ffeaf7812f6f96397190155c05ee134e62fb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- card_title: $BITRISE_APP_TITLE\n  opts:\n    description: |\n      Primary MessageCard title text.\n\n      If no value is given, the default value will be the `BITRISE_APP_TITLE`.\n    summary: The heading text at the top of the MessageCard\n    title: Card Title\n- enable_debug: \"no\"\n  opts:\n    description: |\n      Enables debug logging to the Bitrise console.\n\n      WARNING: This will output the JSON value of the Teams Webhook body, be mindful of what is output here.\n    summary: Toggles whether to log debug info to the build output\n    title: Enable debug logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `359914` if not overridden.\n    summary: Sets the cards theme color to the given hex value for successful builds\n    title: Theme Color - Build Success\n  success_theme_color: 359914\n- failed_theme_color: E04504\n  opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `E04504` if not overridden.\n    summary: Sets the cards theme color to the given hex value for failed builds\n    title: Theme Color - Build Failed\n- enable_primary_section_markdown: \"yes\"\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the each field of the first section of the MessageCard.\n\n      User input fields affected:\n      * section_title\n      * section_subtitle\n      * section_text\n    summary: Sets whether the text fields within the MessageCard's first section should\n      render Markdown text\n    title: Primary Section Markdown\n    value_options:\n    - \"yes\"\n    - \"no\"\n- enable_build_status_facts_markdown: \"no\"\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the default Facts within the MessageCard.\n\n      Fact fields affected:\n      * Build Status\n      * Build Number\n      * Git Branch\n      * Build Triggered\n      * Workflow\n    summary: Sets whether each of the facts should render their values as Markdown\n      text\n    title: Build Status Facts Markdown\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activityTitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit authors' name that triggered the build.\n    summary: Text that is displayed within the MessageCard Section `activityTitle`\n    title: Section Title\n  section_title: $GIT_CLONE_COMMIT_AUTHOR_NAME\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activitySubtitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit message subject that triggered the build.\n    summary: Text that is displayed within the MessageCard Section `activitySubtitle`\n    title: Section Subtitle\n  section_subtitle: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `text` within the primary Section of the MessageCard. By default,\n      this will be set to the commit message body that triggered the build.\n\n      If desired, this is the perfect place to include release notes via the `generate-changelog` Bitrise step, however\n      setting `enable_primary_section_markdown` to `yes` may be necessary to properly format the changelog content.\n    summary: Text that is displayed within the MessageCard Section `text`\n    title: Section Text\n  section_text: $GIT_CLONE_COMMIT_MESSAGE_BODY\n- opts:\n    category: MessageCard Content\n    summary: Image that is displayed within the MessageCard Section `activityImage`\n    title: Section Image\n  section_header_image: null\n- enable_default_actions: \"yes\"\n  opts:\n    category: MessageCard Actions\n    description: \"Allows for disabling the default 'Go To Repo' and 'Go To Build'\n      MessageCard Actions if you wish to provide only your own custom actions \\nvia\n      the `actions` step input (up to a limit of 4 actions in total).\\n\"\n    summary: Toggles the default actions within the MessageCard.\n    title: Default MessageCard Actions\n    value_options:\n    - \"yes\"\n    - \"no\"\n- actions: '[]'\n  opts:\n    category: MessageCard Actions\n    description: \"A stringified JSON object array of additional custom actions to\n      display on the card.\\n\\nThe maximum amount of actions a single card can display\n      is 4, 2 of which are used if \\n`enable_default_actions` is set to `yes`.\\n\\nEach\n      action button object must have a `text` key/value pair, and a list of `target`\n      objects\\nwhich define the `uri`, specific to which platform-client (`os` value)\n      the Teams message is viewed on.\\n\\nValid `os` values are (case-sensitive):\\n\\n*\n      iOS\\n* android\\n* windows\\n* default (shows action button on every Teams client,\n      regardless of platform)\\n\\nNOTE: Step input must be valid JSON. Trailing commas\n      are not permitted.\\n\\nExample input:\\n```json\\n[\\n  {\\n    \\\"text\\\": \\\"Open\n      deep link\\\", \\n    \\\"targets\\\": [\\n      {\\n        \\\"uri\\\": \\\"your_universal_link\\\",\\n\n      \\       \\\"os\\\": \\\"iOS\\\"\\n      },\\n      {\\n        \\\"uri\\\": \\\"your_android_app_link\\\",\\n\n      \\       \\\"os\\\": \\\"android\\\"\\n      },\\n      {\\n        \\\"uri\\\": \\\"https://www.google.com\\\",\\n\n      \\       \\\"os\\\": \\\"default\\\"\\n      }\\n    ]\\n  }                  \\n]\\n```\\nWhile\n      this isn't the most user-friendly way to define custom buttons, Bitrise step\\nparsing\n      is currently limited to string value inputs and does not allow defining a YAML\n      object list, which\\nhas been [feature requested here](https://github.com/bitrise-io/go-steputils/issues/23).\\n\"\n    summary: Additional extra custom actions to display on the MessageCard\n    title: MessageCard Actions\n- opts:\n    description: |\n      If no value is given, the step automatically uses the `$GIT_REPOSITORY_URL` var.\n\n      If a Bitrise project is configured via SSH, `$GIT_REPOSITORY_URL` is not a useable\n      URI Target for the MessageCard, so this allows for overriding this value if SSH is configured.\n    summary: Define a custom repository location\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n"
  },
  {
    "path": "steps/microsoft-teams-integration/2.1.1/step.yml",
    "content": "title: Microsoft Teams Integration\nsummary: Allows you to receive build status updates on Microsoft Team using Incoming\n  Webhooks\ndescription: |\n  Uses Incoming Webhooks feature in Microsft Teams to send updates on your builds\nwebsite: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsource_code_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nsupport_url: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration/issues\npublished_at: 2021-05-21T10:53:00.402374+10:00\nsource:\n  git: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git\n  commit: a3978af618888d655032a8d1fd460d5a09a099d3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/amrfarid140/bitrise-step-microsoft-teams-integration\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- card_title: $BITRISE_APP_TITLE\n  opts:\n    description: |\n      Primary MessageCard title text.\n\n      If no value is given, the default value will be the `BITRISE_APP_TITLE`.\n    summary: The heading text at the top of the MessageCard\n    title: Card Title\n- enable_debug: \"no\"\n  opts:\n    description: |\n      Enables debug logging to the Bitrise console.\n\n      WARNING: This will output the JSON value of the Teams Webhook body, be mindful of what is output here.\n    summary: Toggles whether to log debug info to the build output\n    title: Enable debug logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `359914` if not overridden.\n    summary: Sets the cards theme color to the given hex value for successful builds\n    title: Theme Color - Build Success\n  success_theme_color: 359914\n- failed_theme_color: E04504\n  opts:\n    category: Theme Customisation\n    description: |\n      Given value should be a hexadecimal color, minus the leading `#`.\n\n      Defaults to `E04504` if not overridden.\n    summary: Sets the cards theme color to the given hex value for failed builds\n    title: Theme Color - Build Failed\n- enable_primary_section_markdown: \"yes\"\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the each field of the first section of the MessageCard.\n\n      User input fields affected:\n      * section_title\n      * section_subtitle\n      * section_text\n    summary: Sets whether the text fields within the MessageCard's first section should\n      render Markdown text\n    title: Primary Section Markdown\n    value_options:\n    - \"yes\"\n    - \"no\"\n- enable_build_status_facts_markdown: \"no\"\n  opts:\n    category: Markdown Rules\n    description: |\n      Sets whether to enable Markdown rendering for the default Facts within the MessageCard.\n\n      Fact fields affected:\n      * Build Status\n      * Build Number\n      * Git Branch\n      * Build Triggered\n      * Workflow\n    summary: Sets whether each of the facts should render their values as Markdown\n      text\n    title: Build Status Facts Markdown\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activityTitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit authors' name that triggered the build.\n    summary: Text that is displayed within the MessageCard Section `activityTitle`\n    title: Section Title\n  section_title: $GIT_CLONE_COMMIT_AUTHOR_NAME\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `activitySubtitle` within the primary Section of the MessageCard.\n\n      By default, this will be set to the commit message subject that triggered the build.\n    summary: Text that is displayed within the MessageCard Section `activitySubtitle`\n    title: Section Subtitle\n  section_subtitle: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the text value of `text` within the primary Section of the MessageCard. By default,\n      this will be set to the commit message body that triggered the build.\n\n      If desired, this is the perfect place to include release notes via the `generate-changelog` Bitrise step, however\n      setting `enable_primary_section_markdown` to `yes` may be necessary to properly format the changelog content.\n    summary: Text that is displayed within the MessageCard Section `text`\n    title: Section Text\n  section_text: $GIT_CLONE_COMMIT_MESSAGE_BODY\n- opts:\n    category: MessageCard Content\n    summary: Image that is displayed within the MessageCard Section `activityImage`\n    title: Section Image\n  section_header_image: null\n- opts:\n    category: MessageCard Image\n    summary: Image that is displayed within the MessageCard Section `images`\n    title: Image\n  section_image: null\n- opts:\n    category: MessageCard Image\n    summary: A short description of the image. Typically, description is displayed\n      in a tooltip as the user hovers their mouse over the image.\n    title: Image Description\n  section_image_description: null\n- enable_default_actions: \"yes\"\n  opts:\n    category: MessageCard Actions\n    description: \"Allows for disabling the default 'Go To Repo' and 'Go To Build'\n      MessageCard Actions if you wish to provide only your own custom actions \\nvia\n      the `actions` step input (up to a limit of 4 actions in total).\\n\"\n    summary: Toggles the default actions within the MessageCard.\n    title: Default MessageCard Actions\n    value_options:\n    - \"yes\"\n    - \"no\"\n- actions: '[]'\n  opts:\n    category: MessageCard Actions\n    description: \"A stringified JSON object array of additional custom actions to\n      display on the card.\\n\\nThe maximum amount of actions a single card can display\n      is 4, 2 of which are used if \\n`enable_default_actions` is set to `yes`.\\n\\nEach\n      action button object must have a `text` key/value pair, and a list of `target`\n      objects\\nwhich define the `uri`, specific to which platform-client (`os` value)\n      the Teams message is viewed on.\\n\\nValid `os` values are (case-sensitive):\\n\\n*\n      iOS\\n* android\\n* windows\\n* default (shows action button on every Teams client,\n      regardless of platform)\\n\\nNOTE: Step input must be valid JSON. Trailing commas\n      are not permitted.\\n\\nExample input:\\n```json\\n[\\n  {\\n    \\\"text\\\": \\\"Open\n      deep link\\\", \\n    \\\"targets\\\": [\\n      {\\n        \\\"uri\\\": \\\"your_universal_link\\\",\\n\n      \\       \\\"os\\\": \\\"iOS\\\"\\n      },\\n      {\\n        \\\"uri\\\": \\\"your_android_app_link\\\",\\n\n      \\       \\\"os\\\": \\\"android\\\"\\n      },\\n      {\\n        \\\"uri\\\": \\\"https://www.google.com\\\",\\n\n      \\       \\\"os\\\": \\\"default\\\"\\n      }\\n    ]\\n  }                  \\n]\\n```\\nWhile\n      this isn't the most user-friendly way to define custom buttons, Bitrise step\\nparsing\n      is currently limited to string value inputs and does not allow defining a YAML\n      object list, which\\nhas been [feature requested here](https://github.com/bitrise-io/go-steputils/issues/23).\\n\"\n    summary: Additional extra custom actions to display on the MessageCard\n    title: MessageCard Actions\n- opts:\n    description: |\n      If no value is given, the step automatically uses the `$GIT_REPOSITORY_URL` var.\n\n      If a Bitrise project is configured via SSH, `$GIT_REPOSITORY_URL` is not a useable\n      URI Target for the MessageCard, so this allows for overriding this value if SSH is configured.\n    summary: Define a custom repository location\n    title: Repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- opts:\n    description: |\n      * Go to Microsoft Teams\n      * Click on the three dots next to channel name then **Add Connector**\n      * Select **Incoming Webhook* and in the text input type **Bitrise**\n      * Save and copy the link to the input for this step\n    is_required: true\n    summary: Url of the Incoming Webhook generated by Microsoft Teams\n    title: Incoming Webhook URL\n  webhook_url: null\n- opts:\n    category: MessageCard Content\n    description: |\n      Sets the timezone to use for the 'Build triggered' time in the MessageCard.\n\n      Defaults to UTC if no value is given.\n\n      Valid timezone name inputs can be [found here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).\n    summary: Sets the timezone to use for the 'Build triggered' time\n    title: Timezone\n  timezone: UTC\n"
  },
  {
    "path": "steps/microsoft-teams-integration/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/mobile-quality/1.0.2/step.yml",
    "content": "title: steps-mobile-quality\nsummary: |\n  Check and monitor mobile application's quality\ndescription: |\n  Check mobile application's quality, it can be an APK and/or IPA file. Among other things, you can:\n  - setup a config file, or directly on step's input, the value related to released app to compare the values on each new release candidate eg. to be aware on each new permission and/or app size increased\n  - generate a report file where we will display the result of different check\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after the compilation step (\"Android Build\" for android, \"Xcode Archive\" for iOS)\n  - Launch \"Deploy to Bitrise.io\" step after this one to deploy report files to artifacts\nwebsite: https://github.com/imranMnts/bitrise-step-mobile-quality\nsource_code_url: https://github.com/imranMnts/bitrise-step-mobile-quality\nsupport_url: https://github.com/imranMnts/bitrise-step-mobile-quality/issues\npublished_at: 2021-01-13T18:53:13.683611+01:00\nsource:\n  git: https://github.com/imranMnts/bitrise-step-mobile-quality.git\n  commit: 38689b10539e58026f64b6f0b6cac90aa951b805\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\n- cordova\n- ionic\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: apktool\n  - name: gnu-sed\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: To launch or not android quality check\n    is_expand: true\n    is_required: true\n    summary: Do you want check android part?\n    title: Check Android\n    value_options:\n    - \"yes\"\n    - \"no\"\n- check_ios: \"yes\"\n  opts:\n    description: To launch or not iOS quality check\n    is_expand: true\n    is_required: true\n    summary: Do you want check iOS part?\n    title: Check iOS\n    value_options:\n    - \"yes\"\n    - \"no\"\n- config_file_path: null\n  opts:\n    description: |\n      The config file where we have some informations like the current android app size eg. to compare with next builds and alert if needed.\n      If you want use Environment Variables instead of the config file, do not set this key and add variables. (See [README](https://github.com/imranMnts/bitrise-step-mobile-quality/blob/master/README.md) to see all needed variables)\n    is_expand: false\n    is_required: false\n    summary: Path of the config file\n    title: Config file path\n- opts:\n    description: |\n      You can use the artifacts from another bitrise build of the same project.\n      If you launch this step on the build where you launched Android build step eg. you don't have to set this key\n    is_expand: false\n    is_required: false\n    summary: Build slug of the build where you have the APK/IPA into artifacts\n    title: External Build slug\n  outside_build_slug: null\n- android_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      If you use this step in the same build where you generated the APK\n    is_expand: false\n    is_required: true\n    title: APK path\n- ios_ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      If you use this step in the same build where you generated the IPA\n    is_expand: false\n    is_required: true\n    title: IPA path\n- android_apk_size: null\n  opts:\n    description: |\n      Set this key if you want to follow up on your project's android APK size\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Android APK size (MB)\n    title: Android APK size\n- android_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your android app and be aware when useless permission added to your AndroidManifest.xml\n\n      To know how many permission you have currently in your app, you can check your APK's manifest to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your AndroidManifest.xml\n    title: Android permission\n- ios_app_name: null\n  opts:\n    description: |\n      You have to set this key if you want check ios quality.\n      If not, you can set an empty string.\n\n      You can find it on xcode -> General -> Display Name\n    is_expand: false\n    is_required: true\n    title: iOS app name (Display Name)\n- ios_ipa_size: null\n  opts:\n    description: |\n      Set this key if you want follow up your project's ios IPA size\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: iOS IPA size (MB)\n    title: iOS IPA size\n- ios_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your ios app and be aware when useless permission added to your Info.plist\n      To know how many permission you have currently in your app, you can check your IPA's Info.plist to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your Info.plist\n    title: iOS permission\n- alert_threshold: \"5\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Threshold to alert when app size increase (MB)\n    title: Alert threshold\n    value_options:\n    - \"3\"\n    - \"5\"\n    - \"10\"\n    - \"20\"\noutputs:\n- IOS_PERMISSION_COUNT: null\n  opts:\n    title: Current build's ios permission count\n- NEW_IPA_SIZE: null\n  opts:\n    title: Current build's ios IPA size (MB)\n- ANDROID_PERMISSION_COUNT: null\n  opts:\n    title: Current build's android permission count\n- NEW_APK_SIZE: null\n  opts:\n    title: Current build's android APK size (MB)\n"
  },
  {
    "path": "steps/mobile-quality/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2021-01-21\"\ndeprecate_notes: |\n  This step is deprecated. Now it was split to use each feature separately (eg. Mobile apps permissions monitoring [monitoring-apps-permissions step])\n"
  },
  {
    "path": "steps/mobitru-upload/1.0.0/step.yml",
    "content": "title: Mobitru Upload\nsummary: |\n  Upload an APK or IPA file to Mobitru platform\ndescription: |\n  Upload your application to [Mobitru](https://mobitru.com) and get back the app's artifact ID.\n  It can be used to install the app on Mobitru remote device for manual or automated testing.\nwebsite: https://github.com/Mobitru/bitrise-step-mobitru-upload\nsource_code_url: https://github.com/Mobitru/bitrise-step-mobitru-upload\nsupport_url: https://github.com/Mobitru/bitrise-step-mobitru-upload/issues\npublished_at: 2024-05-27T11:42:06.933734+03:00\nsource:\n  git: https://github.com/Mobitru/bitrise-step-mobitru-upload.git\n  commit: 78cd8386c8f729185bdb97359b9c0df377f14518\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The app file you want to upload to Mobitru, usually $BITRISE\\_APK\\_PATH or $BITRISE\\_IPA\\_PATH.\n    is_expand: true\n    is_required: true\n    summary: Location of the APK or IPA file to upload.\n    title: Location of the APK or IPA file\n  upload_filepath: null\n- mobitru_access_key: null\n  opts:\n    description: |\n      See [Mobitru documentation](https://mobitru.com/docs/access-key/) to learn more about access key.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Mobitru access key used to authorize requests to Mobitru platform.\n    title: Mobitru access key\n- mobitru_billing_unit_slug: personal\n  opts:\n    description: |\n      Specify your billing unit slug if you are using Mobitru team account.\n      Otherwise specify `personal` for personal account.\n\n      See [Mobitru documentation](https://mobitru.com/docs/accounts/) to learn more about account types.\n    is_expand: true\n    is_required: true\n    summary: Mobitru billing unit slug used to identify team space to upload an application\n      to.\n    title: Mobitru billing unit slug\n- mobitru_address: https://app.mobitru.com/\n  opts:\n    description: |\n      Override your target Mobitru instance address if requited.\n    is_expand: true\n    is_required: true\n    summary: HTTP address of the Mobitru instance.\n    title: Mobitru address\n- opts:\n    description: |\n      See [Mobitru documentation](https://mobitru.com/docs/team-apps/) to learn more about shared apps.\n    is_expand: true\n    is_required: true\n    summary: Share uploaded file with the team or allow access to the uploader user\n      only.\n    title: Share with the team\n    value_options:\n    - \"yes\"\n    - \"no\"\n  share_with_team: \"yes\"\n- artifact_alias: null\n  opts:\n    description: |\n      Specify arbitrary text alias for the uploaded artifact, e.g. `v1.2.3`, `2024-05-12`, `stage`, etc.\n      It could be useful to distinguish your artifact in list of previously uploaded apps.\n    is_expand: true\n    is_required: false\n    summary: Alias for the uploaded artifact.\n    title: Artifact alias\noutputs:\n- MOBITRU_ARTIFACT_ID: null\n  opts:\n    description: |\n      Use artifact ID to install uploaded app to Mobitru remote device in your tests.\n\n      See [Mobitru API documentation](https://app.mobitru.com/wiki/apidoc/#api-InstallApp) for more information.\n    summary: Mobitru artifact ID of the uploaded app.\n    title: Mobitru artifact ID\n"
  },
  {
    "path": "steps/mobitru-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/mobsfscan/1.0.0/step.yml",
    "content": "title: MobSFScan\nsummary: |\n  mobsfscan is a static analysis tool (SAST) that can find insecure code patterns in your Android and iOS source code. Supports Java, Kotlin, Android XML, Swift and Objective C Code. mobsfscan uses MobSF static analysis rules and is powered by semgrep and libsast pattern matcher.\ndescription: |\n  Configuration information and troubleshooting information are available on the mobsfscan repository at https://github.com/MobSF/mobsfscan\nwebsite: https://github.com/OhMyApp/bitrise-step-mobsfscan\nsource_code_url: https://github.com/OhMyApp/bitrise-step-mobsfscan\nsupport_url: https://github.com/OhMyApp/bitrise-step-mobsfscan/issues\npublished_at: 2026-01-07T00:52:30.587134+01:00\nsource:\n  git: https://github.com/OhMyApp/bitrise-step-mobsfscan.git\n  commit: 7065e6052017e74b7ad0743ca1b54330f56c5485\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_skippable: true\ninputs:\n- opts:\n    is_required: true\n    title: Path to the project\n  project_path: .\n- opts:\n    is_required: false\n    title: Path to save the report\n  report_file_path: $BITRISE_DEPLOY_DIR/mobsfscan-report.txt\n- opts:\n    is_required: false\n    title: Output format\n    value_options:\n    - txt\n    - json\n    - sarif\n    - sonarqube\n    - html\n  output_format: txt\n- opts:\n    is_required: false\n    summary: Force Android or iOS rules explicitly\n    title: Project type\n    value_options:\n    - auto\n    - android\n    - ios\n  project_type: auto\n- config_file: \"\"\n  opts:\n    is_required: false\n    summary: Location to .mobsf config file\n    title: Configuration file\n- multiprocessing: default\n  opts:\n    is_required: false\n    summary: Specify multiprocessing strategy\n    title: Multiprocessing\n    value_options:\n    - default\n    - billiard\n    - thread\n- fail_on_warning: \"no\"\n  opts:\n    is_required: false\n    summary: non zero exit code on warning\n    title: Fail on warning\n    value_options:\n    - \"yes\"\n    - \"no\"\n- no_fail: \"yes\"\n  opts:\n    is_required: false\n    summary: Force zero exit code, takes precedence over fail_on_warning option\n    title: Step never fails\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/mobsfscan/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/monitoring-apps-logs/1.0.3/step.yml",
    "content": "title: Mobile apps logs\nsummary: |\n  Check if your Android app kept any logs in your release build\ndescription: \"Check if an Android application contain any logs in the release app\\nIf\n  yes, this step will fail and generate a failure where you can see the count \\n\\n###\n  Troubleshooting\\n\\n- Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler)\n  to have informations from your APK\\n\"\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-logs\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-logs\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-logs/issues\npublished_at: 2021-04-06T14:50:50.331496+02:00\nsource:\n  git: https://github.com/imranMnts/bitrise-step-monitoring-apps-logs.git\n  commit: 1cc364a606fff650d95d1321dd0eee4ea8855f2f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- flutter\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: Do you want to check if the Android app contain any logs?\n    is_expand: true\n    is_required: true\n    summary: Do you want to check if the Android app contain any logs?\n    title: Check Android logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- log_count: null\n  opts:\n    description: If you have some logs in your app and want to keep them, set here\n      the count to not fail the step and be aware when new logs added to project\n    is_expand: true\n    is_required: false\n    summary: If you have some logs in your app and want to keep them\n    title: The count of logs in your app\n"
  },
  {
    "path": "steps/monitoring-apps-logs/1.0.4/step.yml",
    "content": "title: Mobile apps logs\nsummary: |\n  Check if your Android app kept any logs in your release build\ndescription: |\n  Check if an Android application contain any logs in the release app\n  If yes, this step will fail and generate a failure where you can see the count and the location of logs\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler) to have informations from your APK\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-logs\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-logs\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-logs/issues\npublished_at: 2021-07-01T12:21:58.885017+02:00\nsource:\n  git: https://github.com/imranMnts/bitrise-step-monitoring-apps-logs.git\n  commit: 643804ced68f4fcb8fb44d6ba6ec761fae0b932d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- flutter\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: Do you want to check if the Android app contain any logs?\n    is_expand: true\n    is_required: true\n    summary: Do you want to check if the Android app contain any logs?\n    title: Check Android logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- filter_path: null\n  opts:\n    description: Fill this key to not take into account when the report contains this\n      path\n    is_expand: true\n    is_required: false\n    summary: Fill this key to not take into account when the report contains this\n      path\n    title: To filter reported files\n- log_count: null\n  opts:\n    description: If you have some logs in your app and want to keep them, set here\n      the count to not fail the step and be aware when new logs added to project\n    is_expand: true\n    is_required: false\n    summary: If you have some logs in your app and want to keep them\n    title: The count of logs in your app\n"
  },
  {
    "path": "steps/monitoring-apps-logs/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/monitoring-apps-permissions/1.0.1/step.yml",
    "content": "title: Mobile apps permissions monitoring\nsummary: |\n  Check and monitor mobile applications permissions\ndescription: |\n  Check mobile applications permissions and compare with configured values to be warned when new permissions have been added\n\n  ### Usage\n\n  To give to our step the information about the expected values, you have:\n  - create a config file (which should be added to your project repository) and set `config_file_path`  to find them. You can find a config example file [here](https://github.com/imranMnts/bitrise-step-monitoring-apps-permissions)\n  - **OR** set these keys with expected values directly on Bitrise side\n    - android_permission_count\n    - ios_permission_count\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler) step\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions/issues\npublished_at: 2021-01-25T10:17:07.909756+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions.git\n  commit: 789545d567969e0a46c9d0459cce9038c3d577af\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: gnu-sed\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: To check or not Android permissions\n    is_expand: true\n    is_required: true\n    summary: Do you want check Android permissions?\n    title: Check Android\n    value_options:\n    - \"yes\"\n    - \"no\"\n- check_ios: \"yes\"\n  opts:\n    description: To check or not iOS permissions\n    is_expand: true\n    is_required: true\n    summary: Do you want check iOS permissions?\n    title: Check iOS\n    value_options:\n    - \"yes\"\n    - \"no\"\n- ios_app_name: null\n  opts:\n    description: |\n      You have to set this key if you want check ios permissions.\n      If not, you can set an empty string.\n\n      You can find it on xcode -> General -> Display Name\n    is_expand: true\n    is_required: true\n    title: iOS app name (Display Name)\n- config_file_path: null\n  opts:\n    description: |\n      The config file where we have some information like the current Android app size eg. to compare with next builds and alert if needed.\n      If you want use Environment Variables instead of the config file, do not set this key and add variables. (See [README](https://github.com/imranMnts/bitrise-step-monitoring-apps-permissions/blob/master/README.md) to see all needed variables)\n    is_expand: false\n    is_required: false\n    summary: Path of the config file\n    title: Config file path\n- android_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your Android app and be aware when useless permission added to your AndroidManifest.xml\n\n      To know how many permission you have currently in your app, you can check your APK's manifest to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your AndroidManifest.xml\n    title: Android permission\n- ios_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your ios app and be aware when useless permission added to your Info.plist\n      To know how many permission you have currently in your app, you can check your IPA's Info.plist to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your Info.plist\n    title: iOS permission\noutputs:\n- IOS_PERMISSION_COUNT: null\n  opts:\n    title: Current build's ios permission count\n- ANDROID_PERMISSION_COUNT: null\n  opts:\n    title: Current build's Android permission count\n"
  },
  {
    "path": "steps/monitoring-apps-permissions/1.0.2/step.yml",
    "content": "title: Mobile apps permissions monitoring\nsummary: |\n  Check and monitor mobile applications permissions\ndescription: |\n  Check mobile applications permissions and compare with configured values to be warned when new permissions have been added\n\n  ### Usage\n\n  To give to our step the information about the expected values, you have:\n  - create a config file (which should be added to your project repository) and set `config_file_path`  to find them. You can find a config example file [here](https://github.com/imranMnts/bitrise-step-monitoring-apps-permissions#config-file-example)\n  - **OR** set these keys with expected values directly on Bitrise side\n    - android_permission_count\n    - ios_permission_count\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler) step\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions/issues\npublished_at: 2021-04-13T12:52:37.507941+02:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions.git\n  commit: b5edf84608402d1683914a466932d4905e70325a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: gnu-sed\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: To check or not Android permissions\n    is_expand: true\n    is_required: true\n    summary: Do you want check Android permissions?\n    title: Check Android\n    value_options:\n    - \"yes\"\n    - \"no\"\n- check_ios: \"yes\"\n  opts:\n    description: To check or not iOS permissions\n    is_expand: true\n    is_required: true\n    summary: Do you want check iOS permissions?\n    title: Check iOS\n    value_options:\n    - \"yes\"\n    - \"no\"\n- ios_app_name: null\n  opts:\n    description: |\n      You have to set this key if you want check ios permissions.\n      If not, you can set an empty string.\n\n      You can find it on xcode -> General -> Display Name\n    is_expand: true\n    is_required: true\n    title: iOS app name (Display Name)\n- config_file_path: null\n  opts:\n    description: |\n      The config file where we have some information like the current Android app size eg. to compare with next builds and alert if needed.\n      If you want use Environment Variables instead of the config file, do not set this key and add variables. (See [README](https://github.com/imranMnts/bitrise-step-monitoring-apps-permissions/blob/master/README.md) to see all needed variables)\n    is_expand: false\n    is_required: false\n    summary: Path of the config file\n    title: Config file path\n- android_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your Android app and be aware when useless permission added to your AndroidManifest.xml\n\n      To know how many permission you have currently in your app, you can check your APK's manifest to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your AndroidManifest.xml\n    title: Android permission\n- ios_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your ios app and be aware when useless permission added to your Info.plist\n      To know how many permission you have currently in your app, you can check your IPA's Info.plist to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your Info.plist\n    title: iOS permission\noutputs:\n- IOS_PERMISSION_COUNT: null\n  opts:\n    title: Current build's ios permission count\n- ANDROID_PERMISSION_COUNT: null\n  opts:\n    title: Current build's Android permission count\n"
  },
  {
    "path": "steps/monitoring-apps-permissions/1.0.4/step.yml",
    "content": "title: Mobile apps permissions monitoring\nsummary: |\n  Check and monitor mobile applications permissions\ndescription: |\n  Check mobile applications permissions and compare with configured values to be warned when new permissions have been added\n\n  ### Usage\n\n  To give to our step the information about the expected values, you have:\n  - create a config file (which should be added to your project repository) and set `config_file_path`  to find them. You can find a config example file [here](https://github.com/imranMnts/bitrise-step-monitoring-apps-permissions#config-file-example)\n  - **OR** set these keys with expected values directly on Bitrise side\n    - android_permission_count\n    - ios_permission_count\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler) step\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions/issues\npublished_at: 2021-04-27T13:03:52.623537+02:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-monitoring-apps-permissions.git\n  commit: 603fbe69677218f31a2e0dea138d56bffd253132\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: gnu-sed\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: To check or not Android permissions\n    is_expand: true\n    is_required: true\n    summary: Do you want check Android permissions?\n    title: Check Android\n    value_options:\n    - \"yes\"\n    - \"no\"\n- check_ios: \"yes\"\n  opts:\n    description: To check or not iOS permissions\n    is_expand: true\n    is_required: true\n    summary: Do you want check iOS permissions?\n    title: Check iOS\n    value_options:\n    - \"yes\"\n    - \"no\"\n- ios_app_name: null\n  opts:\n    description: |\n      You have to set this key if you want check ios permissions.\n      If not, you can set an empty string.\n\n      You can find it on xcode -> General -> Display Name\n    is_expand: true\n    is_required: true\n    title: iOS app name (Display Name)\n- config_file_path: null\n  opts:\n    description: |\n      The config file where we have some information like the current Android app size eg. to compare with next builds and alert if needed.\n      If you want use Environment Variables instead of the config file, do not set this key and add variables. (See [README](https://github.com/imranMnts/bitrise-step-monitoring-apps-permissions/blob/master/README.md) to see all needed variables)\n    is_expand: false\n    is_required: false\n    summary: Path of the config file\n    title: Config file path\n- android_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your Android app and be aware when useless permission added to your AndroidManifest.xml\n\n      To know how many permission you have currently in your app, you can check your APK's manifest to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your AndroidManifest.xml\n    title: Android permission\n- ios_permission_count: null\n  opts:\n    description: |\n      Set this key if you want to follow up the count of permission used by your ios app and be aware when useless permission added to your Info.plist\n      To know how many permission you have currently in your app, you can check your IPA's Info.plist to know the exact count.\n\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Number of permission into your Info.plist\n    title: iOS permission\noutputs:\n- IOS_PERMISSION_COUNT: null\n  opts:\n    title: Current build's ios permission count\n- ANDROID_PERMISSION_COUNT: null\n  opts:\n    title: Current build's Android permission count\n"
  },
  {
    "path": "steps/monitoring-apps-permissions/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/monitoring-apps-sizes/1.0.1/step.yml",
    "content": "title: Mobile apps sizes monitoring\nsummary: |\n  Check and monitor mobile applications sizes\ndescription: |\n  Check mobile applications sizes and compare with configured values to be warned when apps sizes increased\n\n  ### Usage\n\n\n  To give to our step the information about the expected values, you have:\n  - create a config file (which should be added to your project repository) and set `config_file_path`  to find them. You can find a config example file [here](#config-file-example)\n  - **OR** set these keys with expected values directly on Bitrise side\n    - android_apk_size\n    - ios_ipa_size\n    - alert_threshold\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler) step\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes/issues\npublished_at: 2021-01-25T10:18:16.323562+01:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes.git\n  commit: ac8c4730107c9cb6627209966fb23dfce2c0e13f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: To check or not Android size\n    is_expand: true\n    is_required: true\n    summary: Do you want check Android size?\n    title: Check Android\n    value_options:\n    - \"yes\"\n    - \"no\"\n- check_ios: \"yes\"\n  opts:\n    description: To check or not iOS size\n    is_expand: true\n    is_required: true\n    summary: Do you want check iOS size?\n    title: Check iOS\n    value_options:\n    - \"yes\"\n    - \"no\"\n- config_file_path: null\n  opts:\n    description: |\n      The config file where we have some information like the current Android app size eg. to compare with next builds and alert if needed.\n      If you want use Environment Variables instead of the config file, do not set this key and add variables. (See [README](https://github.com/imranMnts/bitrise-step-monitoring-apps-sizes/blob/master/README.md) to see all needed variables)\n    is_expand: false\n    is_required: false\n    summary: Path of the config file\n    title: Config file path\n- android_apk_size: null\n  opts:\n    description: |\n      Set this key if you want to follow up on your project's Android APK size\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Android APK size (MB)\n    title: Android APK size\n- ios_ipa_size: null\n  opts:\n    description: |\n      Set this key if you want follow up your project's ios IPA size\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: iOS IPA size (MB)\n    title: iOS IPA size\n- alert_threshold: \"5\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Threshold to alert when app size increase (MB)\n    title: Alert threshold\n    value_options:\n    - \"3\"\n    - \"5\"\n    - \"10\"\n    - \"20\"\noutputs:\n- NEW_IPA_SIZE: null\n  opts:\n    title: Current build's ios IPA size (MB)\n- NEW_APK_SIZE: null\n  opts:\n    title: Current build's Android APK size (MB)\n"
  },
  {
    "path": "steps/monitoring-apps-sizes/1.0.2/step.yml",
    "content": "title: Mobile apps sizes monitoring\nsummary: |\n  Check and monitor mobile applications sizes\ndescription: |\n  Check mobile applications sizes and compare with configured values to be warned when apps sizes increased\n\n  ### Usage\n\n\n  To give to our step the information about the expected values, you have:\n  - create a config file (which should be added to your project repository) and set `config_file_path`  to find them. You can find a config example file [here](https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes#config-file-example)\n  - **OR** set these keys with expected values directly on Bitrise side\n    - android_apk_size\n    - ios_ipa_size\n    - alert_threshold\n\n  ### Troubleshooting\n\n  - Be aware, you have to launch this step after [apps-decompiler](https://github.com/imranMnts/bitrise-step-apps-decompiler) step\nwebsite: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes\nsource_code_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes\nsupport_url: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes/issues\npublished_at: 2021-04-13T12:51:49.656894+02:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-monitoring-apps-sizes.git\n  commit: dbffbfa4a2a279194eab53ad8cb28f40137f812d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- check_android: \"yes\"\n  opts:\n    description: To check or not Android size\n    is_expand: true\n    is_required: true\n    summary: Do you want check Android size?\n    title: Check Android\n    value_options:\n    - \"yes\"\n    - \"no\"\n- check_ios: \"yes\"\n  opts:\n    description: To check or not iOS size\n    is_expand: true\n    is_required: true\n    summary: Do you want check iOS size?\n    title: Check iOS\n    value_options:\n    - \"yes\"\n    - \"no\"\n- config_file_path: null\n  opts:\n    description: |\n      The config file where we have some information like the current Android app size eg. to compare with next builds and alert if needed.\n      If you want use Environment Variables instead of the config file, do not set this key and add variables. (See [README](https://github.com/imranMnts/bitrise-step-monitoring-apps-sizes/blob/master/README.md) to see all needed variables)\n    is_expand: false\n    is_required: false\n    summary: Path of the config file\n    title: Config file path\n- android_apk_size: null\n  opts:\n    description: |\n      Set this key if you want to follow up on your project's Android APK size\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: Android APK size (MB)\n    title: Android APK size\n- ios_ipa_size: null\n  opts:\n    description: |\n      Set this key if you want follow up your project's ios IPA size\n      You can add a config file where you can add all application information and set `config_file_path` to find it.\n\n      Tip: You can set it to 0 and launch one time this step to check report file to know the current value.\n    is_expand: false\n    is_required: false\n    summary: iOS IPA size (MB)\n    title: iOS IPA size\n- alert_threshold: \"5\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Threshold to alert when app size increase (MB)\n    title: Alert threshold\n    value_options:\n    - \"3\"\n    - \"5\"\n    - \"10\"\n    - \"20\"\noutputs:\n- NEW_IPA_SIZE: null\n  opts:\n    title: Current build's ios IPA size (MB)\n- NEW_APK_SIZE: null\n  opts:\n    title: Current build's Android APK size (MB)\n"
  },
  {
    "path": "steps/monitoring-apps-sizes/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/monkop-android/1.0.1/step.yml",
    "content": "title: Monkop.com Android Testing Cloud.\nsummary: Test your Android app using Monkop. Real performance analysis using real\n  devices.\ndescription: |-\n  Use this step to test your deployed APK on Monkop.\n\n  Monkop enable to run smoke tests on several real devices with no officer. Get detailed information about the native app’s performance.\n\n  If you don't have a Monkop account, register for free [here](https://console.monkop.com/register.xhtml) and get your API KEY!\n  The API_KEY value can be found on \"Add-ons\" section under \"API Key\" option.\nwebsite: https://github.com/MonkopApps/bitrise-monkop-android\nsource_code_url: https://github.com/MonkopApps/bitrise-monkop-android\nsupport_url: https://github.com/MonkopApps/bitrise-monkop-android/issues\npublished_at: 2016-11-04T12:42:53.869512912-03:00\nsource:\n  git: https://github.com/MonkopApps/bitrise-monkop-android.git\n  commit: 80329361ee1c42d07a9a49db50d7165b9fc92a3d\nhost_os_tags:\n- ubuntu\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ndeps:\n  apt_get:\n  - name: git\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: APK file path\n- api_key: $MONKOP_API_KEY\n  opts:\n    description: \"This is the API key value associated to your account.\\n\\n## Where\n      can you get it?\\n\\n[Sign in](https://console.monkop.com/login.xhtml) to your\n      Monkop account,\\nclick on [Add-ons](https://console.monkop.com/addOns.xhtml)\n      and select the \\n\\\"API Key\\\" add-on. Your API key will appear once you enable\n      the add-on.\"\n    is_required: true\n    summary: \"\"\n    title: Account API key\n"
  },
  {
    "path": "steps/monkop-android/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/msbuild-sonarscanner-begin/0.9.1/step.yml",
    "content": "title: MSBuild SonarScanner (Begin)\nsummary: |\n  Step for running SonarScanner agains .NET (Xamarin) projects.\n  This is the first step from two.\ndescription: \"This step runs MSBuild SonarScanner. The scanner for dotnet consists\n  of two steps. \\nThis is the first step that executes `begin` CLI command. \\nIn between\n  of `begin` and `end` steps the build, test run and code coverage should happen.\\n\\nCheck\n  official documentation [SonarScanner for MSBuild](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/)\\nto\n  understand how the scan process happens for dotnet.\\n\\nThis step can be used for\n  self-hosted SonarQube and SonarCloud.\\n\"\nwebsite: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin\nsource_code_url: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin\nsupport_url: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin/issues\npublished_at: 2019-11-23T01:23:13.680037+02:00\nsource:\n  git: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin.git\n  commit: 3500d5ac9f222947116efb24625bf57bb221245a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\n  apt_get:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      The version used to download CLI.\n      Latest version can be found at [SonarQube](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/)\n    is_required: true\n    title: SonarScanner for MSBuild CLI Version\n  scanner_version: 4.7.1.2311\n- opts:\n    description: This will be the value of `sonar.login`\n    is_required: true\n    is_sensitive: true\n    title: Username or access token to authenticate with to SonarQube\n  sonar_login: $SONAR_LOGIN\n- opts:\n    description: This will be the value of `sonar.projectKey`\n    is_required: true\n    title: Key of the analyzed project\n  sonar_project_key: $SONAR_PROJECT_KEY\n- opts:\n    description: |-\n      This will be the value of `sonar.host.url`.\n      It can be SonarQube or SonarCloud.\n    is_required: true\n    title: SonarQube host URL\n  sonar_host_url: https://sonarcloud.io\n- opts:\n    description: This will be the value of `sonar.organization`\n    is_required: false\n    title: Organization Key\n  sonar_organization: null\n- opts:\n    description: Specifies the version of your project.\n    is_required: false\n    title: Version of your project (Recommended)\n  sonar_project_version: null\n- opts:\n    description: |-\n      Specifies the name of the analyzed project in SonarQube.\n      Adding this argument will overwrite the project name in SonarQube if it already exists.\n    is_required: false\n    title: Name of the analyzed project\n  sonar_project_name: null\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: |-\n      Whether trace of shell commands should be printd to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- SONAR_SCANNER_FILE_PATH: null\n  opts:\n    title: The path to `SonarScanner.MSBuild.exe` to be used in the MSBuild SonarScanner\n      End step\n"
  },
  {
    "path": "steps/msbuild-sonarscanner-begin/0.9.2/step.yml",
    "content": "title: MSBuild SonarScanner (Begin)\nsummary: |\n  Step for running SonarScanner agains .NET (Xamarin) projects.\n  This is the first step from two.\ndescription: \"This step runs MSBuild SonarScanner. The scanner for dotnet consists\n  of two steps. \\nThis is the first step that executes `begin` CLI command. \\nIn between\n  of `begin` and `end` steps the build, test run and code coverage should happen.\\n\\nCheck\n  official documentation [SonarScanner for MSBuild](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/)\\nto\n  understand how the scan process happens for dotnet.\\n\\nThis step can be used for\n  self-hosted SonarQube and SonarCloud.\\n\"\nwebsite: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin\nsource_code_url: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin\nsupport_url: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin/issues\npublished_at: 2019-12-03T15:02:17.571279+02:00\nsource:\n  git: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin.git\n  commit: ff6095f09decbb5025649f7ef8d4951830843efc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\n  apt_get:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      The version used to download CLI.\n      Latest version can be found at [SonarQube](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/)\n    is_required: true\n    title: SonarScanner for MSBuild CLI Version\n  scanner_version: 4.7.1.2311\n- opts:\n    description: This will be the value of `sonar.login`\n    is_required: true\n    is_sensitive: true\n    title: Username or access token to authenticate with to SonarQube\n  sonar_login: $SONAR_LOGIN\n- opts:\n    description: This will be the value of `sonar.projectKey`\n    is_required: true\n    title: Key of the analyzed project\n  sonar_project_key: $SONAR_PROJECT_KEY\n- opts:\n    description: |-\n      This will be the value of `sonar.host.url`.\n      It can be SonarQube or SonarCloud.\n    is_required: true\n    title: SonarQube host URL\n  sonar_host_url: https://sonarcloud.io\n- opts:\n    description: This will be the value of `sonar.organization`\n    is_required: false\n    title: Organization Key\n  sonar_organization: null\n- opts:\n    description: Specifies the version of your project.\n    is_required: false\n    title: Version of your project (Recommended)\n  sonar_project_version: null\n- opts:\n    description: |-\n      Specifies the name of the analyzed project in SonarQube.\n      Adding this argument will overwrite the project name in SonarQube if it already exists.\n    is_required: false\n    title: Name of the analyzed project\n  sonar_project_name: null\n- opts:\n    description: |-\n      Specifies any other properties. For example:\n      - sonar.exclusions=Tests/**/*,UITests/**/*\n      - sonar.cs.opencover.reportsPaths=\"path/to/coverage.xml\"\n      - sonar.cs.vstest.reportsPaths=\"path/to/test-results.xml\"\n      Separate properties with a new line.\n    is_required: false\n    title: All other Sonar Scanner Properties\n  sonar_properties: null\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: |-\n      Whether trace of shell commands should be printd to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- SONAR_SCANNER_FILE_PATH: null\n  opts:\n    title: The path to `SonarScanner.MSBuild.exe` to be used in the MSBuild SonarScanner\n      End step\n"
  },
  {
    "path": "steps/msbuild-sonarscanner-begin/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/msbuild-sonarscanner-end/0.9.0/step.yml",
    "content": "title: MSBuild SonarScanner (End)\nsummary: |\n  Step for running SonarScanner agains .NET (Xamarin) projects. This the the last step from two.\ndescription: \"This step runs MSBuild SonarScanner. The scanner for dotnet consists\n  of two steps. \\nThis is the last step that executes `end` CLI command. \\nIn between\n  of `begin` and `end` steps the build, test run and code coverage should happen.\\n\\nCheck\n  official documentation [SonarScanner for MSBuild](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/)\\nto\n  understand how the scan process happens for dotnet.\\n\\nThis step finishes the execution.\n  The main setup happens in the [Begin Step](https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin)\\n\\nThis\n  step will be skipped in case `$SONAR_SCANNER_FILE_PATH` environment variable is\n  not defined.\\n\"\nwebsite: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-end\nsource_code_url: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-end\nsupport_url: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-end/issues\npublished_at: 2019-11-23T01:25:55.09991+02:00\nsource:\n  git: https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-end.git\n  commit: 1a043e35d167be332c2f0aa2ee5d305b98d76798\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: '{{getenv \"SONAR_SCANNER_FILE_PATH\" | ne \"\"}}'\ninputs:\n- opts:\n    description: This will be the value of `sonar.login`\n    is_required: true\n    is_sensitive: true\n    title: Username or access token to authenticate with to SonarQube\n  sonar_login: $SONAR_LOGIN\n- opts:\n    category: Config\n    description: |-\n      SonarScanner should've been prepared in the [MSBuild SonarScanner (Begin)](https://github.com/Diversido/bitrise-step-msbuild-sonarscanner-begin) step.\n      `$SONAR_SCANNER_FILE_PATH` is generated by the Begin step.\n      This property doesn't require a manual change.\n    is_dont_change_value: true\n    is_required: true\n    title: A file path to `SonarScanner.MSBuild.exe`\n  sonarscanner_file_path: $SONAR_SCANNER_FILE_PATH\n- is_debug: \"false\"\n  opts:\n    category: Debug\n    description: |-\n      Whether trace of shell commands should be printd to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/msbuild-sonarscanner-end/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/mussel/1.0.0/step.yml",
    "content": "title: Mussel\nsummary: A framework for easily testing Push Notifications, Universal Links and Routing\n  in XCUITests.\ndescription: \"As of Xcode 14.4, users are able to test Push Notifications via the\n  simulator. \\nUnfortunately, Apple has yet to introduce the ability to leverage this\n  new method within the XCUITest Framework.\\n\\nTesting Universal Links can also be\n  an adventure, potentially accumulating lots of extra unwanted time in UI Tests,\n  especially if your team wants to speed up your app's regression progress. \\nConventional\n  methods resorted to using iMessage or Contacts to open Universal Links which routed\n  to a specific feature within an application.\\n\\nMussel introduces a quick and simple\n  way to test Push Notifications and Universal Links which route to any specific features\n  within your iOS app.\\n\\nHow It Works:\\n  1. An Engineer triggers XCUITests in XCode\n  manually or through your Continuous Integration platform of choice.\\n  2. Mussel\n  Server boots up along with the iOS Simulator.\\n  3. A Test Case triggers a Push\n  Notification or Universal Link Test Case\\n  4. The Test Case sends a payload containing\n  Push Notification or Universal Link data via POST Request.\\n  5. Server runs respective\n  xcrun simctl command for Push Notifications or Universal Links.\\n  6. The command\n  presents a Push Notification or launches a Universal Link within the iOS Simulator.\"\nwebsite: https://github.com/UrbanCompass/bitrise-step-mussel\nsource_code_url: https://github.com/UrbanCompass/bitrise-step-mussel\nsupport_url: https://github.com/UrbanCompass/bitrise-step-mussel/issues\npublished_at: 2021-08-16T13:36:05.300963-04:00\nsource:\n  git: https://github.com/UrbanCompass/bitrise-step-mussel.git\n  commit: 12e06201dd0b06452ffa8102843cd2144bd12345\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- mussel_version: 1.0.0\n  opts:\n    description: |\n      The version of Mussel and MusselServer to use.\n      Choose a version from: https://github.com/UrbanCompass/Mussel/releases\n    is_required: true\n    title: Mussel server version\n"
  },
  {
    "path": "steps/mussel/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/nitro-android/4.2.1/step.yml",
    "content": "title: Nitro for Android\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for Android using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-android\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-android\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-android/issues\npublished_at: 2022-12-05T17:02:45.747299-05:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-android.git\n  commit: 05798810ea84ed1eef233b340ce2db960ff38021\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\n  apt_get:\n  - name: pigz\n  - name: file\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- flavor: null\n  opts:\n    is_expand: true\n    summary: Set product flavor for Gradle build variant\n    title: Flavor\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore url\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore password\n    title: Keystore password\n- keystore_key_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore alias\n    title: Keystore alias\n- keystore_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore key password\n    title: Keystore key password\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: $NITRO_DISABLE_CACHE\n  opts:\n    category: Caching\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed\n    title: Disable builds caching\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: $NITRO_DISABLE_METRO_CACHE\n  opts:\n    category: Advanced\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature\n    title: Disable Metro bundler cache\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n  output_directory: $BITRISE_DEPLOY_DIR\n- entry_file: $ENTRY_FILE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- fail_safe: $NITRO_FAIL_SAFE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps\n    title: Fail-safe mode\n- api_key: $NITRO_API_KEY\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key provided by Nitro. It should be defined by setting NITRO_API_KEY\n      secret.\n    title: Nitro API key\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failed)\n    summary: The status of the latest build (success / failed)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the build artifacts\n    summary: The full path to access the build artifacts\n    title: Build artifacts location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n"
  },
  {
    "path": "steps/nitro-android/4.4.0/step.yml",
    "content": "title: Nitro for Android\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for Android using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-android\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-android\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-android/issues\npublished_at: 2023-01-05T18:28:53.427222-03:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-android.git\n  commit: 4fa4033c35f16f43049614f91d5befe1e76d013c\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\n  apt_get:\n  - name: pigz\n  - name: file\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- flavor: null\n  opts:\n    is_expand: true\n    summary: Set product flavor for Gradle build variant\n    title: Flavor\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore url\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore password\n    title: Keystore password\n- keystore_key_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore alias\n    title: Keystore alias\n- keystore_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore key password\n    title: Keystore key password\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: $NITRO_DISABLE_CACHE\n  opts:\n    category: Caching\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed\n    title: Disable builds caching\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: $NITRO_DISABLE_METRO_CACHE\n  opts:\n    category: Caching\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature\n    title: Disable Metro bundler cache\n- aws_s3_access_key_id: $NITRO_AWS_S3_ACCESS_KEY_ID\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS access key ID for S3 bucket build caching\n    title: AWS S3 access key ID\n- aws_s3_secret_access_key: $NITRO_AWS_S3_SECRET_ACCESS_KEY\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS secret access key for S3 bucket build caching\n    title: AWS S3 secret access key\n- aws_s3_region: $NITRO_AWS_S3_REGION\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS region where S3 bucket for build caching is located\n    title: AWS S3 region\n- aws_s3_bucket: $NITRO_AWS_S3_BUCKET\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS bucket name for S3 bucket build caching\n    title: AWS S3 bucket name\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- detox_configuration: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Select a device configuration from your defined configurations.\n    title: Detox configuration\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n  output_directory: $BITRISE_DEPLOY_DIR\n- entry_file: $ENTRY_FILE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- fail_safe: $NITRO_FAIL_SAFE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps\n    title: Fail-safe mode\n- api_key: $NITRO_API_KEY\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key provided by Nitro. It should be defined by setting NITRO_API_KEY\n      secret.\n    title: Nitro API key\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failed)\n    summary: The status of the latest build (success / failed)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n- NITRO_APP_PATH: null\n  opts:\n    description: The full path to access the Android package (.apk)\n    summary: The full path to access the Android package (.apk)\n    title: Build application package location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the Android package (.apk)\n    summary: The full path to access the Android package (.apk)\n    title: Build application package location\n"
  },
  {
    "path": "steps/nitro-android/4.5.0/step.yml",
    "content": "title: Nitro for Android\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for Android using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-android\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-android\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-android/issues\npublished_at: 2023-01-31T09:21:22.086062-03:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-android.git\n  commit: 74c8e034270873ea9849db1de6bdcb8c146220d7\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\n  apt_get:\n  - name: pigz\n  - name: file\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- flavor: null\n  opts:\n    is_expand: true\n    summary: Set product flavor for Gradle build variant\n    title: Flavor\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore url\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore password\n    title: Keystore password\n- keystore_key_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore alias\n    title: Keystore alias\n- keystore_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore key password\n    title: Keystore key password\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: $NITRO_DISABLE_CACHE\n  opts:\n    category: Caching\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed\n    title: Disable builds caching\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: $NITRO_DISABLE_METRO_CACHE\n  opts:\n    category: Caching\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature\n    title: Disable Metro bundler cache\n- aws_s3_access_key_id: $NITRO_AWS_S3_ACCESS_KEY_ID\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS access key ID for S3 bucket build caching\n    title: AWS S3 access key ID\n- aws_s3_secret_access_key: $NITRO_AWS_S3_SECRET_ACCESS_KEY\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS secret access key for S3 bucket build caching\n    title: AWS S3 secret access key\n- aws_s3_region: $NITRO_AWS_S3_REGION\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS region where S3 bucket for build caching is located\n    title: AWS S3 region\n- aws_s3_bucket: $NITRO_AWS_S3_BUCKET\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS bucket name for S3 bucket build caching\n    title: AWS S3 bucket name\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- detox_configuration: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Select a device configuration from your defined configurations.\n    title: Detox configuration\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n  output_directory: $BITRISE_DEPLOY_DIR\n- entry_file: $ENTRY_FILE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- debug: \"no\"\n  opts:\n    category: Advanced\n    description: Enable step debugging\n    summary: Enable step debugging\n    title: Debug step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fail_safe: $NITRO_FAIL_SAFE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps\n    title: Fail-safe mode\n- api_key: $NITRO_API_KEY\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key provided by Nitro. It should be defined by setting NITRO_API_KEY\n      secret.\n    title: Nitro API key\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failed)\n    summary: The status of the latest build (success / failed)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n- NITRO_APP_PATH: null\n  opts:\n    description: The full path to access the Android package (.apk)\n    summary: The full path to access the Android package (.apk)\n    title: Build application package location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the Android package (.apk)\n    summary: The full path to access the Android package (.apk)\n    title: Build application package location\n"
  },
  {
    "path": "steps/nitro-android/4.6.0/step.yml",
    "content": "title: Nitro for Android\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for Android using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-android\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-android\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-android/issues\npublished_at: 2023-02-28T11:46:57.576398-03:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-android.git\n  commit: 79ebc42d2a515c3ff0ee48f0d66c9941c81aaf2d\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\n  apt_get:\n  - name: pigz\n  - name: file\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: null\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key required by Nitro. It is recommended to set a $NITRO_API_KEY\n      as a Bitrise secret.\n    title: Nitro API key\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- flavor: null\n  opts:\n    is_expand: true\n    summary: Set product flavor for Gradle build variant\n    title: Flavor\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- keystore_url: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore url (defaults to $BITRISEIO_ANDROID_KEYSTORE_URL if present)\n    title: Keystore url\n- keystore_password: null\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore password (defaults to $BITRISEIO_ANDROID_KEYSTORE_PASSWORD if\n      present)\n    title: Keystore password\n- keystore_key_alias: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Keystore alias (defaults to $BITRISEIO_ANDROID_KEYSTORE_ALIAS if present)\n    title: Keystore alias\n- keystore_key_password: null\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Keystore key password (defaults to $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n      if present)\n    title: Keystore key password\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: null\n  opts:\n    category: Caching\n    description: When setting this option to `yes` build cache optimizations won't\n      be performed. (defaults to $NITRO_DISABLE_CACHE if present)\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed. (defaults to $NITRO_DISABLE_CACHE if present)\n    title: Disable builds caching\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: null\n  opts:\n    category: Caching\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature. (defaults to $NITRO_DISABLE_METRO_CACHE if present)\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature. (defaults to $NITRO_DISABLE_METRO_CACHE if present)\n    title: Disable Metro bundler cache\n- aws_s3_access_key_id: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS access key ID for S3 bucket build caching. (defaults to $NITRO_AWS_S3_ACCESS_KEY_ID\n      if present)\n    title: AWS S3 access key ID\n- aws_s3_secret_access_key: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS secret access key for S3 bucket build caching. (defaults to $NITRO_AWS_S3_SECRET_ACCESS_KEY\n      if present)\n    title: AWS S3 secret access key\n- aws_s3_region: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS region where S3 bucket for build caching is located. (defaults to\n      $NITRO_AWS_S3_REGION if present)\n    title: AWS S3 region\n- aws_s3_bucket: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS bucket name for S3 bucket build caching. (defaults to $NITRO_AWS_S3_BUCKET\n      if present)\n    title: AWS S3 bucket name\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- detox_configuration: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Select a device configuration from your defined configurations.\n    title: Detox configuration\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files.\n      (defaults to $BITRISE_DEPLOY_DIR)\n    title: Output directory\n  output_directory: null\n- entry_file: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation. (defaults to $ENTRY_FILE if present)\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- debug: \"no\"\n  opts:\n    category: Advanced\n    description: Enable step debugging\n    summary: Enable step debugging\n    title: Debug step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fail_safe: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps. (defaults to $NITRO_FAIL_SAFE if\n      present)\n    title: Fail-safe mode\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failed)\n    summary: The status of the latest build (success / failed)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n- NITRO_APP_PATH: null\n  opts:\n    description: The full path to access the Android package (.apk)\n    summary: The full path to access the Android package (.apk)\n    title: Build application package location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the Android package (.apk)\n    summary: The full path to access the Android package (.apk)\n    title: Build application package location\n"
  },
  {
    "path": "steps/nitro-android/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/nitro-ios/4.2.1/step.yml",
    "content": "title: Nitro for iOS\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for iOS using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-ios\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-ios\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-ios/issues\npublished_at: 2022-12-06T09:23:28.6884-05:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-ios.git\n  commit: 88689d87044cf19270eae76fe83cd5a1b8b7434e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- opts:\n    is_expand: true\n    summary: The name of the iOS scheme\n    title: The name of the iOS scheme\n  scheme: null\n- opts:\n    is_expand: true\n    summary: The path relative to project root directory where the custom `.xcconfig`\n      file is located\n    title: Path to a custom xcconfig file\n  xcconfig_path: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- certificate_url: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The url to download and install the certificate\n    title: Certificate url\n- certificate_passphrase: null\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Certificate passphrase\n    title: Certificate passphrase\n- codesigning_identity: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Codesigning identity\n    title: Codesigning identity\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: A string containing a '|' separated values where provisioning profiles\n      are located e.g. url1|url2|url3\n    title: Provisioning profile urls\n  provisioning_profile_urls: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: The name of the provisioning profile when using a single one\n    title: Provisioning profile specifier\n  provisioning_profile_specifier: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: Specify the Team ID you want to use for the Apple Developer Portal\n    title: Team ID\n  team_id: null\n- export_method: ad-hoc\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The export method used to generate the IPA\n    title: Export Method\n    value_options:\n    - ad-hoc\n    - app-store\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: $NITRO_DISABLE_CACHE\n  opts:\n    category: Caching\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed\n    title: Disable builds caching\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: $NITRO_DISABLE_METRO_CACHE\n  opts:\n    category: Advanced\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature\n    title: Disable Metro bundler cache\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n  output_directory: $BITRISE_DEPLOY_DIR\n- entry_file: $ENTRY_FILE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- fail_safe: $NITRO_FAIL_SAFE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps\n    title: Fail-safe mode\n- api_key: $NITRO_API_KEY\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key provided by Nitro. It should be defined by setting NITRO_API_KEY\n      secret.\n    title: Nitro API key\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failure)\n    summary: The status of the latest build (success / failure)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the build artifacts\n    summary: The full path to access the build artifacts\n    title: Build artifacts location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n"
  },
  {
    "path": "steps/nitro-ios/4.4.0/step.yml",
    "content": "title: Nitro for iOS\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for iOS using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-ios\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-ios\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-ios/issues\npublished_at: 2023-01-05T18:42:42.103952-03:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-ios.git\n  commit: ae597394f844d8c234e7e4c597ef6da021eb5a9c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- opts:\n    is_expand: true\n    summary: The name of the iOS scheme\n    title: The name of the iOS scheme\n  scheme: null\n- opts:\n    is_expand: true\n    summary: The path relative to project root directory where the custom `.xcconfig`\n      file is located\n    title: Path to a custom xcconfig file\n  xcconfig_path: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- certificate_url: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The url to download and install the certificate\n    title: Certificate url\n- certificate_passphrase: null\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Certificate passphrase\n    title: Certificate passphrase\n- codesigning_identity: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Codesigning identity\n    title: Codesigning identity\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: A string containing a '|' separated values where provisioning profiles\n      are located e.g. url1|url2|url3\n    title: Provisioning profile urls\n  provisioning_profile_urls: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: The name of the provisioning profile when using a single one\n    title: Provisioning profile specifier\n  provisioning_profile_specifier: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: Specify the Team ID you want to use for the Apple Developer Portal\n    title: Team ID\n  team_id: null\n- export_method: ad-hoc\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The export method used to generate the IPA\n    title: Export Method\n    value_options:\n    - ad-hoc\n    - app-store\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: $NITRO_DISABLE_CACHE\n  opts:\n    category: Caching\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed\n    title: Disable builds caching\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: $NITRO_DISABLE_METRO_CACHE\n  opts:\n    category: Caching\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature\n    title: Disable Metro bundler cache\n- aws_s3_access_key_id: $NITRO_AWS_S3_ACCESS_KEY_ID\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS access key ID for S3 bucket build caching\n    title: AWS S3 access key ID\n- aws_s3_secret_access_key: $NITRO_AWS_S3_SECRET_ACCESS_KEY\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS secret access key for S3 bucket build caching\n    title: AWS S3 secret access key\n- aws_s3_region: $NITRO_AWS_S3_REGION\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS region where S3 bucket for build caching is located\n    title: AWS S3 region\n- aws_s3_bucket: $NITRO_AWS_S3_BUCKET\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS bucket name for S3 bucket build caching\n    title: AWS S3 bucket name\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- detox_configuration: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Select a device configuration from your defined configurations.\n    title: Detox configuration\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n  output_directory: $BITRISE_DEPLOY_DIR\n- entry_file: $ENTRY_FILE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- fail_safe: $NITRO_FAIL_SAFE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps\n    title: Fail-safe mode\n- api_key: $NITRO_API_KEY\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key provided by Nitro. It should be defined by setting NITRO_API_KEY\n      secret.\n    title: Nitro API key\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failure)\n    summary: The status of the latest build (success / failure)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n- NITRO_APP_PATH: null\n  opts:\n    description: The full path to access the iOS package (.app or .ipa)\n    summary: The full path to access the iOS package (.app or .ipa)\n    title: Build application package location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the iOS package (.app or .ipa)\n    summary: The full path to access the iOS package (.app or .ipa)\n    title: Build application package location\n"
  },
  {
    "path": "steps/nitro-ios/4.5.0/step.yml",
    "content": "title: Nitro for iOS\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for iOS using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-ios\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-ios\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-ios/issues\npublished_at: 2023-01-31T15:54:07.13303-03:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-ios.git\n  commit: ff2c610dd47e61c1a0ff56ea22c7ba879ef00e44\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- opts:\n    is_expand: true\n    summary: The name of the iOS scheme\n    title: The name of the iOS scheme\n  scheme: null\n- opts:\n    is_expand: true\n    summary: The path relative to project root directory where the custom `.xcconfig`\n      file is located\n    title: Path to a custom xcconfig file\n  xcconfig_path: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- certificate_url: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The url to download and install the certificate\n    title: Certificate url\n- certificate_passphrase: null\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Certificate passphrase\n    title: Certificate passphrase\n- codesigning_identity: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Codesigning identity\n    title: Codesigning identity\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: A string containing a '|' separated values where provisioning profiles\n      are located e.g. url1|url2|url3\n    title: Provisioning profile urls\n  provisioning_profile_urls: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: The name of the provisioning profile when using a single one\n    title: Provisioning profile specifier\n  provisioning_profile_specifier: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: Specify the Team ID you want to use for the Apple Developer Portal\n    title: Team ID\n  team_id: null\n- export_method: ad-hoc\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The export method used to generate the IPA\n    title: Export Method\n    value_options:\n    - ad-hoc\n    - app-store\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: $NITRO_DISABLE_CACHE\n  opts:\n    category: Caching\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed\n    title: Disable builds caching\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: $NITRO_DISABLE_METRO_CACHE\n  opts:\n    category: Caching\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature\n    title: Disable Metro bundler cache\n- aws_s3_access_key_id: $NITRO_AWS_S3_ACCESS_KEY_ID\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS access key ID for S3 bucket build caching\n    title: AWS S3 access key ID\n- aws_s3_secret_access_key: $NITRO_AWS_S3_SECRET_ACCESS_KEY\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS secret access key for S3 bucket build caching\n    title: AWS S3 secret access key\n- aws_s3_region: $NITRO_AWS_S3_REGION\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS region where S3 bucket for build caching is located\n    title: AWS S3 region\n- aws_s3_bucket: $NITRO_AWS_S3_BUCKET\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS bucket name for S3 bucket build caching\n    title: AWS S3 bucket name\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- detox_configuration: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Select a device configuration from your defined configurations.\n    title: Detox configuration\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n  output_directory: $BITRISE_DEPLOY_DIR\n- entry_file: $ENTRY_FILE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- debug: \"no\"\n  opts:\n    category: Advanced\n    description: Enable step debugging\n    summary: Enable step debugging\n    title: Debug step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fail_safe: $NITRO_FAIL_SAFE\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps\n    title: Fail-safe mode\n- api_key: $NITRO_API_KEY\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key provided by Nitro. It should be defined by setting NITRO_API_KEY\n      secret.\n    title: Nitro API key\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failure)\n    summary: The status of the latest build (success / failure)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n- NITRO_APP_PATH: null\n  opts:\n    description: The full path to access the iOS package (.app or .ipa)\n    summary: The full path to access the iOS package (.app or .ipa)\n    title: Build application package location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the iOS package (.app or .ipa)\n    summary: The full path to access the iOS package (.app or .ipa)\n    title: Build application package location\n"
  },
  {
    "path": "steps/nitro-ios/4.7.0/step.yml",
    "content": "title: Nitro for iOS\nsummary: |\n  Build your React Native app faster than ever with Nitro\ndescription: |\n  This step builds your React Native app for iOS using [Nitro](https://nitro.build). Get your **API key** on our [website](https://nitro.build).\nwebsite: https://github.com/nitro-build/bitrise-step-nitro-ios\nsource_code_url: https://github.com/nitro-build/bitrise-step-nitro-ios\nsupport_url: https://github.com/nitro-build/bitrise-step-nitro-ios/issues\npublished_at: 2023-03-07T08:16:37.912187-03:00\nsource:\n  git: https://github.com/nitro-build/bitrise-step-nitro-ios.git\n  commit: b316ffe2c47c95328266ee9e56ce868aa2120b3f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: pigz\n  - name: gnu-sed\n  - name: jq\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: null\n  opts:\n    is_expand: true\n    is_sensitive: true\n    summary: The API key required by Nitro. It is recommended to set a $NITRO_API_KEY\n      as a Bitrise secret.\n    title: Nitro API key\n- opts:\n    is_expand: true\n    summary: The directory within your project, in which your code is located. Leave\n      this field empty if your code is not located in a subdirectory\n    title: Root directory\n  root_directory: ./\n- opts:\n    is_expand: true\n    summary: The name of the iOS scheme\n    title: The name of the iOS scheme\n  scheme: null\n- build_configuration: Release\n  opts:\n    is_expand: true\n    summary: The name of the active build configuration\n    title: The name of the active build configuration\n- opts:\n    is_expand: true\n    summary: The path relative to project root directory where the custom `.xcconfig`\n      file is located\n    title: Path to a custom xcconfig file\n  xcconfig_path: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version name for the app\n    title: Version name\n  version_name: null\n- opts:\n    category: App Versioning\n    is_expand: true\n    summary: The version code for the app\n    title: Version code\n  version_code: null\n- disable_version_name_from_package_json: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will get the 'version' field from package.json and set the\n      version name\n    title: Disable automatic version name configuration\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_version_code_auto_generation: \"no\"\n  opts:\n    category: App Versioning\n    is_expand: true\n    summary: By default will generate a timestamp based number and set the version\n      code\n    title: Disable automatic version code generation\n    value_options:\n    - \"yes\"\n    - \"no\"\n- certificate_url: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The url to download and install the certificate\n    title: Certificate url\n- certificate_passphrase: null\n  opts:\n    category: App Signing\n    is_expand: true\n    is_sensitive: true\n    summary: Certificate passphrase\n    title: Certificate passphrase\n- codesigning_identity: null\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: Codesigning identity\n    title: Codesigning identity\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: A string containing a '|' separated values where provisioning profiles\n      are located e.g. url1|url2|url3\n    title: Provisioning profile urls\n  provisioning_profile_urls: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: The name of the provisioning profile when using a single one\n    title: Provisioning profile specifier\n  provisioning_profile_specifier: null\n- opts:\n    category: App Signing\n    is_expand: true\n    summary: Specify the Team ID you want to use for the Apple Developer Portal\n    title: Team ID\n  team_id: null\n- export_method: ad-hoc\n  opts:\n    category: App Signing\n    is_expand: true\n    summary: The export method used to generate the IPA\n    title: Export Method\n    value_options:\n    - ad-hoc\n    - app-store\n    - development\n    - enterprise\n- cache_provider: s3\n  opts:\n    category: Caching\n    description: |-\n      Choose the provider where cache artifacts will be persisted:\n      - `fs`: File system\n      - `s3`: Amazon - Simple Storage Service\n    is_expand: true\n    summary: Choose the provider where cache artifacts will be persisted\n    title: Cache provider\n    value_options:\n    - fs\n    - s3\n- disable_cache: null\n  opts:\n    category: Caching\n    description: When setting this option to `yes` build cache optimizations won't\n      be performed. (defaults to $NITRO_DISABLE_CACHE if present)\n    is_expand: true\n    summary: When setting this option to `yes` build cache optimizations won't be\n      performed. (defaults to $NITRO_DISABLE_CACHE if present)\n    title: Disable builds caching\n- cache_env_var_lookup_keys: null\n  opts:\n    category: Caching\n    description: A list of `|` separated values with env variable keys to lookup to\n      determine whether the build should be cached or not\n    is_expand: true\n    summary: A list of `|` separated values with env variable keys to lookup to determine\n      whether the build should be cached or not\n    title: List of env var keys for lookup to determine cache fingerprint\n- cache_file_lookup_paths: null\n  opts:\n    category: Caching\n    description: A list of `|` separated value paths (relative to the root of the\n      repo or absolute) to lookup in order to determine whether the build should be\n      cached or not\n    is_expand: true\n    summary: A list of `|` separated value paths (relative to the root of the repo\n      or absolute) to lookup in order to determine whether the build should be cached\n      or not\n    title: List of files for lookup to determine cache fingerprint\n- disable_metro_cache: null\n  opts:\n    category: Caching\n    description: Setting this field to yes will disable the React Native Metro cache\n      feature. (defaults to $NITRO_DISABLE_METRO_CACHE if present)\n    is_expand: true\n    summary: Setting this field to `yes` will disable the React Native Metro cache\n      feature. (defaults to $NITRO_DISABLE_METRO_CACHE if present)\n    title: Disable Metro bundler cache\n- aws_s3_access_key_id: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS access key ID for S3 bucket build caching. (defaults to $NITRO_AWS_S3_ACCESS_KEY_ID\n      if present)\n    title: AWS S3 access key ID\n- aws_s3_secret_access_key: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS secret access key for S3 bucket build caching. (defaults to $NITRO_AWS_S3_SECRET_ACCESS_KEY\n      if present)\n    title: AWS S3 secret access key\n- aws_s3_region: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS region where S3 bucket for build caching is located. (defaults to\n      $NITRO_AWS_S3_REGION if present)\n    title: AWS S3 region\n- aws_s3_bucket: null\n  opts:\n    category: Caching\n    is_expand: true\n    summary: AWS bucket name for S3 bucket build caching. (defaults to $NITRO_AWS_S3_BUCKET\n      if present)\n    title: AWS S3 bucket name\n- opts:\n    category: Hooks\n    description: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    is_expand: true\n    summary: Run command prior to install project dependencies (e.g. `rm -rf ./some-folder`)\n    title: Pre install command\n  pre_install_command: null\n- opts:\n    category: Hooks\n    description: Run command prior to start building the app (e.g. `yarn tsc && yarn\n      test`)\n    is_expand: true\n    summary: Run command prior to start building the app (e.g. `yarn tsc && yarn test`)\n    title: Pre build command\n  pre_build_command: null\n- opts:\n    category: Hooks\n    description: Run command once build successfully finished (e.g. `yarn publish`)\n    is_expand: true\n    summary: Run command once build successfully finished (e.g. `yarn publish`)\n    title: Post build command\n  post_build_command: null\n- detox_configuration: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Select a device configuration from your defined configurations.\n    title: Detox configuration\n- opts:\n    category: Advanced\n    is_expand: true\n    summary: The path to the directory where to place all of Nitro's output files.\n      (defaults to $BITRISE_DEPLOY_DIR)\n    title: Output directory\n  output_directory: null\n- entry_file: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: The entry file for bundle generation. (defaults to $ENTRY_FILE if present)\n    title: The entry file for bundle generation\n- opts:\n    category: Advanced\n    description: Enable verbose logs\n    summary: Enable verbose logs\n    title: Verbose logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- debug: \"no\"\n  opts:\n    category: Advanced\n    description: Enable step debugging\n    summary: Enable step debugging\n    title: Debug step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- fail_safe: null\n  opts:\n    category: Advanced\n    is_expand: true\n    summary: Runing the app in this mode allows you to prevent the build to fail but\n      you can check the status in further steps. (defaults to $NITRO_FAIL_SAFE if\n      present)\n    title: Fail-safe mode\noutputs:\n- NITRO_BUILD_STATUS: null\n  opts:\n    description: The status of the latest build (success / failure)\n    summary: The status of the latest build (success / failure)\n    title: Build status\n- NITRO_OUTPUT_DIR: null\n  opts:\n    description: The path to the directory where to place all of Nitro's output files\n    summary: The path to the directory where to place all of Nitro's output files\n    title: Output directory\n- NITRO_LOGS_PATH: null\n  opts:\n    description: The full path to access the build log\n    summary: The full path to access the build log\n    title: Build log location\n- NITRO_SUMMARY_PATH: null\n  opts:\n    description: The full path to access the build summary report\n    summary: The full path to access the build summary report\n    title: Summary location\n- NITRO_APP_PATH: null\n  opts:\n    description: The full path to access the iOS package (.app or .ipa)\n    summary: The full path to access the iOS package (.app or .ipa)\n    title: Build application package location\n- NITRO_DEPLOY_PATH: null\n  opts:\n    description: The full path to access the iOS package (.app or .ipa)\n    summary: The full path to access the iOS package (.app or .ipa)\n    title: Build application package location\n"
  },
  {
    "path": "steps/nitro-ios/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/npm/0.1.0/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2016-03-09T13:29:24.879012651+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 25d36053a5b9ae0db836eba47cfb12f0c0fa8a04\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- npm\ndeps:\n  brew:\n  - name: node\ninputs:\n- command: null\n  opts:\n    description: Specify the command to run with `npm`. For example `install`, or\n      `test`.\n    title: The `npm` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `npm` command. You can specify multiple arguments, separated\n      by a space character. For example `-dd -ll`\n    title: Arguments for running `npm` commands\n"
  },
  {
    "path": "steps/npm/0.1.1/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2016-08-12T11:10:34.380129264+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 2b365a0254854b29af6589ad4cc9d2ea97f253cb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- npm\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: Specify the command to run with `npm`. For example `install`, or\n      `test`.\n    title: The `npm` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `npm` command. You can specify multiple arguments, separated\n      by a space character. For example `-dd -ll`\n    title: Arguments for running `npm` commands\n"
  },
  {
    "path": "steps/npm/0.9.0/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2017-03-08T14:49:50.634596109+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: a708ceeed0f5bd5ae7325084d2c2fba4fa213e85\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: nodejs\n  - name: npm\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n"
  },
  {
    "path": "steps/npm/0.9.1/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: !!timestamp 2018-03-29T16:23:08.032481309+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: fba36bf902d67ebf11a204953433012b34816d31\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: nodejs\n  - name: npm\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n"
  },
  {
    "path": "steps/npm/1.0.0/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2018-11-21T15:22:34.867137887Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 352a9478756aac77b9cfc1a2a7fcf5ccc57ce741\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n"
  },
  {
    "path": "steps/npm/1.0.1/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2018-11-23T13:22:56.168129075Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 2ec530ccc782688bf4ba48fbfae3860344430ac1\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n"
  },
  {
    "path": "steps/npm/1.0.2/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2019-03-20T08:45:56.726794654Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 673edf878b6262ede27bb0538aeb8955e5b56cb4\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n"
  },
  {
    "path": "steps/npm/1.1.0/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2019-08-15T08:29:42.216410047Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: aade93f2328349114c4fcb7e5258b87b5536863a\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/1.1.1/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2019-12-16T09:45:25.697662001Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 1bc085fc27539d1d289994954ad3f0ae45a5c1ae\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/1.1.2/step.yml",
    "content": "title: Run npm command\nsummary: Runs `npm` with the given command and args.\ndescription: Runs `npm` with the given command and args.\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2020-02-13T10:21:27.294593993Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 8cf1d79dfddf75026a61fe5ba6550da930a7a0c8\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/1.1.3/step.yml",
    "content": "title: Run npm command\nsummary: The Step runs npm with the command and arguments you provide, for example,\n  to install missing packages or run a package's test.\ndescription: \"You can install missing JS dependencies with this Step if you insert\n  it before any build step and provide the `install` command. \\nYou can also test\n  certain packages with the `test` command. \\nYou can do both in one Workflow, however,\n  this requires one **Run npm command** Step for installation followed by another\n  **Run npm command** Step for testing purposes.\\n\\n### Configuring the Step\\n1. Add\n  the **Run npm command** Step to your Workflow preceding any build Step.\\n2. Set\n  the **Working directory**.\\n3. Set the command you want npm to execute, for example\n  `install` to run `npm install` in the **The npm command with arguments to run**\n  input.\\n4. If you're looking for a particular npm version, you can set it in the\n  **Version of npm to use** input.\\n5. You can cache the content of the node modules\n  directory if you select `true` in the drop-down. \\nBy default this input is set\n  to false.\\n\\n### Troubleshooting\\nMake sure you insert the Step before any build\n  Step so that every dependency is downloaded a build Step starts running.\\n\\n###\n  Useful links\\n- [Getting started Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n-\n  [About npm](https://www.npmjs.com/)\"\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2020-02-18T12:06:35.282213234Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: b905adfc99891ee3062c5a4be35ac8d452e1b154\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/1.1.4/step.yml",
    "content": "title: Run npm command\nsummary: The Step runs npm with the command and arguments you provide, for example,\n  to install missing packages or run a package's test.\ndescription: \"You can install missing JS dependencies with this Step if you insert\n  it before any build step and provide the `install` command. \\nYou can also test\n  certain packages with the `test` command. \\nYou can do both in one Workflow, however,\n  this requires one **Run npm command** Step for installation followed by another\n  **Run npm command** Step for testing purposes.\\n\\n### Configuring the Step\\n1. Add\n  the **Run npm command** Step to your Workflow preceding any build Step.\\n2. Set\n  the **Working directory**.\\n3. Set the command you want npm to execute, for example\n  `install` to run `npm install` in the **The npm command with arguments to run**\n  input.\\n4. If you're looking for a particular npm version, you can set it in the\n  **Version of npm to use** input.\\n5. You can cache the content of the node modules\n  directory if you select `true` in the drop-down. \\nBy default this input is set\n  to false.\\n\\n### Troubleshooting\\nMake sure you insert the Step before any build\n  Step so that every dependency is downloaded a build Step starts running.\\n\\n###\n  Useful links\\n- [Getting started Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\\n-\n  [About npm](https://www.npmjs.com/)\"\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2020-11-05T15:30:10.217671571Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 032e06750e80fc6f2fc95b9561f965ac62f979b6\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/1.1.5/step.yml",
    "content": "title: Run npm command\nsummary: The Step runs npm with the command and arguments you provide, for example,\n  to install missing packages or run a package's test.\ndescription: |-\n  You can install missing JS dependencies with this Step if you insert it before any build step and provide the `install` command.\n  You can also test certain packages with the `test` command.\n  You can do both in one Workflow, however, this requires one **Run npm command** Step for installation followed by another **Run npm command** Step for testing purposes.\n\n  ### Configuring the Step\n  1. Add the **Run npm command** Step to your Workflow preceding any build Step.\n  2. Set the **Working directory**.\n  3. Set the command you want npm to execute, for example `install` to run `npm install` in the **The npm command with arguments to run** input.\n  4. If you're looking for a particular npm version, you can set it in the **Version of npm to use** input.\n  5. You can cache the content of the node modules directory if you select `true` in the drop-down.\n  By default this input is set to false.\n\n  ### Troubleshooting\n  Make sure you insert the Step before any build Step so that every dependency is downloaded a build Step starts running.\n\n  ### Useful links\n  - [Getting started Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\n  - [About npm](https://www.npmjs.com/)\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2022-02-23T14:15:50.898352579Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: c3e53f604f688adde60499b61db2160aec491f9c\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/1.1.6/step.yml",
    "content": "title: Run npm command\nsummary: The Step runs npm with the command and arguments you provide, for example,\n  to install missing packages or run a package's test.\ndescription: |-\n  You can install missing JS dependencies with this Step if you insert it before any build step and provide the `install` command.\n  You can also test certain packages with the `test` command.\n  You can do both in one Workflow, however, this requires one **Run npm command** Step for installation followed by another **Run npm command** Step for testing purposes.\n\n  ### Configuring the Step\n  1. Add the **Run npm command** Step to your Workflow preceding any build Step.\n  2. Set the **Working directory**.\n  3. Set the command you want npm to execute, for example `install` to run `npm install` in the **The npm command with arguments to run** input.\n  4. If you're looking for a particular npm version, you can set it in the **Version of npm to use** input.\n  5. You can cache the content of the node modules directory if you select `true` in the drop-down.\n  By default this input is set to false.\n\n  ### Troubleshooting\n  Make sure you insert the Step before any build Step so that every dependency is downloaded a build Step starts running.\n\n  ### Useful links\n  - [Getting started Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\n  - [About npm](https://www.npmjs.com/)\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2022-07-15T09:23:38.232730219Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 15f3332c80aa12f4c83b37bd0cbe71a2bbf0a9ff\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n- cache_local_deps: \"false\"\n  opts:\n    category: Cache\n    description: |\n      Select if the contents of node_modules directory should be cached.\n\n      `true`: Mark local dependencies to be cached.\n\n      `false`: Do not use cache.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/npm/2.0.0/step.yml",
    "content": "title: Run npm command\nsummary: The Step runs npm with the command and arguments you provide, for example,\n  to install missing packages or run a package's test.\ndescription: |-\n  You can install missing JS dependencies with this Step if you insert it before any build step and provide the `install` command.\n  You can also test certain packages with the `test` command.\n  You can do both in one Workflow, however, this requires one **Run npm command** Step for installation followed by another **Run npm command** Step for testing purposes.\n\n  ### Configuring the Step\n  1. Add the **Run npm command** Step to your Workflow preceding any build Step.\n  2. Set the **Working directory**.\n  3. Set the command you want npm to execute, for example `install` to run `npm install` in the **The npm command with arguments to run** input.\n  4. If you're looking for a particular npm version, you can set it in the **Version of npm to use** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before any build Step so that every dependency is downloaded a build Step starts running.\n\n  ### Useful links\n  - [Getting started Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\n  - NPM cache [save](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache) Steps\n  - [About npm](https://www.npmjs.com/)\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2026-01-29T10:39:11.979733498Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 973247a884b17a2ab79cce9a6e4a8ac1a2318d90\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: Set this value to the version of npm that is required to run the\n      command. Must be a valid semver string.\n    title: Version of npm to use\n"
  },
  {
    "path": "steps/npm/3.0.0/step.yml",
    "content": "title: Run npm command\nsummary: The Step runs npm with the command and arguments you provide, for example,\n  to install missing packages or run a package's test.\ndescription: |-\n  You can install missing JS dependencies with this Step if you insert it before any build step and provide the `install` command.\n  You can also test certain packages with the `test` command.\n  You can do both in one Workflow, however, this requires one **Run npm command** Step for installation followed by another **Run npm command** Step for testing purposes.\n\n  ### npm version pinning\n  The Step uses [corepack](https://nodejs.org/api/corepack.html) to manage the npm version. There are two ways to pin the version:\n\n  1. **Recommended: `packageManager` field in `package.json`**: Add `\"packageManager\": \"npm@10.2.0\"` to your `package.json`. The Step will enable corepack, which automatically enforces this version when `npm` is called.\n  2. **`npm_version` input**: Set the **Version of npm to use** input to an exact version number (e.g. `10.2.0`). This takes priority over the `packageManager` field and installs that specific version via `corepack prepare`.\n\n  If neither is set, the Step runs npm as-is without changing the version.\n\n  ### Configuring the Step\n  1. Add the **Run npm command** Step to your Workflow preceding any build Step.\n  2. Set the **Working directory**.\n  3. Set the command you want npm to execute, for example `install` to run `npm install` in the **The npm command with arguments to run** input.\n  4. Optionally pin the npm version via the `packageManager` field in `package.json` or the **Version of npm to use** input.\n\n  ### Troubleshooting\n  Make sure you insert the Step before any build Step so that every dependency is downloaded a build Step starts running.\n\n  ### Useful links\n  - [Getting started Ionic/Cordova apps](https://devcenter.bitrise.io/getting-started/getting-started-with-ionic-cordova-apps/)\n  - NPM cache [save](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache) and [restore](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache) Steps\n  - [About npm](https://www.npmjs.com/)\n  - [Corepack documentation](https://nodejs.org/api/corepack.html)\nwebsite: https://github.com/bitrise-steplib/steps-npm\nsource_code_url: https://github.com/bitrise-steplib/steps-npm\nsupport_url: https://github.com/bitrise-steplib/steps-npm/issues\npublished_at: 2026-02-20T12:11:54.312940199Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-npm.git\n  commit: 01ee959e2ab4f5d25ce8c84edd3b28bf983f339a\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/npm/3.0.0/bin/npm-darwin-amd64\n    hash: sha256-bc2525cd8ef87b725b6ef35f6371af1066002886c81a4564f187c5001e1d9b33\n  darwin-arm64:\n    storage_uri: steps/npm/3.0.0/bin/npm-darwin-arm64\n    hash: sha256-d007107a01098eca6bee4cbd330289db8318376e6110b2b406ea0fa96f500f19\n  linux-amd64:\n    storage_uri: steps/npm/3.0.0/bin/npm-linux-amd64\n    hash: sha256-db0968415f55e340bbd3291e75f2951fc8c1d4799d538d4426cc3d71925db7d2\n  linux-arm64:\n    storage_uri: steps/npm/3.0.0/bin/npm-linux-arm64\n    hash: sha256-1a537e1d16189a63ee1f91492b536dacab9e1d24eccf2fdd2a842bba9d3269c5\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-npm\ndeps:\n  apt_get:\n  - name: nodejs\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `npm`.\n\n      This input value will be append to the end of the `npm` command call.\n\n      For example:\n\n      - `install` -> `npm install`\n      - `install -g cordova` -> `npm install -g cordova`\n    is_required: true\n    title: The `npm` command with arguments to run\n- npm_version: null\n  opts:\n    description: |-\n      Set this to an exact npm version to install (e.g. `10.2.0`).\n\n      This input takes priority over the `packageManager` field in `package.json`.\n      The Step uses corepack (`corepack prepare npm@<version> --activate`) to download and activate the specified version.\n\n      Leave empty to let the Step auto-detect the version from the `packageManager` field in `package.json`.\n    title: Version of npm to use\n"
  },
  {
    "path": "steps/npm/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/nuget-restore/0.9.0/step.yml",
    "content": "title: Step nuget restore\nsummary: Step nuget restore\ndescription: Step nuget restore\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2015-12-17T13:33:46.535004354+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 69960520ad6c2ef70af7d3f795ac7b9b8c85b720\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/nuget-restore/0.9.1/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-03-08T16:41:34.619849157+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: a93ce1a0fc2515ee00ca6235de97085c41e92ffa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/nuget-restore/0.9.2/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-06-21T15:03:32.766008162+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 1c10d5be08912008ee8f6687df977136f1868cf0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: null\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/0.9.3/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-08-11T12:16:24.406903306+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 2cce588ead7d01c37c72f99fff7f0e95a9b46bc7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: null\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.0/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-10-20T12:06:19.747136795+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 2100d8c652f428f8acb2acfe1ba88712158eb76b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: null\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.1/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-10-24T17:42:25.336053388+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 0631ab3856c163bbd4fe4f4da69d80dd5e7ab9a6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: null\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.2/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-12-01T16:29:38.500818137+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 93a6c8132dd6fee44d9e707ee697bdb7b314788a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: null\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.3/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2016-12-05T15:28:12.519135934+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 853abb4810ae9f9245d187ae5468f3dff846c226\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: null\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.4/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2017-05-22T12:12:42.083299505+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: d50824ae9e0a5f32f6b8b228ac5ddf359c68e6ba\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: latest\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.5/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2017-10-24T11:42:42.277005777+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 88f57cee29ae47ba477956b3e0680354f4bb4607\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: latest\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.6/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: !!timestamp 2018-04-12T15:15:41.701055626+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: fab37d97321a5a19a8426ac987a6a3bbd5e0334a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: latest\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.0.7/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: !!timestamp 2018-04-24T16:20:36.598105106+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: ece097066d1f7fabb578b063c4ecd1f326e3d853\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: latest\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n"
  },
  {
    "path": "steps/nuget-restore/1.1.0/step.yml",
    "content": "title: NuGet restore\nsummary: NuGet restore step\ndescription: NuGet restore step\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: !!timestamp 2019-09-27T14:10:00.598105106+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 6754877bcb8d9e9a092518c2a71a0ec7ab6217f4\nproject_type_tags:\n  - xamarin\ntype_tags:\n  - dependency\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ndeps:\n  brew:\n    - name: go\n  apt_get:\n    - name: golang\n      bin_name: go\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ninputs:\n  - xamarin_solution: $BITRISE_PROJECT_PATH\n    opts:\n      title: Path to Xamarin solution\n      description: |\n        Path to Xamarin solution\n      is_required: true\n  - nuget_version: latest\n    opts:\n      title: NuGet version\n      description: |\n        The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n        Specify this input if you would like to use a custom NuGet version.\n        You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n        Format examples:\n\n        - 2.8.6\n        - latest\n  - cache_level: \"local\"\n    opts:\n      category: Options\n      title: Set the level of cache\n      is_required: true\n      description: |-\n        Sets the level of cache.\n\n        'local' enables the caching the packages in the build directory.\n        'global' enables the caching of the global-packages folder, this is where NuGet installs any downloaded package.\n        'all' enables the caching of both local and global caches.\n        'none' disables the caching for the step.\n\n        Please find more information about caching here:\n        https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders\n      value_options:\n        - \"local\"\n        - \"global\"\n        - \"all\"\n        - \"none\""
  },
  {
    "path": "steps/nuget-restore/1.1.1/step.yml",
    "content": "title: NuGet restore\nsummary: Installs packages with NuGet.\ndescription: \"The **NuGet restore** Step downloads the latest or specified NuGet version\n  and runs a restore with it to install missing .NET packages based on your Xamarin\n  solution (.sln).\\nYou can check the installed packages in your build's log.\\n\\n###\n  Configuring the Step\\n1. Add the **NuGet restore** Step to your Workflow after the\n  **Git Clone Repository** Step so that the Step can download and install all the\n  necessary packages.\\n2. Provide the **Path to Xamarin solution**. By default, the\n  Step will use the same solution file that you have provided when you added your\n  app, but you can also modify it if you wish.\\n\\nOptionally, you can set what to\n  cache if you click **Options** and then **Set the level of cache** input:\\n- `local`\n  caches the packages in your build directory.\\n- `global` caches the global-packages\n  folder.\\n- `all` caches local and global.\\n- `none` disables caching for the Step.\\n\\n###\n  Troubleshooting\\nIf your build fails due to a specific NuGet version, you can try\n  to run your build with another version. Click the **NuGet version** input and select\n  a NuGet version.\\n\\n### Useful links\\n- [Available NuGet Distribution Versions](https://www.nuget.org/downloads)\\n-\n  [About NuGet and caching](https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders)\\n\\n###\n  Related Steps\\n- [Xamarin Archive](https://www.bitrise.io/integrations/steps/xamarin-archive)\\n-\n  [NUnit runner](https://www.bitrise.io/integrations/steps/nunit-runner) \"\nwebsite: https://github.com/bitrise-steplib/steps-nuget-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-nuget-restore\nsupport_url: https://github.com/bitrise-steplib/steps-nuget-restore/issues\npublished_at: 2020-01-31T16:10:14.421203404Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-nuget-restore.git\n  commit: 406e3f86eb5a20c7e366b6ee2152ffc60b582f5b\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-nuget-restore\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- nuget_version: latest\n  opts:\n    description: |\n      The default NuGet restore step uses the NuGet version that ships with Xamarin.\n\n      Specify this input if you would like to use a custom NuGet version.\n      You can find all the available NuGet distribution here: https://dist.nuget.org/index.html.\n\n      Format examples:\n\n      - 2.8.6\n      - latest\n    title: NuGet version\n- cache_level: local\n  opts:\n    category: Options\n    description: |-\n      Sets the level of cache.\n\n      'local' enables the caching the packages in the build directory.\n      'global' enables the caching of the global-packages folder, this is where NuGet installs any downloaded package.\n      'all' enables the caching of both local and global caches.\n      'none' disables the caching for the step.\n\n      Please find more information about caching here:\n      https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders\n    is_required: true\n    title: Set the level of cache\n    value_options:\n    - local\n    - global\n    - all\n    - none\n"
  },
  {
    "path": "steps/nuget-restore/step-info.yml",
    "content": "deprecate_notes: |\n  The Xamarin development platform is not officially supported.\n  [More info](https://blog.bitrise.io/post/xamarin-support-ends-in-2022-on-bitrise)\nmaintainer: bitrise\nremoval_date: \"2022-01-31\"\n"
  },
  {
    "path": "steps/nunit-runner/0.9.0/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: Executes a set of NUnit tests against your Xamarin solution file\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-02-18T12:06:06.81991209+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 7e40db7b6bfe38dd2489d02a42746de8c9d10311\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running nunit3-console\n    is_required: false\n    title: NUnit command options\n"
  },
  {
    "path": "steps/nunit-runner/0.9.1/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: Executes a set of NUnit tests against your Xamarin solution file\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-05-18T17:47:19.474042161+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: f718ff34a0378bf6680a1b9ce629f7bc8827170b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running nunit3-console\n    title: NUnit command options\n"
  },
  {
    "path": "steps/nunit-runner/0.9.2/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: Executes a set of NUnit tests against your Xamarin solution file\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-05-25T15:27:14.811776248+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: a01e7ef7b0a0a1e1c8635703101d1ad91669f53a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running nunit3-console\n    title: NUnit command options\n"
  },
  {
    "path": "steps/nunit-runner/0.9.3/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: Executes a set of NUnit tests against your Xamarin solution file\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-09-07T12:59:16.946440062+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 50be11b849c4a24e9a82ffb35b69d786bad5a2cc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running nunit3-console\n    title: NUnit command options\n"
  },
  {
    "path": "steps/nunit-runner/1.0.0/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: Executes a set of NUnit tests against your Xamarin solution file\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-10-19T11:47:15.009175656+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: a5fc6e4e293252f368d8a27ae0cf623f7c50244e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running nunit3-console\n    title: NUnit command options\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.1.0/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: Executes a set of NUnit tests against your Xamarin solution file\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-10-26T12:32:13.608664257+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 6ecd55a8dd1644233c7d73f09879bf184f8dae49\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running nunit3-console\n    title: NUnit command options\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.1.1/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: \"Runs your NUnit 2.x and NUnit 3.0 or higer tests with NUnit Console\n  Runner (nunit3-console.exe),  \\nagainst your xamarin projects.\"\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-11-02T10:57:03.656199812+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 4de613931ef3c5331969a0e21d785bed18f05705\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running NUnit Console Runner (nunit3-console.exe).\n    title: NUnit Console Runner (nunit3-console.exe) command options\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.1.2/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: \"Runs your NUnit 2.x and NUnit 3.0 or higer tests with NUnit Console\n  Runner (nunit3-console.exe),  \\nagainst your xamarin projects.\"\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2016-12-06T12:58:35.946860817+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 6208838b5a46f468dfbaa2c5d7866478b7d565e9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running NUnit Console Runner (nunit3-console.exe).\n    title: NUnit Console Runner (nunit3-console.exe) command options\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.2.0/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: \"Runs your NUnit 2.x and NUnit 3.0 or higer tests with NUnit Console\n  Runner (nunit3-console.exe),  \\nagainst your xamarin projects.\"\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2017-04-03T14:16:17.932700714+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: ba11a4c82de931089425b9b70ab0d3a8e2ad53eb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- nunit_options: null\n  opts:\n    description: |\n      Additional option flags when running NUnit Console Runner (nunit3-console.exe).\n    title: NUnit Console Runner (nunit3-console.exe) command options\n- build_before_test: \"true\"\n  opts:\n    description: |\n      Set this option to `true` if you want to build your test projects before running tests.\n    is_required: true\n    title: Build before test\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.3.0/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: \"Runs your NUnit 2.x and NUnit 3.0 or higer tests with NUnit Console\n  Runner (nunit3-console.exe),  \\nagainst your xamarin projects.\"\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2017-06-27T15:24:09.368332649+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 7574d249ba886f83ec3875dd216e068a17ec2aae\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- build_before_test: \"true\"\n  opts:\n    category: Debug\n    description: |\n      Set this option to `true` if you want to build your test projects before running tests.\n    is_required: true\n    title: Build before test\n    value_options:\n    - \"true\"\n    - \"false\"\n- nunit_options: null\n  opts:\n    category: Debug\n    description: |\n      Additional option flags when running NUnit Console Runner (nunit3-console.exe).\n    title: NUnit Console Runner (nunit3-console.exe) command options\n- build_tool: xbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.4.0/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: \"Runs your NUnit 2.x and NUnit 3.0 or higer tests with NUnit Console\n  Runner (nunit3-console.exe),  \\nagainst your xamarin projects.\"\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2017-08-09T14:48:16.07823306+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 7d831dd8a0ea549ce4fb8acae7545958d0295cb1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- build_before_test: \"true\"\n  opts:\n    category: Debug\n    description: |\n      Set this option to `true` if you want to build your test projects before running tests.\n    is_required: true\n    title: Build before test\n    value_options:\n    - \"true\"\n    - \"false\"\n- nunit_options: null\n  opts:\n    category: Debug\n    description: |\n      Additional option flags when running NUnit Console Runner (nunit3-console.exe).\n    title: NUnit Console Runner (nunit3-console.exe) command options\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/1.4.1/step.yml",
    "content": "title: NUnit runner\nsummary: NUnit runner\ndescription: \"Runs your NUnit 2.x and NUnit 3.0 or higher tests with NUnit Console\n  Runner (nunit3-console.exe),  \\nagainst your xamarin projects.\"\nwebsite: https://github.com/bitrise-steplib/steps-nunit-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-nunit-runner\nsupport_url: https://github.com/bitrise-steplib/steps-nunit-runner/issues\npublished_at: 2019-11-22T12:32:34.697518673Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-nunit-runner.git\n  commit: 7e3ec9a5c5f3bd064779f3b9bba73cc0383a4621\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-nunit-runner\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- build_before_test: \"true\"\n  opts:\n    category: Debug\n    description: |\n      Set this option to `true` if you want to build your test projects before running tests.\n    is_required: true\n    title: Build before test\n    value_options:\n    - \"true\"\n    - \"false\"\n- nunit_options: null\n  opts:\n    category: Debug\n    description: |\n      Additional option flags when running NUnit Console Runner (nunit3-console.exe).\n    title: NUnit Console Runner (nunit3-console.exe) command options\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/nunit-runner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/nvm/0.1.0/step.yml",
    "content": "title: NVM\nsummary: Install NVM and select Node version\ndescription: |\n  Install NVM and select Node version\n  NVM = Node Version Manager - Simple bash script to manage multiple active node.js versions\n  See https://github.com/creationix/nvm\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2016-07-02T22:15:30.551754569+02:00\nsource:\n  git: https://github.com/Almouro/bitrise-nvm-step.git\n  commit: 39aa1b7d154d4498b16a5eb6a0f9d13bc479d62c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- script\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- nvm_version: v0.31.0\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: false\n    is_required: true\n    title: NVM Version\n- node_version: 4.4.2\n  opts:\n    description: |\n      Node version to be installed\n    is_expand: false\n    is_required: true\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.0.0/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/creationix/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2016-07-24T19:29:12.711068565+02:00\nsource:\n  git: https://github.com/Almouro/bitrise-nvm-step.git\n  commit: 215a76f4a17401e5cb42d079c7321e37780f7c47\nhost_os_tags:\n- osx\n- ubuntu\nproject_type_tags:\n- react-native\ntype_tags:\n- npm\n- node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- nvm_version: 0.31.3\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: false\n    is_required: true\n    title: NVM Version\n- node_version: 6.3.1\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like `6`, `6.3` or `6.3.1`.\n      You can also use the NVM version aliases like:\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      More info on NVM aliases [here](https://github.com/creationix/nvm#usage)\n    is_expand: false\n    is_required: true\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.0.1/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/creationix/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2016-07-24T20:30:25.059382503+02:00\nsource:\n  git: https://github.com/Almouro/bitrise-nvm-step.git\n  commit: 04762bdbbda07a883a6710e942900eeb12cfe05e\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- nvm_version: 0.31.3\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: false\n    is_required: true\n    title: NVM Version\n- node_version: 6.3.1\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like `6`, `6.3` or `6.3.1`.\n      You can also use the NVM version aliases like:\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      More info on NVM aliases [here](https://github.com/creationix/nvm#usage)\n    is_expand: false\n    is_required: true\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.1.1/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/creationix/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2017-11-26T19:02:41.207840012+01:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: cb6cd1b478184fcd7a5f580ecdb219a791cdd5f9\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- nvm_version: 0.33.6\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: false\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like `6`, `6.3` or `6.3.1`.\n      You can also use the NVM version aliases like:\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n      - if a `.nvmrc` is present, the version it specifies will be installs\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/creationix/nvm#usage)\n    is_expand: false\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.1.2/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/creationix/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2017-11-26T19:17:36.02863705+01:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: 4b74d50d1e51cbf76cd6fe13e7ffc0841e87d671\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- nvm_version: 0.33.6\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: false\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/creationix/nvm#usage)\n    is_expand: false\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.2.1/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/creationix/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2018-02-13T14:18:03.452060064+01:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: d8c34dd0ce944e693ed52245d1e29f3bca600604\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- nvm_version: 0.33.6\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: false\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/creationix/nvm#usage)\n    is_expand: false\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.2.2/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/creationix/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2018-11-06T16:54:05.738511399+01:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: 9fbca334b88489a00fb13687db1fb2b22bbddb66\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- nvm_version: 0.33.6\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: true\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/creationix/nvm#usage)\n    is_expand: true\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.3.0/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/nvm-sh/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2020-05-09T13:59:55.529554+02:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: ae14e2b57b574a23be3955ff4000d78622adf43a\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- nvm_version: 0.35.3\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: true\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/nvm-sh/nvm#usage)\n    is_expand: true\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.3.1/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/nvm-sh/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2022-07-19T13:45:10.793305+02:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: 9a0b511b31af38c0b9eb76a4b140c611eae05458\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- nvm_version: 0.39.1\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: true\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/nvm-sh/nvm#usage)\n    is_expand: true\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.3.2/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/nvm-sh/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2022-07-20T12:50:28.896963+02:00\nsource:\n  git: https://github.com/almouro/bitrise-nvm-step.git\n  commit: 1815fe6e354507a26c15a39fcfc59eaab3f9844f\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- nvm_version: 0.39.1\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: true\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/nvm-sh/nvm#usage)\n    is_expand: true\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/1.3.3/step.yml",
    "content": "title: Node Version Manager (NVM)\nsummary: Install NVM and select Node version\ndescription: |\n  This step will install a specific node.js version using NVM, and will make it available for all your other steps.\n\n  NVM (Node Version Manager) is a simple bash script to manage multiple active node.js versions.\n  See [here](https://github.com/nvm-sh/nvm) for more details.\nwebsite: https://github.com/almouro/bitrise-nvm-step\nsource_code_url: https://github.com/almouro/bitrise-nvm-step\nsupport_url: https://github.com/almouro/bitrise-nvm-step/issues\npublished_at: 2023-05-16T16:14:52.457506+02:00\nsource:\n  git: https://github.com/Almouro/bitrise-nvm-step.git\n  commit: ea7f95241364c42c38a7bc02f795bf551b072c7c\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- nvm_version: 0.39.1\n  opts:\n    description: |\n      NVM version to be installed\n    is_expand: true\n    is_required: true\n    title: NVM Version\n- node_version: null\n  opts:\n    description: |\n      node.js version that NVM will install.\n\n      You can use a version pointer like:\n\n      - `6`\n      - `6.3`\n      - `6.3.1`\n\n      You can also use the NVM version aliases like:\n\n      - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n\n      If no version is specified:\n\n      - if a `.nvmrc` is present, the version it specifies will be installed\n      - otherwise, the latest node version will be installed\n\n      More info on NVM aliases [here](https://github.com/nvm-sh/nvm#usage)\n    is_expand: true\n    is_required: false\n    title: Node version\n"
  },
  {
    "path": "steps/nvm/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/onesignal-create-push/0.0.1/step.yml",
    "content": "title: |\n    Send OneSignal push message\nsummary: |\n  Create a notification with onesignal. You can send notification with existing OneSignal app\ndescription: |\n  Create a notification with onesignal. You can send notification with existing OneSignal app\nwebsite: https://github.com/sonifex/bitrise-step-onesignal-create-push\nsource_code_url: https://github.com/sonifex/bitrise-step-onesignal-create-push\nsupport_url: https://github.com/sonifex/bitrise-step-onesignal-create-push/issues\npublished_at: 2020-05-09T17:07:55.992745+03:00\nsource:\n  git: https://github.com/sonifex/bitrise-step-onesignal-create-push.git\n  commit: 2c05994e6a465eda27cb61527d1c895e9880b4a5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- notification\ntoolkit: {}\n\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\n\ntoolkit:\n    bash:\n    entry_file: step.sh\n\ninputs:\n- onesignal_rest_api_key: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: |\n      \"OneSignal Rest API KEY\"\n- onesignal_app_id: \"\"\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: |\n      \"OneSignal App ID\"\n- app_public_install_page: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n  opts:\n    is_expand: true\n    title: App Public Install Page Url\n- opts:\n    is_expand: true\n    is_required: true\n    title: |\n      \"Push Notification Title\"\n  push_title: \"\"\n- opts:\n    is_expand: true\n    is_required: true\n    title: |\n      \"Push Notification Message\"\n  push_body: \"\"\n"
  },
  {
    "path": "steps/onesignal-create-push/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/open-vpn/0.0.1/step.yml",
    "content": "title: Connect to OpenVPN Server\nsummary: |\n  Establish a VPN connection with the specified OpenVPN server.\ndescription: |\n  Before using this step, you need to build an OpenVPN server in advance.\n  This article is helpful for how to construct OpenVPN server.\n  https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04\n\n\n  After building the VPN server, you need to register the contents of CA certificate, client certificate, client private key, base64 encoded as Bitrise Secret.\n  You can easily retrieve the contents of Base64 with the following command.\n\n  # base64 <certificate or private key file path>\nwebsite: https://github.com/justice3120/bitrise-step-open-vpn\nsource_code_url: https://github.com/justice3120/bitrise-step-open-vpn\nsupport_url: https://github.com/justice3120/bitrise-step-open-vpn/issues\npublished_at: 2018-11-16T20:32:18.295233074+09:00\nsource:\n  git: https://github.com/justice3120/bitrise-step-open-vpn.git\n  commit: d9191d94863fb355ff3e0689fcb85fcb97428a23\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openvpn\n  apt_get:\n  - name: openvpn\n  - name: net-tools\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- host: null\n  opts:\n    description: |\n      Open VPN Server IP or Hostname.\n      ex1. 111.111.111.111\n      ex2. hoge.com\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server IP or Hostname\n    title: Host\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Port number\n    title: Port\n  port: 1194\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Protocol\n    title: Protocol\n    value_options:\n    - udp\n    - tcp\n  proto: udp\n- ca_crt: $VPN_CA_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encorded CA Certificate\n    title: Base64 encorded CA Certificate\n- client_crt: $VPN_CLIENT_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encorded Client Certificate\n    title: Base64 encorded Client Certificate\n- client_key: $VPN_CLIENT_KEY_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encorded Client Private Key\n    title: Base64 encorded Client Private Key\n"
  },
  {
    "path": "steps/open-vpn/0.0.2/step.yml",
    "content": "title: Connect to OpenVPN Server\nsummary: |\n  Establish a VPN connection with the specified OpenVPN server.\ndescription: |\n  Before using this step, you need to build an OpenVPN server in advance.\n  This article is helpful for how to construct OpenVPN server.\n  https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04\n\n\n  After building the VPN server, you need to register the contents of CA certificate, client certificate, client private key, base64 encoded as Bitrise Secret.\n  You can easily retrieve the contents of Base64 with the following command.\n\n  `$ base64 <certificate or private key file path>`\nwebsite: https://github.com/justice3120/bitrise-step-open-vpn\nsource_code_url: https://github.com/justice3120/bitrise-step-open-vpn\nsupport_url: https://github.com/justice3120/bitrise-step-open-vpn/issues\npublished_at: 2018-11-30T19:03:21.395072665+09:00\nsource:\n  git: https://github.com/justice3120/bitrise-step-open-vpn.git\n  commit: bf313dbc5b14f3adeb9a5f68ac3ca2f1ca3f633c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openvpn\n  apt_get:\n  - name: openvpn\n  - name: net-tools\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- host: null\n  opts:\n    description: |\n      Open VPN Server IP or Hostname.\n      ex1. 111.111.111.111\n      ex2. hoge.com\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server IP or Hostname\n    title: Host\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Port number\n    title: Port\n  port: 1194\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Protocol\n    title: Protocol\n    value_options:\n    - udp\n    - tcp\n  proto: udp\n- ca_crt: $VPN_CA_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded CA Certificate\n    title: Base64 encoded CA Certificate\n- client_crt: $VPN_CLIENT_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Certificate\n    title: Base64 encoded Client Certificate\n- client_key: $VPN_CLIENT_KEY_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Private Key\n    title: Base64 encoded Client Private Key\n"
  },
  {
    "path": "steps/open-vpn/0.0.3/step.yml",
    "content": "title: Connect to OpenVPN Server\nsummary: |\n  Establish a VPN connection with the specified OpenVPN server.\ndescription: |\n  Before using this step, you need to build an OpenVPN server in advance.\n  This article is helpful for how to construct OpenVPN server.\n  https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04\n\n\n  After building the VPN server, you need to register the contents of CA certificate, client certificate, client private key, base64 encoded as Bitrise Secret.\n  You can easily retrieve the contents of Base64 with the following command.\n\n  `$ base64 <certificate or private key file path>`\nwebsite: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn/issues\npublished_at: 2020-10-29T09:16:49.1243787Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-open-vpn.git\n  commit: cbbfb01a1d88a18b37d53e9f845911f430accb02\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openvpn\n  apt_get:\n  - name: openvpn\n  - name: net-tools\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- host: null\n  opts:\n    description: |\n      Open VPN Server IP or Hostname.\n      ex1. 111.111.111.111\n      ex2. hoge.com\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server IP or Hostname\n    title: Host\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Port number\n    title: Port\n  port: 1194\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Protocol\n    title: Protocol\n    value_options:\n    - udp\n    - tcp\n  proto: udp\n- ca_crt: $VPN_CA_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded CA Certificate\n    title: Base64 encoded CA Certificate\n- client_crt: $VPN_CLIENT_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Certificate\n    title: Base64 encoded Client Certificate\n- client_key: $VPN_CLIENT_KEY_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Private Key\n    title: Base64 encoded Client Private Key\n"
  },
  {
    "path": "steps/open-vpn/0.1.0/step.yml",
    "content": "title: Connect to OpenVPN Server\nsummary: |\n  Establish a VPN connection with the specified OpenVPN server.\ndescription: |\n  Before using this step, you need to build an OpenVPN server in advance.\n  This article is helpful for how to construct OpenVPN server.\n  https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04\n\n\n  After building the VPN server, you need to register the contents of CA certificate, client certificate, client private key, base64 encoded as Bitrise Secret.\n  You can easily retrieve the contents of Base64 with the following command.\n\n  `$ base64 <certificate or private key file path>`\nwebsite: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn/issues\npublished_at: 2020-11-13T08:44:32.644219554Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-open-vpn.git\n  commit: 418eb86d194575d0030637e14e23ece4cd613942\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openvpn\n  apt_get:\n  - name: openvpn\n  - name: net-tools\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- host: null\n  opts:\n    description: |\n      Open VPN Server IP or Hostname.\n      ex1. 111.111.111.111\n      ex2. hoge.com\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server IP or Hostname\n    title: Host\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Port number\n    title: Port\n  port: 1194\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Protocol\n    title: Protocol\n    value_options:\n    - udp\n    - tcp\n  proto: udp\n- ca_crt: $VPN_CA_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded CA Certificate\n    title: Base64 encoded CA Certificate\n- client_crt: $VPN_CLIENT_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Certificate\n    title: Base64 encoded Client Certificate\n- client_key: $VPN_CLIENT_KEY_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Private Key\n    title: Base64 encoded Client Private Key\noutputs:\n- OPENVPN_LOG_PATH: null\n  opts:\n    title: Output log file path\n"
  },
  {
    "path": "steps/open-vpn/0.1.1/step.yml",
    "content": "title: Connect to OpenVPN Server\nsummary: |\n  Establish a VPN connection with the specified OpenVPN server.\ndescription: |\n  The Step establishes a VPN connection with the specified OpenVPN server.\n\n  ### Configuring the Step\n\n  Before you start:\n  1. Build an OpenVPN server. You can read [this article](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04) on how to construct an OpenVPN server.\n  1. Register the contents of CA certificate, client certificate, client private key, base64 encoded as Bitrise Secrets.\n     You can easily retrieve the contents of Base64 using command: `$ base64 <certificate or private key file path>`\n\n  To configure the Step:\n\n  1. Add the OpenVPN server IP or hostname to the **Host** input.\n  1. Add the OpenVPN server port number to the **Port** input. The port number is `1194` by default.\n  1. Specify the OpenVPN server protocol in the **Protocol** input.\n  1. Add the CA certificate, client certificate, and client private key Secrets to their respective inputs.\n\n  ### Useful links\n\n  * [Using the Connect to OpenVPN Server Step](https://devcenter.bitrise.io/en/builds/connecting-to-a-vpn-during-a-build.html#using-the-connect-to-openvpn-server-step)\n  * [How To Set Up an OpenVPN Server](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04)\n  * [Configuring network access for Bitrise build machines](https://devcenter.bitrise.io/en/infrastructure/build-machines/configuring-your-network-to-access-our-build-machines.html)\n\n  ### Related Steps\n\n  * [Cisco VPN connect](https://www.bitrise.io/integrations/steps/vpnc-connect)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn/issues\npublished_at: 2022-08-09T10:15:35.985110529Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-open-vpn.git\n  commit: 533f2ea913ea3a264d7f05814839324e2aad7fb0\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openvpn\n  apt_get:\n  - name: openvpn\n  - name: net-tools\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- host: null\n  opts:\n    description: |\n      Open VPN Server IP or Hostname.\n      ex1. 111.111.111.111\n      ex2. hoge.com\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server IP or Hostname\n    title: Host\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Port number\n    title: Port\n  port: 1194\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Protocol\n    title: Protocol\n    value_options:\n    - udp\n    - tcp\n  proto: udp\n- ca_crt: $VPN_CA_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded CA Certificate\n    title: Base64 encoded CA Certificate\n- client_crt: $VPN_CLIENT_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Certificate\n    title: Base64 encoded Client Certificate\n- client_key: $VPN_CLIENT_KEY_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Private Key\n    title: Base64 encoded Client Private Key\noutputs:\n- OPENVPN_LOG_PATH: null\n  opts:\n    title: Output log file path\n"
  },
  {
    "path": "steps/open-vpn/0.1.2/step.yml",
    "content": "title: Connect to OpenVPN Server\nsummary: |\n  Establish a VPN connection with the specified OpenVPN server.\ndescription: |\n  The Step establishes a VPN connection with the specified OpenVPN server.\n\n  ### Configuring the Step\n\n  Before you start:\n  1. Build an OpenVPN server. You can read [this article](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04) on how to construct an OpenVPN server.\n  1. Register the contents of CA certificate, client certificate, client private key, base64 encoded as Bitrise Secrets.\n     You can easily retrieve the contents of Base64 using command: `$ base64 <certificate or private key file path>`\n\n  To configure the Step:\n\n  1. Add the OpenVPN server IP or hostname to the **Host** input.\n  1. Add the OpenVPN server port number to the **Port** input. The port number is `1194` by default.\n  1. Specify the OpenVPN server protocol in the **Protocol** input.\n  1. Add the CA certificate, client certificate, and client private key Secrets to their respective inputs.\n\n  ### Useful links\n\n  * [Using the Connect to OpenVPN Server Step](https://devcenter.bitrise.io/en/builds/connecting-to-a-vpn-during-a-build.html#using-the-connect-to-openvpn-server-step)\n  * [How To Set Up an OpenVPN Server](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04)\n  * [Configuring network access for Bitrise build machines](https://devcenter.bitrise.io/en/infrastructure/build-machines/configuring-your-network-to-access-our-build-machines.html)\n\n  ### Related Steps\n\n  * [Cisco VPN connect](https://www.bitrise.io/integrations/steps/vpnc-connect)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-open-vpn/issues\npublished_at: 2023-06-08T08:44:56.833538149Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-open-vpn.git\n  commit: fc67cb48de21ecece075d04a071969f701b2b289\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: openvpn\n  apt_get:\n  - name: openvpn\n  - name: net-tools\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- host: null\n  opts:\n    description: |\n      Open VPN Server IP or Hostname.\n      ex1. 111.111.111.111\n      ex2. hoge.com\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server IP or Hostname\n    title: Host\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Port number\n    title: Port\n  port: 1194\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Open VPN Server Protocol\n    title: Protocol\n    value_options:\n    - udp\n    - tcp\n  proto: udp\n- ca_crt: $VPN_CA_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded CA Certificate\n    title: Base64 encoded CA Certificate\n- client_crt: $VPN_CLIENT_CRT_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Certificate\n    title: Base64 encoded Client Certificate\n- client_key: $VPN_CLIENT_KEY_BASE64\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Base64 encoded Client Private Key\n    title: Base64 encoded Client Private Key\noutputs:\n- OPENVPN_LOG_PATH: null\n  opts:\n    title: Output log file path\n"
  },
  {
    "path": "steps/open-vpn/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/openstf-connect/0.0.1/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n  1. App compilation e.g. using Gradle Runner step\n  2. Open STF Connect (this step)\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices)\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2017-07-10T13:57:42.724462615+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: 795bd27b7be3cca62e0fd434f89eeb9e4f77341e\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there is more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Private ADB key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Public ADB key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices, even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.2/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2017-09-08T01:27:33.882092501+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: 7859491e65e1e18bcd5b1d961c8de8e8bc5aaae8\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices, even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.3/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2017-11-29T01:08:25.404660983+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: 7d924933f25c9267580ed784a413dcb6e660cf2e\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices, even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.4/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2017-11-29T12:06:04.538759+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: e351a860be6bbc035cbfcdf5db5ac3e8da161b4b\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices, even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.5/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2017-12-11T02:25:40.120619575+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: b099b960711178474a077a663b0ed3cefe1a81f8\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices, even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.6/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2018-09-04T12:56:06.29886161+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: 10cef5ebf729b97df42ce599abbd046c166c851e\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices (matching filter if any), even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.7/step.yml",
    "content": "title: Open STF Connect\nsummary: |\n  Connects with devices from Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/openstf/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2018-11-27T04:03:34.710176114+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: 4ee070d7347b5eae573a34c71000050c606c40fd\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices (matching filter if any), even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/0.0.8/step.yml",
    "content": "title: Device Farmer/Open STF Connect\nsummary: |\n  Connects with devices from Device Farmer/Open Smartphone Test Farm\ndescription: |\n  To use this step, you need an access to running [Device Farmer](https://devicefarmer.github.io/) or [Open STF](https://openstf.io/) instance with at least 1 device connected.\n  [Access token](https://github.com/devicefarmer/stf/blob/master/doc/API.md#authentication) and ADB keys has to be set up using STF web UI.\n  Typical workflow:\n\n  1. App compilation e.g. using Gradle Runner step.\n\n  2. Device Farmer/Open STF Connect (this step).\n\n  3. Android instrumention and/or UI tests e.g. using Gradle Unit Test step.\n\n  4. Device Farmer/Open STF Disconnect step with `is_always_run: true` (to stop using remote devices).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect/issues\npublished_at: 2020-09-30T01:57:41.274441+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-connect.git\n  commit: cb5778c9ab64f683171ac24c94771d7e7c491d25\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-connect\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [STF API documentation](https://github.com/devicefarmer/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: STF API access token\n  stf_access_token: null\n- device_filter: .\n  opts:\n    description: |-\n      If not empty will be passed to `jq` as a select expression. Syntax details can be found in [jq manual](https://stedolan.github.io/jq/manual/#select(boolean_expression)).\n      Non-matching devices will be filtered out. Note that `.present and .owner == null` filter is applied implicitly so you don't need to add it manually.\n    is_expand: true\n    is_required: false\n    summary: Optional device requirements e.g. API level or manufacturer declared\n      as jq select expression. For example to use only devices with API level 21 or\n      newer `.sdk >= \"21\"`. Only present and not used devices are taken into account.\n    title: Device requirements e.g. API level\n- device_number_limit: null\n  opts:\n    description: |\n      Maximum number of devices to be used. 0 and empty mean unlimited.\n      If there are more available devices (after applying filter if any), only amount up to this number will be used. Devices will be chosen randomly.\n    is_expand: true\n    is_required: false\n    title: Device number limit\n- adb_key: null\n  opts:\n    description: |\n      Private ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Private ADB key\n- adb_key_pub: null\n  opts:\n    description: |\n      Public ADB key to be used when debugging on STF devices. If not empty value will be saved to `~/.android/adbkey.pub`.\n      Key used during build has to be registered in STF under `Settings->Keys->ADB Keys`.\n      You have to either provide value here or modify `~/.android/adbkey.pub` before this step.\n      Otherwise devices will be listed as unauthorized and cannot be used during build.\n    is_expand: true\n    is_required: false\n    title: Public ADB key\noutputs:\n- STF_DEVICE_SERIAL_LIST: null\n  opts:\n    description: |-\n      List of serials in JSON string array format to be used to disconnect devices after tests in next steps.\n      List will contain serials of all present and not used devices (matching filter if any), even those for which connection has failed.\n    title: Connected devices serials\n"
  },
  {
    "path": "steps/openstf-connect/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/openstf-disconnect/0.0.1/step.yml",
    "content": "title: OpenSTF Disconnect\nsummary: |\n  Disconnects from devices previously connected using Open STF Connect step\ndescription: |\n  Disconnects from devices previously connected using Open STF Connect step\n  This step has to be inserted after Android instrumention and/or UI tests.\n  It is recommended to set this step to be run always, even if previous step(s) failed to ensure that devices will be released.\n  Otherwise they will be occupied until usage timeout exceeds. This setting is enabled by default.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect/issues\npublished_at: 2017-07-10T14:17:13.489414518+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-stf-disconnect.git\n  commit: 97ed3c6a7ebd56a58a4c87b5a3a6f337bb9be22e\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- opts:\n    description: |\n      List of serials in JSON string array format generated by Open STF Connect step.\n      Empty input is treated like empty array.\n    is_expand: true\n    is_required: true\n    title: Connected devices serials\n  stf_device_serial_list: $STF_DEVICE_SERIAL_LIST\n"
  },
  {
    "path": "steps/openstf-disconnect/0.0.2/step.yml",
    "content": "title: Open STF Disconnect\nsummary: |\n  Disconnects from devices from Open Smartphone Test Farm previously connected using Open STF Connect step\ndescription: |\n  This step has to be inserted after Android instrumention and/or UI tests.\n  It is recommended to set this step to be run always, even if previous step(s) failed to ensure that devices will be released.\n  Otherwise they will be occupied until usage timeout exceeds. This setting is enabled by default.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect/issues\npublished_at: 2017-07-11T12:44:21.335547943+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect.git\n  commit: 3b9761371e041675c41a90fe9e346d579916fb8b\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- opts:\n    description: |\n      List of serials in JSON string array format generated by Open STF Connect step.\n      Empty input is treated like empty array.\n    is_expand: true\n    is_required: true\n    title: Connected devices serials\n  stf_device_serial_list: $STF_DEVICE_SERIAL_LIST\n"
  },
  {
    "path": "steps/openstf-disconnect/0.0.3/step.yml",
    "content": "title: Open STF Disconnect\nsummary: |\n  Disconnects from devices from Open Smartphone Test Farm previously connected using Open STF Connect step\ndescription: |\n  This step has to be inserted after Android instrumention and/or UI tests.\n  It is recommended to set this step to be run always, even if previous step(s) failed to ensure that devices will be released.\n  Otherwise they will be occupied until usage timeout exceeds. This setting is enabled by default.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect/issues\npublished_at: 2017-08-20T02:06:31.87070701+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect.git\n  commit: 13d3e11c1d139ba5f06ffaf760134500ba3542d2\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    title: STF API access token\n  stf_access_token: null\n- opts:\n    description: |\n      List of serials in JSON string array format generated by Open STF Connect step.\n      Empty input is treated like empty array.\n    is_expand: true\n    is_required: true\n    title: Connected devices serials\n  stf_device_serial_list: $STF_DEVICE_SERIAL_LIST\n"
  },
  {
    "path": "steps/openstf-disconnect/0.0.4/step.yml",
    "content": "title: Open STF Disconnect\nsummary: |\n  Disconnects from devices from Open Smartphone Test Farm previously connected using Open STF Connect step\ndescription: |\n  This step has to be inserted after Android instrumention and/or UI tests.\n  It is recommended to set this step to be run always, even if previous step(s) failed to ensure that devices will be released.\n  Otherwise they will be occupied until usage timeout exceeds. This setting is enabled by default.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect/issues\npublished_at: 2018-09-04T13:04:53.325273028+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect.git\n  commit: 609047758316cb5e5774abb56427ce2d86ffa5ae\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: STF API access token\n  stf_access_token: null\n- opts:\n    description: |\n      List of serials in JSON string array format generated by Open STF Connect step.\n      Empty input is treated like empty array.\n    is_expand: true\n    is_required: true\n    title: Connected devices serials\n  stf_device_serial_list: $STF_DEVICE_SERIAL_LIST\n"
  },
  {
    "path": "steps/openstf-disconnect/0.0.5/step.yml",
    "content": "title: Open STF Disconnect\nsummary: |\n  Disconnects from devices from Open Smartphone Test Farm previously connected using Open STF Connect step\ndescription: |\n  This step has to be inserted after Android instrumention and/or UI tests.\n  It is recommended to set this step to be run always, even if previous step(s) failed to ensure that devices will be released.\n  Otherwise they will be occupied until usage timeout exceeds. This setting is enabled by default.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect/issues\npublished_at: 2018-11-25T16:55:45.164940661+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect.git\n  commit: c280b3b2ba30f9df641d4493b535e229596f3286\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [OpenSTF API documentation](https://github.com/openstf/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: STF API access token\n  stf_access_token: null\n- opts:\n    description: |\n      List of serials in JSON string array format generated by Open STF Connect step.\n      Empty input is treated like empty array.\n    is_expand: true\n    is_required: true\n    title: Connected devices serials\n  stf_device_serial_list: $STF_DEVICE_SERIAL_LIST\n"
  },
  {
    "path": "steps/openstf-disconnect/0.0.6/step.yml",
    "content": "title: Device Farmer/Open STF Disconnect\nsummary: |\n  Disconnects from devices from Device Farmer/Open Smartphone Test Farm previously connected using Device Farmer/Open STF Connect step\ndescription: |\n  This step has to be inserted after Android instrumention and/or UI tests.\n  It is recommended to set this step to be run always, even if previous step(s) failed to ensure that devices will be released.\n  Otherwise they will be occupied until usage timeout exceeds. This setting is enabled by default.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect/issues\npublished_at: 2020-09-30T02:30:22.637115+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-openstf-disconnect.git\n  commit: 4ff7eab93e9e3bb4d96a1a9f52155b1720a1e67a\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-openstf-disconnect\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      URL of your STF instance e.g. `https://stf.example.com`\n    is_expand: true\n    is_required: true\n    title: STF Host URL\n  stf_host_url: null\n- opts:\n    description: |\n      STF API access token. Go to `Settings->Keys` on your STF web UI to generate one.\n      Read more about tokens in [STF API documentation](https://github.com/devicefarmer/stf/blob/master/doc/API.md#authentication).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: STF API access token\n  stf_access_token: null\n- opts:\n    description: |\n      List of serials in JSON string array format generated by Open STF Connect step.\n      Empty input is treated like empty array.\n    is_expand: true\n    is_required: true\n    title: Connected devices serials\n  stf_device_serial_list: $STF_DEVICE_SERIAL_LIST\n"
  },
  {
    "path": "steps/openstf-disconnect/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/oversecured/1.0.0/step.yml",
    "content": "title: Oversecured\nsummary: |\n  Detects security vulnerabilities\ndescription: |\n  A SAST Android vulnerability scanner. Searches for vulnerabilities in [90+ categories](https://oversecured.com/vulnerabilities) using Oversecured API.\nwebsite: https://oversecured.com/\nsource_code_url: https://github.com/oversecured/oversecured-bitrise-step\nsupport_url: https://github.com/oversecured/oversecured-bitrise-step/issues\npublished_at: 2020-12-20T02:38:09.581189+03:00\nsource:\n  git: https://github.com/oversecured/oversecured-bitrise-step.git\n  commit: 429c68390965e3048e7ff5017b667f61a31e7274\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/oversecured/oversecured-bitrise-step\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_token: null\n  opts:\n    description: |\n      A key should be generated in your [profile settings](https://oversecured.com/settings).\n    is_required: true\n    is_sensitive: true\n    summary: Your Oversecured access token\n    title: Oversecured API key\n- integration_id: null\n  opts:\n    description: |\n      Integration ID, generated automatically when the Integration is created.\n    is_required: true\n    summary: Oversecured Integration ID\n    title: Oversecured Integration ID\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      This usually gets generated by the \"Gradle Runner\".\n    is_required: true\n    summary: The Android app file you want to send for scanning, usually $BITRISE\\_APK\\_PATH\n    title: A Bitrise generated APK path\n"
  },
  {
    "path": "steps/oversecured/1.0.1/step.yml",
    "content": "title: Oversecured\nsummary: |\n  Detects security vulnerabilities\ndescription: |\n  A SAST Android vulnerability scanner. Searches for vulnerabilities in [90+ categories](https://oversecured.com/vulnerabilities) using Oversecured API.\nwebsite: https://oversecured.com/\nsource_code_url: https://github.com/oversecured/oversecured-bitrise-step\nsupport_url: https://github.com/oversecured/oversecured-bitrise-step/issues\npublished_at: 2021-05-02T20:45:49.564533+03:00\nsource:\n  git: https://github.com/oversecured/oversecured-bitrise-step.git\n  commit: 501beff12f7a531ea99ab1cfe1af43f405f53bb9\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/oversecured/oversecured-bitrise-step\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_token: null\n  opts:\n    description: |\n      A key should be generated in your [profile settings](https://oversecured.com/settings/api-keys).\n    is_required: true\n    is_sensitive: true\n    summary: Your Oversecured access token\n    title: Oversecured API key\n- integration_id: null\n  opts:\n    description: |\n      Integration ID, generated automatically when the Integration is created.\n    is_required: true\n    summary: Oversecured Integration ID\n    title: Oversecured Integration ID\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      This usually gets generated by the \"Gradle Runner\".\n    is_required: true\n    summary: The Android app file you want to send for scanning, usually $BITRISE\\_APK\\_PATH\n    title: A Bitrise generated APK path\n"
  },
  {
    "path": "steps/oversecured/1.0.2/step.yml",
    "content": "title: Oversecured\nsummary: |\n  Detects security vulnerabilities\ndescription: |\n  Enterprise vulnerability scanner for Android and iOS apps. It offers app owners and developers the ability to secure each new version of a mobile app by integrating Oversecured into the development process.\nwebsite: https://oversecured.com/\nsource_code_url: https://github.com/oversecured/oversecured-bitrise-step\nsupport_url: https://github.com/oversecured/oversecured-bitrise-step/issues\npublished_at: 2022-06-26T18:13:58.186333+03:00\nsource:\n  git: https://github.com/oversecured/oversecured-bitrise-step.git\n  commit: 076f82c9679fa875f5148fd2f24395068eef3c78\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/oversecured/oversecured-bitrise-step\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- access_token: null\n  opts:\n    description: |\n      A key should be generated in your [profile settings](https://oversecured.com/settings/api-keys).\n    is_required: true\n    is_sensitive: true\n    summary: Your Oversecured access token\n    title: API Key\n- integration_id: null\n  opts:\n    description: |\n      Integration ID, automatically generated when the Integration is created.\n    is_required: true\n    summary: Integration ID\n    title: Integration ID\n- branch_name: main\n  opts:\n    description: |\n      Branch name, `main` is default. You can create your own branches in the Integration settings.\n    is_required: true\n    summary: Branch name\n    title: Branch\n- app_path: null\n  opts:\n    description: |\n      This usually gets generated by the \"Gradle Runner\". In most cases, you can use $BITRISE\\_APK\\_PATH for Android apps and manually zip sources for iOS.\n    is_required: true\n    summary: Oversecured accepts APK/AAB files for Android and zipped sources for\n      iOS.\n    title: App File\n"
  },
  {
    "path": "steps/oversecured/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/pagerduty/0.1.2/step.yml",
    "content": "title: Create a PagerDuty alert\nsummary: |\n  Create a PagerDuty alert\ndescription: |\n  This step creates a PagerDuty alert with specific parameters. It can use Events API v1 or v2.\nwebsite: https://github.com/PagerDuty/bitrise-step-pagerduty\nsource_code_url: https://github.com/PagerDuty/bitrise-step-pagerduty\nsupport_url: https://github.com/PagerDuty/bitrise-step-pagerduty/issues\npublished_at: 2019-10-16T14:00:23.140207-04:00\nsource:\n  git: https://github.com/PagerDuty/bitrise-step-pagerduty.git\n  commit: 1e9e419f8b2bedaceee57b1fba0f085bc017c17e\ntype_tags:\n- notification\ndeps:\n  brew:\n  - name: curl\n  - name: jq\n  apt_get:\n  - name: curl\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: '{{enveq \"BITRISE_BUILD_STATUS\" \"0\" | not}}'\ninputs:\n- api_version: v2\n  opts:\n    description: Events API v1 or v2 (available in the Integrations tab of the Service\n      Details).\n    is_expand: false\n    is_required: true\n    summary: Events API v1 or v2 (available in the Integrations tab of the Service\n      Details)\n    title: API version\n    value_options:\n    - v1\n    - v2\n- integration_key: null\n  opts:\n    description: The hexadecimal service key (available in the Integrations tab of\n      the Service Details).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The hexadecimal service key (available in the Integrations tab of the\n      Service Details)\n    title: Integration key\n- event_description: null\n  opts:\n    description: The description that the event will be created with.\n    is_expand: true\n    is_required: true\n    summary: The description that the event will be created with\n    title: Event description\n- severity: error\n  opts:\n    description: The severity that the event will be created with (relevant to Event\n      Rules).\n    is_expand: false\n    is_required: true\n    summary: The severity that the event will be created with (relevant to Event Rules)\n    title: Event severity (API v2 only)\n    value_options:\n    - critical\n    - error\n    - warning\n    - info\noutputs:\n- PAGERDUTY_EVENT_MESSAGE: null\n  opts:\n    description: The PagerDuty Events API will return a 'message' which indicates\n      the result of the operation.\n    summary: The message returned by the PagerDuty Events API\n    title: PagerDuty event creation message\n- PAGERDUTY_INCIDENT_KEY: null\n  opts:\n    description: The PagerDuty Events API v1 will return a 'incident_key' which identifies\n      the incident.\n    summary: The incident key returned by the PagerDuty Events API v1\n    title: PagerDuty event creation incident_key\n- PAGERDUTY_DEDUP_KEY: null\n  opts:\n    description: The PagerDuty Events API v2 will return a 'dedup_key' which can be\n      used to group alerts into a single incident.\n    summary: The deduplication key returned by the PagerDuty Events API v2\n    title: PagerDuty event creation dedup_key\n"
  },
  {
    "path": "steps/pagerduty/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/parse-composer-results/0.0.1/step.yml",
    "content": "title: Parse Composer test results\nsummary: |\n  Parses Composer junit test results and stores them in environment variables.\n  `$ALL_TEST_COUNT` and `$PASSED_TEST_COUNT` respectively.\ndescription: |\n  Parses [Composer](https://github.com/gojuno/composer) junit test results and stores them in environment variables:\n    `$ALL_TEST_COUNT` and `$PASSED_TEST_COUNT` respectively.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results/issues\npublished_at: !!timestamp 2018-03-20T02:34:26.115084608+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results.git\n  commit: 536d16c7cd2e2d7a41e170c79e4a99425c628925\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-parse-composer-results\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Directory to search for composer test result files, recursively. By default the entire workspace: `$BITRISE_SOURCE_DIR`.\n    title: Directory to search for composer test result files\n  results_dir: $BITRISE_SOURCE_DIR\noutputs:\n- ALL_TEST_COUNT: null\n  opts:\n    summary: All test count. Passed, failed, skipped and errored. Sum across all found\n      files.\n    title: All test count\n- PASSED_TEST_COUNT: null\n  opts:\n    summary: Passed test count (excluding skipped ones). Sum across all found files.\n    title: Passed test count (excluding skipped)\n"
  },
  {
    "path": "steps/parse-composer-results/0.0.2/step.yml",
    "content": "title: Parse Composer test results\nsummary: |\n  Parses Composer junit test results and stores them in environment variables.\n  `$COMPOSER_ALL_TEST_COUNT` and `$COMPOSER_PASSED_TEST_COUNT` respectively.\ndescription: |\n  Parses [Composer](https://github.com/gojuno/composer) junit test results and stores them in environment variables:\n    `$COMPOSER_ALL_TEST_COUNT` and `$COMPOSER_PASSED_TEST_COUNT` respectively.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results/issues\npublished_at: !!timestamp 2018-03-22T02:08:36.824194894+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-parse-composer-results.git\n  commit: f3df131f59f55664f879cac467b827b4a60aaa37\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-parse-composer-results\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Directory to search for composer test result files, recursively. By default the entire workspace: `$BITRISE_SOURCE_DIR`.\n    title: Directory to search for composer test result files\n  results_dir: $BITRISE_SOURCE_DIR\noutputs:\n- COMPOSER_ALL_TEST_COUNT: null\n  opts:\n    summary: All test count. Passed, failed, skipped and errored. Sum across all found\n      files.\n    title: All test count\n- COMPOSER_PASSED_TEST_COUNT: null\n  opts:\n    summary: Passed test count (excluding skipped ones). Sum across all found files.\n    title: Passed test count (excluding skipped)\n"
  },
  {
    "path": "steps/parse-composer-results/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/pcloudy-app-upload/0.1.2/step.yml",
    "content": "title: pCloudy App Upload\nsummary: |\n  Uploads your APK or IPA to Pcloudy for interactive app testing.\ndescription: |\n  Uploads your APK or IPA to Pcloudy for interactive app testing. Please signup to get more details https://www.pcloudy.com\nwebsite: https://github.com/shibupanda/bitrise-step-pcloudy-upload-app\nsource_code_url: https://github.com/shibupanda/bitrise-step-pcloudy-upload-app\nsupport_url: https://github.com/shibupanda/bitrise-step-pcloudy-upload-app/issues\npublished_at: 2021-06-25T12:43:43.472427114+05:30\nsource:\n  git: https://github.com/shibupanda/bitrise-step-pcloudy-upload-app.git\n  commit: 4f5d221ec046e1c9a3a180dc14079cdde404ab74\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- upload_path:\n  opts:\n    description: |\n      The app file you want to upload to Pcloudy, usually $BITRISE\\_APK\\_PATH or $BITRISE\\_IPA\\_PATH.\n    is_expand: true\n    is_required: true\n    summary: Location of the IPA or APK that you want to upload.\n    title: Location of APK or IPA\n- opts:\n    description: |\n      The cloud URL to upload into specific cloud\n    is_required: true\n    is_sensitive: true\n    summary: Pcloudy cloud url\n    title: Pcloudy cloud url\n  pcloudy_cloudname: $PCLOUDY_CLOUDURL\n- opts:\n    description: |\n      The username you use to log into your Pcloudy account\n    is_required: true\n    is_sensitive: true\n    summary: Your Pcloudy username\n    title: Pcloudy username\n  pcloudy_username: $PCLOUDY_USERNAME\n- opts:\n    description: |\n      The access key you use to log into your Pcloudy account\n    is_required: true\n    is_sensitive: true\n    summary: Your Pcloudy access key\n    title: Pcloudy access key\n  pcloudy_access_key: $PCLOUDY_ACCESS_KEY\noutputs:\n- PCLOUDY_APP_NAME: null\n  opts:\n    description: \"The app name returned by Pcloudy \\nUse this in your remote device\n      tests, usually through your capabilities configuration\\n\"\n    summary: The app name used to automate remote device tests\n    title: Pcloudy Application Name\n"
  },
  {
    "path": "steps/pcloudy-app-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/pebble-build/1.0.0/step.yml",
    "content": "title: Pebble build\nsummary: Builds a Pebble project\ndescription: |\n  Builds a [Pebble project](https://developer.pebble.com) after installing SDK (if necessary).\nwebsite: https://github.com/HBehrens/bitrise-step-pebble-build\nsource_code_url: https://github.com/HBehrens/bitrise-step-pebble-build\nsupport_url: https://github.com/HBehrens/bitrise-step-pebble-build/issues\npublished_at: 2016-07-05T08:01:19.000000000-07:00\nsource:\n  git: https://github.com/HBehrens/bitrise-step-pebble-build.git\n  commit: b98053ef64f5af83da5bbf0846e998fb1083862b\nhost_os_tags:\n- osx-10.10\n- osx-10.11\n- osx-10.12\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\ninputs:\n- opts:\n    description: |-\n      Specify the path to your Pebble project.\n      Use an empty value to skip building the project and only install the SDK.\n    title: Pebble project path\n  project_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      Speed up Pebble SDK installation by skiping the emulator.\n      If you only build your projects, it's safe to do this.\n    title: Install SDK without Emulator?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sdk_without_emulator: \"yes\"\n- opts:\n    description: |-\n      Speed up Pebble SDK installation by skiping Freetype.\n      Only if you don't use any custom fonts, it's safe to set this to \"yes\".\n    title: Install SDK without FreeType?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sdk_without_freetype: \"no\"\n- opts:\n    description: |-\n      Speed up Pebble SDK installation by skiping Node.\n      Only if you don't use Pebble Packages, it's safe to set this to \"yes\".\n    title: Install SDK without Pebble Packages?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sdk_without_node: \"no\"\n- opts:\n    description: |-\n      If set to \"yes\" (recommended), Pebble collects metrics on your usage of their developer tools.\n      This helps them to help prioritise further development of their tooling.\n    title: Send analytics about SDK usage to Pebble?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  sdk_enable_analytics: \"yes\"\n- opts:\n    description: |-\n      To use the Pebble SDK, you must agree to the following:\n\n      PEBBLE TERMS OF USE\n      https://developer.getpebble.com/legal/terms-of-use\n\n      PEBBLE DEVELOPER LICENSE\n      https://developer.getpebble.com/legal/sdk-license\n\n      You have to provide \"yes\" as input value to agree.\n    title: Accept Pebble TERMS OF USE and PEBBLE DEVELOPER LICENSE?\n    is_required: true\n  sdk_accept_legalese:\n"
  },
  {
    "path": "steps/pebble-build/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/perfecto-upload/0.0.3/step.yml",
    "content": "title: Perfecto Upload\nsummary: |\n  Upload APK/IPA files to Perfecto cloud repository\ndescription: |\n  Upload your build files to Perfecto for remote device testing. Upload your IPA/APK file to Perfecto repository\nwebsite: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsource_code_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsupport_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload/issues\npublished_at: 2020-06-15T19:08:15.426826+05:30\nsource:\n  git: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload.git\n  commit: 93ea11970c3eeebed0d9a217665ea543c4a6c513\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    summary: The app file you want to upload to Perfecto, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- opts:\n    description: |\n      The security token you use to log into your Perfecto account\n    is_required: true\n    summary: Your perfecto access key.\n    title: Perfecto access key\n  perfecto_accesskey: $PERFECTO_ACCESS_KEY\n- opts:\n    description: |\n      The perfect cloud name\n    is_required: true\n    summary: Your perfecto cloud name. Ex - abc.perfectomobile.com\n    title: Perfecto cloud name\n  perfecto_cloudname: $PERFECTO_CLOUD_NAME\n- opts:\n    description: |\n      File path on perfecto cloud repository where it would be stored\n    is_required: true\n    summary: Your perfecto repository path\n    title: Perfecto repository path\n  perfecto_filepath: $PERFECTO_FILE_PATH\n"
  },
  {
    "path": "steps/perfecto-upload/0.0.6/step.yml",
    "content": "title: Perfecto Upload\nsummary: |\n  Upload APK/IPA files to Perfecto cloud repository\ndescription: |\n  Upload your build files to Perfecto for remote device testing. Upload your IPA/APK file to Perfecto repository\nwebsite: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsource_code_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsupport_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload/issues\npublished_at: 2020-06-27T19:13:46.420922+05:30\nsource:\n  git: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload.git\n  commit: f7ce84970aee9c8b9e0f4d06cb6123fff31fd445\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    is_sensitive: true\n    summary: The app file you want to upload to Perfecto, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- opts:\n    description: |\n      The security token you use to log into your Perfecto account\n    is_required: true\n    is_sensitive: true\n    summary: Your perfecto access key.\n    title: Perfecto access key\n  perfecto_accesskey: null\n- opts:\n    description: |\n      The perfecto cloud name\n    is_required: true\n    summary: Your perfecto cloud name. Ex - abc.perfectomobile.com\n    title: Perfecto cloud name\n  perfecto_cloudname: null\n- opts:\n    description: |\n      File path on perfecto cloud repository where it would be stored\n    is_required: true\n    summary: Your perfecto repository path\n    title: Perfecto repository path\n  perfecto_filepath: null\n"
  },
  {
    "path": "steps/perfecto-upload/0.0.7/step.yml",
    "content": "title: Perfecto Upload\nsummary: |\n  Upload APK/IPA files to Perfecto cloud repository\ndescription: |\n  Upload your build files to Perfecto for remote device testing. Upload your IPA/APK file to Perfecto repository\nwebsite: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsource_code_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsupport_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload/issues\npublished_at: 2021-03-26T14:01:20.979995+05:30\nsource:\n  git: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload.git\n  commit: dae5742997e24ef921421378542426f03c121e45\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    is_sensitive: true\n    summary: The app file you want to upload to Perfecto, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- opts:\n    description: |\n      The security token you use to log into your Perfecto account\n    is_required: true\n    is_sensitive: true\n    summary: Your perfecto access key.\n    title: Perfecto access key\n  perfecto_accesskey: null\n- opts:\n    description: |\n      The perfecto cloud name\n    is_required: true\n    summary: Your perfecto cloud name. Ex - abc.perfectomobile.com\n    title: Perfecto cloud name\n  perfecto_cloudname: null\n- opts:\n    description: |\n      File path on perfecto cloud repository where it would be stored\n    is_required: true\n    summary: Your perfecto repository path\n    title: Perfecto repository path\n  perfecto_filepath: null\n"
  },
  {
    "path": "steps/perfecto-upload/0.0.8/step.yml",
    "content": "title: Perfecto Upload\nsummary: |\n  Upload APK/IPA files to Perfecto cloud repository\ndescription: |\n  Upload your build files to Perfecto for remote device testing. Upload your IPA/APK file to Perfecto repository\nwebsite: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsource_code_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsupport_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload/issues\npublished_at: 2021-05-04T10:29:43.277059+05:30\nsource:\n  git: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload.git\n  commit: 66f1d5bbf1ece4a71d8375e4f93e042542437d64\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    is_sensitive: true\n    summary: The app file you want to upload to Perfecto, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- opts:\n    description: |\n      The security token you use to log into your Perfecto account\n    is_required: true\n    is_sensitive: true\n    summary: Your perfecto access key.\n    title: Perfecto access key\n  perfecto_accesskey: null\n- opts:\n    description: |\n      The perfecto cloud name\n    is_required: true\n    summary: Your perfecto cloud name. Ex - abc.perfectomobile.com\n    title: Perfecto cloud name\n  perfecto_cloudname: null\n- opts:\n    description: |\n      File path on perfecto cloud repository where it would be stored\n    is_required: true\n    summary: Your perfecto repository path\n    title: Perfecto repository path\n  perfecto_filepath: null\n"
  },
  {
    "path": "steps/perfecto-upload/0.0.9/step.yml",
    "content": "title: Perfecto Upload\nsummary: |\n  Upload APK/IPA files to Perfecto cloud repository\ndescription: |\n  Upload your build files to Perfecto for remote device testing. Upload your IPA/APK file to Perfecto repository\nwebsite: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsource_code_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsupport_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload/issues\npublished_at: 2021-05-06T21:49:44.041043+05:30\nsource:\n  git: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload.git\n  commit: d2265f708d24adc8245f6ff609f7b87a05ac631b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    is_sensitive: true\n    summary: The app file you want to upload to Perfecto, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- opts:\n    description: |\n      The security token you use to log into your Perfecto account\n    is_required: true\n    is_sensitive: true\n    summary: Your perfecto access key.\n    title: Perfecto access key\n  perfecto_accesskey: null\n- opts:\n    description: |\n      The perfecto cloud name\n    is_required: true\n    summary: Your perfecto cloud name. Ex - abc.perfectomobile.com\n    title: Perfecto cloud name\n  perfecto_cloudname: null\n- opts:\n    description: |\n      File path on perfecto cloud repository where it would be stored\n    is_required: true\n    summary: Your perfecto repository path\n    title: Perfecto repository path\n  perfecto_filepath: null\n"
  },
  {
    "path": "steps/perfecto-upload/1.0.0/step.yml",
    "content": "title: Perfecto Upload\nsummary: |\n  Uploads any file to Perfecto cloud repository\ndescription: |\n  Upload your IPA or APK builds, or any files to your Perfecto cloud repository for remote testing on real devices. To get your Perfecto security token using the Perfecto UI, click your user name in the top right corner of the screen and select My security token.\nwebsite: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsource_code_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload\nsupport_url: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload/issues\npublished_at: 2022-03-15T19:19:37.55905+05:30\nsource:\n  git: https://github.com/PerfectoCode/Bitrise_Perfecto_FileUpload.git\n  commit: c97fa2b43a6c574f1ae4b0d01a8a1f01b6ccdb01\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n    is_required: true\n    is_sensitive: true\n    summary: The app file you want to upload to Perfecto, usually $BITRISE\\_APK\\_PATH\n      or $BITRISE\\_IPA\\_PATH\n    title: A Bitrise generated APK or IPA path\n  upload_path: $BITRISE_APK_PATH\n- opts:\n    description: |\n      The security token you use to log into your Perfecto account. To get your Perfecto security token using the Perfecto UI, click your user name in the top right corner of the screen and select My security token. For more details - https://help.perfecto.io/perfecto-help/content/perfecto/automation-testing/generate_security_tokens.htm\n    is_required: true\n    is_sensitive: true\n    summary: Your perfecto access key.\n    title: Perfecto access key\n  perfecto_securityToken: null\n- opts:\n    description: |\n      The perfecto cloud name\n    is_required: true\n    summary: Your perfecto cloud name. Ex - abc.perfectomobile.com\n    title: Perfecto cloud name\n  perfecto_cloudname: null\n- opts:\n    description: |\n      The locator value used to specify the virtual path to the file in the Perfecto cloud repository. Ex – Public:FunAppB.apk\n    is_required: true\n    summary: Your perfecto repository path\n    title: Perfecto repository path\n  perfecto_locator: null\n"
  },
  {
    "path": "steps/perfecto-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.1/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-04-25T12:35:15.120467466+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 65b5f675e1b8f63b0386e075a89f146645b77afa\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: enveq \"BITRISE_PULL_REQUEST\" \"\" | and .IsCI\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_domain: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA domain\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n- JIRA_ISSUE_NAME: null\n  opts:\n    description: The name of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The name of the issue where the comment has been posted\n    title: JIRA issue name\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.10/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2017-01-21T14:29:06.584893837+01:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 91c38231830456f594382a45c3681b0e43f6f8fc\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- jira\n- issue-tracker\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.11/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2017-02-10T13:07:36.012844286+01:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 76308d981ac728de9a6765bae970580d584a1f3c\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_project: null\n  opts:\n    description: JIRA project key that will be added to the issue ID to form the issue\n      key (usually in the form XXX, with issue keys named XXX-123). If none provided,\n      then the issue key must appear in the branch name.\n    is_expand: true\n    is_required: false\n    summary: JIRA project key that will be added to the issue ID\n    title: JIRA project\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.12/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2017-05-01T16:02:39.191194951+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: d612f2a214459b6a24d7012124e9c19073e8b31b\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_project: null\n  opts:\n    description: JIRA project key that will be added to the issue ID to form the issue\n      key (usually in the form XXX, with issue keys named XXX-123). If none provided,\n      then the issue key must appear in the branch name.\n    is_expand: true\n    is_required: false\n    summary: JIRA project key that will be added to the issue ID\n    title: JIRA project\n    value_options: []\n- jira_issue_key: null\n  opts:\n    description: This step can find the issue key from the branch name, but if you\n      want to provide it as part of the environment or determine it earlier in the\n      workflow, you can.\n    is_expand: true\n    is_required: false\n    summary: JIRA issue key, if found earlier in the workflow\n    title: JIRA issue key\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.2/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-04-25T14:44:32.652259558+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 85d4e5fbffe0b3eb20a0e926d822d87bf7e00354\ntype_tags:\n- jira\n- issue-tracker\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: enveq \"BITRISE_PULL_REQUEST\" \"\" | and .IsCI\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_domain: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA domain\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n- JIRA_ISSUE_NAME: null\n  opts:\n    description: The name of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The name of the issue where the comment has been posted\n    title: JIRA issue name\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.4/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-04-27T16:54:10.458834647+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 4cda4d360c96c6312f4e78c70de6588dc55934cc\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- jira\n- issue-tracker\ndeps:\n  brew:\n  - name: homebrew/php/php56\n  apt_get:\n  - name: php5\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.5/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-06-02T17:22:27.322705362+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: ab8861964bc8475154986eb165ea352574a8d7c8\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- jira\n- issue-tracker\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.6/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-07-30T16:45:49.083368045+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 543f30e2d4b32e5b964af22533989215057830ce\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- jira\n- issue-tracker\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.8/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-08-06T14:48:41.437974019+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 3ec682d8e77fa3154e895487bd11ba6282c0e52b\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- jira\n- issue-tracker\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/0.1.9/step.yml",
    "content": "title: Create JIRA comment with build\nsummary: Will post a comment on the issue page with build details (download link,\n  build number, etc)\ndescription: Will post a comment on the issue page with build details (download link,\n  build number, etc)\nwebsite: https://github.com/dag-io/post-jira-comment-with-build-details-step\nsource_code_url: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\nsupport_url: https://github.com/dag-io/post-jira-comment-with-build-details-step/issues\npublished_at: 2016-10-17T17:18:55.492054712+02:00\nsource:\n  git: https://github.com/dag-io/post-jira-comment-with-build-details-step.git\n  commit: 148fea0e92e8e23088ef2015347761dfaa05336f\nhost_os_tags:\n- ubuntu-14.04\n- osx-10.11\ntype_tags:\n- jira\n- issue-tracker\ndeps:\n  apt_get:\n  - name: php7.0\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI | and (not .IsPR)\ninputs:\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    description: The branch name for the build\n    is_expand: true\n    is_required: true\n    summary: The branch name for the build\n    title: Git branch name\n    value_options: []\n- jira_user: null\n  opts:\n    description: JIRA account username that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account username that will be the author of the comment\n    title: JIRA user\n    value_options: []\n- jira_password: null\n  opts:\n    description: JIRA account password that will be the author of the comment\n    is_expand: true\n    is_required: true\n    summary: JIRA account password that will be the author of the comment\n    title: JIRA user password\n    value_options: []\n- jira_build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\\n\n\n    ||Build number|$BITRISE_BUILD_NUMBER|\\n\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\\n\n    ||Branch|$BITRISE_GIT_BRANCH|\\n\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\\n\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\\n\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_expand: true\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n    value_options: []\n- jira_url: null\n  opts:\n    description: 'JIRA instance URL (Ex: http://foobar.atlassian.net/)'\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL\n    title: JIRA URL\n    value_options: []\noutputs:\n- JIRA_ISSUE_KEY: null\n  opts:\n    description: The key of the issue where the comment has been posted\n    is_expand: true\n    is_required: true\n    summary: The key of the issue where the comment has been posted\n    title: JIRA issue key\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/1.0.0/step.yml",
    "content": "title: Post Jira Comment\nsummary: Post comment to an issue at Jira.\ndescription: \"Post comment to an issue at Jira with the build params. \\n- Public download\n  page\\n- Build number\\n- Author\\n- Git branch\\n- Commit hash\\n- Commit message\"\nwebsite: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details\nsource_code_url: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details.git\nsupport_url: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details/issues\npublished_at: !!timestamp 2018-05-02T11:17:52.18391766+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details.git\n  commit: 560ebd03bd5deb7410e115f9c67dd6101a5bfd83\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-post-jira-comment-with-build-details\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: User name on Jira (user's email).\n    is_required: true\n    summary: User name on Jira (user's email).\n    title: Jira user name\n  user_name: null\n- api_token: null\n  opts:\n    description: Api token generated on Jira.\n    is_required: true\n    summary: Api token generated on Jira.\n    title: Jira api token\n- issue_keys: null\n  opts:\n    description: Jira issue keys separatad with `|`\n    is_required: true\n    summary: Jira issue keys separatad with `|`\n    title: Jira issue keys\n- base_url: null\n  opts:\n    description: URL of the presonal Jira software.\n    is_required: true\n    summary: URL of the presonal Jira software.\n    title: Jira base URL.\n- build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\n    ||Build number|$BITRISE_BUILD_NUMBER|\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\n    ||Branch|$BITRISE_GIT_BRANCH|\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/1.1.0/step.yml",
    "content": "title: Post Jira Comment\nsummary: Post comment to an issue at Jira.\ndescription: \"Post comment to an issue at Jira with the build params. \\n- Public download\n  page\\n- Build number\\n- Author\\n- Git branch\\n- Commit hash\\n- Commit message\"\nwebsite: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details\nsource_code_url: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details.git\nsupport_url: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details/issues\npublished_at: 2018-08-31T08:00:15.338429844Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details.git\n  commit: 3008edf193f08478ee8da562fefa53bbe7c4b370\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-post-jira-comment-with-build-details\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: User name on Jira (user's email).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User name on Jira (user's email).\n    title: Jira user name\n  user_name: null\n- api_token: null\n  opts:\n    description: Api token generated on Jira.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Api token generated on Jira.\n    title: Jira api token\n- issue_keys: null\n  opts:\n    description: Jira issue keys separatad with `|`\n    is_required: true\n    summary: Jira issue keys separatad with `|`\n    title: Jira issue keys\n- base_url: null\n  opts:\n    description: URL of the presonal Jira software.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: URL of the presonal Jira software.\n    title: Jira base URL.\n- build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\n    ||Build number|$BITRISE_BUILD_NUMBER|\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\n    ||Branch|$BITRISE_GIT_BRANCH|\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/1.1.1/step.yml",
    "content": "title: Post Jira Comment\nsummary: Post comment to a Jira issue.\ndescription: \"The Step adds a comment to a Jira issue. Using this Step, you can attach\n  your build parameters to a Jira issue, or you can add any comment using Markdown.\\n\\n###\n  Configuring the Step\\n\\n1. Add your Jira email address as a Secret Env Var to the\n  **Jira user name** input.\\n1. Add your Jira API token to the **Jira API token**\n  input. \\n   You can generate your API token according to [this guide](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).\\n1.\n  Add your Jira issue key to the **Jira issue keys** input. You can add multiple Jira\n  issues separated with the `|` character. \\n1. Add your Jira base URL to the **Jira\n  base URL** input. \\n1. Add the comment you would like to attach to your Jira issue\n  in the **Build message** input. You can add any information here using Markdown.\n  By default, this will contain the following Build parameters:\\n   * Public download\n  page\\n   * Build number\\n   * Author\\n   * Git branch\\n   * Commit hash\\n   * Commit\n  message\\n\\n### Useful links\\n\\n* [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)\\n*\n  [What is an issue?](https://support.atlassian.com/jira-software-cloud/docs/what-is-an-issue/)\\n*\n  [How to find your site URL to set up the Jira Data Center and Server mobile app](https://confluence.atlassian.com/jirakb/how-to-find-your-site-url-to-set-up-the-jira-data-center-and-server-mobile-app-954244798.html)\\n\\n###\n  Related Steps\\n\\n* [Send a Slack message](https://www.bitrise.io/integrations/steps/slack)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details\nsource_code_url: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details.git\nsupport_url: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details/issues\npublished_at: 2022-04-14T11:48:43.724867034Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-post-jira-comment-with-build-details.git\n  commit: 4d2d2a0b8a4568546f9dc8a0e6064e26f6083c16\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-post-jira-comment-with-build-details\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- opts:\n    description: User name on Jira (user's email).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: User name on Jira (user's email).\n    title: Jira user name\n  user_name: null\n- api_token: null\n  opts:\n    description: API token generated on Jira.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API token generated on Jira.\n    title: Jira API token\n- issue_keys: null\n  opts:\n    description: Jira issue keys separated with `|`\n    is_required: true\n    summary: Jira issue keys separated with `|`\n    title: Jira issue keys\n- base_url: null\n  opts:\n    description: URL of the personal Jira software.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: URL of the personal Jira software.\n    title: Jira base URL\n- build_message: |\n    *$BITRISE_APP_TITLE* build *$BITRISE_BUILD_NUMBER* is now available: [Download|$BITRISE_PUBLIC_INSTALL_PAGE_URL]\n    ||Build number|$BITRISE_BUILD_NUMBER|\n    ||Author|$GIT_CLONE_COMMIT_AUTHOR_NAME|\n    ||Branch|$BITRISE_GIT_BRANCH|\n    ||Commit hash|$GIT_CLONE_COMMIT_HASH|\n    ||Commit message|$GIT_CLONE_COMMIT_MESSAGE_SUBJECT|\n\n    [Show build details|$BITRISE_BUILD_URL]\n  opts:\n    description: The content of the build message that will be posted. You can use\n      markdown. Details [here|https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all]\n    is_required: true\n    summary: The content of the build message that will be posted\n    title: Build message\n"
  },
  {
    "path": "steps/post-jira-comment-with-build-details/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/project-scanner/0.10.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-09-28T15:16:57.211007096+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: b5f34f6983773645a130f652819512d71d130f8f\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.10.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-09-30T17:48:50.875471+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 1751dd96d914bd5331fc22028f637f9ce587a192\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.11.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-10-11T12:53:16.423131123+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: eaa9c55de544471937c542dff292ce0ff1557ed7\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.11.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-11-02T16:42:28.41917208+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: faa977a14f5bbaf13f50b8203517e0ef1ec0d75b\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.11.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-11-09T13:48:44.261602972+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: bf8867dc412d1d35b0ea3ebc767f2e4fb74295c1\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.11.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-12-14T01:07:17.129886631+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: dc519c989a73f1bfccbe115ff270c29bbd57ea73\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.11.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-12-19T17:15:58.360714014+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: e76113383b9bda0c938c0ebd9b53c338842a3ed4\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.12.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-01-09T14:12:09.477107463+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 83ce22611b92b9adc83a3865daf9e02041ce64ce\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-06-01T15:37:49.072584371+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 7a5ec89cf70fbad439a5aa5ed36b6321060b000d\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-06-01T16:54:54.383570799+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 463cc7868d795e65425e132d11dced4a83813b4e\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.10/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-07-29T17:39:54.879610358+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 3aa2b0fab5471f5aca5715b4ed2a6bb8058307b9\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.11/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-08-10T17:53:28.638246521+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: b9662e866c75096c88844b9f65bb165ebc644929\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.12/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-09-07T15:19:32.26058352+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: a436749373e830960e570a0db2f508a44468fd6b\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.13/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-09-08T16:17:33.052339072+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 773e8811bc6bab43a2b5784ae980b6e29877e823\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.14/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-09-16T17:32:59.932916065+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: bdffac57a4a8700ae61d8d4e50f59ed91835bb9c\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-06-01T18:05:54.81761944+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 4011f020d150fb6dfd804c0e8f17859a92932964\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-06-02T16:03:00.182405597+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 12c3c44d0768da82b1621338966b6739314fc35d\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-06-27T15:40:16.969955421+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 6de0b8ed93b32d97b01bcb9e53f41da3504a2619\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.5/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-06-27T16:07:46.41991459+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 40aa174cf6cdb8c55aecd97b4535993fe215a545\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.6/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-07-01T12:42:47.563979981+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: d4d7f094b0fd8f2aef2ba163edb3ee003032c647\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.7/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-07-05T16:11:05.871801831+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 0c2d05625ab85abb2f10fa0319aba95e92ef44f3\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.8/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-07-20T11:33:07.582361021+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 63a9266ec9f2ad8df26a8f172b7a20d7e1b9a7d8\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/0.9.9/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2016-07-28T12:13:52.150971411+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2ded0df6031b65b7b8b29d1b5b7191f094ac21c4\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.0.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-01-17T14:13:34.951157085+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 7528c86e617361b0ac2a3e47da136c4fff86ca1b\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.0.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-01-18T15:04:48.657739713+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 566872f025c68c9cd674c9310e15f19a15a73971\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.1.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-01-25T15:14:59.631006827+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 3f9b2a3fd73481497ca5e6fd9067155a2a5dadfa\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.1.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-02-02T11:33:39.43687097+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 46f304f9f8aa48144d6733d6ae88ef479b648a6b\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.1.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-02-23T16:34:36.892928924+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 80e30967369b1419708e3117f595693468b10b07\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.1.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, Android, Xamarin and Fastlane projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-03-17T10:32:30.258867649+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 4c7853d9d99b7c1b9e307a677cf794a1e9f9ea9c\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.2.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-05-08T15:49:22.662177256+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ae18afc82fb5424f2aeb995161b0d905a77e5b83\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.2.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-05-08T19:05:47.530397814+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ea41675a62084f79f3fb47c2ba86a7bda219b902\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.2.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-05-17T14:20:54.822710759+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: e180aca83184dbc283efc5a6ded0ee5cafc7c6ab\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.2.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-05-19T11:31:59.052934761+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 0795bc137a50c13634a01a605692f8badab67587\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.3.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-06-02T12:13:25.607507998+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: aa0f9439de1914a0db518c528c8d86ae4b787038\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.4.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-06-09T15:48:54.116663751+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 0c9b3e3487b315004e629f154878b32cbb59bb7a\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.4.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-06-13T17:23:20.695755309+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 6b665a2ba1726cdcc1788790fc943e76ff3643af\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.4.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-07-03T16:07:23.90898467+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 97b69a5ae50ca071ee8da43804e7079f4d75db6b\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-07-14T10:44:47.801127594+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: abc46bbf7bb9bb9d77a330aef5b6fa5c36945ff9\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-07-25T17:12:19.742003396+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 69cfdd85d7952ea79a1ddfc8739d2b6972364d65\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-08-11T10:01:42.042216669+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 59617b97987c2bb32c5901bb18d7e328a3b4de8d\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-08-11T12:41:17.609971129+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 0ffe41c2100a8185779869c8d2ed6b7bc5fb6ed9\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.5/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-08-15T16:44:16.532049143+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 07a3f5f506df6b8073b783b4f796364e899d58d6\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.6/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-08-23T16:22:59.177512612+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 6cf2b3f66c9fda8a1bea046c89102d60e703e96d\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.7/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-08-29T14:55:49.199052191+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 36748e73ff74434d67d375dc0a900a2908c5e15d\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.5.8/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-09-26T12:46:58.342194181+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 5c73bd46f3bc7398ae4e1fa5f7f84925fa89cf07\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-12-11T13:34:42.435602+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2a5171baddf76abc3f8524a9c07983f9a1489bed\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-12-22T11:55:14.216554578+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: efbcfa132f45fcd3db2f594c1fddf14b874377d3\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2017-12-22T14:11:05.755387789+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 0fdfad35800eb4ad3f19e186b59401add9893e2e\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: !!timestamp 2018-04-06T11:10:26.43896691+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: cc211a759943f3c7cbe5d086255360581efe35ec\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks,\n  also checks for gradlew file.\n\n  For Xamarin projects checks the solution files and lists the configuration options,\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects checks for config.xml file.\n\n  For Fastlane detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-05-23T17:47:53.827363814+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: f869820461c6e70a61e19d3a56f67581a4f95942\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.5/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-08-24T13:11:10.315206308Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 374e9a70be8f552ba966bf70be76d97a5e342df3\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.6/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-08-31T14:16:09.180163362Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 90d894214dec0623eaabb3e55177a00acd958cfe\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.7/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-11-29T16:22:35.743070324Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 96e328f42a1d0b7f47e14382e1cb220e3523dc6e\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.6.8/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-11-30T10:18:35.524907835Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: e01384c4c25a5a5c6b41eca09242469f67eb17f8\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.7.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-12-20T15:11:49.830330598Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 3486711d5a933ba3f99aa40130e4e3c96b24a0fa\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.7.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2018-12-21T14:07:49.540630147Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 59995b3a8e6c08cedbc0084a4e02efe9673d6015\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.7.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-01-21T16:19:38.269020695Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 57fa37a1277c2cc8086786a0159d579edeebca92\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.7.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-02-01T12:10:52.770226766Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 1a965818f93d750079ea995cc351093d30c0f405\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.8.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-03-11T09:57:06.838368812Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 1843d759240081ec115f1f07b5ba7e9cf5af68a5\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/1.9.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-04-18T14:51:10.247972202Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: eee06b41970b2f52582842437467327771d29bc0\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    is_required: true\n    title: Directory to save scan results.\n  output_dir: $BITRISE_SOURCE_DIR/scan_result\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/project-scanner/3.0.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-05-15T12:28:50.984512575Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 225d6a5e9f7887c9aa9d1d095df44cc31d1604a5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.1.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-05-16T07:46:18.756025672Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ee0273852348dabd331feee59d2cb36c1521f1ba\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.1.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-06-12T10:39:25.524676648Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: bc1abe883bc313c5174ebcb9b84cf97d7a3b91f2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.10.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-02-12T10:18:29.579183631Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: bbdf41fe7821748aeb4819890cd32197f9f6a058\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.11.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-02-17T15:10:01.162217477Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: cb942d9031d7a46104175cec60bff494614709d2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.12.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-05-19T07:42:26.11365727Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 473a206ddf75c06702ee6447528a5d09db6d58e8\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.13.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-07-26T13:45:51.657353838Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 8d9504f13a2966080d6381e643b6beb66b3cc25d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.14.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-08-25T11:52:29.858574681Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 964b9e5f3d40b861193791761976d1f25f89fba6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.15.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-09-13T14:56:30.956472122Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2a928c9b15d13279c5289e4ac137c82299335724\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.16.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-09-14T14:58:44.914674871Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: e05cfcac54350177c00ed4d8566e898c9e1df681\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.17.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-10-27T14:36:22.466302902Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 101d47181402563f414ef7eac3f36b7dde70a066\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.18.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-12-06T11:36:25.349638562Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 40dfdc544360cf8baae6754b76b4598764821ba4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.19.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-01-26T18:00:45.641231909Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 20a7b2b1bbd07d826ecbdc83628d63c1f299aeb3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.2.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-06-19T08:30:01.202150663Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 20c29c66b1224e9aaed43df46d31c71f937cc7d8\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.20.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-02T15:11:42.910841071Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: b68e0ca4325db3638c072cdf79d484ab324fa991\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.21.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-08T09:24:42.417315781Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 157c0cbef562827dcd4c79debb4b19e4655944f1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.22.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-09T10:13:56.393903362Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: d47fb2cef9cb6ca999f33928155aefdfbcc95ef6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.23.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-14T10:00:13.093308294Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 31f9ff4cdbc1ad3fcda3e6fc710fd6ad9b8da037\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.24.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-14T16:33:33.383073402Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 500be26cd18468bb4eaa3c5644d60a5efaa2b435\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.25.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-16T10:58:28.567937863Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 99aabe4d70092af1c9c431e8374fc3835f962d21\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.26.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-02-25T11:53:28.628348706Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 35b2e9c281785ca8cedb76f3cba07e4f9ccb0df4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.26.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Ionic projects, the step checks for the ionic.config.json and ionic.project files.\n\n  For React Native projects, the step checks for package.json files and also runs the\n  iOS and Android native project scanners.\n\n  For Flutter projects, the step checks for the pubspec.yaml files.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2022-03-04T11:14:35.013491433Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ab2c7e9f92fa12e640af797e355f9a5f5c95335f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.26.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: \"This Step scans your repository to determine your project's type.\\n\\nThe\n  Step scans for:\\n\\n* **iOS** and **macOS** projects, the Step detects `CocoaPods`\n  and scans Xcode project files for valid Xcode command line configurations.\\n* **Android**\n  projects, the Step checks for `build.gradle` files and lists all the Gradle tasks.\n  It also checks for a `gradlew` file.\\n* **Fastlane**, the Step detects `Fastfile`\n  and lists the available lanes.\\n* **Cordova** projects, the Step checks for the\n  `config.xml` file.\\n* **Ionic** projects, the Step checks for the `ionic.config.json`\n  and `ionic.project` files.\\n* **React Native** projects, the Step checks for `package.json`\n  files and also runs the **iOS** and **Android** native project scanners.\\n* **Flutter**\n  projects, the Step checks for the `pubspec.yaml` files.\\n\\n### Configuring the Step\\n\n  \\nTo successfully run the Step, you need: \\n1. An SSH key\\n1. A repository\\n\\nTo\n  configure the Step:\\n\\n1. **POST url to send the scan results to**: You can send\n  your app's scan results to an URL as a POST request.\\n1. **URL to get app icon candidates\n  upload URLs**: You can upload your app's icons using this input. \\n1. **Verbose\n  log option**: You can set this input to `yes` to produce more informative logs.\\n1.\n  **Activate SSH key and clone git repo inside the Step**: You can set this input\n  to `true` to activate an SSH key and clone the git repository of your app.\\n\\n###\n  Troubleshooting\\n\\nIf you receive an error message, `No known platform detected`,\n  make sure that you cloned the correct repository and you have a valid SSH key.\\n\\n###\n  Useful links\\n\\n* [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\"\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-01-05T13:35:41.939690952Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 9ca2b402ca54c9b4352c56123a6051a8ba26bcbf\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.26.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: \"This Step scans your repository to determine your project's type.\\n\\nThe\n  Step scans for:\\n\\n* **iOS** and **macOS** projects, the Step detects `CocoaPods`\n  and scans Xcode project files for valid Xcode command line configurations.\\n* **Android**\n  projects, the Step checks for `build.gradle` files and lists all the Gradle tasks.\n  It also checks for a `gradlew` file.\\n* **Fastlane**, the Step detects `Fastfile`\n  and lists the available lanes.\\n* **Cordova** projects, the Step checks for the\n  `config.xml` file.\\n* **Ionic** projects, the Step checks for the `ionic.config.json`\n  and `ionic.project` files.\\n* **React Native** projects, the Step checks for `package.json`\n  files and also runs the **iOS** and **Android** native project scanners.\\n* **Flutter**\n  projects, the Step checks for the `pubspec.yaml` files.\\n\\n### Configuring the Step\\n\n  \\nTo successfully run the Step, you need: \\n1. An SSH key\\n1. A repository\\n\\nTo\n  configure the Step:\\n\\n1. **POST url to send the scan results to**: You can send\n  your app's scan results to an URL as a POST request.\\n1. **URL to get app icon candidates\n  upload URLs**: You can upload your app's icons using this input. \\n1. **Verbose\n  log option**: You can set this input to `yes` to produce more informative logs.\\n1.\n  **Activate SSH key and clone git repo inside the Step**: You can set this input\n  to `true` to activate an SSH key and clone the git repository of your app.\\n\\n###\n  Troubleshooting\\n\\nIf you receive an error message, `No known platform detected`,\n  make sure that you cloned the correct repository and you have a valid SSH key.\\n\\n###\n  Useful links\\n\\n* [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\"\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-02-20T16:15:03.732860948Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 340672580d01924b9889dcec0373240a24531655\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.26.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: \"This Step scans your repository to determine your project's type.\\n\\nThe\n  Step scans for:\\n\\n* **iOS** and **macOS** projects, the Step detects `CocoaPods`\n  and scans Xcode project files for valid Xcode command line configurations.\\n* **Android**\n  projects, the Step checks for `build.gradle` files and lists all the Gradle tasks.\n  It also checks for a `gradlew` file.\\n* **Fastlane**, the Step detects `Fastfile`\n  and lists the available lanes.\\n* **Cordova** projects, the Step checks for the\n  `config.xml` file.\\n* **Ionic** projects, the Step checks for the `ionic.config.json`\n  and `ionic.project` files.\\n* **React Native** projects, the Step checks for `package.json`\n  files and also runs the **iOS** and **Android** native project scanners.\\n* **Flutter**\n  projects, the Step checks for the `pubspec.yaml` files.\\n\\n### Configuring the Step\\n\n  \\nTo successfully run the Step, you need: \\n1. An SSH key\\n1. A repository\\n\\nTo\n  configure the Step:\\n\\n1. **POST url to send the scan results to**: You can send\n  your app's scan results to an URL as a POST request.\\n1. **URL to get app icon candidates\n  upload URLs**: You can upload your app's icons using this input. \\n1. **Verbose\n  log option**: You can set this input to `yes` to produce more informative logs.\\n1.\n  **Activate SSH key and clone git repo inside the Step**: You can set this input\n  to `true` to activate an SSH key and clone the git repository of your app.\\n\\n###\n  Troubleshooting\\n\\nIf you receive an error message, `No known platform detected`,\n  make sure that you cloned the correct repository and you have a valid SSH key.\\n\\n###\n  Useful links\\n\\n* [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\"\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-03-21T15:32:32.839957371Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 54b756875897d4ccd0c706c42bf1e5e986628bd1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.27.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: \"This Step scans your repository to determine your project's type.\\n\\nThe\n  Step scans for:\\n\\n* **iOS** and **macOS** projects, the Step detects `CocoaPods`\n  and scans Xcode project files for valid Xcode command line configurations.\\n* **Android**\n  projects, the Step checks for `build.gradle` files and lists all the Gradle tasks.\n  It also checks for a `gradlew` file.\\n* **Fastlane**, the Step detects `Fastfile`\n  and lists the available lanes.\\n* **Cordova** projects, the Step checks for the\n  `config.xml` file.\\n* **Ionic** projects, the Step checks for the `ionic.config.json`\n  and `ionic.project` files.\\n* **React Native** projects, the Step checks for `package.json`\n  files and also runs the **iOS** and **Android** native project scanners.\\n* **Flutter**\n  projects, the Step checks for the `pubspec.yaml` files.\\n\\n### Configuring the Step\\n\n  \\nTo successfully run the Step, you need: \\n1. An SSH key\\n1. A repository\\n\\nTo\n  configure the Step:\\n\\n1. **POST url to send the scan results to**: You can send\n  your app's scan results to an URL as a POST request.\\n1. **URL to get app icon candidates\n  upload URLs**: You can upload your app's icons using this input. \\n1. **Verbose\n  log option**: You can set this input to `yes` to produce more informative logs.\\n1.\n  **Activate SSH key and clone git repo inside the Step**: You can set this input\n  to `true` to activate an SSH key and clone the git repository of your app.\\n\\n###\n  Troubleshooting\\n\\nIf you receive an error message, `No known platform detected`,\n  make sure that you cloned the correct repository and you have a valid SSH key.\\n\\n###\n  Useful links\\n\\n* [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\"\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-05-09T08:48:11.148929371Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 587a1a564128a10253ab364bc7f38a752675a918\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.28.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: \"This Step scans your repository to determine your project's type.\\n\\nThe\n  Step scans for:\\n\\n* **iOS** and **macOS** projects, the Step detects `CocoaPods`\n  and scans Xcode project files for valid Xcode command line configurations.\\n* **Android**\n  projects, the Step checks for `build.gradle` files and lists all the Gradle tasks.\n  It also checks for a `gradlew` file.\\n* **Fastlane**, the Step detects `Fastfile`\n  and lists the available lanes.\\n* **Cordova** projects, the Step checks for the\n  `config.xml` file.\\n* **Ionic** projects, the Step checks for the `ionic.config.json`\n  and `ionic.project` files.\\n* **React Native** projects, the Step checks for `package.json`\n  files and also runs the **iOS** and **Android** native project scanners.\\n* **Flutter**\n  projects, the Step checks for the `pubspec.yaml` files.\\n\\n### Configuring the Step\\n\n  \\nTo successfully run the Step, you need: \\n1. An SSH key\\n1. A repository\\n\\nTo\n  configure the Step:\\n\\n1. **POST url to send the scan results to**: You can send\n  your app's scan results to an URL as a POST request.\\n1. **URL to get app icon candidates\n  upload URLs**: You can upload your app's icons using this input. \\n1. **Verbose\n  log option**: You can set this input to `yes` to produce more informative logs.\\n1.\n  **Activate SSH key and clone git repo inside the Step**: You can set this input\n  to `true` to activate an SSH key and clone the git repository of your app.\\n\\n###\n  Troubleshooting\\n\\nIf you receive an error message, `No known platform detected`,\n  make sure that you cloned the correct repository and you have a valid SSH key.\\n\\n###\n  Useful links\\n\\n* [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\"\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-06-06T08:25:44.218130616Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2fb10611acb46e545c099876c35d93633cf20361\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.29.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: \"This Step scans your repository to determine your project's type.\\n\\nThe\n  Step scans for:\\n\\n* **iOS** and **macOS** projects, the Step detects `CocoaPods`\n  and scans Xcode project files for valid Xcode command line configurations.\\n* **Android**\n  projects, the Step checks for `build.gradle` files and lists all the Gradle tasks.\n  It also checks for a `gradlew` file.\\n* **Fastlane**, the Step detects `Fastfile`\n  and lists the available lanes.\\n* **Cordova** projects, the Step checks for the\n  `config.xml` file.\\n* **Ionic** projects, the Step checks for the `ionic.config.json`\n  and `ionic.project` files.\\n* **React Native** projects, the Step checks for `package.json`\n  files and also runs the **iOS** and **Android** native project scanners.\\n* **Flutter**\n  projects, the Step checks for the `pubspec.yaml` files.\\n\\n### Configuring the Step\\n\n  \\nTo successfully run the Step, you need: \\n1. An SSH key\\n1. A repository\\n\\nTo\n  configure the Step:\\n\\n1. **POST url to send the scan results to**: You can send\n  your app's scan results to an URL as a POST request.\\n1. **URL to get app icon candidates\n  upload URLs**: You can upload your app's icons using this input. \\n1. **Verbose\n  log option**: You can set this input to `yes` to produce more informative logs.\\n1.\n  **Activate SSH key and clone git repo inside the Step**: You can set this input\n  to `true` to activate an SSH key and clone the git repository of your app.\\n\\n###\n  Troubleshooting\\n\\nIf you receive an error message, `No known platform detected`,\n  make sure that you cloned the correct repository and you have a valid SSH key.\\n\\n###\n  Useful links\\n\\n* [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\"\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-06-15T10:47:35.567489405Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: b84f61e6cfc2c43d5d44353139ed887e9f43e4a6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the ssh key and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.3.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-09-18T07:45:09.496442758Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 88f0d0fa81e2f8bbf6291d96a31cdfc5090ef707\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.3.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2019-11-07T13:24:49.597906158Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: cc8231c5d2ae4cec5a644cd4ea4cf93b2a891781\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.3.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-04-22T07:59:21.84263649Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2117dc9fe5c2e75a01cc230f95c56d637ec10ed0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.3.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-09-17T07:47:52.904031896Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 861276573163ee59a799fb3b30bd0b16c89093bf\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n"
  },
  {
    "path": "steps/project-scanner/3.30.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-06-19T12:57:46.385439103Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 80f841dca92c485b8a14166f1459773a4d4742f2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.30.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-06-19T14:03:03.956141754Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ea76c5bf2fece437440524e5e691e7a662b935c1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.31.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-10T07:28:37.533555334Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 5c227e1e3a18b8fee85bd521944ada79ce5aec4e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.32.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-14T09:25:56.299486326Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 8d7892e455698542747cad03ed8a844b7002486a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.33.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-14T13:31:11.574264309Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 3fae977ea65ebc04f5987e08930896a4540e3bd3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.34.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-14T14:49:39.571674515Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: a49da015bc65fa8dbc3d20d4af34340c8e8c11c6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.35.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-26T13:27:55.431483771Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 95b6c839ad42d94d951bb447d8cbfa10e3d58663\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.35.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-27T14:12:17.041617139Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 4fd3d646e2e72c73f30b5200b589b7dac2ff616c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.35.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-27T14:41:29.381961475Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 3f9f8cc2508155c7756cba41a8f769dc2e7f3309\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.35.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-28T10:12:36.423492475Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: cb07443a346b4ff9b30b7f2dcaaf40bf2f22d9ff\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.36.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-07-31T12:35:13.47439576Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 5297a463c3c8b4c312758100d17069e5319a1e2e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: 'Unique Identifier (slug) of the Bitrise app '\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.37.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-08-28T09:39:45.438510533Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 378c104418db97d8cc04ed1422b09d139f686ee7\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: 'Unique Identifier (slug) of the Bitrise app '\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.38.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-08-28T11:06:01.667727986Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 62443267859d03b58c332d5aad01b5ae6598f3f4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: 'Unique Identifier (slug) of the Bitrise app '\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.39.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-08-30T10:06:47.331209908Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: bc972648226c35afc749f450d0a1a2f9c3bd4ad9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: 'Unique Identifier (slug) of the Bitrise app '\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.4.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-10-12T12:41:07.954914425Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: a602d80da2c2af93c61455593d15f3fdcd1d37cb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.5.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-10-26T09:48:04.66457096Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 96be1850be07bb666c75e8e15c3567de1e8308a5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.6.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-11-10T11:07:26.180300407Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 1f446467d1ae710466699a061b616f48e6fd5b98\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.6.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-11-12T13:05:28.972267338Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2937b86c56e050b85e4fce9a510003d7340ed124\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.6.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-11-13T09:50:49.866547009Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 168c9dedee17df67ffa31287e8f40de716416ceb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.6.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-11-17T15:03:50.320250992Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 2aa5bdcf6d27adc8c306e885fb97b6247577c660\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.6.5/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-11-18T16:57:50.104964008Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: fa79eb6ba41f5ea593e52359a9042a0453b3b837\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.6.6/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-11-26T13:19:54.737466609Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 72d0286270385156db29fc72a6bb062b5bb67013\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.7.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2020-12-14T14:22:35.219349734Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 6a71a5161ae6026d644cb1af6b60e52202eb2a97\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.8.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-01-04T14:48:37.412140648Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 02da26363b828e6c024a4ce055b407aee3b764bd\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/3.9.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Xamarin, Fastlane and Cordova projects\ndescription: |-\n  For iOS and macOS projects, the step detects CocoaPods and scans Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects, the step checks for build.gradle files and lists all the gradle tasks. It\n  also checks for gradlew file.\n\n  For Xamarin projects, the step checks the solution files and lists the configuration options. It\n  also checks for NuGet and Xamarin Components packages.\n\n  For Cordova projects, the step checks for the config.xml file.\n\n  For Fastlane, the step detects Fastfile and lists the available lanes.\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2021-01-08T14:52:30.788293079Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 280849137549da0a2e031defac696421ee913431\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"true\"\n- enable_repo_clone: \"no\"\n  opts:\n    title: Activate SSH key and clone git repo inside the step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- opts:\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.0.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-09-01T10:58:30.7128893Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 8ebfb6cb5eee7668ed091256b9f0756521d0e7d6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: 'Unique Identifier (slug) of the Bitrise app '\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.0.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2023-10-30T10:01:43.951499412Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 9a995e42f9b5a5960cadde801d331602ba5ef6d9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: 'Unique Identifier (slug) of the Bitrise app '\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.0.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-01-24T12:48:49.763300187Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ee91c395a4053fd4cbc0eae39c5f2c0ea37f9e24\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.1.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-04-01T13:31:05.696317023Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 8bc2240647fc3fda66e467cfff3906724d041a11\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.10.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2026-04-27T08:05:43.298231705Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 9317ca1a7dbbc45a84ab01f458575e3e346b6beb\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/project-scanner/4.10.0/bin/project-scanner-darwin-amd64\n    hash: sha256-cb7794e35543ef000293b1858ffac6eb68470f1db017dbdbdf89a027417c8daa\n  darwin-arm64:\n    storage_uri: steps/project-scanner/4.10.0/bin/project-scanner-darwin-arm64\n    hash: sha256-e3a7b286fb3e3c781c788db0698b6db2cb0a778c2948d52c7b878ba893caa79d\n  linux-amd64:\n    storage_uri: steps/project-scanner/4.10.0/bin/project-scanner-linux-amd64\n    hash: sha256-fbc64074d0e8fdfbf6cac28ef30cae68d401c001e039e7f4a7cd00b4dceb6713\n  linux-arm64:\n    storage_uri: steps/project-scanner/4.10.0/bin/project-scanner-linux-arm64\n    hash: sha256-70a0addb62280c9cee04e1bc326a8b5904b778b5aa1f71cb8ad2fe3540b3e64a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS username\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS password\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Unique Identifier (slug) of the Bitrise app\n    is_dont_change_value: true\n    title: Bitrise app slug\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.2.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-04-02T09:59:08.237857244Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 99e2fa85595e6ef0f63978433165acf05a1fa187\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.3.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-04-10T08:43:04.360996513Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: c695584aa98ca92b540f3c2aa890783449afd38d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.4.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-04-11T08:55:41.482278353Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: fe2e45895903ee0b70c12ded19146fb4887cd2d5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.4.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-04-25T15:23:01.711150621Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: bc040febf0f3cbdd7523922e38b83a5e162ace01\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.5.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-05-13T09:06:00.335694786Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: fcc1347d05883697405de9c5fbd92708090f6a5b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.6.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-05-20T13:43:17.274914528Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 74f1c3d0dae7765967156d3325f64fd451dea899\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.6.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-07-09T14:13:53.644856665Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: b90ac7424b12ed560d005a9b541f868b39ffa3da\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.6.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-08-25T13:27:56.482735189Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: f1f482eb885966fa131da6b865b94166f775ef26\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.7.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-09-08T08:08:27.300693973Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: ad12abcbeeb252ac7df31c917a195ceaddce5b01\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.7.1/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2025-09-09T11:58:19.569283657Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 555de2aea15b8d3b77e3a78e88b108f938f4af7b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key in RSA format\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Username for establishing an HTTP(S) connection to the repository\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Used for analytics purposes\n    is_dont_change_value: true\n    title: Unique Identifier (slug) of the Bitrise app\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.7.2/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2026-02-02T10:00:04.919655825Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: d84e997e9e9c98349df4e8912e150d4674a5938f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS username\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS password\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Unique Identifier (slug) of the Bitrise app\n    is_dont_change_value: true\n    title: Bitrise app slug\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.7.3/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2026-02-19T08:13:53.863332823Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 3077a29bf48b71f82d8eec93e3bc84d4c3c353b9\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/project-scanner/4.7.3/bin/project-scanner-darwin-amd64\n    hash: sha256-f34aa0b3033de205b4c0462b2ae5d4299151e755c27d54abaf3de6a813d0cacf\n  darwin-arm64:\n    storage_uri: steps/project-scanner/4.7.3/bin/project-scanner-darwin-arm64\n    hash: sha256-95797ee3b628b663b9c46cf0cc90e004beeb59f0396857be9c9155b3ed976efc\n  linux-amd64:\n    storage_uri: steps/project-scanner/4.7.3/bin/project-scanner-linux-amd64\n    hash: sha256-89f3caaadf1c2bbf85494f90472079790aa0bcff9fbc54ad711f0d85cba80ea3\n  linux-arm64:\n    storage_uri: steps/project-scanner/4.7.3/bin/project-scanner-linux-arm64\n    hash: sha256-8d64289fcd7fcc80c6d6b15d9a5e9b71b1ec548e7c61244e56dfff60b494ecab\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS username\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS password\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Unique Identifier (slug) of the Bitrise app\n    is_dont_change_value: true\n    title: Bitrise app slug\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.7.4/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2026-02-19T14:46:11.729487408Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: 624bb6f11755ef69336187fc212a369219cf6bd9\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/project-scanner/4.7.4/bin/project-scanner-darwin-amd64\n    hash: sha256-955ebb34f4b707c34b86f437918526ad6f1762c5d580adc7c3f42b67ccf6e575\n  darwin-arm64:\n    storage_uri: steps/project-scanner/4.7.4/bin/project-scanner-darwin-arm64\n    hash: sha256-eceb55f886c8b089a64cf47ab69c105f92786f49fb6b5d00c33143229ee7d7db\n  linux-amd64:\n    storage_uri: steps/project-scanner/4.7.4/bin/project-scanner-linux-amd64\n    hash: sha256-d48d7ee247689d1feb242165ef1d9c7ce246cd9f594a9a730c2e77d337596534\n  linux-arm64:\n    storage_uri: steps/project-scanner/4.7.4/bin/project-scanner-linux-arm64\n    hash: sha256-59dc5cb22d5774944cd34bc4af6e163ef025c6a5416c025a04b3548f50884dfb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS username\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS password\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Unique Identifier (slug) of the Bitrise app\n    is_dont_change_value: true\n    title: Bitrise app slug\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.8.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2026-03-25T12:07:39.941884693Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: a112f084eb4a13f4213c613d7bedb9f26c960441\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/project-scanner/4.8.0/bin/project-scanner-darwin-amd64\n    hash: sha256-861d5e73891abe28eec44660ebf853821f93df5f46f0cc0c000c5472e03ed80a\n  darwin-arm64:\n    storage_uri: steps/project-scanner/4.8.0/bin/project-scanner-darwin-arm64\n    hash: sha256-ca51c5287ae6c9325f401ed89cf36ebaf27b091884be880d31227f5613ad4b63\n  linux-amd64:\n    storage_uri: steps/project-scanner/4.8.0/bin/project-scanner-linux-amd64\n    hash: sha256-597912fc78982caa05ff8030b76bbe0d8f31a135a4e8dbc7a683d5f436216ff6\n  linux-arm64:\n    storage_uri: steps/project-scanner/4.8.0/bin/project-scanner-linux-arm64\n    hash: sha256-edbd90bc04dd96bb583cea09f7e3d696f7e07616eed0ff4eed3bee5cb4946612\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS username\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS password\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Unique Identifier (slug) of the Bitrise app\n    is_dont_change_value: true\n    title: Bitrise app slug\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/4.9.0/step.yml",
    "content": "title: Project scanner\nsummary: Scans repository for iOS, macOS, Android, Fastlane, Cordova, Ionic, React\n  Native and Flutter projects\ndescription: |-\n  This Step scans your repository to determine your project's type.\n\n  The Step scans for:\n\n  * **iOS** and **macOS** projects, the Step detects `CocoaPods` and scans Xcode project files for valid Xcode command line configurations.\n  * **Android** projects, the Step checks for `build.gradle` files and lists all the Gradle tasks. It also checks for a `gradlew` file.\n  * **Fastlane**, the Step detects `Fastfile` and lists the available lanes.\n  * **Cordova** projects, the Step checks for the `config.xml` file.\n  * **Ionic** projects, the Step checks for the `ionic.config.json` and `ionic.project` files.\n  * **React Native** projects, the Step checks for `package.json` files and also runs the **iOS** and **Android** native project scanners.\n  * **Flutter** projects, the Step checks for the `pubspec.yaml` files.\n\n  ### Configuring the Step\n\n  To successfully run the Step, you need:\n  1. An SSH key\n  1. A repository\n\n  To configure the Step:\n\n  1. **POST url to send the scan results to**: You can send your app's scan results to an URL as a POST request.\n  1. **URL to get app icon candidates upload URLs**: You can upload your app's icons using this input.\n  1. **Verbose log option**: You can set this input to `yes` to produce more informative logs.\n  1. **Activate SSH key and clone git repo inside the Step**: You can set this input to `true` to activate an SSH key and clone the git repository of your app.\n\n  ### Troubleshooting\n\n  If you receive an error message, `No known platform detected`, make sure that you cloned the correct repository and you have a valid SSH key.\n\n  ### Useful links\n\n  * [Creating your own project scanner](https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/creating-your-own-bitrise-project-scanner.html)\nwebsite: https://github.com/bitrise-steplib/steps-project-scanner\nsource_code_url: https://github.com/bitrise-steplib/steps-project-scanner\nsupport_url: https://github.com/bitrise-steplib/steps-project-scanner/issues\npublished_at: 2026-04-20T08:15:49.208237491Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-project-scanner.git\n  commit: a16f163b4b0a542bd7524faecca8a066510a2243\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/project-scanner/4.9.0/bin/project-scanner-darwin-amd64\n    hash: sha256-62c13fd666ead9124f374dee81b6b1bf82eca214d2ef158bc61e0dc9e8a6caf7\n  darwin-arm64:\n    storage_uri: steps/project-scanner/4.9.0/bin/project-scanner-darwin-arm64\n    hash: sha256-7ef44806f5271e8a79d042b3ca7a7f0d07c41123f56ac8d4d1077c5b25dbd45f\n  linux-amd64:\n    storage_uri: steps/project-scanner/4.9.0/bin/project-scanner-linux-amd64\n    hash: sha256-9b07a632c92a45ec4d8307c4191b2679a28bcf2e713d10e06510b0cd9065f77a\n  linux-arm64:\n    storage_uri: steps/project-scanner/4.9.0/bin/project-scanner-linux-arm64\n    hash: sha256-9ba7a701cbee894559e579daa0be698020d8574102b567eb3f38b4bed61f6177\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-project-scanner\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Step will look for the projects in this directory.\n    is_required: true\n    title: Directory to scan.\n  scan_dir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_sensitive: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n- icon_candidates_url: $BITRISE_AVATAR_CANDIDATES_POST_URL\n  opts:\n    description: |\n      If provided, the app icons will be uploaded.\n    title: URL to get app icon candidates upload URLs\n- opts:\n    description: |\n      You can enable the verbose log for easier debugging.\n    title: Verbose log option\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- enable_repo_clone: \"no\"\n  opts:\n    description: |\n      If set to yes then it will setup the SSH key (or HTTP credentials) and will clone the repo with the provided url and branch name.\n    title: Activate SSH key and clone git repo inside the Step\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: SSH key to be used for the git clone.\n    is_dont_change_value: true\n    is_expand: true\n    is_sensitive: true\n    title: SSH private key\n  ssh_rsa_private_key: $SSH_RSA_PRIVATE_KEY\n- git_http_username: $GIT_HTTP_USERNAME\n  opts:\n    description: Username for establishing an HTTP(S) connection to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS username\n- git_http_password: $GIT_HTTP_PASSWORD\n  opts:\n    description: Personal access token (or password) for establishing an HTTP(S) connection\n      to the repository\n    is_dont_change_value: true\n    is_sensitive: true\n    title: Git HTTPS password\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    description: Unique Identifier (slug) of the Bitrise app\n    is_dont_change_value: true\n    title: Bitrise app slug\n- opts:\n    description: Url to be used for the git clone.\n    is_dont_change_value: true\n    title: Git repository URL\n  repository_url: $GIT_REPOSITORY_URL\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    category: Clone Config\n    description: Branch to be used for the git clone.\n    is_dont_change_value: true\n    title: Git Branch to clone\n"
  },
  {
    "path": "steps/project-scanner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.0.0/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2022-08-05T15:29:36.43542+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 3e0c17185389111b8323f2b9a2d47eb94ffc086b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths, used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions.\n      The default value (`.*`) means: get every artifact from every Workflow.\n\n      Do not forget to escape the special characters.\n      If you want to match all workflow from a stage then you need to escape the `.` separator and the use the `.*` any characters regex like `{stage-name}\\..*`.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths, used to\n      specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.0.1/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2022-11-25T10:59:18.649300423Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: ae4dbc8f52b2d2b0305e26adb5415559b3ebc6d2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths, used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions.\n      The default value (`.*`) means: get every artifact from every Workflow.\n\n      Do not forget to escape the special characters.\n      If you want to match all workflow from a stage then you need to escape the `.` separator and the use the `.*` any characters regex like `{stage-name}\\..*`.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths, used to\n      specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.0.2/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2023-02-16T09:40:49.374659357Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 80a1467ce4da55e9d309691eb5fa26cf317cfa85\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.0.3/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2023-03-22T09:23:35.177983318Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 3c7991000ec70f8f20177906fe918dcb76476ba6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.0.4/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2023-04-25T08:17:15.329725048Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 5fe16222879e5b741e8804a7d82f364c0c817ea1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.0.5/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2023-06-26T13:09:18.359635888Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 22c66cdb248c6acb31fb71022a4d3af862a262c9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.1.0/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2023-12-19T14:12:24.143956565Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: cf0bc8d0c21d24a9d96df591fbca97e88d37a882\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.1.1/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2024-08-01T09:19:52.736156194Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 76e04701ce01c0c1406eacec667fe90a45a36c2e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished stages for which the step\n      can download build artifacts.\n    title: The finished stages for which artifacts are available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.2.0/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2024-08-21T07:59:32.501867642Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 14968cf471de83abde1ec294c53a05c1480617c1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download build artifacts.\n    title: The finished staged pipeline stages for which artifacts are available to\n      download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download build artifacts.\n    title: The finished graph pipeline workflows for which artifacts are available\n      to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.2.1/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2024-09-16T08:25:01.922021221Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 5a4b03e28c557cee4ca292c38b8ce97cdd0d7db7\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`), used to specify which workflows' artifacts to download.\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      You can use regular expressions. Do not forget to escape the special characters.\n\n      Examples:\n      - `stage1.workflow1` - Gets the artifacts from the stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from the stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1s' artifacts from the previous stages.\n      - `.*` - Gets every generated artifacts from the previous stages.\n    is_required: true\n    summary: A comma (`,`) separated list of the Stage and Workflow paths (`{stage}.{workflow}`),\n      used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download build artifacts.\n    title: The finished staged pipeline stages for which artifacts are available to\n      download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download build artifacts.\n    title: The finished graph pipeline workflows for which artifacts are available\n      to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.2.2/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2025-03-10T14:03:59.898288943Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: c3ae0503a8a85f03d6629127b6275831ee61ca05\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which workflows' artifacts to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets artifacts from the 'build' workflow.\n      - `build,test` - Gets artifacts from both the 'build' and 'test' workflows.\n      - `test.*` - Gets every generated artifact from all previous workflows with names starting with 'test'.\n      - `.*` - Gets every generated artifact from all previous workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets artifacts from stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's artifacts from all previous stages.\n      - `.*` - Gets every generated artifact from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download build artifacts.\n    title: The finished staged pipeline stages for which artifacts are available to\n      download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download build artifacts.\n    title: The finished graph pipeline workflows for which artifacts are available\n      to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.3.0/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are build artifacts generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between pipeline stages** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between pipeline stages** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading an artifact, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all artifacts generated by any workflow of the pipeline are downloaded.\n  This can be limited by setting the *Artifact source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which workflows' artifacts to download in the **Artifact source** input. By default, all workflows artifacts will be downloaded.\n\n    NOTE: You can list multiple artifacts by separating them using a comma. For example: `{stage1}.{workflow1},{stage2}.{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2025-05-23T12:14:31.101288001Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 6768d4ea2ab7fb3cb35618a9188cffe342bf9d57\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which workflows' artifacts to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets artifacts from the 'build' workflow.\n      - `build,test` - Gets artifacts from both the 'build' and 'test' workflows.\n      - `test.*` - Gets every generated artifact from all previous workflows with names starting with 'test'.\n      - `.*` - Gets every generated artifact from all previous workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets artifacts from stage1's workflow1.\n      - `stage1\\..*` - Gets all artifacts from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's artifacts from all previous stages.\n      - `.*` - Gets every generated artifact from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which workflows' artifacts to download.\n    title: Artifact source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download build artifacts.\n    title: The finished staged pipeline stages for which artifacts are available to\n      download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download build artifacts.\n    title: The finished graph pipeline workflows for which artifacts are available\n      to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.3.1/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between Pipeline Workflows** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading a file, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all files shared by any Workflow of the Pipeline are downloaded.\n  This can be limited by setting the *Intermediate file source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which Workflows' intermediate files to download in the **Intermediate file source** input. By default, all Workflows intermediate files will be downloaded.\n\n    NOTE: You can list multiple Workflows by separating them using a comma. For example: `{workflow1},{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2025-05-30T07:18:44.053338092Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: f061dca45f42fbbc018589bcc3fe15b1a518ee76\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which Workflows' files to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the Workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets intermediate files from the 'build' Workflow.\n      - `build,test` - Gets intermediate files from both the 'build' and 'test' Workflows.\n      - `test.*` - Gets every intermediate files from all previous Workflows with names starting with 'test'.\n      - `.*` - Gets every intermediate files from all previous Workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets intermediate files from stage1's workflow1.\n      - `stage1\\..*` - Gets all intermediate files from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's intermediate files from all previous stages.\n      - `.*` - Gets every intermediate files from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which Workflows' files to download.\n    title: Intermediate file source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download intermediate files.\n    title: The finished staged pipeline stages for which intermediate files are available\n      to download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download intermediate files.\n    title: The finished graph pipeline workflows for which intermediate files are\n      available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.3.2/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between Pipeline Workflows** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading a file, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all files shared by any Workflow of the Pipeline are downloaded.\n  This can be limited by setting the *Intermediate file source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which Workflows' intermediate files to download in the **Intermediate file source** input. By default, all Workflows intermediate files will be downloaded.\n\n    NOTE: You can list multiple Workflows by separating them using a comma. For example: `{workflow1},{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2025-06-17T07:27:09.826450464Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: fb58df26c40d32fe97a501ef9628c34ce6c67e76\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which Workflows' files to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the Workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets intermediate files from the 'build' Workflow.\n      - `build,test` - Gets intermediate files from both the 'build' and 'test' Workflows.\n      - `test.*` - Gets every intermediate files from all previous Workflows with names starting with 'test'.\n      - `.*` - Gets every intermediate files from all previous Workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets intermediate files from stage1's workflow1.\n      - `stage1\\..*` - Gets all intermediate files from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's intermediate files from all previous stages.\n      - `.*` - Gets every intermediate files from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which Workflows' files to download.\n    title: Intermediate file source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download intermediate files.\n    title: The finished staged pipeline stages for which intermediate files are available\n      to download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download intermediate files.\n    title: The finished graph pipeline workflows for which intermediate files are\n      available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.3.3/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between Pipeline Workflows** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading a file, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all files shared by any Workflow of the Pipeline are downloaded.\n  This can be limited by setting the *Intermediate file source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which Workflows' intermediate files to download in the **Intermediate file source** input. By default, all Workflows intermediate files will be downloaded.\n\n    NOTE: You can list multiple Workflows by separating them using a comma. For example: `{workflow1},{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2025-06-20T08:08:12.033284058Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: a7b6ed3443c5c6c85e90b7bed53173116fb0da8a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which Workflows' files to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the Workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets intermediate files from the 'build' Workflow.\n      - `build,test` - Gets intermediate files from both the 'build' and 'test' Workflows.\n      - `test.*` - Gets every intermediate files from all previous Workflows with names starting with 'test'.\n      - `.*` - Gets every intermediate files from all previous Workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets intermediate files from stage1's workflow1.\n      - `stage1\\..*` - Gets all intermediate files from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's intermediate files from all previous stages.\n      - `.*` - Gets every intermediate files from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which Workflows' files to download.\n    title: Intermediate file source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download intermediate files.\n    title: The finished staged pipeline stages for which intermediate files are available\n      to download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download intermediate files.\n    title: The finished graph pipeline workflows for which intermediate files are\n      available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.3.4/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between Pipeline Workflows** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading a file, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all files shared by any Workflow of the Pipeline are downloaded.\n  This can be limited by setting the *Intermediate file source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which Workflows' intermediate files to download in the **Intermediate file source** input. By default, all Workflows intermediate files will be downloaded.\n\n    NOTE: You can list multiple Workflows by separating them using a comma. For example: `{workflow1},{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2025-06-24T09:33:29.262534736Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: bc4de7e560f7d7f6e4ec55599a8f7d40de4baf65\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which Workflows' files to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the Workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets intermediate files from the 'build' Workflow.\n      - `build,test` - Gets intermediate files from both the 'build' and 'test' Workflows.\n      - `test.*` - Gets every intermediate files from all previous Workflows with names starting with 'test'.\n      - `.*` - Gets every intermediate files from all previous Workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets intermediate files from stage1's workflow1.\n      - `stage1\\..*` - Gets all intermediate files from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's intermediate files from all previous stages.\n      - `.*` - Gets every intermediate files from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which Workflows' files to download.\n    title: Intermediate file source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download intermediate files.\n    title: The finished staged pipeline stages for which intermediate files are available\n      to download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download intermediate files.\n    title: The finished graph pipeline workflows for which intermediate files are\n      available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/1.3.5/step.yml",
    "content": "title: Pull Pipeline intermediate files\nsummary: The Step downloads Pipeline intermediate files to a local folder.\ndescription: |-\n  The Step downloads Pipeline intermediate files to a local folder.\n  These intermediate files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.\n\n  Make sure to add this Step after you have uploaded the intermediate files.\n  You can upload the intermediate files using the [Deploy to Bitrise.io Step](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)'s **Files to share between Pipeline Workflows** input.\n  The directories you specify will be archived and uploaded as a single file.\n\n  When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the **Files to share between Pipeline Workflows** input.\n  After downloading the files, the environment variable key will point to the file's local path.\n\n  When downloading a file, that was a directory originally, they are extracted,\n  and the specified environment variable will point to the directory's local path.\n\n  By default, all files shared by any Workflow of the Pipeline are downloaded.\n  This can be limited by setting the *Intermediate file source* input.\n\n  Please note that this step is designed to be executed on the CI only.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Specify which Workflows' intermediate files to download in the **Intermediate file source** input. By default, all Workflows intermediate files will be downloaded.\n\n    NOTE: You can list multiple Workflows by separating them using a comma. For example: `{workflow1},{workflow2}`\n\n  2. (Optional) Set the **Enable verbose logging** input to `true` if you want to log additional information for debugging purposes.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files/issues\npublished_at: 2026-04-01T09:33:32.011691777Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-pull-intermediate-files.git\n  commit: 604aeecd8b31bb094b67932d912f154199da8489\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/pull-intermediate-files/1.3.5/bin/pull-intermediate-files-darwin-amd64\n    hash: sha256-165ddd79ffbf495ac707ce226bebb41ce59dc4136ba8d3a11dc7180f943df2fe\n  darwin-arm64:\n    storage_uri: steps/pull-intermediate-files/1.3.5/bin/pull-intermediate-files-darwin-arm64\n    hash: sha256-f9922b6f00646b1bb7e6d0b54a66255539ff3462acec073deefe77a9754cc737\n  linux-amd64:\n    storage_uri: steps/pull-intermediate-files/1.3.5/bin/pull-intermediate-files-linux-amd64\n    hash: sha256-8e93e715a8c8d9c7700e6f476a7262f252500b5ac5f1f8ff7c8756a85e511197\n  linux-arm64:\n    storage_uri: steps/pull-intermediate-files/1.3.5/bin/pull-intermediate-files-linux-arm64\n    hash: sha256-e41d569fde872d42a112beb8ce5f33e945a2eedad2b7e889d99e9e24e1bdc57d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-pull-intermediate-files\nrun_if: .IsCI\ninputs:\n- artifact_sources: .*\n  opts:\n    description: |-\n      A comma (`,`) separated list of Workflow names or Stage and Workflow paths, used to specify which Workflows' files to download.\n\n      **Graph Pipelines:**\n\n      Simply specify the Workflow name directly. For example, `build` or `test`.\n\n      Examples:\n      - `build` - Gets intermediate files from the 'build' Workflow.\n      - `build,test` - Gets intermediate files from both the 'build' and 'test' Workflows.\n      - `test.*` - Gets every intermediate files from all previous Workflows with names starting with 'test'.\n      - `.*` - Gets every intermediate files from all previous Workflows.\n\n      **Staged Pipelines:**\n\n      The input uses a `{stage}.{workflow}` syntax.\n      The dot character (`.`) is the delimiter between the Stage and the Workflow.\n\n      Examples:\n      - `stage1.workflow1` - Gets intermediate files from stage1's workflow1.\n      - `stage1\\..*` - Gets all intermediate files from stage1's workflows.\n      - `.*\\.workflow1` - Gets workflow1's intermediate files from all previous stages.\n      - `.*` - Gets every intermediate files from all previous stages.\n\n      You can use regular expressions for both pipeline types. Remember to escape special characters.\n    is_required: true\n    summary: A comma (`,`) separated list of Workflow names or Stage and Workflow\n      paths, used to specify which Workflows' files to download.\n    title: Intermediate file source\n- opts:\n    is_required: true\n    summary: Enable logging additional information for debugging\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The slug that uniquely identifies your app on bitrise.io. It’s part of\n      the app URL, too.\n    title: Bitrise App Slug\n- finished_stage: $BITRISEIO_FINISHED_STAGES\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished staged pipeline stages\n      for which the step can download intermediate files.\n    title: The finished staged pipeline stages for which intermediate files are available\n      to download\n- finished_workflows: $BITRISEIO_FINISHED_WORKFLOWS\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: This is a JSON representation of the finished graph pipeline workflows\n      for which the step can download intermediate files.\n    title: The finished graph pipeline workflows for which intermediate files are\n      available to download\n- bitrise_api_base_url: https://api.bitrise.io\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The base URL of the Bitrise API used to process the download requests.\n    title: Bitrise API base URL\n- bitrise_api_access_token: $BITRISEIO_ARTIFACT_PULL_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: false\n    is_sensitive: true\n    summary: The OAuth access token that authorizes to call the Bitrise API.\n    title: Access token to call the Bitrise API\n"
  },
  {
    "path": "steps/pull-intermediate-files/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/push-notification-with-parse/2.0.0/step.yml",
    "content": "title: Send Push Notification with Parse\nsummary: |-\n  When an email or an IM isn't enough you can send a push notification,\n  now even from your workflow!\ndescription: |-\n  Send a push notification with [Parse](https://parse.com/).\n\n  To use their service you have to register first.\n  It is possible to register a trial account for free.\n\n  You can get the required keys and IDs from your parse app's page,\n  similar to this: [https://www.parse.com/apps/your-parse-apps-name/edit#app_keys](https://www.parse.com/apps/your-parse-apps-name/edit#app_keys)\n\n  You have to install your own Push Receiver app to receive the push notifications - you can find a\n  template app here: [https://github.com/bitrise-io/example-parse-notification-center-ios-app](https://github.com/bitrise-io/example-parse-notification-center-ios-app)\nwebsite: https://github.com/bitrise-io/steps-push-notification-with-parse\nsource_code_url: https://github.com/bitrise-io/steps-push-notification-with-parse\nsupport_url: https://github.com/bitrise-io/steps-push-notification-with-parse/issues\npublished_at: 2015-09-08T21:24:49.75929616+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-push-notification-with-parse.git\n  commit: cfef29fe361ea2020ac2338196aac11c07e26685\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_id: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Parse App ID\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Parse REST API Key\n  rest_key: \"\"\n- message: Automatic build with Bitrise.\n  opts:\n    description: |\n      The text of the push message.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Message\n"
  },
  {
    "path": "steps/push-notification-with-parse/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, Push Notifications are no longer supported by Parse server.\nmaintainer: bitrise\nremoval_date: 2019-02-29\n"
  },
  {
    "path": "steps/random-quote/3.0.0/step.yml",
    "content": "title: Random Quote\nsummary: |-\n  Got no idea how to spice up your every day build notifications? How about a\n  random quote to pass the time while your app is being installed on your device?\ndescription: |\n  Prints a random quote and saves it into the $quote environment variable (adds it to the ~/.bash_profile)\n  Uses the http://www.iheartquotes.com API\nwebsite: https://github.com/bitrise-io/steps-random-quote\nsource_code_url: https://github.com/bitrise-io/steps-random-quote\nsupport_url: https://github.com/bitrise-io/steps-random-quote/issues\npublished_at: 2015-09-08T14:56:23.493268529+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-random-quote.git\n  commit: f875ec1b94069aae97713710018b5f8693c9a6bf\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndependencies:\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\noutputs:\n- RANDOM_QUOTE: null\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: the quote\n"
  },
  {
    "path": "steps/random-quote/3.0.2/step.yml",
    "content": "title: Random Quote\nsummary: |-\n  Got no idea how to spice up your every day build notifications? How about a\n  random quote to pass the time while your app is being installed on your device?\ndescription: |-\n  Prints a random quote and saves it into the $quote environment variable (adds it to the ~/.bash_profile)\n  Uses the http://www.iheartquotes.com API\nwebsite: https://github.com/bitrise-io/steps-random-quote\nsource_code_url: https://github.com/bitrise-io/steps-random-quote\nsupport_url: https://github.com/bitrise-io/steps-random-quote/issues\npublished_at: 2016-08-01T12:28:57.683951092+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-random-quote.git\n  commit: f6c08c7883f78b848f499b6478d2deba22c1e634\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\noutputs:\n- RANDOM_QUOTE: null\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: the quote\n"
  },
  {
    "path": "steps/random-quote/3.0.3/step.yml",
    "content": "title: Random Quote\nsummary: |-\n  Got no idea how to spice up your every day build notifications? How about a\n  random quote to pass the time while your app is being installed on your device?\ndescription: |-\n  Prints a random quote and saves it into the $quote environment variable (adds it to the ~/.bash_profile)\n  Uses the http://www.iheartquotes.com API\nwebsite: https://github.com/bitrise-io/steps-random-quote\nsource_code_url: https://github.com/bitrise-io/steps-random-quote\nsupport_url: https://github.com/bitrise-io/steps-random-quote/issues\npublished_at: 2018-05-08T12:41:11.221348039+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-random-quote.git\n  commit: fb8949254189d11476daab846ea2dd5eca148f00\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\noutputs:\n- RANDOM_QUOTE: null\n  opts:\n    description: \"\"\n    is_dont_change_value: true\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: the quote\n"
  },
  {
    "path": "steps/random-quote/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/raygun/1.0.0/step.yml",
    "content": "title: Raygun dSYM Upload\nsummary: Upload your dSym to Raygun\ndescription: Upload your dSYM to Xamarin.Insights\nwebsite: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload\nsource_code_url: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload\nsupport_url: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload/issues\npublished_at: 2016-12-20T10:13:01.863060192-08:00\nsource:\n  git: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload.git\n  commit: 5a08676e33e9ff004b854503dd9a5326f5c94440\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- ios\n- mac\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      This is a Base64 encode of your username:password, you can run the following command in the terminal - 'echo -n 'username:password | openssl base64' to get it\n    is_expand: true\n    is_required: true\n    title: API Key for Raygun. This is a Base64 encode of your username:password.\n  raygun_api_key: null\n- app_id: null\n  opts:\n    description: |\n      App ID from the Raygun portal\n    is_expand: true\n    is_required: true\n    title: Raygun App ID\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      Path to your dSYM file\n    is_expand: true\n    is_required: true\n    title: Path to your dSYM file\n"
  },
  {
    "path": "steps/raygun/1.0.1/step.yml",
    "content": "title: Raygun dSYM Upload\nsummary: Upload your dSym to Raygun\ndescription: Upload your dSYM to Raygun\nwebsite: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload\nsource_code_url: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload\nsupport_url: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload/issues\npublished_at: 2016-12-20T10:28:44.995871095-08:00\nsource:\n  git: https://github.com/jamesmontemagno/bitrise-step-raygun-dsym-upload.git\n  commit: ba76c47b82475207c6db3e21354ecdfc3115ff5b\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      This is a Base64 encode of your username:password, you can run the following command in the terminal - 'echo -n 'username:password | openssl base64' to get it\n    is_expand: true\n    is_required: true\n    title: API Key for Raygun. This is a Base64 encode of your username:password.\n  raygun_api_key: null\n- app_id: null\n  opts:\n    description: |\n      App ID from the Raygun portal\n    is_expand: true\n    is_required: true\n    title: Raygun App ID\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      Path to your dSYM file\n    is_expand: true\n    is_required: true\n    title: Path to your dSYM file\n"
  },
  {
    "path": "steps/raygun/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/react-native-bundle/0.1.0/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2016-03-09T13:33:12.704985935+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: b29fe9c100fb7e1c999e2aefdb98adfee2afa518\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- dev: \"false\"\n  opts:\n    description: Set DEV flag.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- minify: \"false\"\n  opts:\n    description: Minify js bundle.\n    title: Minification\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Add another root(s) to be used in bundling in this project.\n    title: Root\n  root: null\n- assetRoots: null\n  opts:\n    description: Specify the root directories of app assets.\n    title: Asset root directories\n- opts:\n    description: Specify the output file.\n    title: Output file\n  out: null\n- opts:\n    description: Specify the bundle file URL.\n    title: Bundle file URL\n  url: null\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n"
  },
  {
    "path": "steps/react-native-bundle/0.1.2/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2016-06-23T15:00:52.948800075+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: ab4e9a80019c0771d113254e81be7721a9144793\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- dev: \"false\"\n  opts:\n    description: Set DEV flag.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- minify: \"false\"\n  opts:\n    description: Minify js bundle.\n    title: Minification\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Add another root(s) to be used in bundling in this project.\n    title: Root\n  root: null\n- assetRoots: null\n  opts:\n    description: Specify the root directories of app assets.\n    title: Asset root directories\n- entry_file: null\n  opts:\n    description: Specify the entry file.\n    title: Entry file\n- opts:\n    description: Specify the output file.\n    title: Output file\n  out: null\n- opts:\n    description: Specify the bundle file URL.\n    title: Bundle file URL\n  url: null\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n"
  },
  {
    "path": "steps/react-native-bundle/0.2.0/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2016-08-19T18:18:11.643057143+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: 5ef970c6d5943be2ba914d415f42c3c8d00ec5a0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- dev: \"false\"\n  opts:\n    description: Set DEV flag.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Add another root(s) to be used in bundling in this project.\n    title: Root\n  root: null\n- assetRoots: null\n  opts:\n    description: Specify the root directories of app assets.\n    title: Asset root directories\n- entry_file: null\n  opts:\n    description: Specify the entry file.\n    title: Entry file\n- opts:\n    description: Specify the output file.\n    title: Output file\n  out: null\n- opts:\n    description: Specify the bundle file URL.\n    title: Bundle file URL\n  url: null\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n"
  },
  {
    "path": "steps/react-native-bundle/1.0.0/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2016-09-01T12:23:49.302852378+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: ffea1ec2fd1538125df6e6496758d99d93bb0dc3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- dev: \"false\"\n  opts:\n    description: Set DEV flag.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: Add another root(s) to be used in bundling in this project.\n    title: Root\n  root: null\n- assetRoots: null\n  opts:\n    description: Specify the root directories of app assets.\n    title: Asset root directories\n- entry_file: null\n  opts:\n    description: Specify the entry file.\n    title: Entry file\n- opts:\n    description: Specify the output file.\n    title: Output file\n  out: null\n- opts:\n    description: Specify the bundle file URL.\n    title: Bundle file URL\n  url: null\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n"
  },
  {
    "path": "steps/react-native-bundle/1.0.1/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2016-09-06T17:38:53.458023404+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: daf62caa1af4086d84f7385ccc73fa156b07fa96\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/1.0.2/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2016-12-16T12:32:11.172371206+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: c369fc3c2c63ca4efae691c01c8dd24f37aab73d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- android\n- ios\ntype_tags:\n- react-native\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/1.0.3/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2017-03-09T14:35:52.944966162+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: f0b45084906ae9ae5686030c252826bc7b4bd70e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/1.0.4/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2019-10-11T08:54:39.688481978Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: 72af82bbea9d1690eb96bd2b09f9d418f3845653\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- android\n- ios\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: node\ninputs:\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/1.1.0/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2021-10-15T13:11:03.669410761Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: fd26b71612bef5cb6c8a7227e7af12c834e05f56\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- android\n- ios\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: node\ninputs:\n- binary_path: null\n  opts:\n    description: |-\n      Location of a custom `react-native` binary, either absolute or relative. The path should not contain the `react-native` part itself.\n      Useful when configuring distinct package managers, installing globally,\n      or in a relative path like `./node_modules/.bin`\n    summary: Location of a custom React Native binary to use\n    title: Custom React Native binary location\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/1.1.1/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2022-10-12T14:08:58.327928821Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: c45edae93793ca69b9be8c800f414ead00237c1e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- android\n- ios\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: node\ninputs:\n- binary_path: null\n  opts:\n    description: |-\n      Location of a custom `react-native` binary, either absolute or relative. The path should not contain the `react-native` part itself.\n      Useful when configuring distinct package managers, installing globally,\n      or in a relative path like `./node_modules/.bin`\n    summary: Location of a custom React Native binary to use\n    title: Custom React Native binary location\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/1.2.0/step.yml",
    "content": "title: React Native bundle\nsummary: Bundles your React Native app.\ndescription: Bundles your React Native app.\nwebsite: https://github.com/bitrise-steplib/steps-react-native-bundle\nsource_code_url: https://github.com/bitrise-steplib/steps-react-native-bundle\nsupport_url: https://github.com/bitrise-steplib/steps-react-native-bundle/issues\npublished_at: 2022-12-09T15:01:30.675867421Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-react-native-bundle.git\n  commit: 7d2c6458ac45f58fdf1b49b82c6aa7c640c0b499\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\n- android\n- ios\ntype_tags:\n- build\ndeps:\n  brew:\n  - name: node\ninputs:\n- binary_path: null\n  opts:\n    description: |-\n      Location of a custom `react-native` binary, either absolute or relative. The path should not contain the `react-native` part itself.\n      Useful when configuring distinct package managers, installing globally,\n      or in a relative path like `./node_modules/.bin`\n    summary: Location of a custom React Native binary to use\n    title: Custom React Native binary location\n- opts:\n    description: Specify either `ios`, or `android` as platform for the bundler.\n    is_required: true\n    title: Bundle platform\n    value_options:\n    - ios\n    - android\n  platform: ios\n- entry_file: index.${platform}.js\n  opts:\n    description: Path to the root JS file, either absolute or relative to JS root.\n    is_required: true\n    title: Entry file\n- opts:\n    description: File name where to store the resulting bundle, ex. /tmp/groups.bundle.\n    title: Bundle output\n  out: ${platform}/main.jsbundle\n- dev: \"true\"\n  opts:\n    description: If false, warnings are disabled and the bundle is minified.\n    title: DEV flag\n    value_options:\n    - \"true\"\n    - \"false\"\n- assetRoots: null\n  opts:\n    description: Directory name where to store assets referenced in the bundle.\n    title: Assets Destination\n- options: null\n  opts:\n    description: |-\n      Options are added to `react-native bundle`. You can use multiple options, separated\n      by a space character.\n    title: Additional options for running `react-native bundle`\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Specify the bundle file URL.\n    title: '[DEPRECATED] Bundle file URL'\n  url: null\n- opts:\n    description: |-\n      __DEPRECATED__, removed from react-native tool.\n\n      Add another root(s) to be used in bundling in this project.\n    title: '[DEPRECATED] Root'\n  root: null\n"
  },
  {
    "path": "steps/react-native-bundle/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/recreate-user-schemes/0.9.0/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2016-07-27T17:38:19.025276826+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: 6ee2c5cc0c5978ddfbad10ea0edfb2fa1774994a\nproject_type_tags:\n- ios\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/0.9.1/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2016-07-29T16:40:40.395368804+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: 02717b3f6e1795b4724ef4e4c2a21b13b2e6a0f7\nproject_type_tags:\n- ios\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/0.9.2/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2016-09-06T17:27:28.112223278+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: ca5ce8b3e38fe7d9a07bf829e033557cc64b950d\nproject_type_tags:\n- ios\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/0.9.4/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2016-09-08T14:59:38.434401509+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: 6a13d691f3553708aa0eb6d4b0d7cef7a2d14611\nproject_type_tags:\n- ios\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/0.9.5/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2016-12-19T17:20:02.207748267+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: e7eec070db7dfaede5a1afa365bf1f10eb2a4cde\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ndeps: {}\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.0.0/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2017-05-18T14:42:35.130294652+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: b768695bf7c9b084ec483d28080a77d636abe49b\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.0.1/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2017-05-22T13:42:56.279467652+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: 75ff408523e01a985a4b87f55cd5127654b84120\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.0.2/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2017-08-23T15:11:48.661155169+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: d8e2313fa84a075d0c13c6c93ff852797c8c1cf9\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.0.3/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: \"This step recreates default user schemes.\\n\\nIf no shared schemes exist\n  in the project/workspace, step will recreate default user schemes, \\njust like Xcode\n  does. \"\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2021-07-09T08:13:54.308501049Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: a19a15650646af1920889652b92b2a6b4bd9f9c0\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj/.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project or Workspace path\n  project_path: null\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.0.4/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: |-\n  This step recreates default user schemes.\n\n  If no shared schemes exist in the project/workspace, step will recreate default user schemes, just like Xcode does.\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2022-02-24T09:29:09.704296584Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: 350385055739472ba3f8dd6b2fdd6aef2e5c3746\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: A `.xcodeproj/.xcworkspace` path.\n    title: Project or Workspace path\n  project_path: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.0.5/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: |-\n  This step recreates default user schemes.\n\n  If no shared schemes exist in the project/workspace, step will recreate default user schemes, just like Xcode does.\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2022-02-28T10:50:23.080361602Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: 6b4e088ada9762b6d561d3dbec2f2ee43c61fb88\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: A `.xcodeproj/.xcworkspace` path.\n    title: Project or Workspace path\n  project_path: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.1.0/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: |-\n  This step recreates default user schemes.\n\n  If no shared schemes exist in the project/workspace, step will recreate default user schemes, just like Xcode does.\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2023-08-28T14:53:33.810664005Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: a6b39a64d8a170a8e65c854fd0b3c061f887c21a\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: A `.xcodeproj/.xcworkspace` path.\n    title: Project or Workspace path\n  project_path: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/recreate-user-schemes/1.1.1/step.yml",
    "content": "title: Recreate User Schemes\nsummary: Recreate User Schemes\ndescription: |-\n  This step recreates default user schemes.\n\n  If no shared schemes exist in the project/workspace, step will recreate default user schemes, just like Xcode does.\nwebsite: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsource_code_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes\nsupport_url: https://github.com/bitrise-steplib/steps-recreate-user-schemes/issues\npublished_at: 2025-11-12T13:13:20.15365296Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-recreate-user-schemes.git\n  commit: b85848c9aa61e79d5193bbcfcc666a4319131492\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recreate-user-schemes\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: A `.xcodeproj/.xcworkspace` path.\n    title: Project or Workspace path\n  project_path: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/recreate-user-schemes/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/recursive-touch/0.9.0/step.yml",
    "content": "title: Recursive touch for Cache\nsummary: Touches all the files in a directory\ndescription: |-\n  Touches all the files in a directory so you can keep your project's file statuses between builds.\n  Put this step before any `xcodebuild` related step that uses `build`, `test` or `build-for-testing` commands, so `DerivedData` cache can work properly.\nwebsite: https://github.com/bitrise-steplib/steps-recursive-touch\nsource_code_url: https://github.com/bitrise-steplib/steps-recursive-touch\nsupport_url: https://github.com/bitrise-steplib/steps-recursive-touch/issues\npublished_at: 2017-09-15T13:51:17.308572911+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-recursive-touch.git\n  commit: b0640bb209410393a9c24816f811db313d930f94\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-recursive-touch\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- directory_path: $BITRISE_SOURCE_DIR\n  opts:\n    description: |\n      The path pointing to a directory where the files will be touched.\n    is_expand: true\n    is_required: true\n    summary: The path pointing to a directory.\n    title: Path\n- opts:\n    description: |\n      The time in RFC3339 format that will be set on the files.\n\n      For example: `2017-09-08T14:50:17+02:00`\n    is_expand: true\n    is_required: false\n    summary: |\n      The time in RFC3339 format that will be set on the files.\n\n      For example: `2017-09-08T14:50:17+02:00`\n    title: Touch Time\n  touch_time: 2017-09-01T15:00:00+00:00\n"
  },
  {
    "path": "steps/recursive-touch/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated as it is not reliable in daily development.\nmaintainer: bitrise\nremoval_date: \"2019-12-14\"\n"
  },
  {
    "path": "steps/release-notes-extractor/0.0.1/step.yml",
    "content": "title: Release notes extractor\nsummary: |\n  Easily extract release notes for your project's changelog\ndescription: |\n  With this step you can easily extract the last entry of your project's changelog to be used as release notes!\nwebsite: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step\nsource_code_url: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step\nsupport_url: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step/issues\npublished_at: 2019-12-04T12:17:58.423355307+02:00\nsource:\n  git: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step.git\n  commit: e7d2ab07462035b6a45e63a1d16c7a153c84f51a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- changelog_file_path: CHANGELOG.md\n  opts:\n    description: |\n      - If it's in your project directory, just type the file's name.\n      - If it's in a relative path to your project directory, type that relative file path.\n      CHANGELOG.md format is expected to match the standards here keepachangelog.com.\n    is_required: true\n    summary: The path of your changelog file\n    title: Changelog file path\n- opts:\n    description: |\n      - If set to 'Yes', the output will be trimmed of all '###' prefixes before change types.\n      - If set to 'No', the output will remain exactly as in the changelog.\n    is_required: true\n    summary: Decides whether to keep the output release notes trimmed or not\n    title: Trim markdown output\n    value_options:\n    - \"Yes\"\n    - \"No\"\n  trim_markdown_output: \"Yes\"\noutputs:\n- RELEASE_NOTES: null\n  opts:\n    description: |\n      This output will contain the string value of the release notes keeping it's format\n      as found in the Changelog just stripping the hashes before change categories.\n    summary: The string value of the extracted release notes\n    title: Release notes\n"
  },
  {
    "path": "steps/release-notes-extractor/0.1.0/step.yml",
    "content": "title: Release notes extractor\nsummary: |\n  Easily extract release notes for your project's changelog\ndescription: |\n  With this step you can easily extract the last entry of your project's changelog to be used as release notes!\nwebsite: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step\nsource_code_url: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step\nsupport_url: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step/issues\npublished_at: 2019-12-20T15:07:44.738594792+02:00\nsource:\n  git: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step.git\n  commit: 34a864c0608728d84afe47d272dcf39e8bfd8052\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- changelog_file_path: CHANGELOG.md\n  opts:\n    description: |\n      - If it's in your project directory, just type the file's name.\n      - If it's in a relative path to your project directory, type that relative file path.\n      CHANGELOG.md format is expected to match the standards here keepachangelog.com.\n    is_required: true\n    summary: The path of your changelog file\n    title: Changelog file path\n- opts:\n    description: |\n      - If set to 'Yes', the output will be trimmed of all '###' prefixes before change types.\n      - If set to 'No', the output will remain exactly as in the changelog.\n    is_required: true\n    summary: Decides whether to keep the output release notes trimmed or not\n    title: Trim markdown output\n    value_options:\n    - \"Yes\"\n    - \"No\"\n  trim_markdown_output: \"Yes\"\noutputs:\n- EXTRACTED_RELEASE_NOTES: null\n  opts:\n    description: |\n      This output will contain the string value of the release notes as found in the Changelog entry.\n    summary: The string value of the extracted release notes\n    title: Release notes\n- EXTRACTED_VERSION_NAME: null\n  opts:\n    description: |\n      This output will contain the version name as found in the Changelog entry.\n    summary: The string value of the extracted version name\n    title: Version name\n"
  },
  {
    "path": "steps/release-notes-extractor/0.1.1/step.yml",
    "content": "title: Release notes extractor\nsummary: |\n  Easily extract release notes for your project's changelog\ndescription: |\n  With this step you can easily extract the last entry of your project's changelog to be used as release notes!\nwebsite: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step\nsource_code_url: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step\nsupport_url: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step/issues\npublished_at: 2020-01-09T18:01:59.773890497+02:00\nsource:\n  git: https://gitlab.com/areebgroup-open-source/bitrise-release-notes-step.git\n  commit: c0790ecd8e415a1478d1ee80344827b1b3dd5ba8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- changelog_file_path: CHANGELOG.md\n  opts:\n    description: |\n      - If it's in your project directory, just type the file's name.\n      - If it's in a relative path to your project directory, type that relative file path.\n      CHANGELOG.md format is expected to match the standards here keepachangelog.com.\n    is_required: true\n    summary: The path of your changelog file\n    title: Changelog file path\n- opts:\n    description: |\n      - If set to 'Yes', the output will be trimmed of all '###' prefixes before change types.\n      - If set to 'No', the output will remain exactly as in the changelog.\n    is_required: true\n    summary: Decides whether to keep the output release notes trimmed or not\n    title: Trim markdown output\n    value_options:\n    - \"Yes\"\n    - \"No\"\n  trim_markdown_output: \"Yes\"\noutputs:\n- EXTRACTED_RELEASE_NOTES: null\n  opts:\n    description: |\n      This output will contain the string value of the release notes as found in the Changelog entry.\n    summary: The string value of the extracted release notes\n    title: Release notes\n- EXTRACTED_VERSION_NAME: null\n  opts:\n    description: |\n      This output will contain the version name as found in the Changelog entry.\n    summary: The string value of the extracted version name\n    title: Version name\n"
  },
  {
    "path": "steps/release-notes-extractor/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/remote-script-runner/2.0.0/step.yml",
    "content": "title: Remote Bash Script Runner\nsummary: |-\n  Found a great GitHub Gist that you'd like to use during your workflow?\n  Just add the raw URL, Bitrise will download it and run it as a bash script!\ndescription: |-\n  Downloads the content of the input url and runs it as a bash script.\n  For example you can provide a GitHub Gist *raw* url.\nwebsite: https://github.com/bitrise-io/steps-remote-script-runner\nsource_code_url: https://github.com/bitrise-io/steps-remote-script-runner\nsupport_url: https://github.com/bitrise-io/steps-remote-script-runner/issues\npublished_at: 2015-09-08T17:17:35.012335346+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-remote-script-runner.git\n  commit: 64c2c30a37d2ded7a4fbb72f24b515cdff5e87a8\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- script\n- bash\n- runner\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Bash Script URL which returns a *text* response (not an HTML one!)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Script URL\n  script_url: \"\"\n"
  },
  {
    "path": "steps/remote-script-runner/2.0.1/step.yml",
    "content": "title: Remote Bash Script Runner\nsummary: |-\n  Found a great GitHub Gist that you'd like to use during your workflow?\n  Just add the raw URL, Bitrise will download it and run it as a bash script!\ndescription: |-\n  Downloads the content of the input url and runs it as a bash script.\n  For example you can provide a GitHub Gist *raw* url.\nwebsite: https://github.com/bitrise-io/steps-remote-script-runner\nsource_code_url: https://github.com/bitrise-io/steps-remote-script-runner\nsupport_url: https://github.com/bitrise-io/steps-remote-script-runner/issues\npublished_at: 2016-02-29T11:09:25.386525399+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-remote-script-runner.git\n  commit: 9af47356cc73a51160e060ca72ad5a326845d6a8\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Bash Script URL which returns a *text* response (not an HTML one!)\n    is_required: true\n    title: Script URL\n  script_url: \"\"\n"
  },
  {
    "path": "steps/remote-script-runner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/repeato-test-runner/0.0.1/step.yml",
    "content": "title: Repeato Test Runner\nsummary: |\n  Step for executing repeato tests.\ndescription: |\n  You can execute repeato tests before deploying your app build.\nwebsite: https://github.com/repeato-qa/bitrise-repeato-cli-step.git\nsource_code_url: https://github.com/repeato-qa/bitrise-repeato-cli-step.git\nsupport_url: https://github.com/repeato-qa/bitrise-repeato-cli-step/issues\npublished_at: 2022-10-19T02:04:13.435289+05:00\nsource:\n  git: https://github.com/repeato-qa/bitrise-repeato-cli-step.git\n  commit: 57a7c0bf5a8cd933c2a005ede9a5d1172592f57c\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  apt_get:\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    summary: Set the repeato CLI version compatible to your workspace tests.\n    title: Repeato CLI Version\n  repeato_cli_version: latest\n- opts:\n    is_required: true\n    summary: Repeato test runner need workspace path for setting up the workspace\n      before executing batch.\n    title: Workspace Path\n  workspace_path: $BITRISE_SOURCE_DIR\n- batch_id: null\n  opts:\n    is_required: true\n    summary: Provide batch id for the tests execution.\n    title: Repeato Batch ID\n- license_key: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Provide licensse key for the tests execution.\n    title: Repeato License Key\noutputs:\n- REPEATO_REPORT: null\n  opts:\n    summary: Repeato batch report of executed tests.\n    title: Repeato Batch Report Zip File\n- REPEATO_JUNIT_REPORT: null\n  opts:\n    summary: Repeato executed tests report in JUnit XML format.\n    title: Repeato JUnit XML File\n"
  },
  {
    "path": "steps/repeato-test-runner/0.0.2/step.yml",
    "content": "title: Repeato Test Runner\nsummary: |\n  Step for executing repeato tests.\ndescription: |\n  You can execute repeato tests before deploying your app build.\nwebsite: https://github.com/repeato-qa/bitrise-repeato-cli-step.git\nsource_code_url: https://github.com/repeato-qa/bitrise-repeato-cli-step.git\nsupport_url: https://github.com/repeato-qa/bitrise-repeato-cli-step/issues\npublished_at: 2022-11-07T18:43:25.327965+05:00\nsource:\n  git: https://github.com/repeato-qa/bitrise-repeato-cli-step.git\n  commit: ebe9c3fdf9043667c5bc286eaa264034d65a8611\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  apt_get:\n  - name: wget\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    summary: Set the repeato CLI version compatible to your workspace tests.\n    title: Repeato CLI Version\n  repeato_cli_version: latest\n- opts:\n    is_required: true\n    summary: Repeato test runner need workspace path for setting up the workspace\n      before executing batch.\n    title: Workspace Path\n  workspace_path: $BITRISE_SOURCE_DIR\n- batch_id: null\n  opts:\n    is_required: true\n    summary: Provide batch id for the tests execution.\n    title: Repeato Batch ID\n- license_key: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: Provide licensse key for the tests execution.\n    title: Repeato License Key\n- log_level: INFO\n  opts:\n    is_required: true\n    summary: Switch to DEBUG if you have troubles running your batches. This prints\n      a lot of additional information to the log.\n    title: Log Level\n    value_options:\n    - WARN\n    - INFO\n    - DEBUG\noutputs:\n- REPEATO_REPORT: null\n  opts:\n    summary: Repeato batch report of executed tests.\n    title: Repeato Batch Report Zip File\n- REPEATO_JUNIT_REPORT: null\n  opts:\n    summary: Repeato executed tests report in JUnit XML format.\n    title: Repeato JUnit XML File\n"
  },
  {
    "path": "steps/repeato-test-runner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/repository-scanner/1.0.0/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-10-31T13:46:43.174196417Z\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 97a15b57a42a569b3b8c1c5d3bd032f8a9d4ac51\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.1.0/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-11-11T22:02:22.58569242+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: b9a75916a331c3a5eb072ddf034667bc9704bae0\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.1.1/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-11-15T17:55:27.501380056+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 3bbb17935fc4061d2d017e60c08420dd03586d10\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.1.2/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-11-24T16:47:21.601392864+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: f3ebf102faa69ebd6c5572c655829a07282f7721\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.2.0/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-12-15T19:12:46.606476403+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: dee9e42d7e0e56f14027f791af660cdebfef5c29\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.3.0/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-12-17T18:50:30.579290121+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 2fe982fdae2a103e925292b9fb95bac8560a74ad\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.3.1/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2015-12-23T14:20:55.010375316+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 8288d385833b78e29e5edf07630be6c2aa9b2aa9\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.3.2/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2016-02-09T17:10:56.285256145+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: c13747f92692b9b0fb6c08f5a735fd0b244f69cf\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If this parameter is provided then only the specified branch\n      will be scanned, all other branches will be ignored.\n    is_expand: true\n    title: Scan only a single branch\n  scan_only_branch: \"\"\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.4.0/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2016-02-16T16:31:43.987453789+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 2e40a797b3557044b673e2d90a9c963cc9429efc\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.4.1/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2016-02-25T16:57:45.924669179+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 44984942511a4c370b661030b4b6ac1763edd496\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.4.2/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2016-03-09T15:52:13.402410353+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 791a4261ed9cfddfcc8b8b81389738e132d1b2ae\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- xcode\n- cocoapods\n- pod\n- gradle\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/1.4.3/step.yml",
    "content": "title: Repository scanner\nsummary: Scans repository for iOS and Android projects\ndescription: |-\n  For iOS projects detects CocoaPods and scan Xcode project files\n  for valid Xcode command line configurations.\n\n  For Android projects checks for build.gradle files and lists all the gradle tasks\n\n  For Xamarin projects checks the solution files and lists the configuration options\nwebsite: https://github.com/bitrise-io/steps-repository-scanner\nsource_code_url: https://github.com/bitrise-io/steps-repository-scanner\nsupport_url: https://github.com/bitrise-io/steps-repository-scanner/issues\npublished_at: 2016-04-06T12:14:28.392562311+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-repository-scanner.git\n  commit: 3c8be4a4f4e5c967a012808b577aa42ce4eb331a\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- ios\n- android\n- xamarin\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    title: Source Code Directory path.\n  source_root_path: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      If provided, the scan results will be sent to the given\n      URL, with a POST request.\n    is_dont_change_value: true\n    title: POST url to send the scan results to\n  scan_result_submit_url: $BITRISE_SCAN_RESULT_POST_URL\n- opts:\n    description: |\n      If provided and `scan_result_submit_url` also provided,\n      this API Token will be used for sending the Scan Results.\n    is_dont_change_value: true\n    title: API Token for scan result submission\n  scan_result_submit_api_token: $BITRISE_APP_API_TOKEN\n"
  },
  {
    "path": "steps/repository-scanner/step-info.yml",
    "content": "deprecate_notes: This step is deprecated, use [Project scanner](https://github.com/bitrise-steplib/steps-project-scanner)\n  instead.\nmaintainer: bitrise\nremoval_date: \"2019-02-28\"\n"
  },
  {
    "path": "steps/resource-archive/2.0.0/step.yml",
    "content": "title: ZIP resource archive downloader\nsummary: ZIP resource archive downloader\ndescription: Downloads and extracts a .ZIP archive to a specified path.\nwebsite: https://github.com/bitrise-io/steps-resource-archive\nsource_code_url: https://github.com/bitrise-io/steps-resource-archive\nsupport_url: https://github.com/bitrise-io/steps-resource-archive/issues\npublished_at: 2015-09-10T17:03:10.344675485+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-resource-archive.git\n  commit: d3756dd4bc2ed3f057ccc0ad766a4f2e24b7686e\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_url: \"\"\n  opts:\n    description: Path of the resource .ZIP file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Resource path\n- extract_to_path: \"\"\n  opts:\n    description: Resource extract path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Extract path\n"
  },
  {
    "path": "steps/resource-archive/2.0.1/step.yml",
    "content": "title: ZIP resource archive downloader\nsummary: ZIP resource archive downloader\ndescription: Downloads and extracts a .ZIP archive to a specified path.\nwebsite: https://github.com/bitrise-io/steps-resource-archive\nsource_code_url: https://github.com/bitrise-io/steps-resource-archive\nsupport_url: https://github.com/bitrise-io/steps-resource-archive/issues\npublished_at: 2018-02-08T12:17:28.096431524+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-resource-archive.git\n  commit: 899410298363620b2ec8cb823ab56e6af4a4f119\nhost_os_tags:\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_url: \"\"\n  opts:\n    description: Path of the resource .ZIP file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Resource path\n- extract_to_path: \"\"\n  opts:\n    description: Resource extract path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Extract path\n"
  },
  {
    "path": "steps/resource-archive/2.0.3/step.yml",
    "content": "title: ZIP resource archive downloader\nsummary: ZIP resource archive downloader\ndescription: Downloads and extracts a .ZIP archive to a specified path. Please note\n  that the step creates an `unarchived` folder at the specified location. You will\n  find the contents of the .ZIP archive in the `unarchived` folder.\nwebsite: https://github.com/bitrise-io/steps-resource-archive\nsource_code_url: https://github.com/bitrise-io/steps-resource-archive\nsupport_url: https://github.com/bitrise-io/steps-resource-archive/issues\npublished_at: 2021-01-04T13:58:31.354150622Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-resource-archive.git\n  commit: f8af123462cc46ef99f8c7da5c4147893ccf5d5c\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- archive_url: \"\"\n  opts:\n    description: Path of the resource .ZIP file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Resource path. It can be a remote URL too.\n    title: Resource path\n- extract_to_path: \"\"\n  opts:\n    description: Resource extract path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: 'Extract path. Path to your local directory: path/to/dir'\n    title: Extract path\n"
  },
  {
    "path": "steps/resource-archive/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-cache/1.0.0/step.yml",
    "content": "title: Restore Cache (Beta)\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2022-09-14T17:22:32.508867+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: c3857bf1b8283e88e303f02a9e31d4778fd71cbb\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-cache/1.0.1/step.yml",
    "content": "title: Restore Cache (Beta)\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2022-09-22T10:11:48.433209521Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: e3b1aecf6196e7bfa7e489c03c13a5d8a89a24d0\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-cache/1.0.2/step.yml",
    "content": "title: Restore Cache (Beta)\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2022-10-18T13:47:26.765940722Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: a180ecf10e4270b54fb6e14b3561de252a008591\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-cache/1.1.0/step.yml",
    "content": "title: Restore Cache (Beta)\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2023-01-12T10:52:08.44472288Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: e0bac19186908b9a85613e56f804d615c29c62e5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/1.1.1/step.yml",
    "content": "title: Restore Cache (Beta)\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2023-02-10T08:48:13.38935636Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 10ff1b7a6f7769a056d426fc202fb7788e4065b9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/1.1.2/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2023-02-10T13:31:01.321726403Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 3de863a3de3803dadc514d613351fad9cbe65062\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.0.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2023-11-20T22:49:41.110178304Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 890b552fbbcec3ab8805f16729841af984457d36\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.1.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2024-01-08T14:01:13.262070307Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: f6c5a11b8d1991e4a8b5fa4f154acdf0730acad3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.2.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2024-02-05T08:52:20.750191349Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 562583036ec27d8d66e24208e45c434a8462750a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.3.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2024-03-07T16:41:08.267854921Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 4ffe7b02e2b7ccad3634c9b707480d9991d65215\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.4.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2024-03-14T09:41:07.316388307Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 16a2f90a8c52c5810ac8e3175f7be5ff84dd8afa\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.4.1/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2024-05-16T13:54:41.611184439Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 817979e6e85c24d986112982ce71275cd14074f3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.5.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2024-09-03T12:12:18.707601065Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 305ae9278b141740cdf5a4b7ffa60f6fe86e9c21\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/2.6.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2025-09-30T11:22:24.174897314Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: 6e733c8b74a5be25bd86555a67003bf87168984f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/3.0.0/step.yml",
    "content": "title: Restore Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cache/issues\npublished_at: 2026-03-03T12:29:53.98204949Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cache.git\n  commit: de35f32855c9a251243a2e7505d50b662dacd319\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-cache/3.0.0/bin/restore-cache-darwin-amd64\n    hash: sha256-c9fe441e4af1371a7468552cceb035d4b51bdee9614e71295664c24f3c72bd7a\n  darwin-arm64:\n    storage_uri: steps/restore-cache/3.0.0/bin/restore-cache-darwin-arm64\n    hash: sha256-0f6951d1868f09ff750ebf2bf393b8cff3252f79cc95f9387a89375c9376bc37\n  linux-amd64:\n    storage_uri: steps/restore-cache/3.0.0/bin/restore-cache-linux-amd64\n    hash: sha256-f5fa7845c9dde3dc96da21b120abf8bc4ca394607fd5b2593b7644824dd50216\n  linux-arm64:\n    storage_uri: steps/restore-cache/3.0.0/bin/restore-cache-linux-arm64\n    hash: sha256-3e5bbf457bd064ef5279ddb2920599dd28ec61a90971fc4a0d926884de28dc02\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-carthage-cache/1.0.0/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2023-02-10T10:03:24.688459+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 60f64657a0c7a98530b2e7a7f1d8e2c6464fd9bc\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/2.0.0/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2023-11-29T18:05:12.727608966Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 73fd2bf5b8bc5b827915312e81eb3e3debaff280\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/2.1.0/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2024-05-30T13:06:24.471187742Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 6b5af77c173fbb25c1543dda246682fbbeff9e61\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/2.1.1/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2024-09-13T12:04:14.342368868Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 0eddee817eb0efecad322383f74135458301647f\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/2.1.2/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2025-09-30T11:24:32.816904241Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 8fb018d73c694fc01d72f979ec9402f0286e687d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/2.1.3/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2025-11-12T08:29:07.38250167Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 4f7049fe69f95d78ff33fd566df42c760c52da16\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/3.0.0/step.yml",
    "content": "title: Restore Carthage Cache\nsummary: Restores cached Carthage dependencies. This Step needs to be used in combination\n  with **Save Carthage Cache**.\ndescription: |\n  Restores cached Carthage prebuilt frameworks. This Step needs to be used in combination with **Save Carthage Cache**.\n\n  This Step is based on [key-based caching](https://docs.bitrise.io/en/bitrise-ci/dependencies-and-caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Carthage cache](https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/issues\npublished_at: 2026-03-03T14:59:43.143486566Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache.git\n  commit: 8582558f3474fa9ba84fbb2cda83ab07e6173cde\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-carthage-cache/3.0.0/bin/restore-carthage-cache-darwin-amd64\n    hash: sha256-853ef1607ffede6080096a7dec8fb72f2e3b37f02e428ad9337bb173ea312196\n  darwin-arm64:\n    storage_uri: steps/restore-carthage-cache/3.0.0/bin/restore-carthage-cache-darwin-arm64\n    hash: sha256-d7ac73d102b15ad401503a3bc98a81eb4c32cdf2fe96a28b4962a81158c2ae8c\n  linux-amd64:\n    storage_uri: steps/restore-carthage-cache/3.0.0/bin/restore-carthage-cache-linux-amd64\n    hash: sha256-f6ebaabe58a31e6c132d6f46101c7ec91ba80d34c5c23c170a7d673f6b472a2c\n  linux-arm64:\n    storage_uri: steps/restore-carthage-cache/3.0.0/bin/restore-carthage-cache-linux-arm64\n    hash: sha256-1055a7ee65762894888aeb6e497a2595f0f9bef745da42531cd5a8d2d1f7cf61\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-carthage-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-carthage-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/1.0.0/step.yml",
    "content": "title: Restore Cocoapods Cache (Beta)\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2022-11-09T17:40:07.10921+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 2f2707fb18f2b2a4b036f370fd93c3be16d3ca32\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/1.1.0/step.yml",
    "content": "title: Restore Cocoapods Cache (Beta)\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2023-01-12T10:51:19.74849286Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 6ef3eaa4c923bb9469dbb40033cfa63e11df7cff\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/1.1.1/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2023-02-10T08:45:55.6553859Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 770547cd0e0f1ca88d46a1ba15571303cd704271\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/2.0.0/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2023-11-16T17:19:20.123455646Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: fbf1ebfd7aa07188dbf1d28b6ff19f1482015a22\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/2.1.0/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2024-05-30T13:06:11.61899102Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 5f08a210fb274214913007d2ae24a37832798e64\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/2.1.1/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2024-09-13T12:03:56.980190527Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 70a5e311194d5e836b05a36f2971e576059e9936\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/2.1.2/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2025-09-30T11:24:14.570089751Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 5e748b90d6bcd4aac0fecbe8b60f1bd191f5933f\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/2.1.3/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2025-11-10T15:37:49.757447374Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: eed24cbbd248d31796229834f6feb9eb3ac8aae8\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/3.0.0/step.yml",
    "content": "title: Restore Cocoapods Cache\nsummary: Restores cached Cocoapods dependencies. This Step needs to be used in combination\n  with **Save Cocoapods Cache**.\ndescription: |\n  Restores cached Cocoapods dependencies. This Step needs to be used in combination with **Save Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://docs.bitrise.io/en/bitrise-ci/dependencies-and-caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/issues\npublished_at: 2026-03-03T16:10:28.504736504Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache.git\n  commit: 7734436088012fb9972430187a1b863af09fc37c\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-cocoapods-cache/3.0.0/bin/restore-cocoapods-cache-darwin-amd64\n    hash: sha256-26a525155747c20fc843396a0b66dc29084e1ca19a09f5ca49dbed2e2e3196f0\n  darwin-arm64:\n    storage_uri: steps/restore-cocoapods-cache/3.0.0/bin/restore-cocoapods-cache-darwin-arm64\n    hash: sha256-0ce2439b338763802d2050adb0696d7424e463ff857ab02f8c47ff0bf124c46f\n  linux-amd64:\n    storage_uri: steps/restore-cocoapods-cache/3.0.0/bin/restore-cocoapods-cache-linux-amd64\n    hash: sha256-30fdfc26f18ae12f76489aad1defe4bfcb3102adbf728305bd8481f520ff3725\n  linux-arm64:\n    storage_uri: steps/restore-cocoapods-cache/3.0.0/bin/restore-cocoapods-cache-linux-arm64\n    hash: sha256-57ff2c041054941434e3261ff3cbd7c1a00a9618c91ecd22eeb98a55d85a09cd\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-cocoapods-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-dart-cache/1.0.0/step.yml",
    "content": "title: Restore Dart Cache\nsummary: Restores Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Save Dart Cache**.\ndescription: |\n  Restores Dart (Flutter) dependencies. This Step needs to be used in combination with **Save Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Dart cache](https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/issues\npublished_at: 2023-02-10T10:10:31.598659+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache.git\n  commit: 6fa41b4a4723db98e052b25ec26754bf7a541af4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-dart-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-dart-cache/2.0.0/step.yml",
    "content": "title: Restore Dart Cache\nsummary: Restores Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Save Dart Cache**.\ndescription: |\n  Restores Dart (Flutter) dependencies. This Step needs to be used in combination with **Save Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Dart cache](https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/issues\npublished_at: 2023-11-27T00:21:44.119555577Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache.git\n  commit: 5155edb4d91c4d5c07d2bd88e338ef9380d44232\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-dart-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-dart-cache/2.1.0/step.yml",
    "content": "title: Restore Dart Cache\nsummary: Restores Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Save Dart Cache**.\ndescription: |\n  Restores Dart (Flutter) dependencies. This Step needs to be used in combination with **Save Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Dart cache](https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/issues\npublished_at: 2024-05-30T13:05:43.255731604Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache.git\n  commit: 6ce461e9d316112db1240cbc257072cced7f6919\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-dart-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-dart-cache/2.1.1/step.yml",
    "content": "title: Restore Dart Cache\nsummary: Restores Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Save Dart Cache**.\ndescription: |\n  Restores Dart (Flutter) dependencies. This Step needs to be used in combination with **Save Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Dart cache](https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/issues\npublished_at: 2024-09-13T12:03:16.290749304Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache.git\n  commit: bccb97d9843db5ccc489c7dc43208c67bb5e3a57\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-dart-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-dart-cache/2.1.2/step.yml",
    "content": "title: Restore Dart Cache\nsummary: Restores Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Save Dart Cache**.\ndescription: |\n  Restores Dart (Flutter) dependencies. This Step needs to be used in combination with **Save Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Dart cache](https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/issues\npublished_at: 2025-09-30T11:23:51.912823562Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache.git\n  commit: a716f038100bc6a8da7f0b2e05ec68bc6d28302a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-dart-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-dart-cache/3.0.0/step.yml",
    "content": "title: Restore Dart Cache\nsummary: Restores Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Save Dart Cache**.\ndescription: |\n  Restores Dart (Flutter) dependencies. This Step needs to be used in combination with **Save Dart Cache**.\n\n  This Step is based on [key-based caching](https://docs.bitrise.io/en/bitrise-ci/dependencies-and-caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Dart cache](https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/issues\npublished_at: 2026-03-03T16:14:52.179185364Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache.git\n  commit: 9218faccd1f54a1de3ae3f52f365ef5abdc25da2\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-dart-cache/3.0.0/bin/restore-dart-cache-darwin-amd64\n    hash: sha256-9f7a957b68f0a55a7da2d645de46ceaa60c40b18ba872493daf6dc7d36c526e5\n  darwin-arm64:\n    storage_uri: steps/restore-dart-cache/3.0.0/bin/restore-dart-cache-darwin-arm64\n    hash: sha256-c613fdbfec60d0452e67ee8abc445f80ac11dda794a43758a205b103515f13f1\n  linux-amd64:\n    storage_uri: steps/restore-dart-cache/3.0.0/bin/restore-dart-cache-linux-amd64\n    hash: sha256-cfeab9e0fdafc5794d4335a55ccf1a0382e69c1540523f0f307f66e76b8b9923\n  linux-arm64:\n    storage_uri: steps/restore-dart-cache/3.0.0/bin/restore-dart-cache-linux-arm64\n    hash: sha256-66a548ee8b26c618aaf54a14f115cf639f3f583dd378ffc551206a7936c7e4d5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-dart-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-dart-cache/step-info.yml",
    "content": "maintainer: bitrise\n\n"
  },
  {
    "path": "steps/restore-gradle-cache/1.0.0/step.yml",
    "content": "title: Restore Gradle Cache (Beta)\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle caches (dependencies and optionally build cache). This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2022-11-09T15:18:32.465473+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: b0a78d9a8ad6094b5118826a107498ae73543bdb\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-cache/1.1.0/step.yml",
    "content": "title: Restore Gradle Cache (Beta)\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle caches (dependencies and optionally build cache). This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2023-01-12T10:41:11.697279496Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 6772a96397ff5ec5b22f5025dc0e3bbd46bb8210\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/1.1.1/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle caches (dependencies and optionally build cache). This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2023-02-10T08:46:09.723011699Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: fd9ae1631400b4debd2a98ce93fe12c8e84f1661\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/1.1.2/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2023-07-13T07:34:10.769452951Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 550efcf5b6a9272accfa657a4ca6cb3e3be403b2\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/2.0.0/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2023-11-27T00:27:57.007568781Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 557800f7bc23e8017054c5fb0e7cbaf03f70188d\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/2.1.0/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2024-02-05T09:44:58.81323665Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 716e8478529101f136d68e6dddee49c46a8e5889\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/2.2.0/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2024-05-30T13:06:48.826084194Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 828da510370eb19ce3d06796612ca7552ca5879d\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/2.2.1/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2024-09-17T08:31:18.072405117Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 4bfb9654170d71672dc3d9d04678af0407e0c15f\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/2.2.3/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2025-09-30T13:12:38.681257286Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 6936bbca6dffbfa8c2e6abeee2235e639efd0eee\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/2.2.4/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2025-11-11T08:11:25.116006877Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: ff1eb5df0889253e47a00b673b6c3ac076da8d00\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/3.0.0/step.yml",
    "content": "title: Restore Gradle Cache\nsummary: Restores Gradle caches. This Step needs to be used in combination with **Save\n  Gradle Cache**.\ndescription: |\n  Restores Gradle dependency caches. This Step needs to be used in combination with **Save Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save Gradle cache](https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/issues\npublished_at: 2026-03-03T14:54:58.213738277Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache.git\n  commit: 1cda97dca32d3e70b0819c583424472783993be9\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-gradle-cache/3.0.0/bin/restore-gradle-cache-darwin-amd64\n    hash: sha256-05c762f6032a3bec6dfe40285a467a92eb071e10fe3998f05b7ea1b8d0b06ca0\n  darwin-arm64:\n    storage_uri: steps/restore-gradle-cache/3.0.0/bin/restore-gradle-cache-darwin-arm64\n    hash: sha256-4bda026164d285266d5c2f49fdce7c6515af112e585105d8c81e746a0d79ee2b\n  linux-amd64:\n    storage_uri: steps/restore-gradle-cache/3.0.0/bin/restore-gradle-cache-linux-amd64\n    hash: sha256-3e8c69393270e760b332b3386ec426c78c501aa080f0f41d7ca2a3641a0f2b8e\n  linux-arm64:\n    storage_uri: steps/restore-gradle-cache/3.0.0/bin/restore-gradle-cache-linux-arm64\n    hash: sha256-28086896e35cb7dee012fc09f0562905024eec995c35e71a6ea9f7d0dcfd9cf2\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-gradle-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.0/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2024-10-21T16:36:06.559025+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 4dfd56fe23a88963d55ab4e33a1aba1c21bd22ed\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.1/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-01-09T10:50:30.500915397Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 7c3153ac910aeb96586eac30face3169e3272626\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.10/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-11-12T13:14:59.417649229Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 6e4822bc16fe2f4198808334c606e2cfc843129e\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.3/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-01-29T08:55:49.283730838Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 17a9130d898bf79e8ef62594d2f5d88f070baaf6\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.5/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-03-18T15:03:09.7117892Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 01080f41be63e7b0b6bc6436bd5bfb115038aebb\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.6/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-04-07T16:34:44.397483773Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 78b588d0a74864cf03db474b318abaf84a2d56f7\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.7/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-05-13T11:05:28.700380296Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: c728e586272e09a7d0a805a547a434478fda2e34\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.8/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-07-02T09:08:02.815508287Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 2ae7f583549e3381249f15592dfe51c98a9cb044\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/1.0.9/step.yml",
    "content": "title: Restore Gradle configuration cache\nsummary: Restores the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step restores the Gradle configuration cache folder from the Bitrise Build Cache to speed up future builds.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache\npublished_at: 2025-07-31T09:09:20.814220554Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-gradle-configuration-cache.git\n  commit: 6e5b745931c55646d36b6f4c53555efb466a0176\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Custom override key used to restore the cache from a previously saved entry (by the `Save Gradle configuration cache` step).\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents can also be restored from a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for restoring from the cache. By default the app slug\n      and branch is used\n    title: Cache key override\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-gradle-configuration-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-npm-cache/1.0.0/step.yml",
    "content": "title: Restore NPM Cache (Beta)\nsummary: Restores cached node_modules dependencies. This Step needs to be used in\n  combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2022-11-09T17:25:04.384187+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 591efdaf58d6edcb9250f6aa1dcdaa1180c3b154\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-npm-cache/1.1.0/step.yml",
    "content": "title: Restore NPM Cache (Beta)\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2023-01-12T10:52:37.41526156Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 49e78f67ab25c812b812a099282c2f13ce606653\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/1.1.1/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2023-02-10T08:48:26.28565634Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 389ed3e0530c7ef3bfec7ea69c9f597ee54c8088\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/2.0.0/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2023-11-27T00:23:41.494176755Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 1e174d77c850b0c49d6af94d6c79c4a8cb3f52a7\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/2.1.0/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2024-02-05T08:57:22.801815954Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 6a508a3f8644642f982d0803fab7b8e02c8be331\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/2.2.0/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2024-05-30T13:05:43.593993701Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 9845f42f23474f9d3087578bddcec96d7e446a6f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/2.3.0/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2024-07-29T13:15:40.402872104Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 8017d9bcb1bc52c9ccc89170782f48c54fcfbf79\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/2.3.1/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2024-09-17T08:31:42.400928085Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: b9e89fa7f03740432f7350654a930ab617e4c1cd\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/2.3.2/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2025-09-30T15:20:11.727865826Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: c9ccbc3053a1361c9a987667a2843caa4f387d3c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/3.0.0/step.yml",
    "content": "title: Restore NPM Cache\nsummary: Restores cached node_modules dependencies, used by NPM and Yarn. This Step\n  needs to be used in combination with **Save NPM Cache**.\ndescription: |\n  Restores cached node_modules dependencies. This Step needs to be used in combination with **Save NPM Cache**.\n\n  This Step is based on [key-based caching](https://docs.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Save NPM cache](https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/issues\npublished_at: 2026-03-03T15:43:22.345911882Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache.git\n  commit: 341f8b2117b789799bdf9703552aa6150125bb11\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-npm-cache/3.0.0/bin/restore-npm-cache-darwin-amd64\n    hash: sha256-b28b39f67849709c4bb47f97a5f58950cf09d846fe107856d6b0f62462d09507\n  darwin-arm64:\n    storage_uri: steps/restore-npm-cache/3.0.0/bin/restore-npm-cache-darwin-arm64\n    hash: sha256-2bbf87ed7a81b7d7d493db6dbb709aa544ac852b4cd39c354c51a5452bcca757\n  linux-amd64:\n    storage_uri: steps/restore-npm-cache/3.0.0/bin/restore-npm-cache-linux-amd64\n    hash: sha256-d1d15537cd0f4bfbc3242e2c37d1c303ab461b3ba9888186ca45cac8460e22b2\n  linux-arm64:\n    storage_uri: steps/restore-npm-cache/3.0.0/bin/restore-npm-cache-linux-arm64\n    hash: sha256-933f32545dc7f59142a6edca769bd235009972311d469fd0ab140a0ffd2b69c2\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-npm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-npm-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-s3-cache/0.9.1/step.yml",
    "content": "title: Restore S3 Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save S3 Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save S3 Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore S3 Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache/issues\npublished_at: 2024-05-29T15:21:05.713629+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache.git\n  commit: ab45e1a4ef9612c3cc6be95077298fdf1b1eb4ee\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-s3-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\n- aws_bucket: null\n  opts:\n    category: AWS\n    description: |-\n      Bring your own bucket: exercise full control over the cache location.\n\n      The provided AWS bucket acts as cache backend for the Restore Cache step.\n\n      The step expects either:\n      - CACHE_AWS_ACCESS_KEY_ID, CACHE_AWS_SECRET_ACCESS_KEY secrets to be setup for the workflow\n      - The build is running on an EC2 instance. In this case, the steps expects the instance to have access to the bucket.\n    is_required: true\n    summary: Provide an AWS bucket name to be used as cache backend.\n    title: AWS Bucket name\n- aws_region: us-east-1\n  opts:\n    category: AWS\n    description: AWS Region specifies the region where the bucket belongs.\n    is_required: true\n    summary: Region of the S3 bucket.\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - ca-west-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-central-2\n    - eu-south-1\n    - eu-south-2\n    - ap-south-1\n    - ap-south-2\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-southeast-3\n    - ap-southeast-4\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - me-south-1\n    - me-central-1\n    - af-south-1\n    - il-central-1\n- aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID with access to the bucket.\n    title: AWS_ACCESS_KEY_ID\n- aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS\n    description: |\n      The secret access key that matches the secret key ID.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY with access to the bucket.\n    title: AWS_SECRET_ACCESS_KEY\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-s3-cache/0.9.2/step.yml",
    "content": "title: Restore S3 Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save S3 Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save S3 Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore S3 Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache/issues\npublished_at: 2024-06-04T07:56:15.776602184Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache.git\n  commit: a470232557c090633b950d880e62060d5c9cc33c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-s3-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\n- aws_bucket: null\n  opts:\n    category: AWS\n    description: |-\n      Bring your own bucket: exercise full control over the cache location.\n\n      The provided AWS bucket acts as cache backend for the Restore Cache step.\n\n      The step expects either:\n      - CACHE_AWS_ACCESS_KEY_ID, CACHE_AWS_SECRET_ACCESS_KEY secrets to be setup for the workflow\n      - The build is running on an EC2 instance. In this case, the steps expects the instance to have access to the bucket.\n    is_required: true\n    summary: Provide an AWS bucket name to be used as cache backend.\n    title: AWS Bucket name\n- aws_region: us-east-1\n  opts:\n    category: AWS\n    description: AWS Region specifies the region where the bucket belongs.\n    is_required: true\n    summary: Region of the S3 bucket.\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - ca-west-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-central-2\n    - eu-south-1\n    - eu-south-2\n    - ap-south-1\n    - ap-south-2\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-southeast-3\n    - ap-southeast-4\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - me-south-1\n    - me-central-1\n    - af-south-1\n    - il-central-1\n- aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID with access to the bucket.\n    title: AWS_ACCESS_KEY_ID\n- aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS\n    description: |\n      The secret access key that matches the secret key ID.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY with access to the bucket.\n    title: AWS_SECRET_ACCESS_KEY\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-s3-cache/0.9.3/step.yml",
    "content": "title: Restore S3 Cache\nsummary: Restores build cache using a cache key. This Step needs to be used in combination\n  with **Save S3 Cache**.\ndescription: |\n  Restores build cache using a cache key. This Step needs to be used in combination with **Save S3 Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore S3 Cache Step** downloads a cache archive associated with the key provided as a Step input.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when downloading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The Step evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo.\n\n  The following variables are supported in cache keys input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching and fallback keys\n\n  The most straightforward use case is that a cache archive is downloaded and restored if the provided key matches a cache archive uploaded previously using the Save Cache Step. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  It's possible to define more than one key in the cache keys input. You can specify additional keys by listing one key per line. The list is in priority order, so the Step will first try to find a match for the first key you provided, and if there is no cache stored for the key, it will move on to find a match for the second key (and so on).\n\n  In addition to listing multiple keys, each key can be a prefix of a saved cache key and still get a matching cache archive. For example, the key `my-cache-` can match an existing archive saved with the key `my-cache-a6a102ff`.\n\n  We recommend configuring the keys in a way that the first key is an exact match to a checksum key, and to use a more generic prefix key as a fallback:\n\n  ```\n  inputs:\n    key: |\n      npm-cache-{{ checksum \"package-lock.json\" }}\n      npm-cache-\n  ```\n\n  #### Related steps\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache/issues\npublished_at: 2025-09-30T11:23:24.923060919Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-s3-cache.git\n  commit: 3b7ebd2741d2bd02433f72f78bc023959df8ccbf\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-s3-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Keys used for restoring a cache archive. One cache key per line in priority order.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated) and you can list at most 8 keys using this input. Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Keys used for restoring a cache archive. The key can contain template\n      elements.\n    title: Cache keys\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting.\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\n- aws_bucket: null\n  opts:\n    category: AWS\n    description: |-\n      Bring your own bucket: exercise full control over the cache location.\n\n      The provided AWS bucket acts as cache backend for the Restore Cache step.\n\n      The step expects either:\n      - CACHE_AWS_ACCESS_KEY_ID, CACHE_AWS_SECRET_ACCESS_KEY secrets to be setup for the workflow\n      - The build is running on an EC2 instance. In this case, the steps expects the instance to have access to the bucket.\n    is_required: true\n    summary: Provide an AWS bucket name to be used as cache backend.\n    title: AWS Bucket name\n- aws_region: us-east-1\n  opts:\n    category: AWS\n    description: AWS Region specifies the region where the bucket belongs.\n    is_required: true\n    summary: Region of the S3 bucket.\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - ca-west-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-central-2\n    - eu-south-1\n    - eu-south-2\n    - ap-south-1\n    - ap-south-2\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-southeast-3\n    - ap-southeast-4\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - me-south-1\n    - me-central-1\n    - af-south-1\n    - il-central-1\n- aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID with access to the bucket.\n    title: AWS_ACCESS_KEY_ID\n- aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS\n    description: |\n      The secret access key that matches the secret key ID.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY with access to the bucket.\n    title: AWS_SECRET_ACCESS_KEY\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-s3-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/restore-spm-cache/1.0.0/step.yml",
    "content": "title: Restore SPM Cache (Beta)\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2022-11-09T17:30:32.888004+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 5e2bf5fbb157ff1dac6240b361b813dcec6f27a6\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/restore-spm-cache/1.1.0/step.yml",
    "content": "title: Restore SPM Cache (Beta)\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2023-01-12T10:39:09.392020618Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 6307fd13aa55ed524c4ff582397e431c6916b47d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/1.1.1/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2023-02-10T08:46:26.781708269Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 4e547661f1fc7b76a104956824d8acdfb39e77bc\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/2.0.0/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2023-11-27T00:25:38.769766394Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 7fad1ccc60c18d26a613755612456b0f81b4c4c4\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/2.1.0/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2024-03-21T10:22:06.08366436Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 093e11ad29ef92b85ed0ca330f6a83bab616cfab\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/2.1.1/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2024-09-10T14:28:04.796167942Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 20296845ec190d8798d353b7561497d8087a6c4e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/2.1.2/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2025-09-29T14:46:58.979315519Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: 6c952205ff9af610f812a5e80a9e1a08a296edf8\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/2.1.3/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2025-11-10T15:38:28.557592622Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: e04fca4f0eefd1bdf797afb176c69acb8159d7c1\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/3.0.0/step.yml",
    "content": "title: Restore SPM Cache\nsummary: Restores cached Swift Package Manager dependencies. This Step needs to be\n  used in combination with **Save SPM Cache**.\ndescription: |\n  Restores cached Swift Package Manager dependencies. This Step needs to be used in combination with **Save SPM Cache**.\n\n  This Step is based on [key-based caching](https://docs.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache keys, you might want to use the generic [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache) Step instead.\n\n  #### Related steps\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/issues\npublished_at: 2026-03-03T15:41:25.874970569Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache.git\n  commit: ec587e8e3326a854b6814415e0ea942a3dbfc6b5\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/restore-spm-cache/3.0.0/bin/restore-spm-cache-darwin-amd64\n    hash: sha256-eb71763794259bd34f0ae1d9fd4ae17648e5188242245bf17000ae6b0ac305cc\n  darwin-arm64:\n    storage_uri: steps/restore-spm-cache/3.0.0/bin/restore-spm-cache-darwin-arm64\n    hash: sha256-8de7e9c5ae92cb94f6507f2495d552061b1055d5172457cb8354f60f32e66556\n  linux-amd64:\n    storage_uri: steps/restore-spm-cache/3.0.0/bin/restore-spm-cache-linux-amd64\n    hash: sha256-5fa22724419f8bd96e9aa15c0bff90f7dcbeaccce0fc98830d2987a008a68d33\n  linux-arm64:\n    storage_uri: steps/restore-spm-cache/3.0.0/bin/restore-spm-cache-linux-arm64\n    hash: sha256-68c048d582454e7b34327ba0e08a08a95ab9a899afa1192e14d3fe1fe2833ad1\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-restore-spm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- opts:\n    category: Debugging\n    description: Timeout in seconds\n    is_required: true\n    summary: Timeout in seconds\n    title: Timeout\n  timeout: 600\n- opts:\n    category: Debugging\n    description: |-\n      Number of retries to attempt when downloading a cache archive fails.\n\n      The value 0 means no retries are attempted.\n    is_required: true\n    summary: Number of retries to attempt when downloading a cache archive fails.\n    title: Number of retries\n  retries: 3\noutputs:\n- BITRISE_CACHE_HIT: null\n  opts:\n    description: |-\n      Indicates if a cache entry was restored. Possible values:\n      - `exact`: Exact cache hit for the first requested cache key\n      - `partial`: Cache hit for a key other than the first\n      - `false` No cache hit, nothing was restored\n    title: Cache hit\n"
  },
  {
    "path": "steps/restore-spm-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/revopush-command-line-interface/0.0.1/step.yml",
    "content": "title: Run Revopush command\nsummary: |\n  The Step runs Revopush cli with the command and arguments you provide, for example,\n  to release release-react bundle .\ndescription: \"You can run any commands available for Revopush cli in your workflow.\n  \\n\\n### Configuring the Step\\n1. Add the **Run Revopush command** Step to your Workflow\n  after build Step.\\n2. Set the **Working directory**.\\n3. Set the command you want\n  revopush to execute, for example `release-react MyApp ios` to releases the React\n  Native \\niOS project in the current working directory to the \\\"MyApp\\\" app's \\\"Staging\\\"\n  deployment\\n4. If you're looking for a particular revopush cli version, you can\n  set it in the **Version of revopush cli to use** input.\\n5. Set the **Revopush Access\n  Key**.\\n\"\nwebsite: https://github.com/revopush/revopush-bitrise-step\nsource_code_url: https://github.com/revopush/revopush-bitrise-step\nsupport_url: https://github.com/revopush/revopush-bitrise-step/issues\npublished_at: 2025-02-25T19:56:00.922264+04:00\nsource:\n  git: https://github.com/revopush/revopush-bitrise-step.git\n  commit: fc6733a88782766869818dac0d0e0d8bb2f1a7de\nproject_type_tags:\n- react-native\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: node\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |-\n      Specify the command with arguments to run with `revopush`.\n\n      This input value will be append to the end of the `revopush` command call.\n\n      For example:\n\n      - `release-react MyApp ios` -> `revopush release-react MyApp ios`\n      - `promote MyApp Staging Production --des \"Production rollout\" -r 25` -> `revopush promote MyApp Staging Production --des \"Production rollout\" -r 25`\n    is_required: true\n    title: The `revopush` command with arguments to run\n- opts:\n    description: Set this value to the version of revopush cli that is required to\n      run the command. Must be a valid semver string.\n    title: Version of revopush cli to use\n  version: null\n- access_key: $REVOPUSH_ACCESS_KEY\n  opts:\n    description: |\n      Your Revopush access key  authentication token (see https://app.revopush.org/settings).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Revopush Access Key\n    title: Access Key\n"
  },
  {
    "path": "steps/revopush-command-line-interface/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/ruby-script/2.0.0/step.yml",
    "content": "title: Ruby Script runner with optional Gemfile support\nsummary: Install the gems you need, run the script you'd like.\ndescription: Run a Ruby script with optional Gemfile.\nwebsite: https://github.com/bitrise-io/steps-ruby-script\nsource_code_url: https://github.com/bitrise-io/steps-ruby-script\nsupport_url: https://github.com/bitrise-io/steps-ruby-script/issues\npublished_at: 2015-09-08T16:48:19.649281442+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ruby-script.git\n  commit: 8400225b2596f186975eff83f8ae02430f0119cf\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- script\n- ruby\n- runner\n- glue\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- gemfile_content: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Gemfile's content\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: The Ruby script\n  ruby_content: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: |-\n      Specify a directory - this will be set as the\n      current working directory for the script\n    title: Run in directory\n  script_run_dir: \"\"\n"
  },
  {
    "path": "steps/ruby-script/2.0.1/step.yml",
    "content": "title: Ruby Script runner with optional Gemfile support\nsummary: Install the gems you need, run the script you'd like.\ndescription: Run a Ruby script with optional Gemfile.\nwebsite: https://github.com/bitrise-io/steps-ruby-script\nsource_code_url: https://github.com/bitrise-io/steps-ruby-script\nsupport_url: https://github.com/bitrise-io/steps-ruby-script/issues\npublished_at: 2015-09-12T13:35:16.999682597+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ruby-script.git\n  commit: a501c5edd97902b1c53ec287680255bc6fa70e01\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- script\n- ruby\n- runner\n- glue\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- gemfile_content: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Gemfile's content\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: The Ruby script\n  ruby_content: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: |-\n      Specify a directory - this will be set as the\n      current working directory for the script\n    title: Run in directory\n  script_run_dir: \"\"\n"
  },
  {
    "path": "steps/ruby-script/2.1.0/step.yml",
    "content": "title: Ruby Script runner with optional Gemfile support\nsummary: |\n  Install the gems you need, run the script you'd like.\ndescription: |\n  Run a Ruby script with optional Gemfile.\nwebsite: https://github.com/bitrise-io/steps-ruby-script\nsource_code_url: https://github.com/bitrise-io/steps-ruby-script\nsupport_url: https://github.com/bitrise-io/steps-ruby-script/issues\npublished_at: 2016-06-12T19:53:32.688754363+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-ruby-script.git\n  commit: 1f3fa082042c2fd9ece19525dcecaa94c86b8305\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- gemfile_content: |\n    source 'https://rubygems.org'\n\n    # gem 'json', '~> 1.8', '>= 1.8.3'\n  opts:\n    description: Gemfile's content\n    is_expand: false\n    summary: Gemfile's content\n    title: Gemfile's content\n- opts:\n    description: The Ruby script to run\n    is_expand: false\n    is_required: true\n    summary: The Ruby script to run\n    title: The Ruby script\n  ruby_content: |\n    puts \"Hello World!\"\n- opts:\n    description: |\n      Specify a directory - this will be set as the\n      current working directory for the script\n    summary: |\n      Specify a directory - this will be set as the\n      current working directory for the script\n    title: Run in directory\n  script_run_dir: \"\"\n"
  },
  {
    "path": "steps/ruby-script/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/run-eas-build/0.1.0/step.yml",
    "content": "title: Run Expo Application Services (EAS) build\nsummary: Runs a build on Expo Application Services (EAS).\ndescription: |-\n  Runs a build on Expo Application Services (EAS).\n\n  The step runs `EXPO_TOKEN=[access_token] npx eas-cli build --platform [platform] --non-interactive [eas_options]`\n\n  in the provided `[work_dir]`.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-run-eas-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-run-eas-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-run-eas-build/issues\npublished_at: 2022-02-07T13:42:38.014928+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-run-eas-build.git\n  commit: f715d2e36baf33bf1185c1fb67c2d2c1146d795a\nproject_type_tags:\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-run-eas-build\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: nodejs\n  - name: npm\ninputs:\n- access_token: null\n  opts:\n    description: |-\n      Expo Access Token.\n\n      Visit [Expo Documentation](https://docs.expo.dev/accounts/programmatic-access) to generate one.\n    is_required: true\n    is_sensitive: true\n    summary: Expo Access Token.\n    title: Access Token\n- opts:\n    is_required: true\n    summary: Platform to build.\n    title: Platform\n    value_options:\n    - all\n    - android\n    - ios\n  platform: all\n- opts:\n    is_required: true\n    summary: Directory containing the Expo project (`app.json`).\n    title: Work dir\n  work_dir: $BITRISE_SOURCE_DIR\n- eas_options: null\n  opts:\n    description: |-\n      Additional options for the eas command.\n\n      The step runs `EXPO_TOKEN=[access_token] npx eas-cli build --platform [platform] --non-interactive`,\n      use this input to pass additional option to the command.\n\n      Example: `--profile=development`.\n    summary: Additional options for the eas command.\n    title: eas command options\n"
  },
  {
    "path": "steps/run-eas-build/0.1.1/step.yml",
    "content": "title: Run Expo Application Services (EAS) build\nsummary: Runs a build on Expo Application Services (EAS).\ndescription: |-\n  Runs a build on Expo Application Services (EAS).\n\n  The step runs `EXPO_TOKEN=[access_token] npx eas-cli build --platform [platform] --non-interactive [eas_options]`\n\n  in the provided `[work_dir]`.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-run-eas-build\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-run-eas-build\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-run-eas-build/issues\npublished_at: 2022-02-23T15:06:37.202326724Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-run-eas-build.git\n  commit: d37d574f557ac714f38f7aca129256e7d599a4d1\nproject_type_tags:\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-run-eas-build\ndeps:\n  brew:\n  - name: node\n  apt_get:\n  - name: nodejs\n  - name: npm\ninputs:\n- access_token: null\n  opts:\n    description: |-\n      Expo Access Token.\n\n      Visit [Expo Documentation](https://docs.expo.dev/accounts/programmatic-access) to generate one.\n    is_required: true\n    is_sensitive: true\n    summary: Expo Access Token.\n    title: Access Token\n- opts:\n    is_required: true\n    summary: Platform to build.\n    title: Platform\n    value_options:\n    - all\n    - android\n    - ios\n  platform: all\n- opts:\n    is_required: true\n    summary: Directory containing the Expo project (`app.json`).\n    title: Work dir\n  work_dir: $BITRISE_SOURCE_DIR\n- eas_options: null\n  opts:\n    description: |-\n      Additional options for the eas command.\n\n      The step runs `EXPO_TOKEN=[access_token] npx eas-cli build --platform [platform] --non-interactive`,\n      use this input to pass additional option to the command.\n\n      Example: `--profile=development`.\n    summary: Additional options for the eas command.\n    title: eas command options\n"
  },
  {
    "path": "steps/run-eas-build/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/run-tests-using-marathon-cloud/0.1.2/step.yml",
    "content": "title: Run tests using Marathon Cloud\nsummary: |\n  Run all your automated tests in just 15 minutes, no matter how many tests you have\ndescription: |\n  With this step you can easily run your Android instrumentation and iOS tests. Marathon Cloud is designed to run all your automated tests in just 15 minutes, no matter how many tests you have.\nwebsite: https://marathonlabs.io\nsource_code_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud\nsupport_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud/issues\npublished_at: 2023-07-14T12:40:42.213318151+03:00\nsource:\n  git: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud.git\n  commit: e1c93a1527ff2afd59a08c8dc3906efde973ce76\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: malinskiy/tap/marathon-cloud\ninputs:\n- application: \"\"\n  opts:\n    description: \"Application binary path.  \\nFor an Android project: app APK file\n      path.  \\nFor an iOS project: an ARM compatible Simulator build packaged in a\n      ZIP archive.  \\n\"\n    is_expand: true\n    is_required: true\n    summary: The application binary path refers to the APK file for Android or the\n      ZIP file for the iOS application.\n    title: App File\n- opts:\n    description: \"Test application binary path.  \\nFor an Android project: test app\n      APK file path.  \\nFor an iOS project: an ARM compatible Simulator iOS Test Runner\n      app packaged in a ZIP archive.  \\n\"\n    is_expand: true\n    is_required: true\n    summary: The test application binary path refers to the APK file for Android or\n      the ZIP file for the iOS Test Runner app.\n    title: Test App File\n  test_application: \"\"\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Testing platform. `Android` or `iOS` only\n    title: Testing platform\n  platform: \"\"\n- api_key: null\n  opts:\n    description: \"Have a look at [the tokens page](https://cloud.marathonlabs.io/tokens)\n      in the dashboard to obtain your token.      \\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API key for authenticating with Marathon Cloud\n    title: Marathon Cloud API key\n- docker_image: marathonlabs/marathon-cloud:latest\n  opts:\n    description: \"\"\n    is_required: false\n    summary: You can specify your own custom image with a Docker Registry proxy here\n    title: Docker image to use for running marathon-cloud cli on Linux hosts\n"
  },
  {
    "path": "steps/run-tests-using-marathon-cloud/0.2.0/step.yml",
    "content": "title: Run tests using Marathon Cloud\nsummary: |\n  Run all your automated tests in just 15 minutes, no matter how many tests you have\ndescription: |\n  With this step you can easily run your Android instrumentation and iOS tests. Marathon Cloud is designed to run all your automated tests in just 15 minutes, no matter how many tests you have.\nwebsite: https://marathonlabs.io\nsource_code_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud\nsupport_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud/issues\npublished_at: 2023-08-31T21:17:04.213318151+03:00\nsource:\n  git: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud.git\n  commit: ddbcf9063a07342938fb626f86a659b15105404d\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: malinskiy/tap/marathon-cloud\ninputs:\n- application: \"\"\n  opts:\n    description: \"Application binary path.  \\nFor an Android project: app APK file\n      path.  \\nFor an iOS project: an ARM compatible Simulator build packaged in a\n      ZIP archive.  \\n\"\n    is_expand: true\n    is_required: true\n    summary: The application binary path refers to the APK file for Android or the\n      ZIP file for the iOS application.\n    title: App File\n- opts:\n    description: \"Test application binary path.  \\nFor an Android project: test app\n      APK file path.  \\nFor an iOS project: an ARM compatible Simulator iOS Test Runner\n      app packaged in a ZIP archive.  \\n\"\n    is_expand: true\n    is_required: true\n    summary: The test application binary path refers to the APK file for Android or\n      the ZIP file for the iOS Test Runner app.\n    title: Test App File\n  test_application: \"\"\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    summary: Testing platform. `Android` or `iOS` only\n    title: Testing platform\n  platform: \"\"\n- api_key: null\n  opts:\n    description: \"Have a look at [the tokens page](https://cloud.marathonlabs.io/tokens)\n      in the dashboard to obtain your token.      \\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: API key for authenticating with Marathon Cloud\n    title: Marathon Cloud API key\n- docker_image: marathonlabs/marathon-cloud:latest\n  opts:\n    description: \"\"\n    is_required: false\n    summary: You can specify your own custom image with a Docker Registry proxy here\n    title: Docker image to use for running marathon-cloud cli on Linux hosts\n- os_version: \"\"\n  opts:\n    title: OS version\n    summary: Android or iOS OS version\n    description: \"\"\n    is_expand: true\n    is_required: false\n- run_name: \"\"\n  opts:\n    title: Name for run\n    summary: Name for run, for example it could be description of commit\n    description: \"\"\n    is_expand: true\n    is_required: false\n- link: \"\"\n  opts:\n    title: Link to commit\n    summary: Link to commit\n    description: \"\"\n    is_expand: true\n    is_required: false"
  },
  {
    "path": "steps/run-tests-using-marathon-cloud/1.0.0/step.yml",
    "content": "title: Run tests using Marathon Cloud\nsummary: |\n  Run all your automated tests in just 15 minutes, no matter how many tests you have\ndescription: |\n  With this step you can easily run your Android instrumentation and iOS tests. Marathon Cloud is designed to run all your automated tests in just 15 minutes, no matter how many tests you have.\nwebsite: https://marathonlabs.io\nsource_code_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud\nsupport_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud/issues\npublished_at: 2024-02-20T18:55:21+10:00\nsource:\n  git: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud.git\n  commit: 8d51d5102314a4f28097574e61f0376e4df91c17\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: malinskiy/tap/marathon-cloud\ninputs:\n  - application: \"\"\n    opts:\n      title: App File\n      summary: The application binary path refers to the APK file for Android or the ZIP file for the iOS application.\n      description: |\n        Application binary path.  \n        For an Android project: app APK file path.  \n        For an iOS project: an ARM compatible Simulator build packaged in a ZIP archive.\n      is_expand: true\n      is_required: true\n  - test_application: \"\"\n    opts:\n      title: Test App File\n      summary: The test application binary path refers to the APK file for Android or the ZIP file for the iOS Test Runner app.\n      description: |\n        Test application binary path.  \n        For an Android project: test app APK file path.  \n        For an iOS project: an ARM compatible Simulator iOS Test Runner app packaged in a ZIP archive.\n      is_expand: true\n      is_required: true\n  - platform: \"\"\n    opts:\n      title: Testing platform\n      summary: Testing platform. `Android` or `iOS` only\n      description: \"\"\n      value_options:\n        - \"Android\"\n        - \"iOS\"\n      is_expand: true\n      is_required: true\n  - api_key:\n    opts:\n      title: Marathon Cloud API key\n      summary: API key for authenticating with Marathon Cloud\n      description: |\n        Have a look at [the tokens page](https://cloud.marathonlabs.io/tokens) in the dashboard to obtain your token.\n      is_expand: true\n      is_required: true\n      is_sensitive: true\n  - docker_image: marathonlabs/marathon-cloud:latest\n    opts:\n      title: Docker image to use for running marathon-cloud cli on Linux hosts\n      summary: You can specify your own custom image with a Docker Registry proxy here\n      description: \"\"\n      is_required: false\n  - os_version: \"\"\n    opts:\n      title: OS version\n      summary: Android or iOS OS version\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - run_name: \"\"\n    opts:\n      title: Name for run\n      summary: Name for run, for example it could be description of commit\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - link: \"\"\n    opts:\n      title: Optional link, for example it could be a link to source control commit or CI run\n      summary: Optional link, for example it could be a link to source control commit or CI run\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - system_image: default\n    opts:\n      title: OS-specific system image\n      summary: OS-specific system image. For Android one of `default` ,`google_apis`. For iOS only `default`\n      description: \"\"\n      value_options:\n        - \"default\"\n        - \"google_apis\"\n      is_expand: true\n      is_required: false\n  - isolated: false\n    opts:\n      title: Run each test using isolated execution\n      summary: Run each test using isolated execution. Default is false\n      description: \"\"\n      value_options:\n        - \"true\"\n        - \"false\"\n      is_expand: true\n      is_required: false\n  - ignore_test_failures: false\n    opts:\n      title: Ignore test failures\n      summary: When tests fail and this option is true then cli will exit with code 0. By default, cli will exit with code 1 in case of test failures and 0 for passing tests\n      description: \"\"\n      value_options:\n        - \"true\"\n        - \"false\"\n      is_expand: true\n      is_required: false\n"
  },
  {
    "path": "steps/run-tests-using-marathon-cloud/1.0.1/step.yml",
    "content": "title: Run tests using Marathon Cloud\nsummary: |\n  Run all your automated tests in just 15 minutes, no matter how many tests you have\ndescription: |\n  With this step you can easily run your Android instrumentation and iOS tests. Marathon Cloud is designed to run all your automated tests in just 15 minutes, no matter how many tests you have.\nwebsite: https://marathonlabs.io\nsource_code_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud\nsupport_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud/issues\npublished_at: 2024-11-06T20:43:56+03:00\nsource:\n  git: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud.git\n  commit: fa9c6f4ecedbf2babba03c3843da2195a399e6c4\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: malinskiy/tap/marathon-cloud\ninputs:\n  - application: \"\"\n    opts:\n      title: App File\n      summary: The application binary path refers to the APK file for Android or the ZIP file for the iOS application.\n      description: |\n        Application binary path.  \n        For an Android project: app APK file path.  \n        For an iOS project: an ARM compatible Simulator build packaged in a ZIP archive.\n      is_expand: true\n      is_required: true\n  - test_application: \"\"\n    opts:\n      title: Test App File\n      summary: The test application binary path refers to the APK file for Android or the ZIP file for the iOS Test Runner app.\n      description: |\n        Test application binary path.  \n        For an Android project: test app APK file path.  \n        For an iOS project: an ARM compatible Simulator iOS Test Runner app packaged in a ZIP archive.\n      is_expand: true\n      is_required: true\n  - platform: \"\"\n    opts:\n      title: Testing platform\n      summary: Testing platform. `Android` or `iOS` only\n      description: \"\"\n      value_options:\n        - \"Android\"\n        - \"iOS\"\n      is_expand: true\n      is_required: true\n  - api_key:\n    opts:\n      title: Marathon Cloud API key\n      summary: API key for authenticating with Marathon Cloud\n      description: |\n        Have a look at [the tokens page](https://cloud.marathonlabs.io/tokens) in the dashboard to obtain your token.\n      is_expand: true\n      is_required: true\n      is_sensitive: true\n  - docker_image: marathonlabs/marathon-cloud:latest\n    opts:\n      title: Docker image to use for running marathon-cloud cli on Linux hosts\n      summary: You can specify your own custom image with a Docker Registry proxy here\n      description: \"\"\n      is_required: false\n  - os_version: \"\"\n    opts:\n      title: OS version\n      summary: Android or iOS OS version\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - run_name: \"\"\n    opts:\n      title: Name for run\n      summary: Name for run, for example it could be description of commit\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - link: \"\"\n    opts:\n      title: Optional link, for example it could be a link to source control commit or CI run\n      summary: Optional link, for example it could be a link to source control commit or CI run\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - system_image: \"\"\n    opts:\n      title: Runtime system image. Only for Android\n      summary: Runtime system image. Possible values are `default` ,`google_apis`\n      description: \"\"\n      value_options:\n        - \"default\"\n        - \"google_apis\"\n      is_expand: true\n      is_required: false\n  - isolated: false\n    opts:\n      title: Run each test using isolated execution\n      summary: Run each test using isolated execution. Default is false\n      description: \"\"\n      value_options:\n        - \"true\"\n        - \"false\"\n      is_expand: true\n      is_required: false\n  - ignore_test_failures: false\n    opts:\n      title: Ignore test failures\n      summary: When tests fail and this option is true then cli will exit with code 0. By default, cli will exit with code 1 in case of test failures and 0 for passing tests\n      description: \"\"\n      value_options:\n        - \"true\"\n        - \"false\"\n      is_expand: true\n      is_required: false\n  - output: \"\"\n    opts:\n      title: Output folder\n      summary: Output folder for test run results\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - filter_file: \"\"\n    opts:\n      title: Filter file\n      summary: File containing test filters in YAML format, following the schema described at https://docs.marathonlabs.io/runner/configuration/filtering/#filtering-logic. For iOS see also https://docs.marathonlabs.io/runner/next/ios#test-plans.\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - device: \"\"\n    opts:\n      title: Device type\n      summary: Device type. For Android one of [phone, tv, watch]. For iOS one of [iPhone-15, iPhone-15-Pro, iPhone-15-Pro-Max]\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - xcode_version: \"\"\n    opts:\n      title: Xcode version. Only for iOS\n      summary: Xcode version. Only for iOS. Possible values are [15.2, 15.4]\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - xctestplan_filter_file: \"\"\n    opts:\n      title: Test filters supplied as .xctestplan file. Only for iOS\n      summary: Test filters supplied as .xctestplan file\n      description: \"\"\n      is_expand: true\n      is_required: false\n  - xctestplan_target_name: \"\"\n    opts:\n      title: Target name to use for test filtering in .xctestplan. Only for iOS\n      summary: Target name to use for test filtering in .xctestplan\n      description: \"\"\n      is_expand: true\n      is_required: false\n"
  },
  {
    "path": "steps/run-tests-using-marathon-cloud/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/rustup-install/0.1.0/step.yml",
    "content": "title: Rust Install\nsummary: |\n  Install the Rust Toolchain.\ndescription: |\n  Install the required components to build and run Rust projects in the current workflow.\nwebsite: https://github.com/nick0602/bitrise-step-rustup/\nsource_code_url: https://github.com/nick0602/bitrise-step-rustup/\nsupport_url: https://github.com/nick0602/bitrise-step-rustup/issues\npublished_at: 2022-08-08T19:03:48.196370409+02:00\nsource:\n  git: https://github.com/nick0602/bitrise-step-rustup.git\n  commit: 07a5e3648e169f01e4903ecfbc2b66097e73b598\ntype_tags:\n- installer\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- opts:\n    description: |\n      If `true`, forces the use of the nightly version of the toolchain.\n    is_expand: true\n    summary: Installs and uses a nightly version of the toolchain\n    title: Use Rustup Nightly\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_rustup_nightly: \"false\"\n- auto_update_toolchain: \"false\"\n  opts:\n    description: |\n      If `true`, forces the update of the Rust Toolchain.\n    is_expand: true\n    summary: Automatically update the Rust Toolchain on every run.\n    title: Update the Rust Toolchain\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: none\n  opts:\n    description: |\n      `all` will cache cargo binaries and rustup root folder, `none` won't cache any of the above.\n    is_expand: true\n    summary: Sets the local folders to be cached.\n    title: Set cache level\n    value_options:\n    - all\n    - none\n- opts:\n    description: |\n      If `true`, prints the exported `$RUSTUP_VERSION`, `$RUSTC_VERSION` and `$CARGO_VERSION` at the end of the step.\n    is_expand: true\n    summary: Shows the version of the Toolchain components at the end of the step.\n    title: Show Toolchain versions\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_exported_envs: \"false\"\noutputs:\n- RUSTUP_VERSION: null\n  opts:\n    description: |\n      The version returned by the `rustup -V` command.\n    summary: The current Rust Toolchain version\n    title: Current `rustup` version\n- RUSTC_VERSION: null\n  opts:\n    description: |\n      The version returned by the `rustc -V` command.\n    summary: The current Rustc version\n    title: Current `rustc` version\n- CARGO_VERSION: null\n  opts:\n    description: |\n      The version returned by the `cargo -V` command.\n    summary: The current Cargo version\n    title: Current `cargo` version\n"
  },
  {
    "path": "steps/rustup-install/0.1.1/step.yml",
    "content": "title: Rust Install\nsummary: |\n  Install the Rust Toolchain.\ndescription: |\n  Install the required components to build and run Rust projects in the current workflow.\nwebsite: https://github.com/nick0602/bitrise-step-rustup/\nsource_code_url: https://github.com/nick0602/bitrise-step-rustup/\nsupport_url: https://github.com/nick0602/bitrise-step-rustup/issues\npublished_at: 2022-09-08T23:20:56.532577496+02:00\nsource:\n  git: https://github.com/nick0602/bitrise-step-rustup.git\n  commit: efef8905b38b07c112da860497b21980ad4d4039\ntype_tags:\n- installer\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- opts:\n    description: |\n      If `true`, forces the use of the nightly version of the toolchain.\n    is_expand: true\n    summary: Installs and uses a nightly version of the toolchain\n    title: Use Rustup Nightly\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_rustup_nightly: \"false\"\n- auto_update_toolchain: \"false\"\n  opts:\n    description: |\n      If `true`, forces the update of the Rust Toolchain.\n    is_expand: true\n    summary: Automatically update the Rust Toolchain on every run.\n    title: Update the Rust Toolchain\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: none\n  opts:\n    description: |\n      `all` will cache cargo binaries and rustup root folder, `none` won't cache any of the above.\n    is_expand: true\n    summary: Sets the local folders to be cached.\n    title: Set cache level\n    value_options:\n    - all\n    - none\n- opts:\n    description: |\n      If `true`, prints the exported `$RUSTUP_VERSION`, `$RUSTC_VERSION` and `$CARGO_VERSION` at the end of the step.\n    is_expand: true\n    summary: Shows the version of the Toolchain components at the end of the step.\n    title: Show Toolchain versions\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_exported_envs: \"false\"\noutputs:\n- RUSTUP_VERSION: null\n  opts:\n    description: |\n      The version returned by the `rustup -V` command.\n    summary: The current Rust Toolchain version\n    title: Current `rustup` version\n- RUSTC_VERSION: null\n  opts:\n    description: |\n      The version returned by the `rustc -V` command.\n    summary: The current Rustc version\n    title: Current `rustc` version\n- CARGO_VERSION: null\n  opts:\n    description: |\n      The version returned by the `cargo -V` command.\n    summary: The current Cargo version\n    title: Current `cargo` version\n"
  },
  {
    "path": "steps/rustup-install/0.2.0/step.yml",
    "content": "title: Rust Install\nsummary: |\n  Install the Rust Toolchain.\ndescription: |\n  Install the required components to build and run Rust projects in the current workflow.\nwebsite: https://github.com/nick0602/bitrise-step-rustup/\nsource_code_url: https://github.com/nick0602/bitrise-step-rustup/\nsupport_url: https://github.com/nick0602/bitrise-step-rustup/issues\npublished_at: 2022-09-26T07:34:06.74688916+02:00\nsource:\n  git: https://github.com/nick0602/bitrise-step-rustup.git\n  commit: 62335ebdf8926f2201cfa9dc55ba80b418e6e1b1\ntype_tags:\n- installer\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- opts:\n    description: |\n      Specify a Rust version. If blank, defaults to the current `stable` version.\n    is_expand: true\n    summary: Installs and uses the specified Rust version.\n    title: Rust version\n  rust_version: stable\n- auto_update_toolchain: \"false\"\n  opts:\n    description: |\n      If `true`, forces the update of the Rust Toolchain. Valid for `stable` and `nightly` versions only.\n    is_expand: true\n    summary: Automatically update the Rust Toolchain on every run.\n    title: Update the Rust Toolchain\n    value_options:\n    - \"true\"\n    - \"false\"\n- cache_level: none\n  opts:\n    description: |\n      `all` will cache cargo binaries and rustup root folder, `none` won't cache any of the above.\n    is_expand: true\n    summary: Sets the local folders to be cached.\n    title: Set cache level\n    value_options:\n    - all\n    - none\n- opts:\n    description: |\n      If `true`, prints the exported `$RUSTUP_VERSION`, `$RUSTC_VERSION` and `$CARGO_VERSION` at the end of the step.\n    is_expand: true\n    summary: Shows the version of the Toolchain components at the end of the step.\n    title: Show Toolchain versions\n    value_options:\n    - \"true\"\n    - \"false\"\n  show_exported_envs: \"false\"\noutputs:\n- RUSTUP_VERSION: null\n  opts:\n    description: |\n      The version returned by the `rustup -V` command.\n    summary: The current Rust Toolchain version\n    title: Current `rustup` version\n- RUSTC_VERSION: null\n  opts:\n    description: |\n      The version returned by the `rustc -V` command.\n    summary: The current Rustc version\n    title: Current `rustc` version\n- CARGO_VERSION: null\n  opts:\n    description: |\n      The version returned by the `cargo -V` command.\n    summary: The current Cargo version\n    title: Current `cargo` version\n"
  },
  {
    "path": "steps/rustup-install/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/s3-cache-pull/0.1.0/step.yml",
    "content": "title: S3 Cache Pull\nsummary: |\n  A step to retrieve your cache from a S3 bucket using custom keys with fallback.\n\n  This should be used with the s3-cache-push step to store the cache.\n\n  If you want to retrieve multiple items, you'll need run this step multiple times.\n\n  *Bucket Access*\n  For this step to work you'll need an user in aws with programmatic access to a bucket.\n  The user should have permissions to list, get, and put objects in the bucket.\n\n  You can set the credentials using the Bitrise Secrets with the keys specified in the inputs\n  or set them directly in the inputs.\nwebsite: https://github.com/alephao/bitrise-step-s3-cache-pull\nsource_code_url: https://github.com/alephao/bitrise-step-s3-cache-pull\nsupport_url: https://github.com/alephao/bitrise-step-s3-cache-pull/issues\npublished_at: 2021-06-24T12:20:12.105573-03:00\nsource:\n  git: https://github.com/alephao/bitrise-step-s3-cache-pull.git\n  commit: 5a060fbe7421a60a272ae51a5f668b2e8e05b804\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/alephao/bitrise-step-s3-cache-pull\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- cache_aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS Access\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, and `s3:GetObject`.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID to access the bucket.\n    title: AWS_ACCESS_KEY_ID\n- cache_aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS Access\n    description: |\n      The secret access key that matches the access key id.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, and `s3:GetObject`.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY to access the bucket.\n    title: AWS_SECRET_ACCESS_KEY\n- cache_aws_region: $CACHE_AWS_S3_REGION\n  opts:\n    category: AWS Bucket\n    is_expand: true\n    is_required: true\n    summary: The region of the S3 bucket\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-south-1\n    - ap-south-1\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - us-gov-secret-1\n    - us-gov-topsecret-1\n    - me-south-1\n    - af-south-1\n- cache_bucket_name: $CACHE_S3_BUCKET_NAME\n  opts:\n    category: AWS Bucket\n    is_expand: true\n    is_required: true\n    summary: The name of the s3 bucket where you want to store the cache\n    title: Bucket Name\n- cache_restore_keys: null\n  opts:\n    category: Cache\n    description: |\n      The cache key can contain special values for convenience.\n\n      You can use '{{ checksum path/to/file }}' to get the file content's sha256 checksum.\n      You can use '{{ branch }}' to get the name of the current branch.\n      You can use '{{ stackrev }}' to get the machine's stack id.\n\n      This step will loop through the specified keys and retrieve the cache for the first\n      key that matches the prefix of a cache key. For example:\n\n      If you only have a cache stored with the key `carthage-a-b-c` and the following restore Keys:\n\n      cache_restore_keys: |\n        carthage-a-b-123\n        carthage-a-123\n        carthage-\n        car\n\n      It will try looking for a key prefixed with `carthage-a-b-123` and will find nothing. Then\n      it will try the same for `carthage-a-123` and will find nothing. Then it will try the same for\n      `carthage-` and it will find our cache `carthage-a-b-c` and retrieve it.\n\n      If a cache is not found for the key, this step is skipped.\n    is_expand: false\n    is_required: true\n    summary: List of cache key prefixes to find the cached file\n    title: Cache restore keys\n- cache_path: null\n  opts:\n    category: Cache\n    description: |\n      If you stored the cache as `/path/to/my/folder`, the compressed file in the bucket will contain\n      only `folder`, therefore you'll need to set this to `/path/to/my/`\n    is_expand: false\n    is_required: true\n    summary: Path to extract the file or directory cached. Relative to the root of\n      the git repo.\n    title: Cache path\n"
  },
  {
    "path": "steps/s3-cache-pull/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/s3-cache-push/0.1.0/step.yml",
    "content": "title: S3 Cache Push\nsummary: |\n  Store your cache in a s3 bucket with custom keys.\ndescription: |\n  A step to store your cache in a s3 bucket using custom keys.\n\n  This should be used with the s3-cache-pull step to retrieve the cache.\n\n  If you want to cache multiple items, you'll need run this step multiple times.\n\n  *Bucket Access*\n  For this step to work you'll need an user in aws with programmatic access to a bucket.\n  The user should have permissions to list, get, and put objects in the bucket.\n\n  You can set the credentials using the Bitrise Secrets with the keys specified in the inputs\n  or set them directly in the inputs.\nwebsite: https://github.com/alephao/bitrise-step-s3-cache-push\nsource_code_url: https://github.com/alephao/bitrise-step-s3-cache-push\nsupport_url: https://github.com/alephao/bitrise-step-s3-cache-push/issues\npublished_at: 2021-06-24T12:19:11.947795-03:00\nsource:\n  git: https://github.com/alephao/bitrise-step-s3-cache-push.git\n  commit: 0d378ab707258082a6ac54e9397ffc2ce38465be\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/alephao/bitrise-step-s3-cache-push\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- cache_aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS Access\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, and `s3:GetObject`.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID to access the bucket.\n    title: AWS_ACCESS_KEY_ID\n- cache_aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS Access\n    description: |\n      The secret access key that matches the access key id.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, and `s3:GetObject`.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY to access the bucket.\n    title: AWS_SECRET_ACCESS_KEY\n- cache_aws_region: $CACHE_AWS_S3_REGION\n  opts:\n    category: AWS Bucket\n    is_expand: true\n    is_required: true\n    summary: The region of the S3 bucket\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-south-1\n    - ap-south-1\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - us-gov-secret-1\n    - us-gov-topsecret-1\n    - me-south-1\n    - af-south-1\n- cache_bucket_name: $CACHE_S3_BUCKET_NAME\n  opts:\n    category: AWS Bucket\n    is_expand: true\n    is_required: true\n    summary: The name of the s3 bucket where you want to store the cache\n    title: Bucket Name\n- cache_key: null\n  opts:\n    category: Cache\n    description: |\n      The cache key can contain special values for convenience.\n\n      You can use '{{ checksum path/to/file }}' to get the file content's sha256 checksum.\n      You can use '{{ branch }}' to get the name of the current branch.\n      You can use '{{ stackrev }}' to get the machine's stack id.\n\n      E.g.: key: {{ stackrev }}-carthage-{{ branch }}-{{ checksum \"Cartfile.resolved\" }}\n    is_expand: false\n    is_required: true\n    summary: The key that will be used on S3 as the file key. This is used to retrieve\n      the cache with s3-cache-pull.\n    title: Cache key\n- cache_path: null\n  opts:\n    category: Cache\n    description: |\n      The entire folder will be compressed before sending to the S3 bucket\n\n      For instance, if you cache `/path/to/my/folder`, only \"folder\" will be compressed.\n      When retrieving the cachee with s3-cache-pull, you will have to use `/path/to/my/` to extract the folder there.\n    is_expand: false\n    is_required: true\n    summary: Path to file or directory to be cached. Relative to the root of the git\n      repo.\n    title: Cache path\n"
  },
  {
    "path": "steps/s3-cache-push/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/s3-download/1.0.0/step.yml",
    "content": "title: S3 Download\nsummary: This step allows to download a file from an S3 bucket.\ndescription: This step allows to download a file from an S3 bucket using an Access/secret\n  keypair for authentication.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-s3-download\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-s3-download\npublished_at: 2020-10-13T14:15:12.622558+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-s3-download.git\n  commit: 1d72ad20a1e8139680c500c277ab6aec0f2539bc\nhost_os_tags:\n- osx-10.10\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aws_access_key: \"\"\n  opts:\n    description: This is the AWS Access key of an user with read permission to the\n      S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Access Key for the S3 user\n    title: AWS Access Key\n- aws_secret_access_key: \"\"\n  opts:\n    description: This is the AWS Secret Access key of an user with read permission\n      to the S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Secret Access Key for the S3 user\n    title: AWS Secret Access Key\n- opts:\n    description: This is the S3 bucket containing the file to download\n    is_expand: true\n    is_required: true\n    summary: The S3 bucket containing the file to download\n    title: S3 Bucket\n  s3_bucket: \"\"\n- opts:\n    description: This is the file path of the file to download from the bucket.\n    is_expand: true\n    is_required: true\n    summary: The file path of the file to download\n    title: File path\n  s3_filepath: \"\"\n- opts:\n    description: The folder where to store the downloaded file (must exist).\n    is_expand: true\n    is_required: true\n    summary: Where to store the downloaded file.\n    title: File path\n  output_location: .\noutputs:\n- S3_DOWNLOAD_OUTPUT_PATH: Path were the file was saved\n  opts:\n    category: aws\n    is_dont_change_value: false\n    title: S3 Download output\n"
  },
  {
    "path": "steps/s3-download/1.1.0/step.yml",
    "content": "title: S3 Download\nsummary: This step allows to download a file from an S3 bucket.\ndescription: This step allows to download a file from an S3 bucket using an Access/secret\n  keypair for authentication.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-s3-download\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-s3-download\npublished_at: 2021-04-14T23:29:59.538838+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-s3-download.git\n  commit: fb93dbb6b02c69677bddf2ef232da197ff55163e\nhost_os_tags:\n- osx-10.10\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aws_access_key: \"\"\n  opts:\n    description: This is the AWS Access key of an user with read permission to the\n      S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Access Key for the S3 user\n    title: AWS Access Key\n- aws_secret_access_key: \"\"\n  opts:\n    description: This is the AWS Secret Access key of an user with read permission\n      to the S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Secret Access Key for the S3 user\n    title: AWS Secret Access Key\n- opts:\n    description: This is the S3 bucket containing the file to download\n    is_expand: true\n    is_required: true\n    summary: The S3 bucket containing the file to download\n    title: S3 Bucket\n  s3_bucket: \"\"\n- opts:\n    description: This is the file path of the file to download from the bucket.\n    is_expand: true\n    is_required: true\n    summary: The file path of the file to download\n    title: File path\n  s3_filepath: \"\"\n- opts:\n    description: The folder where to store the downloaded file (must exist).\n    is_expand: true\n    is_required: true\n    summary: Where to store the downloaded file.\n    title: File path\n  output_location: .\noutputs:\n- S3_DOWNLOAD_OUTPUT_PATH: null\n  opts:\n    description: This is the full path to the downloaded file. It will be composed\n      by resolved output_location and s3_filepath\n    summary: Path were the file was saved\n    title: S3 Download output\n"
  },
  {
    "path": "steps/s3-download/1.2.0/step.yml",
    "content": "title: S3 Download\nsummary: This step allows to download a file from an S3 bucket.\ndescription: This step allows to download a file from an S3 bucket using an Access/secret\n  keypair for authentication.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-s3-download\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-s3-download\npublished_at: 2021-04-15T17:35:05.765147+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-s3-download.git\n  commit: 91153ac6d6b39b83524d742fbefc1dbce43f0f32\nhost_os_tags:\n- osx-10.10\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aws_access_key: \"\"\n  opts:\n    description: This is the AWS Access key of an user with read permission to the\n      S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Access Key for the S3 user\n    title: AWS Access Key\n- aws_secret_access_key: \"\"\n  opts:\n    description: This is the AWS Secret Access key of an user with read permission\n      to the S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Secret Access Key for the S3 user\n    title: AWS Secret Access Key\n- opts:\n    description: This is the S3 bucket containing the file to download\n    is_expand: true\n    is_required: true\n    summary: The S3 bucket containing the file to download\n    title: S3 Bucket\n  s3_bucket: \"\"\n- opts:\n    description: This is the file path of the file to download from the bucket.\n    is_expand: true\n    is_required: true\n    summary: The file path of the file to download\n    title: File path\n  s3_filepath: \"\"\n- opts:\n    description: The folder where to store the downloaded file (must exist).\n    is_expand: true\n    is_required: true\n    summary: Where to store the downloaded file.\n    title: File path\n  output_location: .\noutputs:\n- S3_DOWNLOAD_OUTPUT_PATH: null\n  opts:\n    description: This is the full path to the downloaded file. It will be composed\n      by resolved output_location and s3_filepath\n    summary: Path were the file was saved\n    title: S3 Download output\n"
  },
  {
    "path": "steps/s3-download/1.2.1/step.yml",
    "content": "title: S3 Download\nsummary: This step allows to download a file from an S3 bucket.\ndescription: This step allows to download a file from an S3 bucket using an Access/secret\n  keypair for authentication.\nwebsite: https://github.com/FutureWorkshops/bitrise-step-s3-download\nsource_code_url: https://github.com/FutureWorkshops/bitrise-step-s3-download\npublished_at: 2021-04-19T19:38:39.53618+02:00\nsource:\n  git: https://github.com/FutureWorkshops/bitrise-step-s3-download.git\n  commit: 257f703ed0e6ca715b81e50dd7673127f561c541\nhost_os_tags:\n- osx-10.10\n- osx-10.9\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- aws_access_key: \"\"\n  opts:\n    description: This is the AWS Access key of an user with read permission to the\n      S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Access Key for the S3 user\n    title: AWS Access Key\n- aws_secret_access_key: \"\"\n  opts:\n    description: This is the AWS Secret Access key of an user with read permission\n      to the S3 bucket/file.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The Secret Access Key for the S3 user\n    title: AWS Secret Access Key\n- opts:\n    description: This is the S3 bucket containing the file to download\n    is_expand: true\n    is_required: true\n    summary: The S3 bucket containing the file to download\n    title: S3 Bucket\n  s3_bucket: \"\"\n- opts:\n    description: This is the file path of the file to download from the bucket.\n    is_expand: true\n    is_required: true\n    summary: The file path of the file to download\n    title: File path\n  s3_filepath: \"\"\n- opts:\n    description: The folder where to store the downloaded file (must exist).\n    is_expand: true\n    is_required: true\n    summary: Where to store the downloaded file.\n    title: File path\n  output_location: .\noutputs:\n- S3_DOWNLOAD_OUTPUT_PATH: null\n  opts:\n    description: This is the full path to the downloaded file. It will be composed\n      by resolved output_location and s3_filepath\n    summary: Path were the file was saved\n    title: S3 Download output\n"
  },
  {
    "path": "steps/s3-download/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/saucelabs-espresso-app-automate/0.1.1/step.yml",
    "content": "title: SauceLabs App Automate\nsummary: |\n  Upload an app apk and an Espresso test apk to SauceLabs and run tests with App Automate.\ndescription: |\n  This step uploads a provided app apk and  test apk to SauceLabs.  It then will execute the Espresso Tests for the provided apks in SauceLabs app automate.\nwebsite: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate/issues\npublished_at: 2019-11-05T17:16:51.810497+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate.git\n  commit: 02d031d39bdbfa2be18ed52d327c4d73da29d1ff\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\n\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The .apk file for your app\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app, likely generated by the Android Build for UI Testing step\n    is_expand: true\n    is_required: true\n    summary: Path to the espresso test .apk file\n    title: Test suite apk path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs username\n  saucelabs_username: null\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs access key\n  saucelabs_access_key: null\n- opts:\n    category: Automated Test Options\n    description: |\n      Provide a comma separated list of Device and OS version you want to run your tests on, with quotes. Acceptable format example: \"Google Pixel GoogleAPI Emulator,platformVersion=7.0\", \"LG Nexus 4 GoogleAPI Emulator,platformVersion=4.4\"\n      A list of available device and OS combinations can be found [here](https://saucelabs.com/platform/supported-browsers-devices)\n    is_expand: true\n    is_required: true\n    summary: A comma separated list of desired test devices\n    title: Device list\n  saucelabs_device_list: '\"deviceName=Google Pixel GoogleAPI Emulator,platformVersion=7.0\",\n    \"deviceName=LG Nexus 4 GoogleAPI Emulator,platformVersion=4.4\"'\n- opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter if you want to specify a Sauce Labs datacenter Options: \"us-west-1\" or \"eu-central-1\"\n    is_expand: true\n    is_required: false\n    summary: |\n      Set this parameter if you want to run tests only for particular annotations.\n    title: SauceLabs Data Center\n  saucelabs_data_center: null\n"
  },
  {
    "path": "steps/saucelabs-espresso-app-automate/0.1.2/step.yml",
    "content": "title: SauceLabs App Automate\nsummary: |\n  Upload an app apk and an Espresso test apk to SauceLabs and run tests with App Automate.\ndescription: |\n  This step uploads a provided app apk and  test apk to SauceLabs.  It then will execute the Espresso Tests for the provided apks in SauceLabs app automate.\nwebsite: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate/issues\npublished_at: 2019-11-09T00:11:36.945868+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate.git\n  commit: 4f69179f961a10b868f66cb049f827137f2bb5fd\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The .apk file for your app\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app, likely generated by the Android Build for UI Testing step\n    is_expand: true\n    is_required: true\n    summary: Path to the espresso test .apk file\n    title: Test suite apk path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs username\n  saucelabs_username: null\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs access key\n  saucelabs_access_key: null\n- opts:\n    category: Automated Test Options\n    description: |\n      Provide a comma separated list of Device and OS version you want to run your tests on, with quotes. Acceptable format example: \"Google Pixel GoogleAPI Emulator,platformVersion=7.0\", \"LG Nexus 4 GoogleAPI Emulator,platformVersion=4.4\"\n      A list of available device and OS combinations can be found [here](https://saucelabs.com/platform/supported-browsers-devices)\n    is_expand: true\n    is_required: true\n    summary: A comma separated list of desired test devices\n    title: Device list\n  saucelabs_device_list: '\"deviceName=Google Pixel GoogleAPI Emulator,platformVersion=7.0\",\n    \"deviceName=LG Nexus 4 GoogleAPI Emulator,platformVersion=4.4\"'\n- opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter if you want to specify a Sauce Labs datacenter Options: \"us-west-1\" , \"eu-central-1\"\n    is_expand: true\n    is_required: true\n    summary: |\n      Set this parameter if you want to run tests only for particular annotations.\n    title: SauceLabs Data Center\n  saucelabs_data_center: eu-central-1\n"
  },
  {
    "path": "steps/saucelabs-espresso-app-automate/0.1.3/step.yml",
    "content": "title: SauceLabs App Automate\nsummary: |\n  Upload an app apk and an Espresso test apk to SauceLabs and run tests with App Automate.\ndescription: |\n  This step uploads a provided app apk and  test apk to SauceLabs.  It then will execute the Espresso Tests for the provided apks in SauceLabs app automate.\nwebsite: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate/issues\npublished_at: 2019-11-14T15:17:24.191549+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate.git\n  commit: c69588dbb400660c476d788bb22b0b80b4f4090d\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The .apk file for your app\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app, likely generated by the Android Build for UI Testing step\n    is_expand: true\n    is_required: true\n    summary: Path to the espresso test .apk file\n    title: Test suite apk path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs username\n  saucelabs_username: null\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs access key\n  saucelabs_access_key: null\n- opts:\n    category: Automated Test Options\n    description: |\n      Provide a comma separated list of Device and OS version you want to run your tests on, with quotes. Acceptable format example: \"deviceName=Google Pixel GoogleAPI Emulator,platformVersion=7.0\", \"deviceName=LG Nexus 4 GoogleAPI Emulator,platformVersion=4.4\"\n      A list of available device and OS combinations can be found [here](https://saucelabs.com/platform/supported-browsers-devices)\n    is_expand: true\n    is_required: true\n    summary: A comma separated list of desired test devices\n    title: Device list\n  saucelabs_device_list: \"\"\n- opts:\n    category: Automated Test Options\n    description: |\n      Set this parameter if you want to specify a Sauce Labs datacenter Options: \"us-west-1\" , \"eu-central-1\"\n    is_expand: false\n    is_required: true\n    summary: |\n      Set this parameter if you want to run tests only for particular annotations.\n    title: SauceLabs Data Center\n  saucelabs_data_center: eu-central-1\n"
  },
  {
    "path": "steps/saucelabs-espresso-app-automate/0.1.4/step.yml",
    "content": "title: SauceLabs App Automate\nsummary: |\n  Upload an app apk and an Espresso test apk to SauceLabs and run tests with App Automate.\ndescription: |\n  This step uploads a provided app apk and  test apk to SauceLabs.  It then will execute the Espresso Tests for the provided apks in SauceLabs app automate.\nwebsite: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate/issues\npublished_at: 2019-12-02T14:59:29.085238+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate.git\n  commit: d7834fcf1d96dde102e4e741c8263c16b61d914e\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The .apk file for your app\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app, likely generated by the Android Build for UI Testing step\n    is_expand: true\n    is_required: true\n    summary: Path to the espresso test .apk file\n    title: Test suite apk path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs Username\n  saucelabs_username: null\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access key for saucelabs\n    title: SauceLabs Access Key\n  saucelabs_access_key: null\n- opts:\n    description: |\n      The Device and OS version you want to run your tests on, with quotes. Acceptable format example: deviceName=Google Pixel GoogleAPI Emulator,platformVersion=7.0\n      A list of available device and OS combinations can be found [here](https://saucelabs.com/platform/supported-browsers-devices)\n    is_expand: true\n    is_required: true\n    summary: The desired test device\n    title: Device Name\n  saucelabs_device_name: \"\"\n- opts:\n    description: |\n      Set this parameter if you want to specify a Sauce Labs datacenter Options: \"us-west-1\" , \"eu-central-1\"\n    is_expand: false\n    is_required: true\n    summary: |\n      Set this parameter if you want to run tests only for particular annotations.\n    title: SauceLabs Data Center\n  saucelabs_data_center: eu-central-1\n"
  },
  {
    "path": "steps/saucelabs-espresso-app-automate/0.1.6/step.yml",
    "content": "title: SauceLabs App Automate\nsummary: |\n  Upload an app apk and an Espresso test apk to SauceLabs and run tests with App Automate.\ndescription: |\n  This step uploads a provided app apk and  test apk to SauceLabs.  It then will execute the Espresso Tests for the provided apks in SauceLabs app automate.\nwebsite: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsource_code_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate\nsupport_url: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate/issues\npublished_at: 2019-12-09T13:21:49.675148+01:00\nsource:\n  git: https://github.com/moatazeldebsy/bitrise-step-saucelabs-espresso-app-automate.git\n  commit: 82bcd7ccff0178fe3f269c981de4f401cf31db1a\nhost_os_tags:\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The .apk file for your app\n    is_expand: true\n    is_required: true\n    summary: Path to the app .apk file\n    title: App apk path\n- opts:\n    description: |\n      The test .apk file for your app, likely generated by the Android Build for UI Testing step\n    is_expand: true\n    is_required: true\n    summary: Path to the espresso test .apk file\n    title: Test suite apk path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your username for saucelabs\n    title: SauceLabs username\n  saucelabs_username: null\n- opts:\n    description: \"\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your access key for saucelabs\n    title: SauceLabs access key\n  saucelabs_access_key: null\n- opts:\n    description: |\n      The Device and OS version you want to run your tests on, with quotes. Acceptable format example: Google Pixel GoogleAPI Emulator,platformVersion=7.0\n      A list of available device and OS combinations can be found [here](https://saucelabs.com/platform/supported-browsers-devices)\n    is_expand: true\n    is_required: true\n    summary: The desired test device\n    title: Device Name\n  saucelabs_device_name: \"\"\n- opts:\n    description: |\n      Set this parameter if you want to specify a Sauce Labs datacenter Options: \"us-west-1\" , \"eu-central-1\"\n    is_expand: false\n    is_required: true\n    summary: |\n      Set this parameter if you want to run tests only for particular annotations.\n    title: SauceLabs Data Center\n    value_options:\n    - us-west-1\n    - eu-central-1\n  saucelabs_data_center: eu-central-1\n"
  },
  {
    "path": "steps/saucelabs-espresso-app-automate/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/save-cache/1.0.0/step.yml",
    "content": "title: Save Cache (Beta)\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2022-09-14T17:12:19.39975+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 7f51168e673fe0794d84977dfdec1664cc49f8e1\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      The path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.0.1/step.yml",
    "content": "title: Save Cache (Beta)\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2022-09-22T10:12:12.523204061Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: c1649b08c3c009b2b4ca73e5ac024890f054c8cc\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      The path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.0.2/step.yml",
    "content": "title: Save Cache (Beta)\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2022-09-23T13:45:41.574720291Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 01e8f19565a06a048c4e224a96c14d00eda236ef\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      The path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.1.0/step.yml",
    "content": "title: Save Cache (Beta)\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2022-10-18T13:57:15.4841922Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 900dd187712cdf19299640377c427ff0f27ae4ee\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      The path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n"
  },
  {
    "path": "steps/save-cache/1.1.1/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2023-02-10T08:49:37.205256304Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: f122ec1ec2d6de1262f49e1c6b03db45dcb1c1f3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.1.2/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2023-04-13T14:07:42.392896179Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 4d712bab6b2cf30141eb264575f8133f5d9d849c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.2.0/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2024-02-05T08:51:20.683806071Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 9b3bd9ef55a6440b980a01911a1afdd81ad8961d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.3.0/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2024-05-24T14:30:15.912188589Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: cbb767ab0bb5ce044f72ff599b6e5b579e4fb7d3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level. Valid values are between 1 and 19. Defaults to\n      3.\n    title: Compression level\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.3.1/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2024-05-27T12:45:53.997798809Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 66378027559704654006f20a590ebad5e22b0a2e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.4.0/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2024-07-05T10:07:06.463005968Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 5b8265117c71fe8c54479334049b20e73c4cea68\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- custom_tar_args: null\n  opts:\n    description: |-\n      Additional arguments to pass to the tar command when creating the cache archive.\n\n      The arguments are passed directly to the `tar` command. Use this input to customize the behavior of the tar command when creating the cache archive\n      (these are appended to the default arguments used by the step).\n\n      Example: `--format posix`\n    is_required: false\n    summary: Additional arguments to pass to the tar command when creating the cache\n      archive.\n    title: Custom tar arguments\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.5.0/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2025-08-28T12:59:37.483889278Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 41d3422c5cee6a1c17c2e76baed651ea6a9b4f5a\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- custom_tar_args: null\n  opts:\n    description: |-\n      Additional arguments to pass to the tar command when creating the cache archive.\n\n      The arguments are passed directly to the `tar` command. Use this input to customize the behavior of the tar command when creating the cache archive\n      (these are appended to the default arguments used by the step).\n\n      Example: `--format posix`\n    is_required: false\n    summary: Additional arguments to pass to the tar command when creating the cache\n      archive.\n    title: Custom tar arguments\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.5.1/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2025-11-13T15:31:28.876162756Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: 728a6d3059a2d7dc87b4fe7591f9617ee9479a95\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- custom_tar_args: null\n  opts:\n    description: |-\n      Additional arguments to pass to the tar command when creating the cache archive.\n\n      The arguments are passed directly to the `tar` command. Use this input to customize the behavior of the tar command when creating the cache archive\n      (these are appended to the default arguments used by the step).\n\n      Example: `--format posix`\n    is_required: false\n    summary: Additional arguments to pass to the tar command when creating the cache\n      archive.\n    title: Custom tar arguments\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/1.5.2/step.yml",
    "content": "title: Save Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore Cache**.\ndescription: |\n  Saves build cache using a cache key. This Step needs to be used in combination with **Restore Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save cache** and **Restore cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored. Make sure to use unique cache keys with a checksum, and enable the **Unique cache key** input for the most optimal execution.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cache/issues\npublished_at: 2026-03-03T14:07:44.138592881Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cache.git\n  commit: f4fc198147a7aed2d4fe5b7b55ca5ff415d17102\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/save-cache/1.5.2/bin/save-cache-darwin-amd64\n    hash: sha256-ff15c558ea2431988b2cdf175dfb2f99ba0f7f04c0f4ee7a8b010aba1b5f541d\n  darwin-arm64:\n    storage_uri: steps/save-cache/1.5.2/bin/save-cache-darwin-arm64\n    hash: sha256-0ef128abaaaddc614f6db807fef4fb8dec03142659b05b7399514ecd9fdb156a\n  linux-amd64:\n    storage_uri: steps/save-cache/1.5.2/bin/save-cache-linux-amd64\n    hash: sha256-8ab6d766ed02781a88884469baba2a0f5fea9e5e411e1904981071e11c5fc4a6\n  linux-arm64:\n    storage_uri: steps/save-cache/1.5.2/bin/save-cache-linux-arm64\n    hash: sha256-f600db4e1adc18fc0913b71ec922c649b758122429a8effb8c3e7d8e6397342d\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- custom_tar_args: null\n  opts:\n    description: |-\n      Additional arguments to pass to the tar command when creating the cache archive.\n\n      The arguments are passed directly to the `tar` command. Use this input to customize the behavior of the tar command when creating the cache archive\n      (these are appended to the default arguments used by the step).\n\n      Example: `--format posix`\n    is_required: false\n    summary: Additional arguments to pass to the tar command when creating the cache\n      archive.\n    title: Custom tar arguments\n- is_key_unique: \"false\"\n  opts:\n    description: |-\n      Enabling this allows the Step to skip creating a new cache archive when the workflow previously restored the cache with the same key.\n\n      This requires the cache key to be unique, so that the key changes whenever the files in the cache change. In practice, this means adding a `checksum` part to the key template with a file that describes the cache content (such as a lockfile).\n\n      Example of a cache key where this can be safely turned on: `npm-cache-{{ checksum \"package-lock.json\" }}`. On the other hand, `my-cache-{{ .OS }}-{{ .Arch }}` is not unique (even though it uses templates).\n\n      Note: the Step can still skip uploading a cache when this input is `false`, it just needs to create the archive first to compute its checksum (which takes time).\n    summary: This allows the Step to skip creating a new cache in certain conditions.\n      Only set to `true` if the key is unique to the cached content!\n    title: Unique cache key\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/save-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-carthage-cache/1.0.0/step.yml",
    "content": "title: Save Carthage Cache\nsummary: Caches Carthage prebuilt frameworks. This Step needs to be used in combination\n  with **Restore Carthage Cache**.\ndescription: |\n  Caches prebuilt frameworks in the Carthage folder. This Step needs to be used in combination with **Restore Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Carthage cache](https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/issues\npublished_at: 2023-02-10T10:16:46.322599+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache.git\n  commit: d5e301be0da3e5d224bdea5171f689e7e40862e9\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-carthage-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-carthage-cache/1.0.1/step.yml",
    "content": "title: Save Carthage Cache\nsummary: Caches Carthage prebuilt frameworks. This Step needs to be used in combination\n  with **Restore Carthage Cache**.\ndescription: |\n  Caches prebuilt frameworks in the Carthage folder. This Step needs to be used in combination with **Restore Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Carthage cache](https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/issues\npublished_at: 2023-04-13T14:07:48.806190672Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache.git\n  commit: d5e301be0da3e5d224bdea5171f689e7e40862e9\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-carthage-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-carthage-cache/1.0.2/step.yml",
    "content": "title: Save Carthage Cache\nsummary: Caches Carthage prebuilt frameworks. This Step needs to be used in combination\n  with **Restore Carthage Cache**.\ndescription: |\n  Caches prebuilt frameworks in the Carthage folder. This Step needs to be used in combination with **Restore Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Carthage cache](https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/issues\npublished_at: 2023-04-27T13:02:37.839187983Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache.git\n  commit: b1ec7e123d31882fe80a095f7beaeb79a3ca5230\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-carthage-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-carthage-cache/1.1.0/step.yml",
    "content": "title: Save Carthage Cache\nsummary: Caches Carthage prebuilt frameworks. This Step needs to be used in combination\n  with **Restore Carthage Cache**.\ndescription: |\n  Caches prebuilt frameworks in the Carthage folder. This Step needs to be used in combination with **Restore Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Carthage cache](https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/issues\npublished_at: 2024-05-27T13:36:32.67441475Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache.git\n  commit: 7cbe044bd8a2caf562dccac9d2b20d1ec5f4aeab\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-carthage-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-carthage-cache/1.1.1/step.yml",
    "content": "title: Save Carthage Cache\nsummary: Caches Carthage prebuilt frameworks. This Step needs to be used in combination\n  with **Restore Carthage Cache**.\ndescription: |\n  Caches prebuilt frameworks in the Carthage folder. This Step needs to be used in combination with **Restore Carthage Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Carthage. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Carthage cache](https://github.com/bitrise-steplib/bitrise-step-restore-carthage-cache/)\n\n  [Save Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/)\n\n  [Save SPM cache](https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache/issues\npublished_at: 2025-11-12T08:30:07.533288622Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-carthage-cache.git\n  commit: 304512fb28c895687cdc5f70036d2eef0490a8c7\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-carthage-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-carthage-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-cocoapods-cache/1.0.0/step.yml",
    "content": "title: Save Cocoapods Cache (Beta)\nsummary: Caches the Pods folder. This Step needs to be used in combination with **Restore\n  Cocoapods Cache**.\ndescription: |\n  Caches dependencies in the Pods folder. This Step needs to be used in combination with **Restore Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/issues\npublished_at: 2022-11-09T17:33:45.40002+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache.git\n  commit: a088bb985fe4fa9b424877e3ad8387dd52e5f630\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cocoapods-cache/1.0.1/step.yml",
    "content": "title: Save Cocoapods Cache (Beta)\nsummary: Caches the Pods folder. This Step needs to be used in combination with **Restore\n  Cocoapods Cache**.\ndescription: |\n  Caches dependencies in the Pods folder. This Step needs to be used in combination with **Restore Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/issues\npublished_at: 2022-12-06T08:12:15.184932681Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache.git\n  commit: 1810a5856eb17d4e1972851494442e17ff8c6edc\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cocoapods-cache/1.0.2/step.yml",
    "content": "title: Save Cocoapods Cache\nsummary: Caches the Pods folder. This Step needs to be used in combination with **Restore\n  Cocoapods Cache**.\ndescription: |\n  Caches dependencies in the Pods folder. This Step needs to be used in combination with **Restore Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/issues\npublished_at: 2023-02-10T08:49:59.063895125Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache.git\n  commit: 99ea9c452dc133b3abe167246e48dd5a39309b73\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cocoapods-cache/1.0.3/step.yml",
    "content": "title: Save Cocoapods Cache\nsummary: Caches the Pods folder. This Step needs to be used in combination with **Restore\n  Cocoapods Cache**.\ndescription: |\n  Caches dependencies in the Pods folder. This Step needs to be used in combination with **Restore Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/issues\npublished_at: 2023-04-13T14:06:21.620077908Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache.git\n  commit: ffad050d61600dd5449bf288cae7cd08f27ebc43\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-cocoapods-cache/1.1.0/step.yml",
    "content": "title: Save Cocoapods Cache\nsummary: Caches the Pods folder. This Step needs to be used in combination with **Restore\n  Cocoapods Cache**.\ndescription: |\n  Caches dependencies in the Pods folder. This Step needs to be used in combination with **Restore Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/issues\npublished_at: 2024-05-27T13:37:38.831883646Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache.git\n  commit: cd97201cbb91863de8f34f98db48be72f1c3d12c\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-cocoapods-cache/1.1.1/step.yml",
    "content": "title: Save Cocoapods Cache\nsummary: Caches the Pods folder. This Step needs to be used in combination with **Restore\n  Cocoapods Cache**.\ndescription: |\n  Caches dependencies in the Pods folder. This Step needs to be used in combination with **Restore Cocoapods Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Cocoapods dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Cocoapods cache](https://github.com/bitrise-steplib/bitrise-step-restore-cocoapods-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache/issues\npublished_at: 2025-11-12T08:31:02.895463651Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache.git\n  commit: 798fd6884c479148e802edff1b94d79e50e6f0f6\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-cocoapods-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-cocoapods-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-dart-cache/1.0.0/step.yml",
    "content": "title: Save Dart Cache\nsummary: Saves Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Restore Dart Cache**.\ndescription: |\n  Saves Dart (Flutter) dependencies. This Step needs to be used in combination with **Restore Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Dart cache](https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/issues\npublished_at: 2023-02-10T10:13:39.17037+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache.git\n  commit: 4ae384577f0957fa733469a5813886283fd0c9c6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-dart-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-dart-cache/1.0.1/step.yml",
    "content": "title: Save Dart Cache\nsummary: Saves Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Restore Dart Cache**.\ndescription: |\n  Saves Dart (Flutter) dependencies. This Step needs to be used in combination with **Restore Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Dart cache](https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/issues\npublished_at: 2023-04-13T14:05:29.245011389Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache.git\n  commit: f4ba4a4a91c80557e9308f4dc203c11fda139b1f\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-dart-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-dart-cache/1.1.0/step.yml",
    "content": "title: Save Dart Cache\nsummary: Saves Dart (Flutter) dependencies. This Step needs to be used in combination\n  with **Restore Dart Cache**.\ndescription: |\n  Saves Dart (Flutter) dependencies. This Step needs to be used in combination with **Restore Dart Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Dart dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Dart cache](https://github.com/bitrise-steplib/bitrise-step-restore-dart-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache/issues\npublished_at: 2024-05-27T13:34:57.007894385Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-dart-cache.git\n  commit: e3da8c169f9e4e6e70a8763ef18a316b9da2a9f4\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-dart-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-dart-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-gradle-cache/1.0.0/step.yml",
    "content": "title: Save Gradle Cache (Beta)\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2022-11-09T14:49:16.709415+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 2cc8aa621ddf5e108dc857197fc1c80862898432\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.0.1/step.yml",
    "content": "title: Save Gradle Cache (Beta)\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2022-11-11T09:37:50.147818393Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 023f308e5179dfda195002f91c9c620234263ce0\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.1.0/step.yml",
    "content": "title: Save Gradle Cache (Beta)\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2022-12-21T10:23:58.45544828Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 79027b24b2a3a2c667b9e4be66d7ce20b18d5593\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.1.1/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2023-02-10T08:50:43.370594853Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 039c9be7fb660bd30f2f61304bedcd9b9cf0c6ca\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.1.2/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2023-02-21T12:15:31.955724349Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: cb17abd104e0de517e694c5e62493f8ff2f0912e\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.1.3/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2023-04-13T14:58:17.738532152Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: f281185c7a43a05c56872414a0f0502f8ac12259\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.1.4/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency and build caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2023-04-24T07:14:24.596807058Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 82f3e4fd0b0acfed614c26ddb6a8efc5d43f0a7f\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.1.5/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2023-07-13T07:33:48.734679069Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 4969bf9d0778302f8637f3af7ff4cc8d2a3e9ef0\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.2.0/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2024-02-05T09:55:22.345245991Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 2ba01423465d3c5a2bddc2e0942cdb0981c54c74\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.3.0/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2024-05-27T07:46:07.036578453Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: d78487a9c1815872f8a4219fa38c4eea258d891f\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-gradle-cache/1.4.0/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2024-11-04T08:37:24.222629628Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 36262e2a5934d5090590bcad764f72d852f6a3d2\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- opts:\n    is_required: true\n    summary: Save transformed classes and resources under `$HOME/.gradle/caches/**/transforms`\n    title: Save transforms\n    value_options:\n    - \"true\"\n    - \"false\"\n  save_transforms: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.4.1/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2024-11-08T09:32:18.291974157Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: a7b8640c0223d3d26b298482bc3d5247894130d0\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- opts:\n    is_required: true\n    summary: Save transformed classes and resources under `$HOME/.gradle/caches/**/transforms`\n    title: Save transforms\n    value_options:\n    - \"true\"\n    - \"false\"\n  save_transforms: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.4.2/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2025-01-20T15:23:43.686490599Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: 7fc7bc6f890e9bee8f766fc5c4b1a1b3ade57e26\nproject_type_tags:\n- android\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- opts:\n    is_required: true\n    summary: Save transformed classes and resources under `$HOME/.gradle/caches/**/transforms`\n    title: Save transforms\n    value_options:\n    - \"true\"\n    - \"false\"\n  save_transforms: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/1.4.3/step.yml",
    "content": "title: Save Gradle Cache\nsummary: Saves Gradle caches. This Step needs to be used in combination with **Restore\n  Gradle Cache**.\ndescription: |\n  Saves Gradle dependency caches. This Step needs to be used in combination with **Restore Gradle Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for Gradle. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore Gradle cache](https://github.com/bitrise-steplib/bitrise-step-restore-gradle-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache/issues\npublished_at: 2025-11-10T15:36:42.910704908Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-cache.git\n  commit: c827bff5be6d2f6379996b34eece9e8369f8b8f4\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-gradle-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n- opts:\n    is_required: true\n    summary: Save transformed classes and resources under `$HOME/.gradle/caches/**/transforms`\n    title: Save transforms\n    value_options:\n    - \"true\"\n    - \"false\"\n  save_transforms: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.0/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2024-10-21T16:24:45.288202+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: e3e829938ac6288c88b5aaa2f4e72ea4cb33492c\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.1/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-01-09T10:49:27.24992327Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: 8b5643673923b257ffe65d0f5802526eddeb7fb5\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.10/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-11-12T13:14:06.905697657Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: 5e56bba2e5bccf236111ea4df2282bdca0a921ee\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- java\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.3/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-01-29T08:56:19.966622742Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: 246dc16f27e2215505fbed56dde08bb5f13d73be\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.5/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-03-18T15:02:51.670913284Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: 50b5d49e6042e236c95f2b4988cf513872fedad0\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.6/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-04-07T16:33:45.328555996Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: c1569a692d417e9da9a8584dac20ee0e8f90e896\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.7/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-05-13T11:04:53.813220317Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: f4d2bac6ad24e207d5ce8f42d8a6bcafc4bf02ce\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.8/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-07-21T14:52:11.466317918Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: 13ccf6008afc1367f1990a3cf6f061397478219a\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/1.0.9/step.yml",
    "content": "title: Save Gradle configuration cache\nsummary: Caches the Gradle configuration cache folder used by Gradle. Uses the Bitrise\n  Build Cache infrastructure.\ndescription: |\n  This step caches the Gradle configuration cache folder along with the necessary metadata to speed up future builds. The cache is stored within the Bitrise Build Cache infrastructure.\n\n  For more information on how configuration caching works, refer to the [Gradle user guide](https://docs.gradle.org/current/userguide/configuration_cache.html).\n\n  Unless specified otherwise, the current directory is assumed to be the project directory, and therefore the `./gradle/configuration-cache` directory will be saved.\n\n  **IMPORTANT NOTES:**\n  - You must have an active Bitrise Build Cache Trial or Subscription for your workspace to use this step.\n  - You also need to set up the encryption key `GRADLE_ENCRYPTION_KEY` in Bitrise Secrets by using the result from running `openssl rand -base64 16`.\n  - Setting the encryption key is supported only from Gradle version 8.6 onwards, so your project must be using Gradle 8.6 or higher.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache\npublished_at: 2025-07-31T09:09:28.2543397Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-gradle-configuration-cache.git\n  commit: 53483051cd53d97477c8f062edf5254f38743c1e\nproject_type_tags:\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key_override: null\n  opts:\n    description: |-\n      Manually provided override key used for saving the cache.\n\n      If not specified, by default a key is generated from the app slug and the current branch. If not specified, the contents are also saved to a fallback key consisting only of the app slug. This helps reduce cache misses on new feature branches.\n    is_required: false\n    summary: Override key used for saving the cache. By default the app slug and branch\n      is used\n    title: Cache key override\n- config_cache_dir: ./.gradle/configuration-cache\n  opts:\n    description: This needs to be set to the config cache folder generated by Gradle.\n      It's usually in the project and NOT in the Gradle home.\n    is_required: true\n    summary: Path to the configuration cache folder\n    title: Configuration cache directory\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-gradle-configuration-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-npm-cache/1.0.0/step.yml",
    "content": "title: Save NPM Cache (Beta)\nsummary: Saves node_modules dependencies. This Step needs to be used in combination\n  with **Restore NPM Cache**.\ndescription: |\n  Saves node_modules dependencies. This Step needs to be used in combination with **Restore NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore NPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/issues\npublished_at: 2022-11-09T17:19:26.808497+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache.git\n  commit: dd8a83ac10ad09cbeb8b22a194f964a99b4f90b8\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-npm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-npm-cache/1.0.1/step.yml",
    "content": "title: Save NPM Cache\nsummary: Saves node_modules dependencies, used by NPM and Yarn. This Step needs to\n  be used in combination with **Restore NPM Cache**.\ndescription: |\n  Saves node_modules dependencies. This Step needs to be used in combination with **Restore NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Restore NPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/issues\npublished_at: 2023-02-10T08:47:21.005469322Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache.git\n  commit: fae71626b39176e6bcdf4893df525b5d356ea687\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-npm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-npm-cache/1.0.2/step.yml",
    "content": "title: Save NPM Cache\nsummary: Saves node_modules dependencies, used by NPM and Yarn. This Step needs to\n  be used in combination with **Restore NPM Cache**.\ndescription: |\n  Saves node_modules dependencies. This Step needs to be used in combination with **Restore NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Restore NPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/issues\npublished_at: 2023-04-13T14:04:58.641456547Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache.git\n  commit: 8133c8ae0d27b354709c29c146678355739c5ae6\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-npm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-npm-cache/1.1.0/step.yml",
    "content": "title: Save NPM Cache\nsummary: Saves node_modules dependencies, used by NPM and Yarn. This Step needs to\n  be used in combination with **Restore NPM Cache**.\ndescription: |\n  Saves node_modules dependencies. This Step needs to be used in combination with **Restore NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Restore NPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/issues\npublished_at: 2024-02-05T09:54:09.70921463Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache.git\n  commit: 3f015b6759d932df13394e9f5f5eff1622ebc1e3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-npm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-npm-cache/1.2.0/step.yml",
    "content": "title: Save NPM Cache\nsummary: Saves node_modules dependencies, used by NPM and Yarn. This Step needs to\n  be used in combination with **Restore NPM Cache**.\ndescription: |\n  Saves node_modules dependencies. This Step needs to be used in combination with **Restore NPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for NPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  Note: NPM and Yarn package managers are both supported.\n\n  #### Related steps\n\n  [Restore NPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-npm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache/issues\npublished_at: 2024-05-27T12:49:35.722072212Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-npm-cache.git\n  commit: 7ac13fdfbe24083e3cabb7e5bbcbf65aa5e8b93b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-npm-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-npm-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-s3-cache/0.9.0/step.yml",
    "content": "title: Save S3 Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore S3 Cache**.\ndescription: |\n  Saves build cache to an arbitrary S3 bucket using a cache key. This Step needs to be used in combination with **Restore S3 Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore S3 Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save S3 Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore S3 cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save S3 cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save S3 cache** and **Restore S3 cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore S3 cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore S3 cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache/issues\npublished_at: 2024-05-29T13:13:53.348471+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache.git\n  commit: b491089f814895268bad9cf5e0af406f51afe056\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-s3-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- aws_bucket: null\n  opts:\n    category: AWS\n    description: |-\n      Bring your own bucket: exercise full control over the cache location.\n\n      The provided AWS bucket acts as cache backend for the Restore Cache step.\n\n      The step expects either:\n      - CACHE_AWS_ACCESS_KEY_ID, CACHE_AWS_SECRET_ACCESS_KEY secrets to be setup for the workflow\n      - The build is running on an EC2 instance. In this case, the steps expects the instance to have access to the bucket.\n    is_required: true\n    summary: Provide an AWS bucket name to be used as cache backend.\n    title: AWS Bucket name\n- aws_region: us-east-1\n  opts:\n    category: AWS\n    description: AWS Region specifies the region where the bucket belongs.\n    is_required: true\n    summary: Region of the S3 bucket.\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - ca-west-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-central-2\n    - eu-south-1\n    - eu-south-2\n    - ap-south-1\n    - ap-south-2\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-southeast-3\n    - ap-southeast-4\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - me-south-1\n    - me-central-1\n    - af-south-1\n    - il-central-1\n- aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID with access to the bucket.\n    title: AWS_ACCESS_KEY_ID\n- aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS\n    description: |\n      The secret access key that matches the secret key ID.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY with access to the bucket.\n    title: AWS_SECRET_ACCESS_KEY\n"
  },
  {
    "path": "steps/save-s3-cache/0.9.1/step.yml",
    "content": "title: Save S3 Cache\nsummary: Saves build cache using a cache key. This Step needs to be used in combination\n  with **Restore S3 Cache**.\ndescription: |\n  Saves build cache to an arbitrary S3 bucket using a cache key. This Step needs to be used in combination with **Restore S3 Cache**.\n\n  #### About key-based caching\n\n  Key-based caching is a concept where cache archives are saved and restored using a unique cache key. One Bitrise project can have multiple cache archives stored simultaneously, and the **Restore S3 Cache Step** downloads a cache archive associated with the key provided as a Step input. The **Save S3 Cache** Step is responsible for uploading the cache archive with an exact key.\n\n  Caches can become outdated across builds when something changes in the project (for example, a dependency gets upgraded to a new version). In this case, a new (unique) cache key is needed to save the new cache contents. This is possible if the cache key is dynamic and changes based on the project state (for example, a checksum of the dependency lockfile is part of the cache key). If you use the same dynamic cache key when restoring the cache, the Step will download the most relevant cache archive available.\n\n  Key-based caching is platform-agnostic and can be used to cache anything by carefully selecting the cache key and the files/folders to include in the cache.\n\n  #### Templates\n\n  The Step requires a string key to use when uploading a cache archive. In order to always download the most relevant cache archive for each build, the cache key input can contain template elements. The **Restore S3 cache Step** evaluates the key template at runtime and the final key value can change based on the build environment or files in the repo. Similarly, the **Save S3 cache** Step also uses templates to compute a unique cache key when uploading a cache archive.\n\n  The following variables are supported in the **Cache key** input:\n\n  - `cache-key-{{ .Branch }}`: Current git branch the build runs on\n  - `cache-key-{{ .CommitHash }}`: SHA-256 hash of the git commit the build runs on\n  - `cache-key-{{ .Workflow }}`: Current Bitrise workflow name (eg. `primary`)\n  - `{{ .Arch }}-cache-key`: Current CPU architecture (`amd64` or `arm64`)\n  - `{{ .OS }}-cache-key`: Current operating system (`linux` or `darwin`)\n\n  Functions available in a template:\n\n  `checksum`: This function takes one or more file paths and computes the SHA256 [checksum](https://en.wikipedia.org/wiki/Checksum) of the file contents. This is useful for creating unique cache keys based on files that describe content to cache.\n\n  Examples of using `checksum`:\n  - `cache-key-{{ checksum \"package-lock.json\" }}`\n  - `cache-key-{{ checksum \"**/Package.resolved\" }}`\n  - `cache-key-{{ checksum \"**/*.gradle*\" \"gradle.properties\" }}`\n\n  `getenv`: This function returns the value of an environment variable or an empty string if the variable is not defined.\n\n  Examples of `getenv`:\n  - `cache-key-{{ getenv \"PR\" }}`\n  - `cache-key-{{ getenv \"BITRISEIO_PIPELINE_ID\" }}`\n\n  #### Key matching\n\n  The most straightforward use case is when both the **Save S3 cache** and **Restore S3 cache** Steps use the same exact key to transfer cache between builds. Stored cache archives are scoped to the Bitrise project. Builds can restore caches saved by any previous Workflow run on any Bitrise Stack.\n\n  Unlike this Step, the **Restore S3 cache** Step can define multiple keys as fallbacks when there is no match for the first cache key. See the docs of the **Restore S3 cache** Step for more details.\n\n  #### Skip saving the cache\n\n  The Step can decide to skip saving a new cache entry to avoid unnecessary work. This happens when there is a previously restored cache in the same workflow and the new cache would have the same contents as the one restored.\n\n  #### Related steps\n\n  [Restore cache](https://github.com/bitrise-steplib/bitrise-step-restore-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache/issues\npublished_at: 2024-06-04T07:55:33.979287189Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-s3-cache.git\n  commit: 7cbc38aa0bae49f14c4bb466afa52f4951e2f5d9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-s3-cache\ndeps:\n  brew:\n  - name: zstd\n  apt_get:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- key: null\n  opts:\n    description: |-\n      Key used for saving a cache archive.\n\n      The key supports template elements for creating dynamic cache keys. These dynamic keys change the final key value based on the build environment or files in the repo in order to create new cache archives. See the Step description for more details and examples.\n\n      The maximum length of a key is 512 characters (longer keys get truncated). Commas (`,`) are not allowed in keys.\n    is_required: true\n    summary: Key used for saving a cache archive. This can contain template elements.\n    title: Cache key\n- opts:\n    description: |-\n      List of files and folders to include in the cache.\n\n      Add one path per line. Each path can contain wildcards (`*` and `**`) that are evaluated at runtime.\n    is_required: true\n    summary: List of files and folders to include in the cache.\n    title: Paths to cache\n  paths: null\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- aws_bucket: null\n  opts:\n    category: AWS\n    description: |-\n      Bring your own bucket: exercise full control over the cache location.\n\n      The provided AWS bucket acts as cache backend for the Restore Cache step.\n\n      The step expects either:\n      - CACHE_AWS_ACCESS_KEY_ID, CACHE_AWS_SECRET_ACCESS_KEY secrets to be setup for the workflow\n      - The build is running on an EC2 instance. In this case, the steps expects the instance to have access to the bucket.\n    is_required: true\n    summary: Provide an AWS bucket name to be used as cache backend.\n    title: AWS Bucket name\n- aws_region: us-east-1\n  opts:\n    category: AWS\n    description: AWS Region specifies the region where the bucket belongs.\n    is_required: true\n    summary: Region of the S3 bucket.\n    title: AWS Region\n    value_options:\n    - us-east-1\n    - us-east-2\n    - us-west-1\n    - us-west-2\n    - ca-central-1\n    - ca-west-1\n    - eu-north-1\n    - eu-west-3\n    - eu-west-2\n    - eu-west-1\n    - eu-central-1\n    - eu-central-2\n    - eu-south-1\n    - eu-south-2\n    - ap-south-1\n    - ap-south-2\n    - ap-northeast-1\n    - ap-northeast-2\n    - ap-northeast-3\n    - ap-southeast-1\n    - ap-southeast-2\n    - ap-southeast-3\n    - ap-southeast-4\n    - ap-east-1\n    - sa-east-1\n    - cn-north-1\n    - cn-northwest-1\n    - us-gov-east-1\n    - us-gov-west-1\n    - me-south-1\n    - me-central-1\n    - af-south-1\n    - il-central-1\n- aws_access_key_id: $CACHE_AWS_ACCESS_KEY_ID\n  opts:\n    category: AWS\n    description: |\n      The access key id that matches the secret access key.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_ACCESS_KEY_ID with access to the bucket.\n    title: AWS_ACCESS_KEY_ID\n- aws_secret_access_key: $CACHE_AWS_SECRET_ACCESS_KEY\n  opts:\n    category: AWS\n    description: |\n      The secret access key that matches the secret key ID.\n\n      The credentials need to be from a user that has at least the following permissions\n      in the bucket specified bellow `s3:ListObjects`, `s3:PutObject`, `s3:GetObjectAttributes` and `s3:GetObject`.\n\n      If the build instance has S3 access via IAM Instance role, this variable can be left empty.\n    is_required: false\n    is_sensitive: true\n    summary: The AWS_SECRET_ACCESS_KEY with access to the bucket.\n    title: AWS_SECRET_ACCESS_KEY\n"
  },
  {
    "path": "steps/save-s3-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/save-spm-cache/1.0.0/step.yml",
    "content": "title: Save SPM Cache (Beta)\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2022-11-09T17:28:10.612999+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 339d2f62f278adc18edfc419c96e339cc2b602f3\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-spm-cache/1.0.1/step.yml",
    "content": "title: Save SPM Cache (Beta)\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2022-11-11T09:37:38.524385491Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 5756b06e8b50156741bb37e83111e93887c82068\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-spm-cache/1.0.2/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2023-02-10T08:46:52.144756716Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: db92f20412e32e204ae792bdeddd02851da35316\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-spm-cache/1.0.3/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2023-04-13T14:04:21.636023988Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 3adaab1eeba70584ceed2b790cab66a570c76a1d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-spm-cache/1.1.0/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2024-04-09T08:24:04.119630211Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: ade13504b8ccc14ec276ddaa4273d676df6a1711\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- derived_data_path: ~/Library/Developer/Xcode/DerivedData/**\n  opts:\n    description: Path of the project's Derived Data folder. Supports glob patterns.\n    is_required: true\n    summary: Path of the project's Derived Data folder.\n    title: Derived Data Path\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-spm-cache/1.2.0/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2024-04-09T12:45:49.274176033Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 8a30aff1325f337c02b0f7e330d5e4704fc017d7\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- derived_data_path: ~/Library/Developer/Xcode/DerivedData/**\n  opts:\n    description: Path of the project's Derived Data folder. Supports glob patterns.\n    is_required: false\n    summary: Path of the project's Derived Data folder.\n    title: Derived Data Path\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: false\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Xcode Project path. Used to automatically find Derived Data path, only\n      when `Derived Data Path` is empty (not provided).\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/save-spm-cache/1.3.0/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2024-05-27T08:36:11.54263033Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 327c076d83f682a2cef4337ead9ccc9200da1b7e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- derived_data_path: ~/Library/Developer/Xcode/DerivedData/**\n  opts:\n    description: Path of the project's Derived Data folder. Supports glob patterns.\n    is_required: false\n    summary: Path of the project's Derived Data folder.\n    title: Derived Data Path\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: false\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Xcode Project path. Used to automatically find Derived Data path, only\n      when `Derived Data Path` is empty (not provided).\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-spm-cache/1.3.1/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2025-01-23T09:38:35.319778023Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 7b11e7b59c20f6218c703ed817b3ee626edc735d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- derived_data_path: ~/Library/Developer/Xcode/DerivedData/**\n  opts:\n    description: Path of the project's Derived Data folder. Supports glob patterns.\n    is_required: false\n    summary: Path of the project's Derived Data folder.\n    title: Derived Data Path\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: false\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Xcode Project path. Used to automatically find Derived Data path, only\n      when `Derived Data Path` is empty (not provided).\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-spm-cache/1.3.2/step.yml",
    "content": "title: Save SPM Cache\nsummary: Saves Swift Package Manager dependency cache. This Step needs to be used\n  in combination with **Restore SPM Cache**.\ndescription: |\n  Saves Swift Package Manager dependency cache. This Step needs to be used in combination with **Restore SPM Cache**.\n\n  This Step is based on [key-based caching](https://devcenter.bitrise.io/en/builds/caching/key-based-caching.html) and sets up the cache key and path automatically for SPM dependencies. If you'd like to change the cache key (or paths to cache), you might want to use the generic [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache) Step instead.\n\n  #### Related steps\n\n  [Restore SPM cache](https://github.com/bitrise-steplib/bitrise-step-restore-spm-cache/)\n\n  [Save cache](https://github.com/bitrise-steplib/bitrise-step-save-cache/)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache/issues\npublished_at: 2025-11-12T08:36:19.537412422Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-save-spm-cache.git\n  commit: 400c2401d07f244802463b7e5513bb04eedb18bf\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-save-spm-cache\ndeps:\n  brew:\n  - name: zstd\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- derived_data_path: ~/Library/Developer/Xcode/DerivedData/**\n  opts:\n    description: Path of the project's Derived Data folder. Supports glob patterns.\n    is_required: false\n    summary: Path of the project's Derived Data folder.\n    title: Derived Data Path\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: false\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Xcode Project path. Used to automatically find Derived Data path, only\n      when `Derived Data Path` is empty (not provided).\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    is_required: true\n    summary: Enable logging additional information for troubleshooting\n    title: Verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n- compression_level: 3\n  opts:\n    is_required: false\n    summary: Zstd compression level to control speed / archive size. Set to 1 for\n      fastest option. Valid values are between 1 and 19. Defaults to 3.\n    title: Compression level\n"
  },
  {
    "path": "steps/save-spm-cache/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/scan-with-appsweep/1.0.0/step.yml",
    "content": "title: AppSweep Mobile Security Testing\nsummary: Scan your Android app using Guardsquare's mobile application security testing tool AppSweep\ndescription: \"The build of your app is automatically uploaded to [AppSweep](https://appsweep.guardsquare.com)\n  for scanning. \\n\\nAppSweep is Guardsquare's free tool enabling developers to put\n  mobile security at the forefront of app development. AppSweep helps you identify\n  and fix security issues in your code and dependencies with actionable recommendations\n  and insights that will help you build more secure mobile apps.\"\nwebsite: https://www.guardsquare.com/appsweep-mobile-application-security-testing\nsource_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep\nsupport_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues\npublished_at: 2022-01-19T13:15:42.006047158+01:00\nsource:\n  git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git\n  commit: 74d0913911c69563ddb08b86887fbbce721c1745\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- appsweep_api_key: $APPSWEEP_API_KEY\n  opts:\n    description: |\n      An `APPSWEEP_API_KEY` must be set to allow scanning of the app inside an AppSweep project. You can generate it in the API Keys section of your project settings.\n    is_required: true\n    is_sensitive: true\n    title: AppSweep API key\n- build_variant: release\n  opts:\n    description: |\n      Set to `debug` to upload the debug version of your app, or to `release` to upload the release version.\n    is_required: true\n    title: Select the build variant which should be uploaded\n    value_options:\n    - debug\n    - release\n- opts:\n    description: |\n      Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.\n    is_required: true\n    title: Project file path\n  project_location: $PROJECT_LOCATION\n- gradle_plugin_version: 1.0.0\n  opts:\n    description: |\n      The version of AppSweep gradle plugin. Can be set to particular numerical value or to `latest.release`, which requires at least Gradle 7.\n    is_required: true\n    title: AppSweep gradle plugin version\noutputs:\n- APPSWEEP_UPLOAD_URL: null\n  opts:\n    description: |\n      This URL of a particular scan is generated during the execution of this step, the results of the scan can be accessed in AppSweep directly via this URL.\n    summary: Direct link to the scan results on AppSweep website\n    title: AppSweep upload URL\n"
  },
  {
    "path": "steps/scan-with-appsweep/2.0.0/step.yml",
    "content": "title: AppSweep Mobile Security Testing\nsummary: Scan your app using Guardsquare's mobile application security testing tool\n  AppSweep\ndescription: \"The build of your app is automatically uploaded to [AppSweep](https://appsweep.guardsquare.com)\n  for scanning. \\n\\nAppSweep is Guardsquare's free tool enabling developers to put\n  mobile security at the forefront of app development. AppSweep helps you identify\n  and fix security issues in your code and dependencies with actionable recommendations\n  and insights that will help you build more secure mobile apps.\"\nwebsite: https://www.guardsquare.com/appsweep-mobile-application-security-testing\nsource_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep\nsupport_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues\npublished_at: 2024-02-16T13:44:39.510838434+01:00\nsource:\n  git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git\n  commit: ec957a0853dc8ee70d9e383645e40f4ec27b41d7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- ios\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- appsweep_api_key: $APPSWEEP_API_KEY\n  opts:\n    description: |\n      An `APPSWEEP_API_KEY` must be set to allow scanning of the app inside an AppSweep project. You can generate it in the API Keys section of your project settings.\n    is_required: true\n    is_sensitive: true\n    title: AppSweep API key\n- ios_archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    category: iOS\n    description: |\n      AppSweep works with both, an IPA file or an xcarchive directory. This has to be set if you want to analyze iOS builds.\n    is_required: false\n    title: The path of the iOS archive (IPA file or xcarchive directory)\n- ios_dsyms_dir_path: $BITRISE_DSYM_DIR_PATH\n  opts:\n    category: iOS\n    description: |\n      Should the archive not include debug symbols, it is possible to pass in the path to the dSYM directory explicitly. Lacking debug symbols prevents AppSweep from performing an in-depth analysis.\n    is_required: false\n    title: The path of the dSYM directory.\n- build_variant: release\n  opts:\n    category: Android\n    description: |\n      Set to `debug` to upload the debug version of your app, or to `release` to upload the release version.\n    is_required: false\n    title: Select the build variant which should be uploaded\n    value_options:\n    - debug\n    - release\n- opts:\n    category: Android\n    description: |\n      Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.\n    is_required: false\n    title: Project file path\n  project_location: $PROJECT_LOCATION\n- gradle_plugin_version: 1.0.0\n  opts:\n    category: Android\n    description: |\n      The version of AppSweep gradle plugin. Can be set to particular numerical value or to `latest.release`, which requires at least Gradle 7.\n    is_required: true\n    title: AppSweep gradle plugin version\noutputs:\n- APPSWEEP_UPLOAD_URL: null\n  opts:\n    description: |\n      This URL of a particular scan is generated during the execution of this step, the results of the scan can be accessed in AppSweep directly via this URL.\n    summary: Direct link to the scan results on AppSweep website\n    title: AppSweep upload URL\n"
  },
  {
    "path": "steps/scan-with-appsweep/2.0.2/step.yml",
    "content": "title: AppSweep Mobile Security Testing\nsummary: Scan your app using Guardsquare's mobile application security testing tool\n  AppSweep\ndescription: \"The build of your app is automatically uploaded to [AppSweep](https://appsweep.guardsquare.com)\n  for scanning. \\n\\nAppSweep is Guardsquare's free tool enabling developers to put\n  mobile security at the forefront of app development. AppSweep helps you identify\n  and fix security issues in your code and dependencies with actionable recommendations\n  and insights that will help you build more secure mobile apps.\"\nwebsite: https://www.guardsquare.com/appsweep-mobile-application-security-testing\nsource_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep\nsupport_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues\npublished_at: 2024-04-10T15:30:54.718315675+02:00\nsource:\n  git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git\n  commit: 23e4d3606877ebc892fb73b935017c603c7fa2c8\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- ios\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- appsweep_api_key: $APPSWEEP_API_KEY\n  opts:\n    description: |\n      An `APPSWEEP_API_KEY` must be set to allow scanning of the app inside an AppSweep project. You can generate it in the API Keys section of your project settings.\n    is_required: true\n    is_sensitive: true\n    title: AppSweep API key\n- ios_archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    category: iOS\n    description: |\n      AppSweep works with both, an IPA file or an xcarchive directory. This has to be set if you want to analyze iOS builds.\n    is_required: false\n    title: The path of the iOS archive (IPA file or xcarchive directory)\n- ios_dsyms_dir_path: $BITRISE_DSYM_DIR_PATH\n  opts:\n    category: iOS\n    description: |\n      Should the archive not include debug symbols, it is possible to pass in the path to the dSYM directory explicitly. Lacking debug symbols prevents AppSweep from performing an in-depth analysis.\n    is_required: false\n    title: The path of the dSYM directory.\n- build_variant: release\n  opts:\n    category: Android\n    description: |\n      Set to the desired build variant, e.g. `debug`. By default, the `release` variant will be uploaded.\n    is_required: false\n    title: Select the build variant which should be uploaded\n- opts:\n    category: Android\n    description: |\n      Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.\n    is_required: false\n    title: Project file path\n  project_location: $PROJECT_LOCATION\n- gradle_plugin_version: 1.0.0\n  opts:\n    category: Android\n    description: |\n      The version of AppSweep gradle plugin. Can be set to particular numerical value or to `latest.release`, which requires at least Gradle 7.\n    is_required: true\n    title: AppSweep gradle plugin version\noutputs:\n- APPSWEEP_UPLOAD_URL: null\n  opts:\n    description: |\n      This URL of a particular scan is generated during the execution of this step, the results of the scan can be accessed in AppSweep directly via this URL.\n    summary: Direct link to the scan results on AppSweep website\n    title: AppSweep upload URL\n"
  },
  {
    "path": "steps/scan-with-appsweep/3.0.0/step.yml",
    "content": "title: AppSweep Mobile Security Testing\nsummary: Scan your app using Guardsquare's mobile application security testing tool\n  AppSweep\ndescription: \"The build of your Android or iOS app is automatically uploaded to [AppSweep](https://appsweep.guardsquare.com)\n  for scanning. \\n\\nAppSweep is Guardsquare's free tool enabling developers to put\n  mobile security at the forefront of app development. AppSweep helps you identify\n  and fix security issues in your code and dependencies with actionable recommendations\n  and insights that will help you build more secure mobile apps.\"\nwebsite: https://www.guardsquare.com/appsweep-mobile-application-security-testing\nsource_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep\nsupport_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues\npublished_at: 2025-02-04T08:40:54.61564+01:00\nsource:\n  git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git\n  commit: c7e0e6f16b8876d05ddfb0680b1041cab5f3dcb2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- ios\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- appsweep_api_key: $APPSWEEP_API_KEY\n  opts:\n    description: |\n      An `APPSWEEP_API_KEY` must be set to allow scanning of the app inside an AppSweep project. You can generate it in the API Keys section of your app settings inside AppSweep.\n    is_required: true\n    is_sensitive: true\n    title: AppSweep API key\n- commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    description: |\n      The commit for this build. This commit will be associated with the app scan.\n    title: Git commit hash\n- ios_archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    category: iOS\n    description: |\n      AppSweep works with both, an IPA file or an xcarchive directory. This has to be set if you want to analyze iOS builds.\n    is_required: false\n    title: The path of the iOS archive\n- ios_dsyms_dir_path: $BITRISE_DSYM_DIR_PATH\n  opts:\n    category: iOS\n    description: |\n      Should the archive not include debug symbols, it is possible to pass in the path to the dSYM directory explicitly. Lacking debug symbols prevents AppSweep from performing an in-depth analysis.\n    is_required: false\n    title: The path of the dSYM directory.\n- android_app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      Path name to the built app. Can be an Android apk / aab.\n    is_required: false\n    title: The path of the Android app\n- android_mappingfile_path: null\n  opts:\n    category: Android\n    description: |\n      Path to the obfuscation mapping file. E.g., ./app/build/outputs/mapping/debug/mapping.txt\n    is_required: false\n    title: The path to the obfuscation mapping file\n- android_project_location: $PROJECT_LOCATION\n  opts:\n    category: Android\n    description: |\n      Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.\n    is_required: false\n    title: Project file path\noutputs:\n- APPSWEEP_UPLOAD_URL: null\n  opts:\n    description: |\n      This URL of a particular scan is generated during the execution of this step, the results of the scan can be accessed in AppSweep directly via this URL.\n    summary: Direct link to the scan results on AppSweep website\n    title: AppSweep upload URL\n"
  },
  {
    "path": "steps/scan-with-appsweep/3.0.1/step.yml",
    "content": "title: AppSweep Mobile Security Testing\nsummary: Scan your app using Guardsquare's mobile application security testing tool\n  AppSweep\ndescription: \"The build of your Android or iOS app is automatically uploaded to [AppSweep](https://appsweep.guardsquare.com)\n  for scanning. \\n\\nAppSweep is Guardsquare's free tool enabling developers to put\n  mobile security at the forefront of app development. AppSweep helps you identify\n  and fix security issues in your code and dependencies with actionable recommendations\n  and insights that will help you build more secure mobile apps.\"\nwebsite: https://www.guardsquare.com/appsweep-mobile-application-security-testing\nsource_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep\nsupport_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues\npublished_at: 2025-03-07T11:53:23.652163+01:00\nsource:\n  git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git\n  commit: af6daeb73c79e4cae73966a9f3b6e9c0a0fcf8e7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- ios\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- appsweep_api_key: $APPSWEEP_API_KEY\n  opts:\n    description: |\n      An `APPSWEEP_API_KEY` must be set to allow scanning of the app inside an AppSweep project. You can generate it in the API Keys section of your app settings inside AppSweep.\n    is_required: true\n    is_sensitive: true\n    summary: The AppSweep API key to use for the scan.\n    title: AppSweep API key\n- commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    description: |\n      The commit for this build. This commit will be associated with the app scan.\n    summary: The commit hash to show in AppSweep for the scan.\n    title: Git commit hash\n- ios_archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    category: iOS\n    description: |\n      AppSweep works with both, an IPA file or an xcarchive directory. This has to be set if you want to analyze iOS builds.\n    is_required: false\n    summary: The iOS app (IPA or xcarchive file) to scan.\n    title: The path of the iOS archive\n- ios_dsyms_dir_path: $BITRISE_DSYM_DIR_PATH\n  opts:\n    category: iOS\n    description: |\n      Should the archive not include debug symbols, it is possible to pass in the path to the dSYM directory explicitly. Lacking debug symbols prevents AppSweep from performing an in-depth analysis.\n    is_required: false\n    summary: The path to the directory of additional dSYM files to use.\n    title: The path of the dSYM directory.\n- android_app_path: $BITRISE_APK_PATH\n  opts:\n    category: Android\n    description: |\n      Path name to the built app. Can be an Android apk / aab.\n    is_required: false\n    summary: The Android app (apk or aab file) to scan.\n    title: The path of the Android app\n- android_mappingfile_path: null\n  opts:\n    category: Android\n    description: |\n      Path to the obfuscation mapping file. E.g., ./app/build/outputs/mapping/debug/mapping.txt\n    is_required: false\n    summary: The path to the obfuscation mapping file.\n    title: The path to the obfuscation mapping file\n- android_project_location: $PROJECT_LOCATION\n  opts:\n    category: Android\n    description: |\n      Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.\n    is_required: false\n    summary: The file path to your project inside your repository.\n    title: Project file path\noutputs:\n- APPSWEEP_UPLOAD_URL: null\n  opts:\n    description: |\n      This URL of a particular scan is generated during the execution of this step, the results of the scan can be accessed in AppSweep directly via this URL.\n    summary: Direct link to the scan results on AppSweep website\n    title: AppSweep upload URL\n"
  },
  {
    "path": "steps/scan-with-appsweep/3.1.1/step.yml",
    "content": "title: AppSweep Mobile Security Testing\nsummary: Scan your app using Guardsquare's mobile application security testing tool\n  AppSweep\ndescription: \"The build of your Android or iOS app is automatically uploaded to [AppSweep](https://appsweep.guardsquare.com)\n  for scanning. \\n\\nAppSweep is Guardsquare's free tool enabling developers to put\n  mobile security at the forefront of app development. AppSweep helps you identify\n  and fix security issues in your code and dependencies with actionable recommendations\n  and insights that will help you build more secure mobile apps.\"\nwebsite: https://www.guardsquare.com/appsweep-mobile-application-security-testing\nsource_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep\nsupport_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues\npublished_at: 2026-01-20T13:56:16.328909+01:00\nsource:\n  git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git\n  commit: 5f26ffd0a1e92fdbd5e33d7326f4f8acec65dbf2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- ios\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\ninputs:\n- appsweep_api_key: $APPSWEEP_API_KEY\n  opts:\n    description: |\n      An `APPSWEEP_API_KEY` can be set to authenticate and associate an AppSweep app. You can generate it in the API Keys section of your app settings inside AppSweep. If this is not set, ssh-agent authentication needs to be enable\n    is_sensitive: true\n    summary: The AppSweep API key to use for the scan. Alternatively, you can configure\n      ssh-agent authentication which will then be picked up automatically.\n    title: AppSweep API key\n- commit_hash: $GIT_CLONE_COMMIT_HASH\n  opts:\n    description: |\n      The commit for this build. This commit will be associated with the app scan.\n    summary: The commit hash to show in AppSweep for the scan.\n    title: Git commit hash\n- ios_archive_path: $BITRISE_XCARCHIVE_PATH\n  opts:\n    category: iOS\n    description: |\n      AppSweep works with both, an IPA file or an xcarchive directory. This has to be set if you want to analyze iOS builds.\n    is_required: false\n    summary: The iOS app (IPA or xcarchive file) to scan.\n    title: The path of the iOS archive\n- ios_dsyms_dir_path: $BITRISE_DSYM_DIR_PATH\n  opts:\n    category: iOS\n    description: |\n      Should the archive not include debug symbols, it is possible to pass in the path to the dSYM directory explicitly. Lacking debug symbols prevents AppSweep from performing an in-depth analysis.\n    is_required: false\n    summary: The path to the directory of additional dSYM files to use.\n    title: The path of the dSYM directory.\n- android_app_path: $BITRISE_APK_PATH\n  opts:\n    category: Android\n    description: |\n      Path name to the built app. Can be an Android apk / aab.\n    is_required: false\n    summary: The Android app (apk or aab file) to scan.\n    title: The path of the Android app\n- android_mappingfile_path: null\n  opts:\n    category: Android\n    description: |\n      Path to the obfuscation mapping file. E.g., ./app/build/outputs/mapping/debug/mapping.txt\n    is_required: false\n    summary: The path to the obfuscation mapping file.\n    title: The path to the obfuscation mapping file\n- android_project_location: $PROJECT_LOCATION\n  opts:\n    category: Android\n    description: |\n      Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.\n    is_required: false\n    summary: The file path to your project inside your repository.\n    title: Project file path\noutputs:\n- APPSWEEP_UPLOAD_URL: null\n  opts:\n    description: |\n      This URL of a particular scan is generated during the execution of this step, the results of the scan can be accessed in AppSweep directly via this URL.\n    summary: Direct link to the scan results on AppSweep website\n    title: AppSweep upload URL\n"
  },
  {
    "path": "steps/scan-with-appsweep/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/script/0.9.0/step.yml",
    "content": "title: \"Script\"\nsummary: The power is in your hands. Use it wisely!\ndescription: |\n  Specify the script content and (optionally) the script runner\n  binary and this step will execute it.\n\n  The *runner* can even be a command, if it's available in the PATH\n  and can execute the script it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n      package main\n      import \"fmt\"\n      func main() {\n          fmt.Println(\"hello world\")\n      }\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a .go extension (just specify `step.go` as the script path).\n\n  If the `go` binary can be found in the PATH your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\npublished_at: 2015-08-17T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: 28c5ba4f81162fbd7f9484c9fb26711f5d27cb1c\nhost_os_tags:\n  - osx-10.10\nproject_type_tags: []\ntype_tags:\n  - script\nis_requires_admin_user: true\ninputs:\n- content: |\n    #!/bin/bash\n    echo \"Welcome to Bitrise!!\"\n  opts:\n    title: \"Script content\"\n    description: |\n      Type your script here.\n    is_expand: false\n    is_required: true\n- runner_bin: \"/bin/bash\"\n  opts:\n    title: \"Execute with / runner binary\"\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_expand: false\n    is_required: true\n- is_debug: \"no\"\n  opts:\n    title: \"Debug?\"\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    value_options:\n        - \"no\"\n        - \"yes\"\n    is_expand: false\n    is_required: false\n- working_dir: \"\"\n  opts:\n    title: \"Working directory\"\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    is_expand: true\n    is_required: false\n- script_file_path: \"\"\n  opts:\n    title: \"Script file path\"\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optinally specify as well).\n    is_expand: true\n    is_required: false\n"
  },
  {
    "path": "steps/script/0.9.1/step.yml",
    "content": "title: Generic Script Runner\ndescription: |-\n  Specify the script content and (optionally) the script runner\n  binary and this step will execute it.\n\n  The *runner* can even be a command, if it's available in the PATH\n  and can execute the script it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n      package main\n      import \"fmt\"\n      func main() {\n          fmt.Println(\"hello world\")\n      }\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a .go extension (just specify `step.go` as the script path).\n\n  If the `go` binary can be found in the PATH your Hello World\n  script will run without any problem.\nsummary: |-\n  The power is in your hands. Use it wisely!\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2015-08-18T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: 3b6857b016aa021cd5c86c78b54681679f996fc7\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n\n    echo \"Hello Bitrise!\"\n  opts:\n    description: |\n      Type your script here.\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_expand: false\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    is_expand: false\n    is_required: false\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optinally specify as well).\n    is_expand: true\n    is_required: false\n    title: Script file path\n  script_file_path: null\n"
  },
  {
    "path": "steps/script/1.0.0/step.yml",
    "content": "title: Script\nsummary: |-\n  The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner\n  binary and this step will execute it.\n\n  The *runner* can even be a command, if it's available in the PATH\n  and can execute the script it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n      package main\n      import \"fmt\"\n      func main() {\n          fmt.Println(\"hello world\")\n      }\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a .go extension (just specify `step.go` as the script path).\n\n  If the `go` binary can be found in the PATH your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2015-09-23T11:01:34.159018061+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: e5789cf626ea17901b0d86cac88d82d49f0a9fb8\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n\n    echo \"Hello Bitrise!\"\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_expand: false\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    is_expand: false\n    is_required: false\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optinally specify as well).\n    is_expand: true\n    is_required: false\n    title: Script file path\n  script_file_path: null\n"
  },
  {
    "path": "steps/script/1.1.0/step.yml",
    "content": "title: Script\nsummary: The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner\n  binary and this step will execute it.\n\n  The *runner* can even be a command, if it's available in the PATH\n  and can execute the script it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n      package main\n      import \"fmt\"\n      func main() {\n          fmt.Println(\"hello world\")\n      }\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a .go extension (just specify `step.go` as the script path).\n\n  If the `go` binary can be found in the PATH your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2015-10-14T16:50:36.159715639+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: c1ab0707c383b5ff3a8e0d76c1c57f9fb86acf21\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- script\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n\n    echo \"Hello Bitrise!\"\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_expand: false\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    is_expand: false\n    is_required: false\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  working_dir: null\n- opts:\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optinally specify as well).\n    is_expand: true\n    is_required: false\n    title: Script file path\n  script_file_path: null\n"
  },
  {
    "path": "steps/script/1.1.1/step.yml",
    "content": "title: Script\nsummary: The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner,\n  to run any custom script in your [bitrise.io](https://www.bitrise.io/) workflow!\n\n  The **runner** can even be a command, as long as it's available in the `PATH`\n  and can execute the script, it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n  ```\n  package main\n  import \"fmt\"\n  func main() {\n      fmt.Println(\"Hello World\")\n  }\n  ```\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a `.go` extension (just specify `main.go` or `step.go` as the script path).\n\n  If the `go` binary can be found in the `$PATH` your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2016-06-09T14:01:30.316345844+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: e6e761292648d6a8f2c7092499d8aebca4620d3e\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- script\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n    # fail if any commands fails\n    set -e\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    title: Working directory\n  working_dir: \"\"\n- opts:\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optinally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n"
  },
  {
    "path": "steps/script/1.1.2/step.yml",
    "content": "title: Script\nsummary: The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner,\n  to run any custom script in your [bitrise.io](https://www.bitrise.io/) workflow!\n\n  The **runner** can even be a command, as long as it's available in the `PATH`\n  and can execute the script, it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n  ```\n  package main\n  import \"fmt\"\n  func main() {\n      fmt.Println(\"Hello World\")\n  }\n  ```\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a `.go` extension (just specify `main.go` or `step.go` as the script path).\n\n  If the `go` binary can be found in the `$PATH` your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2016-07-30T14:02:21.667258567+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: 562ca4e7f05c8edba0545c0850bff90bd058b327\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- script\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n    # fail if any commands fails\n    set -e\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    title: Working directory\n  working_dir: \"\"\n- opts:\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optinally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n"
  },
  {
    "path": "steps/script/1.1.3/step.yml",
    "content": "title: Script\nsummary: The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner,\n  to run any custom script in your [bitrise.io](https://www.bitrise.io/) workflow!\n\n  The **runner** can even be a command, as long as it's available in the `PATH`\n  and can execute the script, it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n  ```\n  package main\n  import \"fmt\"\n  func main() {\n      fmt.Println(\"Hello World\")\n  }\n  ```\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a `.go` extension (just specify `main.go` or `step.go` as the script path).\n\n  If the `go` binary can be found in the `$PATH` your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2016-09-07T07:24:54.977963479+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: c97f55274de863faa9b1b45e3563c17e779338cd\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n    # fail if any commands fails\n    set -e\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- is_debug: \"no\"\n  opts:\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug?\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n    title: Working directory\n  working_dir: \"\"\n- opts:\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optionally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n"
  },
  {
    "path": "steps/script/1.1.4/step.yml",
    "content": "title: Script\nsummary: The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner,\n  to run any custom script in your [bitrise.io](https://www.bitrise.io/) workflow!\n\n  The **runner** can even be a command, as long as it's available in the `PATH`\n  and can execute the script, it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n  ```\n  package main\n  import \"fmt\"\n  func main() {\n      fmt.Println(\"Hello World\")\n  }\n  ```\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a `.go` extension (just specify `main.go` or `step.go` as the script path).\n\n  If the `go` binary can be found in the `$PATH` your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2017-06-09T17:24:33.479151912+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: 71be038fcd810a17514c39e94b86d14ed997dcac\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/bin/bash\n    # fail if any commands fails\n    set -e\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    category: Config\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- opts:\n    category: Config\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n\n      Any relative path in the Script (content) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optionally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script/1.1.5/step.yml",
    "content": "title: Script\nsummary: The power is in your hands. Use it wisely!\ndescription: |-\n  Specify the script content and (optionally) the script runner,\n  to run any custom script in your [bitrise.io](https://www.bitrise.io/) workflow!\n\n  The **runner** can even be a command, as long as it's available in the `PATH`\n  and can execute the script, it will work.\n\n  For example to run a [Go](https://golang.org/) Hello World \"script\"\n  you can define the content:\n\n  ```\n  package main\n  import \"fmt\"\n  func main() {\n      fmt.Println(\"Hello World\")\n  }\n  ```\n\n  Set the *Execute with* parameter to `go run` and specify\n  a *script file path* because `go run` can only accept (at the moment)\n  files with a `.go` extension (just specify `main.go` or `step.go` as the script path).\n\n  If the `go` binary can be found in the `$PATH` your Hello World\n  script will run without any problem.\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2017-10-27T15:11:04.97198177+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-script.git\n  commit: b8dd4ca6839dfeb34c4637dde402f86414135b5f\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/usr/bin/env bash\n    # fail if any commands fails\n    set -e\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    category: Config\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- opts:\n    category: Config\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n\n      Any relative path in the Script (content) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optionally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script/1.1.6/step.yml",
    "content": "title: Script\nsummary: Run any custom script you want. The power is in your hands. Use it wisely!\ndescription: \"\\nRun any custom script you want as part of your Bitrise build. All\n  you need to do is specifying the script runner  \\n(the default is bash), add the\n  script, and run a build. \\n\\nYou can also read the script from a file.\\n\\n### Configuring\n  the Step\\n\\n1. Set the **Execute with/runner binary** input.\\n\\n   Either define\n  the path of the executor, or simply just add its name if you know it is available\n  in the PATH, such as `ruby` or `python`. It can even be a command, such as `go run`.\n  \\ \\n\\n1. Write your script in the **Script content** input or specify a script file.\\n\\n\n  \\  If you have a script in your repository, you can simply run it from the file,\n  either by calling it in the **Script content** input  \\n   or, optionally, by specifying\n  the path to it in the **Script file path** input. \\n   \\n   Be aware that relative\n  paths are relative to the value set in the **Working directory** input - by default,\n  it is your app's source directory.\\n\\n### Troubleshooting\\n\\nIf the script fails,\n  check the executor first - obviously, a Python script will not work with a bash\n  runner.\\n\\nNote that in certain cases, the filename or the filepath actually matters.\n  For example, the `go run` command only accepts `.go` files.\\n\\n### Useful links\\n\\n*\n  [System reports to check out the pre-installed executors](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\\n*\n  [Exporting to Test Reports from custom Script Steps](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\\n\\n###\n  Related Steps\\n\\n* [Script Runner](https://www.bitrise.io/integrations/steps/script-runner)\\n*\n  [Remote Bash Script Runner](https://www.bitrise.io/integrations/steps/remote-script-runner)\"\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2020-01-16T10:07:50.157726891Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-script.git\n  commit: 21279bc046fe10e7a71cca2ef76d2f921f2fae2b\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/usr/bin/env bash\n    # fail if any commands fails\n    set -e\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    category: Config\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- opts:\n    category: Config\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n\n      Any relative path in the Script (content) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optionally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script/1.2.0/step.yml",
    "content": "title: Script\nsummary: Run any custom script you want. The power is in your hands. Use it wisely!\ndescription: \"\\nRun any custom script you want as part of your Bitrise build. All\n  you need to do is specifying the script runner  \\n(the default is bash), add the\n  script, and run a build. \\n\\nYou can also read the script from a file.\\n\\n### Configuring\n  the Step\\n\\n1. Set the **Execute with/runner binary** input.\\n\\n   Either define\n  the path of the executor, or simply just add its name if you know it is available\n  in the PATH, such as `ruby` or `python`. It can even be a command, such as `go run`.\n  \\ \\n\\n1. Write your script in the **Script content** input or specify a script file.\\n\\n\n  \\  If you have a script in your repository, you can simply run it from the file,\n  either by calling it in the **Script content** input  \\n   or, optionally, by specifying\n  the path to it in the **Script file path** input. \\n   \\n   Be aware that relative\n  paths are relative to the value set in the **Working directory** input - by default,\n  it is your app's source directory.\\n\\n### Troubleshooting\\n\\nIf the script fails,\n  check the executor first - obviously, a Python script will not work with a bash\n  runner.\\n\\nNote that in certain cases, the filename or the filepath actually matters.\n  For example, the `go run` command only accepts `.go` files.\\n\\n### Useful links\\n\\n*\n  [System reports to check out the pre-installed executors](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\\n*\n  [Exporting to Test Reports from custom Script Steps](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\\n\\n###\n  Related Steps\\n\\n* [Script Runner](https://www.bitrise.io/integrations/steps/script-runner)\\n*\n  [Remote Bash Script Runner](https://www.bitrise.io/integrations/steps/remote-script-runner)\"\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2022-04-22T07:43:22.121803717Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-script.git\n  commit: 61461540896930c04d0d56dbfd2c9a3a72378ef4\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/usr/bin/env bash\n    # fail if any commands fails\n    set -e\n    # make pipelines' return status equal the last command to exit with a non-zero status, or zero if all commands exit successfully\n    set -o pipefail\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    category: Config\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- opts:\n    category: Config\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n\n      Any relative path in the Script (content) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optionally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script/1.2.1/step.yml",
    "content": "title: Script\nsummary: Run any custom script you want. The power is in your hands. Use it wisely!\ndescription: \"\\nRun any custom script you want as part of your Bitrise build. All\n  you need to do is specifying the script runner  \\n(the default is bash), add the\n  script, and run a build. \\n\\nYou can also read the script from a file.\\n\\n### Configuring\n  the Step\\n\\n1. Set the **Execute with/runner binary** input.\\n\\n   Either define\n  the path of the executor, or simply just add its name if you know it is available\n  in the PATH, such as `ruby` or `python`. It can even be a command, such as `go run`.\n  \\ \\n\\n1. Write your script in the **Script content** input or specify a script file.\\n\\n\n  \\  If you have a script in your repository, you can simply run it from the file,\n  either by calling it in the **Script content** input  \\n   or, optionally, by specifying\n  the path to it in the **Script file path** input. \\n   \\n   Be aware that relative\n  paths are relative to the value set in the **Working directory** input - by default,\n  it is your app's source directory.\\n\\n### Troubleshooting\\n\\nIf the script fails,\n  check the executor first - obviously, a Python script will not work with a bash\n  runner.\\n\\nNote that in certain cases, the filename or the filepath actually matters.\n  For example, the `go run` command only accepts `.go` files.\\n\\n### Useful links\\n\\n*\n  [System reports to check out the pre-installed executors](https://stacks.bitrise.io)\\n*\n  [Exporting to Test Reports from custom Script Steps](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)\\n\\n###\n  Related Steps\\n\\n* [Script Runner](https://www.bitrise.io/integrations/steps/script-runner)\\n*\n  [Remote Bash Script Runner](https://www.bitrise.io/integrations/steps/remote-script-runner)\"\nwebsite: https://github.com/bitrise-io/steps-script\nsource_code_url: https://github.com/bitrise-io/steps-script\nsupport_url: https://github.com/bitrise-io/steps-script/issues\npublished_at: 2023-09-18T13:21:55.992180288Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-script.git\n  commit: 48d256c50746e2625a25cb7499bc22c62e04cf71\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- content: |-\n    #!/usr/bin/env bash\n    # fail if any commands fails\n    set -e\n    # make pipelines' return status equal the last command to exit with a non-zero status, or zero if all commands exit successfully\n    set -o pipefail\n    # debug log\n    set -x\n\n    # write your script here\n    echo \"Hello World!\"\n\n    # or run a script from your repository, like:\n    # bash ./path/to/script.sh\n    # not just bash, e.g.:\n    # ruby ./path/to/script.rb\n  opts:\n    description: |\n      Type your script here.\n\n      **Make sure that it returns a non zero exit code in case of an error!**\n      The step will only fail if your script returns with a non zero exit code!\n    is_expand: false\n    is_required: true\n    title: Script content\n- opts:\n    category: Config\n    description: |\n      The executor to be used for running the script.\n      If it's available in the PATH you can just\n      specify `ruby` or `python`, generally\n      if you know the path of the executor you should\n      define that, like `/bin/bash`.\n\n      You can even specify an execution command\n      like `go run` instead of just a binary.\n    is_required: true\n    title: Execute with / runner binary\n  runner_bin: /bin/bash\n- opts:\n    category: Config\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n\n      Any relative path in the Script (content) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Config\n    description: |\n      Save the specified script content to this path\n      before execution. The file will be removed after\n      the script finishes.\n\n      Generally you don't have to define this but\n      there might be cases where the file's name or path\n      actually matters.\n      For example `go run` only accepts `.go` files.\n\n      If you specify a relative path then it will be\n      relative to the *working directory* (which you\n      can optionally specify as well).\n    title: Script file path\n  script_file_path: \"\"\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/script-runner/0.9.2/step.yml",
    "content": "title: Script Runner\nsummary: |\n  Run scripts from file\ndescription: |\n  Run scripts from file\nwebsite: https://github.com/bitrise-steplib/steps-script-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-script-runner\nsupport_url: https://github.com/bitrise-steplib/steps-script-runner/issues\npublished_at: 2017-09-01T12:26:19.233850492+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-script-runner.git\n  commit: 9ebce1ae85d29b54e8da066aab26bed414273d41\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-script-runner\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: null\n  opts:\n    description: |\n      The script you want to run.\n    is_expand: true\n    is_required: true\n    title: Script location\n- opts:\n    description: \"The executor to be used for running the script.\\nYou can use any\n      binary which is in the PATH (bash/ruby/etc.), \\nmultipart commands (e. g. go\n      run), absolut paths (e. g. /bin/sh) \\nor binaries from env (e. g. /usr/bin/env\n      python). You can \\nspecify flags as well (e. g. /bin/bash -l).\\n\"\n    is_required: true\n    title: Execute with / runner binary\n  runner: bash\n- opts:\n    category: Debug\n    description: |\n      This directory will be set as the current working\n      directory for the script.\n      Any relative path in the Script (file_path) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script-runner/0.9.3/step.yml",
    "content": "title: Script Runner\nsummary: |\n  Run scripts from file\ndescription: |\n  Run scripts from file\nwebsite: https://github.com/bitrise-steplib/steps-script-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-script-runner\nsupport_url: https://github.com/bitrise-steplib/steps-script-runner/issues\npublished_at: 2017-09-29T16:31:56.22439+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-script-runner.git\n  commit: 0e0fc3483b271c45d4e321ddc2a68e9e92593399\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-script-runner\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: null\n  opts:\n    description: The script you want to run.\n    is_expand: true\n    is_required: true\n    title: Script location\n- opts:\n    description: \"The executor to be used for running the script.\\nYou can use any\n      binary which is in the PATH (bash/ruby/etc.), \\nmultipart commands (e. g. go\n      run), absolute paths (e. g. /bin/sh) \\nor binaries from env (e. g. /usr/bin/env\n      python). You can \\nspecify flags as well (e. g. /bin/bash -l).\"\n    is_required: true\n    title: Execute with / runner binary\n  runner: bash\n- opts:\n    category: Debug\n    description: |-\n      This directory will be set as the current working\n      directory for the script.\n      Any relative path in the Script (file_path) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |-\n      If debug=yes the step will print debug infos about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script-runner/0.9.4/step.yml",
    "content": "title: Script Runner\nsummary: |\n  Run scripts from a file\ndescription: |\n  The Step runs a script from a file using a specified executor. It provides great flexibility and lets you run any file written in any scripting language, such as Bash, Ruby, PHP, Python, etc.\n\n  ### Configuring the Step\n\n  1. Choose a script to run by specifying its location and name in the **Script location** input. For example, if you have a `script.py` in your root directory, you could put in: `$BITRISE_SOURCE_DIR/script.py`.\n  1. Specify which executor to use for the script in the **Execute with / runner binary** input.\n  1. (Optional) Under the **Debug** tab, you can specify a working directory for the script in the **Working directory** input and enable debug logging in the **Debug print?** input.\n\n  ### Related Steps\n\n  * [Script](https://www.bitrise.io/integrations/steps/script)\n  * [Remote Bash Script Runner](https://www.bitrise.io/integrations/steps/remote-script-runner)\n  * [Ruby Script runner with optional Gemfile support](https://www.bitrise.io/integrations/steps/ruby-script)\nwebsite: https://github.com/bitrise-steplib/steps-script-runner\nsource_code_url: https://github.com/bitrise-steplib/steps-script-runner\nsupport_url: https://github.com/bitrise-steplib/steps-script-runner/issues\npublished_at: 2024-02-07T13:52:31.830308428Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-script-runner.git\n  commit: 0f349f3f7721163395d75b3ec8263a30cdecfc69\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-script-runner\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- file_path: null\n  opts:\n    description: The script you want to run.\n    is_expand: true\n    is_required: true\n    title: Script location\n- opts:\n    description: |-\n      The executor to be used for running the script.\n      You can use any binary which is in the PATH (bash/ruby/etc.),\n      multipart commands (e. g. go run), absolute paths (e. g. /bin/sh)\n      or binaries from env (e. g. /usr/bin/env python). You can\n      specify flags as well (e. g. /bin/bash -l).\n    is_required: true\n    title: Execute with / runner binary\n  runner: bash\n- opts:\n    category: Debug\n    description: |-\n      This directory will be set as the current working\n      directory for the script.\n      Any relative path in the script (file_path) will be\n      relative to this directory.\n    title: Working directory\n  working_dir: $BITRISE_SOURCE_DIR\n- is_debug: \"no\"\n  opts:\n    category: Debug\n    description: |-\n      If you set this input to `yes` the Step will print debug related information about\n      the working dir, tmp file path, exit code, etc.\n    title: Debug print?\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/script-runner/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/secure-delete-path/2.0.0/step.yml",
    "content": "title: Secure Delete a given path\nsummary: Delete a file or a folder. You can even use sudo to do so.\ndescription: |\n  Calls 'rm -rfP the-path' to securely delete the given file or folder.\n  From the OS X rm man documentation (https://developer.apple.com/library/mac/documentation/Darwin/Reference/Manpages/man1/rm.1.html):\n  Option -P: Overwrite regular files before deleting them.  Files are overwritten three times, first\n  with the byte pattern 0xff, then 0x00, and then 0xff again, before they are deleted.\nwebsite: https://github.com/bitrise-io/steps-secure-delete-path\nsource_code_url: https://github.com/bitrise-io/steps-secure-delete-path\nsupport_url: https://github.com/bitrise-io/steps-secure-delete-path/issues\npublished_at: 2015-09-08T15:57:26.567815454+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-secure-delete-path.git\n  commit: 543cca2b481fa921d0dcf59fcce587ead1cf3009\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: File or Folder path to delete.\n  path: \"\"\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: |-\n      Use sudo for delete? Options:\n        * true (default): use sudo\n        * false: don't use sudo\n    value_options:\n    - \"true\"\n    - \"false\"\n  with_sudo: \"true\"\n"
  },
  {
    "path": "steps/secure-delete-path/2.0.1/step.yml",
    "content": "title: Secure Delete a given path\nsummary: Delete a file or a folder. You can even use sudo to do so.\ndescription: |\n  Calls 'rm -rfP the-path' to securely delete the given file or folder.\n  From the OS X rm man documentation (https://developer.apple.com/library/mac/documentation/Darwin/Reference/Manpages/man1/rm.1.html):\n  Option -P: Overwrite regular files before deleting them.  Files are overwritten three times, first\n  with the byte pattern 0xff, then 0x00, and then 0xff again, before they are deleted.\nwebsite: https://github.com/bitrise-io/steps-secure-delete-path\nsource_code_url: https://github.com/bitrise-io/steps-secure-delete-path\nsupport_url: https://github.com/bitrise-io/steps-secure-delete-path/issues\npublished_at: 2020-11-26T10:05:26.270255479Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-secure-delete-path.git\n  commit: 4b71bda8491656ef585166d28392395d3e6069d5\ntype_tags:\n- utility\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: File or Folder path to delete.\n    title: File or Folder path to delete.\n  path: \"\"\n- opts:\n    description: |-\n      Use sudo for delete? Options:\n        * true (default): use sudo\n        * false: don't use sudo\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: When this flag is enabled, the step will use sudo for the deletion.\n    title: Use sudo for delete.\n    value_options:\n    - \"true\"\n    - \"false\"\n  with_sudo: \"true\"\n"
  },
  {
    "path": "steps/secure-delete-path/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/send-google-chat-message/1.1.0/step.yml",
    "content": "title: Send a card message to Google Chat\nsummary: |\n  Sends a custom card message to a Google Chat webhook.\ndescription: |\n  Sends a simple, emoji-based card message to Google Chat to report build success or failure.\n\n  This step is designed to be run as the last step in a workflow and should be set to 'is_always_run: true'.\nwebsite: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat\nsource_code_url: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat\nsupport_url: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat/issues\npublished_at: 2025-11-19T11:21:29.254946-05:00\nsource:\n  git: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat.git\n  commit: 54f9745b80d1d0caba425d4df3e5c25cacc015aa\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: true\ninputs:\n- google_chat_webhook_url: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: The incoming webhook URL from your Google Chat space.\n    title: Google Chat Webhook URL\n- notify_on_success: \"false\"\n  opts:\n    description: If set to 'false', notifications will only be sent for failed builds.\n    is_required: true\n    title: Notify on Success\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no Step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  state_override: auto\n- opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Pipeline Build.\n    is_dont_change_value: true\n    summary: It sets the status as if the Pipeline Build had finished with the previous\n      stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Build.\n    is_dont_change_value: true\n    title: Build Status\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    title: App Title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    title: Build Number\n- opts:\n    is_dont_change_value: true\n    title: Workflow ID\n  workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the GitHub UI to allow users to easily see the source of the status.\n    is_dont_change_value: true\n    summary: Build URL for this status\n    title: Build URL\n"
  },
  {
    "path": "steps/send-google-chat-message/1.1.1/step.yml",
    "content": "title: Send a card message to Google Chat\nsummary: |\n  Sends a custom card message to a Google Chat webhook.\ndescription: |\n  Sends a simple, emoji-based card message to Google Chat to report build success or failure.\n\n  This step is designed to be run as the last step in a workflow and should be set to 'is_always_run: true'.\nwebsite: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat\nsource_code_url: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat\nsupport_url: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat/issues\npublished_at: 2025-11-20T10:11:21.880148-05:00\nsource:\n  git: https://github.com/Blue-Marble-Geographics/bitrise-step-google-chat.git\n  commit: d43f17bf0b5b42ec3d4915c82d2ffa109e5f4a5a\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: true\ninputs:\n- google_chat_webhook_url: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    summary: The incoming webhook URL from your Google Chat space.\n    title: Google Chat Webhook URL\n- notify_on_success: \"false\"\n  opts:\n    description: If set to 'false', notifications will only be sent for failed builds.\n    is_required: true\n    title: Notify on Success\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      The state of the status.\n\n      If you select `auto`, the step will send `success` status if the current build status is successful (no Step failed previously)\n      or `failure` status if the build previously failed.\n    summary: The state of the status\n    title: Set Specific Status\n    value_options:\n    - auto\n    - pending\n    - success\n    - error\n    - failure\n  state_override: auto\n- opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Pipeline Build.\n    is_dont_change_value: true\n    summary: It sets the status as if the Pipeline Build had finished with the previous\n      stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: This status will be used for calculating the GitHub Status to send\n      in case of a Build.\n    is_dont_change_value: true\n    title: Build Status\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_dont_change_value: true\n    title: App Title\n- build_number: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: true\n    title: Build Number\n- opts:\n    is_dont_change_value: true\n    title: Workflow ID\n  workflow_id: $BITRISE_TRIGGERED_WORKFLOW_ID\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    description: |-\n      The target URL to associate with this status.\n      This URL will be linked from the Google Chat card to allow users to easily see the build source.\n    is_dont_change_value: true\n    summary: Build URL for this status\n    title: Build URL\n"
  },
  {
    "path": "steps/send-google-chat-message/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/send-microsoft-teams-message/0.1.0/step.yml",
    "content": "title: Send Microsoft Teams message\nsummary: |\n  Send Microsoft Teams message to a channel\ndescription: |\n  Send Microsoft Teams message to a channel\nwebsite: https://github.com/maguhiro/bitrise-step-send-microsoft-teams-message\nsource_code_url: https://github.com/maguhiro/bitrise-step-send-microsoft-teams-message\nsupport_url: https://github.com/maguhiro/bitrise-step-send-microsoft-teams-message/issues\npublished_at: 2018-12-07T21:01:25.668996525+09:00\nsource:\n  git: https://github.com/maguhiro/bitrise-step-send-microsoft-teams-message.git\n  commit: 3ad28627d21de9fc5a7e6e3906ef30b55a0f6d13\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/maguhiro/bitrise-step-send-microsoft-teams-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Microsoft Teams Webhook URL\n    is_required: true\n    is_sensitive: true\n    title: Microsoft Teams Webhook URL\n  webhook_url: null\n- opts:\n    description: \"Specifies a custom brand color for the card. \\nCan input any hex\n      color code (eg. ff0000).\\n\\n[documentation of MS Teams](https://docs.microsoft.com/en-us/outlook/actionable-messages/message-card-reference#card-fields).\\n\"\n    title: Message card theme color\n  theme_color: 10c289\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.**\n    title: Message card theme color if the build failed\n  theme_color_on_error: ff2158\n- opts:\n    description: |\n      The `title` property is meant to be rendered in a prominent way, at the very top of the card.\n      Use it to introduce the content of the card in such a way users will immediately know what to expect.\n    title: Message card title\n  title: Build Succeeded!\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.**\n    title: Message card title if the build failed\n  title_on_error: Build Failed!\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: A small text used to display the subject.\n    title: A small text used to display the subject.\n  subject: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n    Branch|${BITRISE_GIT_BRANCH}\n    Tag|${BITRISE_GIT_TAG}\n    Message|${BITRISE_GIT_MESSAGE}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a section\n- images: null\n  opts:\n    description: |\n      Fields separated by newlines and each image contains a `title` and a `url`.\n      The `title` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *image url* is shown.\n    title: A list of images to be displayed in a section\n- images_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      Fields separated by newlines and each image contains a `title` and a `url`.\n      The `title` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *image url* is shown.\n    title: A list of images to be displayed in a section if the build failed\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 4 buttons.\n    title: A list of buttons attached to the message as link buttons\n- buttons_on_error: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    category: If Build Failed\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 4 buttons.\n    title: A list of buttons attached to the message as link buttons if the build\n      failed\n"
  },
  {
    "path": "steps/send-microsoft-teams-message/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/sentry-dsym-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-android-application-attributes/0.9.0/step.yml",
    "content": "title: Android Manifest Application Attributes\nsummary: Sets the specified `<application>` attributes in the AndroidManifest.xml\ndescription: \"This step allows to change the initial attributes of the application\n  tag specified in AndroidManifest.xml\\nThis is mainly required for the android app\n  created with Xamarin. \\nXamarin doesn't provide an easy wayt to change such attributes\n  as `android:label` or `android:icon` depending on the configuration. So this step\n  may be used to do so.\"\nwebsite: https://github.com/Memorado/bitrise-android-application-attributes-step\nsource_code_url: https://github.com/Memorado/bitrise-android-application-attributes-step\nsupport_url: https://github.com/Memorado/bitrise-android-application-attributes-step/issues\npublished_at: 2016-04-05T17:19:32.12257686+02:00\nsource:\n  git: https://github.com/Memorado/bitrise-android-application-attributes-step.git\n  commit: 5bec41b7466061efc8088e7c14beea78ab53c5df\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- manifest_file: $BITRISE_ANDROID_MANIFEST_PATH\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- app_name: null\n  opts:\n    is_required: false\n    summary: Set the `android:label` attribute in the AndroidManifest.xml to a specified\n      value. the value may be specific string o string resource id. E.g. @string/app_name_staging\n    title: Application Name\n- app_icon: null\n  opts:\n    is_required: false\n    summary: Set the `android:icon` attribute in the AndroidManifest.xml to a specified\n      value. E.g. @drawable/ic_launcher_staging\n    title: Application Icon\n"
  },
  {
    "path": "steps/set-android-application-attributes/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-android-manifest-package-name/0.9.0/step.yml",
    "content": "title: Android Manifest Package Name\nsummary: Sets the specified package name in the AndroidManifest.xml\ndescription: \"This step allows to change the initial package name specified in AndroidManifest.xml\\nThis\n  is mainly required for the android app created with Xamarin. \\nXamarin doesn't provide\n  an easy wayt to change package name depending on the configuration. So this step\n  may be used to do so.\"\nwebsite: https://github.com/Memorado/bitrise-android-package-name-step\nsource_code_url: https://github.com/Memorado/bitrise-android-package-name-step\nsupport_url: https://github.com/Memorado/bitrise-android-package-name-step/issues\npublished_at: 2016-03-31T11:12:52.857027332+02:00\nsource:\n  git: https://github.com/Memorado/bitrise-android-package-name-step.git\n  commit: 810ce06a3098a772d9091161c9ac8934729ccc45\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- manifest_file: $BITRISE_ANDROID_MANIFEST_PATH\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- opts:\n    is_required: true\n    summary: Set the package attribute in the AndroidManifest.xml to a specified value\n    title: Package Name\n  package_name: null\n"
  },
  {
    "path": "steps/set-android-manifest-package-name/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-android-manifest-values/1.0.1/step.yml",
    "content": "title: Set Android Manifest Values\nsummary: |\n  Sets some important values in AndroidManifest.xml\ndescription: |\n  Sets the package, label, android:versionCode, and android:versionName attributes in AndroidManifest.xml.\n\n  Examples:\n  - package: \"com.myorganization.myapp\"\n  - label: \"MyApp\" (displayed with the app icon)\n  - android:versionCode: \"1\"\n  - android:versionName: \"1.0\"\nwebsite: https://github.com/jsauve/set-android-manifest-values\nsource_code_url: https://github.com/jsauve/set-android-manifest-values\nsupport_url: https://github.com/jsauve/set-android-manifest-values/issues\npublished_at: 2018-02-01T15:58:33.181858568-06:00\nsource:\n  git: https://github.com/jsauve/set-android-manifest-values.git\n  commit: 9bcbfb97748c673a18bd145b3da410dfbbf2e305\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: xmlstarlet\n  apt_get:\n  - name: xmlstarlet\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- android_manifest_path: \"\"\n  opts:\n    description: |\n      \"The path to the AndroidManifest.xml, including the filename. Example: MyAndroidApp/Properties/AndroidManifest.xml\"\n    is_expand: true\n    is_required: true\n    summary: The path to the AndroidManifest.xml, including the filename\n    title: Android Manifest Path\n- opts:\n    description: |\n      \"The package value. Example: com.organization.appname\"\n    is_expand: true\n    is_required: false\n    summary: 'The app package identifier. Example: com.organization.appname'\n    title: App Package Identifier\n  package_identifier: \"\"\n- app_label: \"\"\n  opts:\n    description: |\n      \"This is the label that accompanies the app icon.\"\n    is_expand: true\n    is_required: false\n    summary: The app label shown with the app icon\n    title: App Label\n- opts:\n    description: |\n      \"The app version code. Example: 1\"\n    is_expand: true\n    is_required: false\n    summary: 'The app version code. Example: 1'\n    title: App Version Code\n  version_code: \"\"\n- opts:\n    description: |\n      \"The app version name. Example: 1.0\"\n    is_expand: true\n    is_required: false\n    summary: 'The app version name. Example: 1.0'\n    title: App Version Name\n  version_name: \"\"\n"
  },
  {
    "path": "steps/set-android-manifest-values/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-android-manifest-versions/1.0.0/step.yml",
    "content": "title: Set Android Manifest Version Code and Name\nsummary: Sets the Android Manifest Version Code and Name to the specified value, in\n  the target AndroidManifest.xml file for the next build.\ndescription: Sets the Android Manifest Version Code and Name to the specified value,\n  in the target AndroidManifest.xml file for the next build.\nwebsite: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsource_code_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsupport_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions/issues\npublished_at: 2016-01-21T12:16:13.229894608-07:00\nsource:\n  git: https://github.com/jamesmontemagno/steps-set-android-manifest-versions.git\n  commit: 98749a72f1f3aa56d5c2921bb81099f1818ca287\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- build\n- utils\nrun_if: .IsCI\ninputs:\n- manifest_file: null\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- opts:\n    is_required: true\n    summary: Set the android:versionCode to a specified value. Should be integer type.\n    title: Version Code\n  version_code: $BITRISE_BUILD_NUMBER\n- opts:\n    is_required: true\n    summary: 'Set the android:versionName to a specified value that is usually display.\n      For example: 1.0.5'\n    title: Version Name\n  version_name: 1.0.$BITRISE_BUILD_NUMBER\n"
  },
  {
    "path": "steps/set-android-manifest-versions/1.0.1/step.yml",
    "content": "title: Set Android Manifest Version Code and Name\nsummary: Sets the Android Manifest Version Code and Name to the specified value, in\n  the target AndroidManifest.xml file for the next build.\ndescription: Sets the Android Manifest Version Code and Name to the specified value,\n  in the target AndroidManifest.xml file for the next build.\nwebsite: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsource_code_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsupport_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions/issues\npublished_at: 2016-01-22T10:29:07.915821404-07:00\nsource:\n  git: https://github.com/jamesmontemagno/steps-set-android-manifest-versions.git\n  commit: 5da68ab4bb6a7c59d001691b750dbed28840ee8f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- build\n- utils\nrun_if: .IsCI\ninputs:\n- manifest_file: null\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- opts:\n    is_required: true\n    summary: Set the android:versionCode to a specified value. Should be integer type.\n    title: Version Code\n  version_code: $BITRISE_BUILD_NUMBER\n- opts:\n    is_required: true\n    summary: 'Set the android:versionName to a specified value that is usually display.\n      For example: 1.0.5'\n    title: Version Name\n  version_name: 1.0.$BITRISE_BUILD_NUMBER\n"
  },
  {
    "path": "steps/set-android-manifest-versions/1.0.2/step.yml",
    "content": "title: Set Android Manifest Version Code and Name\nsummary: Sets the Android Manifest Version Code and Name to the specified value, in\n  the target AndroidManifest.xml file for the next build.\ndescription: Sets the Android Manifest Version Code and Name to the specified value,\n  in the target AndroidManifest.xml file for the next build.\nwebsite: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsource_code_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsupport_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions/issues\npublished_at: 2016-02-24T18:50:32.511900926-08:00\nsource:\n  git: https://github.com/jamesmontemagno/steps-set-android-manifest-versions.git\n  commit: f134313ef1610765c17fc17e0f050fbff020d0c3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- build\n- utils\nrun_if: .IsCI\ninputs:\n- manifest_file: null\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- opts:\n    is_required: true\n    summary: Set the android:versionCode to a specified value. Should be integer type.\n    title: Version Code\n  version_code: $BITRISE_BUILD_NUMBER\n- opts:\n    is_required: true\n    summary: 'Set the android:versionName to a specified value that is usually display.\n      For example: 1.0.5'\n    title: Version Name\n  version_name: 1.0.$BITRISE_BUILD_NUMBER\n"
  },
  {
    "path": "steps/set-android-manifest-versions/1.0.4/step.yml",
    "content": "title: Set Android Manifest Version Code and Name\nsummary: Sets the Android Manifest Version Code and Name to the specified value, in\n  the target AndroidManifest.xml file for the next build.\ndescription: Sets the Android Manifest Version Code and Name to the specified value,\n  in the target AndroidManifest.xml file for the next build.\nwebsite: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsource_code_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsupport_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions/issues\npublished_at: 2016-05-17T14:17:21.34872863-05:00\nsource:\n  git: https://github.com/jamesmontemagno/steps-set-android-manifest-versions.git\n  commit: 0b0fc2def3b16c61f28a28a11e806c8ea516d8ea\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- build\n- utils\nrun_if: .IsCI\ninputs:\n- manifest_file: null\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- opts:\n    is_required: true\n    summary: Set the android:versionCode to a specified value. Should be integer type.\n    title: Version Code\n  version_code: $BITRISE_BUILD_NUMBER\n- opts:\n    description: |\n      This offset will be added to `version code` input's value.\n    title: Version Code Offset\n  version_code_offset: null\n- opts:\n    is_required: true\n    summary: 'Set the android:versionName to a specified value that is usually display.\n      For example: 1.0.5'\n    title: Version Name\n  version_name: null\n"
  },
  {
    "path": "steps/set-android-manifest-versions/1.0.5/step.yml",
    "content": "title: Set Android Manifest Version Code and Name\nsummary: Sets the Android Manifest Version Code and Name to the specified value, in\n  the target AndroidManifest.xml file for the next build.\ndescription: Sets the Android Manifest Version Code and Name to the specified value,\n  in the target AndroidManifest.xml file for the next build.\nwebsite: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsource_code_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions\nsupport_url: https://github.com/jamesmontemagno/steps-set-android-manifest-versions/issues\npublished_at: 2016-05-20T12:32:15.82547014-07:00\nsource:\n  git: https://github.com/jamesmontemagno/steps-set-android-manifest-versions.git\n  commit: 04e25e8fd9dcf5ef0ab0f1ff4a6111393c0a1341\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- manifest_file: null\n  opts:\n    description: |\n      Path to the given project's AndroidManifest.xml file.\n    is_required: true\n    summary: \"\"\n    title: AndroidManifest.xml file path\n- opts:\n    is_required: true\n    summary: Set the android:versionCode to a specified value. Should be integer type.\n    title: Version Code\n  version_code: $BITRISE_BUILD_NUMBER\n- opts:\n    description: |\n      This offset will be added to `version code` input's value.\n    title: Version Code Offset\n  version_code_offset: null\n- opts:\n    is_required: true\n    summary: 'Set the android:versionName to a specified value that is usually display.\n      For example: 1.0.5'\n    title: Version Name\n  version_name: null\n"
  },
  {
    "path": "steps/set-android-manifest-versions/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-env-var/0.9.0/step.yml",
    "content": "title: Set environment variable\nsummary: |\n  Set environment variable\ndescription: |\n  With this step you can copy a value into as many environment variables as you like.\nwebsite: https://github.com/bitrise-steplib/steps-set-env-var\nsource_code_url: https://github.com/bitrise-steplib/steps-set-env-var\nsupport_url: https://github.com/bitrise-steplib/steps-set-env-var/issues\npublished_at: 2017-10-31T17:05:44.602748128+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-env-var.git\n  commit: c62571ae181ac00498f69753005fb03dc8e62a9c\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-env-var\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The value will be copied into the destination environment variables.\n    is_expand: true\n    is_required: false\n    summary: Value for copy into Environment variables\n    title: Value for copy into Envirhnment variables\n    value_options: []\n  value: null\n- destination_keys: null\n  opts:\n    description: |\n      Space separated list of the keys of the destination environment variables.\n      The value will be copied into these environment variables.\n\n      `envman add --key [destination_key] --value [value]`\n    is_expand: true\n    is_required: true\n    summary: Destination Environment variables\n    title: Destination Environment variables\n    value_options: []\n"
  },
  {
    "path": "steps/set-env-var/0.9.1/step.yml",
    "content": "title: Set environment variable\nsummary: |\n  Set environment variable\ndescription: |\n  With this step you can copy a value into as many environment variables as you like.\nwebsite: https://github.com/bitrise-steplib/steps-set-env-var\nsource_code_url: https://github.com/bitrise-steplib/steps-set-env-var\nsupport_url: https://github.com/bitrise-steplib/steps-set-env-var/issues\npublished_at: 2018-05-07T16:46:28.929133685+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-env-var.git\n  commit: b6491e02d728c1e14d5c2d0b232d620e9bddec40\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-env-var\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The value will be copied into the destination environment variables.\n    is_expand: true\n    is_required: false\n    summary: Value for copy into Environment variables\n    title: Value for copy into Environment variables\n    value_options: []\n  value: null\n- destination_keys: null\n  opts:\n    description: |\n      Space separated list of the keys of the destination environment variables.\n      The value will be copied into these environment variables.\n\n      `envman add --key [destination_key] --value [value]`\n    is_expand: true\n    is_required: true\n    summary: Destination Environment variables\n    title: Destination Environment variables\n    value_options: []\n"
  },
  {
    "path": "steps/set-env-var/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/set-gem-home/0.0.1/step.yml",
    "content": "title: Set GEM_HOME\nsummary: Set GEM_HOME\ndescription: Set GEM_HOME\nwebsite: https://github.com/chrisfuller/bitrise-step-set-gem-home\nsource_code_url: https://github.com/chrisfuller/bitrise-step-set-gem-home\nsupport_url: https://github.com/chrisfuller/bitrise-step-set-gem-home/issues\npublished_at: 2019-08-25T17:04:27.365047-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-set-gem-home.git\n  commit: 8052c8be7113bb47638e23785dd50f318a9a2fe6\nhost_os_tags:\n- osx\ntype_tags:\n- utility\n- dependency\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\n"
  },
  {
    "path": "steps/set-gem-home/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-git-credentials/1.0.0/step.yml",
    "content": "title: Set Git Credentials\nsummary: Sets the Git credentials used in a workflow\ndescription: |\n  Sets the name and email address of the Git credentials used in a workflow\nwebsite: https://github.com/prosperllc/bitrise-step-set-git-credentials\nsource_code_url: https://github.com/prosperllc/bitrise-step-set-git-credentials\nsupport_url: https://github.com/prosperllc/bitrise-step-set-git-credentials/issues\npublished_at: 2019-12-18T12:38:06.7977513-08:00\nsource:\n  git: https://github.com/prosperllc/bitrise-step-set-git-credentials.git\n  commit: 0a25b468684fde8b3002e5a20792aec4112f6196\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- git_user_name: Bitrise Buildbot\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Username to set in Git during workflow execution\n    title: Git Username\n- git_email_address: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Email address to set in Git during workflow execution\n    title: Git Email Address\n"
  },
  {
    "path": "steps/set-git-credentials/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-ios-bundle-identifier/1.0.1/step.yml",
    "content": "title: Set iOS Info.plist - Bundle Identifier\nsummary: Sets the Bundle Identifier to the specified value, in the target Info.plist\n  file for the next build.\ndescription: Sets the Bundle Identifier to the specified value, in the target Info.plist\n  file for the next build.\nwebsite: https://github.com/teference/steps-set-ios-bundle-identifier\nsource_code_url: https://github.com/teference/steps-set-ios-bundle-identifier\nsupport_url: https://github.com/teference/steps-set-ios-bundle-identifier/issues\npublished_at: 2016-04-30T13:18:15.748193166+05:30\nsource:\n  git: https://github.com/teference/steps-set-ios-bundle-identifier.git\n  commit: bc8cf19b20fb4082e07844feac41562ae19c2eb3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- utils\n- xcode\n- xamarin\n- ios\n- info.plist\nrun_if: .IsCI\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_identifier: null\n  opts:\n    description: |\n      Bundle Identifier e.g.: com.yourcompany.$(PRODUCT_NAME:rfc1034identifier) Read more: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html\n    is_required: true\n    summary: Set the :CFBundleIdentifier to a specified value. Should be string.\n    title: Bundle Identifier to set\n"
  },
  {
    "path": "steps/set-ios-bundle-identifier/1.0.2/step.yml",
    "content": "title: Set iOS Info.plist - Bundle Identifier\nsummary: Sets the Bundle Identifier to the specified value, in the target Info.plist\n  file for the next build.\ndescription: Sets the Bundle Identifier to the specified value, in the target Info.plist\n  file for the next build.\nwebsite: https://github.com/teference/steps-set-ios-bundle-identifier\nsource_code_url: https://github.com/teference/steps-set-ios-bundle-identifier\nsupport_url: https://github.com/teference/steps-set-ios-bundle-identifier/issues\npublished_at: 2016-04-30T14:01:52.641687065+05:30\nsource:\n  git: https://github.com/teference/steps-set-ios-bundle-identifier.git\n  commit: c97b4b8cdacddfec0e76e6a1ab756bd1bf043d96\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_identifier: null\n  opts:\n    description: |\n      Bundle Identifier e.g.: com.yourcompany.$(PRODUCT_NAME:rfc1034identifier) Read more: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html\n    is_required: true\n    summary: Set the :CFBundleIdentifier to a specified value. Should be string.\n    title: Bundle Identifier to set\n"
  },
  {
    "path": "steps/set-ios-bundle-identifier/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-ios-info-plist-unified/1.1.4/step.yml",
    "content": "title: Set iOS Info.plist Values (unified)\nsummary: Sets various values in the target Info.plist file for the next build.\ndescription: Sets various values in the target Info.plist file for the next build.\nwebsite: https://github.com/mapletonhillmedia/steps-set-ios-info-plist\nsource_code_url: https://github.com/mapletonhillmedia/steps-set-ios-info-plist\nsupport_url: https://github.com/mapletonhillmedia/steps-set-ios-info-plist/issues\npublished_at: 2017-01-09T11:41:51.352974964-07:00\nsource:\n  git: https://github.com/mapletonhillmedia/steps-set-ios-info-plist.git\n  commit: d24eeb860f6b81f23b27c338bc36e6b25ee835b4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_identifier: null\n  opts:\n    description: |\n      Bundle Identifier e.g.: com.yourcompany.$(PRODUCT_NAME:rfc1034identifier) Read more: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html\n    is_required: false\n    summary: Set the :CFBundleIdentifier to a specified value. Should be string.\n    title: Bundle Identifier to set\n- bundle_version: null\n  opts:\n    description: |\n      CFBundleVersion e.g.: 1.0.0\n    is_required: false\n    summary: Set the :CFBundleVersion to a specified value. Should be string.\n    title: Bundle Version to set\n- bundle_version_short: null\n  opts:\n    description: |\n      CFBundleShortVersionString e.g.: 1.0\n    is_required: false\n    summary: Set the :CFBundleShortVersionString to a specified value. Should be string.\n    title: Bundle Short Version to set\n- bundle_name: null\n  opts:\n    description: |\n      Bundle CFBundleName e.g.: My App    Read more: https://developer.apple.com/library/prerelease/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/TP40009249-109585\n    is_required: false\n    summary: Set the :CFBundleName to a specified value. Should be string (16 characters\n      max).\n    title: Bundle Short Name to set\n- bundle_display_name: null\n  opts:\n    description: |\n      Bundle CFBundleDisplayName e.g.: My App    Read more: https://developer.apple.com/library/prerelease/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-110725\n    is_required: false\n    summary: Set the :CFBundleDisplayName to a specified value. Should be string.\n    title: Bundle Display Name to set (visible to users and used by Siri)\n- app_icon_asset_catalog: null\n  opts:\n    description: |\n      Asset Catalog path e.g.: Resources/Images.xcassets/AppIcons-FreeEdition.appiconset    Read more: https://developer.apple.com/library/prerelease/content/documentation/Xcode/Reference/xcode_ref-Asset_Catalog_Format/AssetTypes.html#//apple_ref/doc/uid/TP40015170-CH30-SW1\n    is_required: false\n    summary: Set the :XSAppIconAssets to a specified value. Should be string.\n    title: Path to App Icon Asset Catalog\n"
  },
  {
    "path": "steps/set-ios-info-plist-unified/1.1.6/step.yml",
    "content": "title: Set iOS Info.plist Values (unified)\nsummary: Sets various values in the target Info.plist file for the next build.\ndescription: Sets various values in the target Info.plist file for the next build.\nwebsite: https://github.com/mapletonhillmedia/steps-set-ios-info-plist\nsource_code_url: https://github.com/mapletonhillmedia/steps-set-ios-info-plist\nsupport_url: https://github.com/mapletonhillmedia/steps-set-ios-info-plist/issues\npublished_at: 2017-06-26T08:27:44.112413206-06:00\nsource:\n  git: https://github.com/mapletonhillmedia/steps-set-ios-info-plist.git\n  commit: e1a2b38ee3f2bb09f9ca4f07886cb991586bd930\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_identifier: null\n  opts:\n    description: |\n      Bundle Identifier e.g.: com.yourcompany.$(PRODUCT_NAME:rfc1034identifier) Read more: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html\n    is_required: false\n    summary: Set the :CFBundleIdentifier to a specified value. Should be string.\n    title: Bundle Identifier to set\n- bundle_version: null\n  opts:\n    description: |\n      CFBundleVersion e.g.: 1.0.0\n    is_required: false\n    summary: Set the :CFBundleVersion to a specified value. Should be string.\n    title: Bundle Version to set\n- bundle_version_short: null\n  opts:\n    description: |\n      CFBundleShortVersionString e.g.: 1.0\n    is_required: false\n    summary: Set the :CFBundleShortVersionString to a specified value. Should be string.\n    title: Bundle Short Version to set\n- bundle_name: null\n  opts:\n    description: |\n      Bundle CFBundleName e.g.: My App    Read more: https://developer.apple.com/library/prerelease/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/TP40009249-109585\n    is_required: false\n    summary: Set the :CFBundleName to a specified value. Should be string (16 characters\n      max).\n    title: Bundle Short Name to set\n- bundle_display_name: null\n  opts:\n    description: |\n      Bundle CFBundleDisplayName e.g.: My App    Read more: https://developer.apple.com/library/prerelease/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-110725\n    is_required: false\n    summary: Set the :CFBundleDisplayName to a specified value. Should be string.\n    title: Bundle Display Name to set (visible to users and used by Siri)\n- app_icon_asset_catalog: null\n  opts:\n    description: |\n      Asset Catalog path e.g.: Resources/Images.xcassets/AppIcons-FreeEdition.appiconset    Read more: https://developer.apple.com/library/prerelease/content/documentation/Xcode/Reference/xcode_ref-Asset_Catalog_Format/AssetTypes.html#//apple_ref/doc/uid/TP40015170-CH30-SW1\n    is_required: false\n    summary: Set the :XSAppIconAssets to a specified value. Should be string.\n    title: Path to App Icon Asset Catalog\n- app_launch_images_asset_catalog: null\n  opts:\n    description: |\n      Asset Catalog path e.g.: Resources/Images.xcassets/AppIcons-FreeEdition.appiconset    Read more: https://developer.apple.com/library/prerelease/content/documentation/Xcode/Reference/xcode_ref-Asset_Catalog_Format/AssetTypes.html#//apple_ref/doc/uid/TP40015170-CH30-SW1\n    is_required: false\n    summary: Set the :XSLaunchImageAssets to a specified value. Should be string.\n    title: Path to App Launch Images Asset Catalog\n- app_launch_screen: null\n  opts:\n    description: |\n      UILaunchStoryboardName e.g.: MyLaunchScreen    Read more: https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html\n    is_required: false\n    summary: Set the :UILaunchStoryboardName to a specified value. Should be string.\n    title: 'Name of Launch screen Storyboard '\n"
  },
  {
    "path": "steps/set-ios-info-plist-unified/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-ios-product-bundle-identifier/1.1.0/step.yml",
    "content": "title: Replaces Xcode's project PRODUCT_BUNDLE_IDENTIFIER\nsummary: Replaces Xcode's project PRODUCT_BUNDLE_IDENTIFIER setting.\ndescription: |-\n  Replaces Xcode's project `PRODUCT_BUNDLE_IDENTIFIER` setting by passing in a new value.\n  This is the recommended way to substitute the bundle identifier\n  instead of modifiying the `CFBundleIdentifier` setting in the `Info.plist` file.\n\n  From [Xcode 7 Release Notes](https://developer.apple.com/library/content/documentation/Xcode/Conceptual/RN-Xcode-Archive/Chapters/xc7_release_notes.html):\n  > The new build setting Product Bundle Identifier (PRODUCT_BUNDLE_IDENTIFIER) is the recommended place to set the Bundle Identifier for a target. The target’s Info.plist should be configured to use this build setting by referencing it as $(PRODUCT_BUNDLE_IDENTIFIER) in the value for the CFBundleIdentifier key.\nwebsite: https://github.com/emenegro/bitrise-step-product-bundle-identifier\nsource_code_url: https://github.com/emenegro/bitrise-step-product-bundle-identifier\nsupport_url: https://github.com/emenegro/bitrise-step-product-bundle-identifier/issues\npublished_at: 2017-03-29T13:00:55.894351683+02:00\nsource:\n  git: https://github.com/emenegro/bitrise-step-product-bundle-identifier.git\n  commit: 35c0a260082f20423b232dd6ca7e42f1fde1f184\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    is_required: true\n    summary: Path to the iOS project `.xcodeproj` file.\n    title: Xcode project path\n  project_path: null\n- new_bundle_identifier: null\n  opts:\n    is_required: true\n    summary: The new bundle identifier to be set.\n    title: New bundle identifier\n"
  },
  {
    "path": "steps/set-ios-product-bundle-identifier/1.1.2/step.yml",
    "content": "title: Replaces Xcode's project PRODUCT_BUNDLE_IDENTIFIER\nsummary: Replaces Xcode's project PRODUCT_BUNDLE_IDENTIFIER setting.\ndescription: |-\n  Replaces Xcode's project `PRODUCT_BUNDLE_IDENTIFIER` setting by passing in a new value.\n  This is the recommended way to substitute the bundle identifier\n  instead of modifiying the `CFBundleIdentifier` setting in the `Info.plist` file.\n\n  From [Xcode 7 Release Notes](https://developer.apple.com/library/content/documentation/Xcode/Conceptual/RN-Xcode-Archive/Chapters/xc7_release_notes.html):\n  «The new build setting Product Bundle Identifier (PRODUCT_BUNDLE_IDENTIFIER) is the recommended place to set the Bundle Identifier for a target. The target’s Info.plist should be configured to use this build setting by referencing it as $(PRODUCT_BUNDLE_IDENTIFIER) in the value for the CFBundleIdentifier key.»\nwebsite: https://github.com/emenegro/bitrise-step-product-bundle-identifier\nsource_code_url: https://github.com/emenegro/bitrise-step-product-bundle-identifier\nsupport_url: https://github.com/emenegro/bitrise-step-product-bundle-identifier/issues\npublished_at: 2017-04-18T17:45:26.022337757+02:00\nsource:\n  git: https://github.com/emenegro/bitrise-step-product-bundle-identifier.git\n  commit: 4381b52c09fb4fb60c69da2a994a1e764d22ef9d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to the iOS project `.xcodeproj` file.\n    is_required: true\n    summary: Path to the iOS project `.xcodeproj` file.\n    title: Xcode project path\n  project_path: null\n- new_bundle_identifier: null\n  opts:\n    description: |\n      The new bundle identifier to be set.\n    is_required: true\n    summary: The new bundle identifier to be set.\n    title: New bundle identifier\n"
  },
  {
    "path": "steps/set-ios-product-bundle-identifier/1.1.3/step.yml",
    "content": "title: Replaces Xcode's project PRODUCT_BUNDLE_IDENTIFIER\nsummary: Replaces Xcode's project PRODUCT_BUNDLE_IDENTIFIER setting.\ndescription: |-\n  Replaces Xcode's project `PRODUCT_BUNDLE_IDENTIFIER` setting by passing in a new value.\n  This is the recommended way to substitute the bundle identifier\n  instead of modifiying the `CFBundleIdentifier` setting in the `Info.plist` file.\n\n  From [Xcode 7 Release Notes](https://developer.apple.com/library/content/documentation/Xcode/Conceptual/RN-Xcode-Archive/Chapters/xc7_release_notes.html):\n  «The new build setting Product Bundle Identifier (PRODUCT_BUNDLE_IDENTIFIER) is the recommended place to set the Bundle Identifier for a target. The target’s Info.plist should be configured to use this build setting by referencing it as $(PRODUCT_BUNDLE_IDENTIFIER) in the value for the CFBundleIdentifier key.»\nwebsite: https://github.com/emenegro/bitrise-step-product-bundle-identifier\nsource_code_url: https://github.com/emenegro/bitrise-step-product-bundle-identifier\nsupport_url: https://github.com/emenegro/bitrise-step-product-bundle-identifier/issues\npublished_at: 2017-12-15T08:50:12.738961+01:00\nsource:\n  git: https://github.com/emenegro/bitrise-step-product-bundle-identifier.git\n  commit: 4eafd951bac95284534540e3f6c4807ffe39f757\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to the iOS project `.xcodeproj` file.\n    is_required: true\n    summary: Path to the iOS project `.xcodeproj` file.\n    title: Xcode project path\n  project_path: null\n- new_bundle_identifier: null\n  opts:\n    description: |\n      The new bundle identifier to be set.\n    is_required: true\n    summary: The new bundle identifier to be set.\n    title: New bundle identifier\n"
  },
  {
    "path": "steps/set-ios-product-bundle-identifier/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-ios-version/1.0.2/step.yml",
    "content": "title: Set iOS Info.plist - Bundle Identifier\nsummary: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\ndescription: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\nwebsite: https://github.com/BOOMik/steps-set-ios-version\nsource_code_url: https://github.com/BOOMik/steps-set-ios-version\nsupport_url: https://github.com/BOOMik/steps-set-ios-version/issues\npublished_at: 2016-06-07T20:41:18.504380527+03:00\nsource:\n  git: https://github.com/BOOMik/steps-set-ios-version.git\n  commit: 48a80ba9d24caca021f7a7561f50c8a443665bec\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- utils\n- xcode\n- xamarin\n- ios\n- info.plist\n- versioning\nrun_if: .IsCI\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_version: null\n  opts:\n    description: |\n      CFBundleVersion e.g.: 1.0.0\n    is_required: true\n    summary: Set the :CFBundleVersion to a specified value. Should be string.\n    title: Bundle Version to set\n- bundle_version_short: null\n  opts:\n    description: |\n      CFBundleShortVersionString e.g.: 1.0\n    is_required: true\n    summary: Set the :CFBundleShortVersionString to a specified value. Should be string.\n    title: Bundle Short Version String to set\noutputs:\n- APP_VERSION: null\n  opts:\n    title: Version (CFBundleVersion from Info.plist)\n- APP_BUILD: null\n  opts:\n    title: Build (CFBundleShortVersionString from Info.plist)\n"
  },
  {
    "path": "steps/set-ios-version/1.1.0/step.yml",
    "content": "title: Set iOS Info.plist - Bundle Version and Bundle Short Version String\nsummary: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\ndescription: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\nwebsite: https://github.com/BOOMik/steps-set-ios-version\nsource_code_url: https://github.com/BOOMik/steps-set-ios-version\nsupport_url: https://github.com/BOOMik/steps-set-ios-version/issues\npublished_at: 2016-06-08T13:06:26.611278019+03:00\nsource:\n  git: https://github.com/BOOMik/steps-set-ios-version.git\n  commit: cc6a7e4ca9fcf64cb8cfbfeb34b74647eb38053b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- utils\n- xcode\n- xamarin\n- ios\n- info.plist\n- versioning\nrun_if: .IsCI\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_version: null\n  opts:\n    description: |\n      CFBundleVersion e.g.: 1.0.0\n    is_required: true\n    summary: Set the :CFBundleVersion to a specified value. Should be string.\n    title: Bundle Version to set\n- bundle_version_short: null\n  opts:\n    description: |\n      CFBundleShortVersionString e.g.: 1.0\n    is_required: true\n    summary: Set the :CFBundleShortVersionString to a specified value. Should be string.\n    title: Bundle Short Version String to set\n- opts:\n    description: |\n      This offset will be added to `Short Version` input's value. If this set - Offset and Short Version must be integer!.\n    title: Bundle Short Version String Offset\n  version_short_offset: null\n- append_version: \"no\"\n  opts:\n    is_required: true\n    summary: It appends to the current CFBundleVersion. e.g. Current version in Info.plist\n      is '1.0.'. After step will be '1.0.YOU_ENTERED_VERSION NAME'\n    title: Append Version\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- APP_VERSION: null\n  opts:\n    title: Version (CFBundleVersion from Info.plist)\n- APP_BUILD: null\n  opts:\n    title: Build (CFBundleShortVersionString from Info.plist)\n"
  },
  {
    "path": "steps/set-ios-version/1.1.1/step.yml",
    "content": "title: Set iOS Info.plist - Bundle Version and Bundle Short Version String\nsummary: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\ndescription: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\nwebsite: https://github.com/BOOMik/steps-set-ios-version\nsource_code_url: https://github.com/BOOMik/steps-set-ios-version\nsupport_url: https://github.com/BOOMik/steps-set-ios-version/issues\npublished_at: 2016-06-08T13:38:59.398685979+03:00\nsource:\n  git: https://github.com/BOOMik/steps-set-ios-version.git\n  commit: 9808a8b9f4e552fc60b54fc54d091b0beda8429b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_version: null\n  opts:\n    description: |\n      CFBundleVersion e.g.: 1.0.0\n    is_required: true\n    summary: Set the :CFBundleVersion to a specified value. Should be string.\n    title: Bundle Version to set\n- bundle_version_short: null\n  opts:\n    description: |\n      CFBundleShortVersionString e.g.: 1.0\n    is_required: true\n    summary: Set the :CFBundleShortVersionString to a specified value. Should be string.\n    title: Bundle Short Version String to set\n- opts:\n    description: |\n      This offset will be added to `Short Version` input's value. If this set - Offset and Short Version must be integer!.\n    title: Bundle Short Version String Offset\n  version_short_offset: null\n- append_version: \"false\"\n  opts:\n    is_required: true\n    summary: It appends to the current CFBundleVersion. e.g. Current version in Info.plist\n      is '1.0.'. After step will be '1.0.YOU_ENTERED_VERSION NAME'\n    title: Append Version\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- APP_VERSION: null\n  opts:\n    title: Version (CFBundleVersion from Info.plist)\n- APP_BUILD: null\n  opts:\n    title: Build (CFBundleShortVersionString from Info.plist)\n"
  },
  {
    "path": "steps/set-ios-version/2.0.0/step.yml",
    "content": "title: Set iOS Info.plist - Bundle Version and Bundle Short Version String\nsummary: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\ndescription: Sets the Bundle Version and Bundle Short Version String to the specified\n  value, in the target Info.plist file for the next build.\nwebsite: https://github.com/BOOMik/steps-set-ios-version\nsource_code_url: https://github.com/BOOMik/steps-set-ios-version\nsupport_url: https://github.com/BOOMik/steps-set-ios-version/issues\npublished_at: 2017-11-28T00:12:19.548767526+03:00\nsource:\n  git: https://github.com/BOOMik/steps-set-ios-version.git\n  commit: 75a1b1cf5f8f91987e14379eefa46fcd0dc9c986\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- info_plist_file: null\n  opts:\n    description: |\n      Path to the given iOS project's Info.plist file.\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n- bundle_version: null\n  opts:\n    description: |\n      CFBundleVersion e.g.: 42\n    is_required: false\n    summary: Set the :CFBundleVersion to a specified value. Should be string or empty.\n      If the field is empty, the current version will be used.\n    title: Bundle Version to set\n- bundle_version_short: null\n  opts:\n    description: |\n      CFBundleShortVersionString e.g.: 1.0.0\n    is_required: false\n    summary: Set the :CFBundleShortVersionString to a specified value. Should be string\n      or empty. If the field is empty, the current short version will be used.\n    title: Bundle Short Version String to set\n- opts:\n    description: |\n      This offset will be added to `Version` input's value. If this set - Offset and Version must be integer!.\n    title: Bundle Version Offset\n  version_short_offset: null\n- append_version: \"false\"\n  opts:\n    is_required: true\n    summary: It appends to the current CFBundleShortVersionString. e.g. Current version\n      in Info.plist is '1.0.'. After step will be '1.0.YOU_ENTERED_VERSION NAME'\n    title: Append Version\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- APP_VERSION: null\n  opts:\n    title: Version (CFBundleShortVersionString from Info.plist)\n- APP_BUILD: null\n  opts:\n    title: Build (CFBundleVersion from Info.plist)\n"
  },
  {
    "path": "steps/set-ios-version/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-java-version/1.0.1/step.yml",
    "content": "title: Set java version\nsummary: This step helps you in setting an already installed java version on the virtual\n  machine.\ndescription: |\n  This step helps you in setting an already installed java version on the virtual machine. Mind you, that this step can't install any java version, it's only for changing between the already installed versions.\n\n  If you want to install other java version you can do it by [this guide](https://devcenter.bitrise.io/infrastructure/virtual-machines/#switching-to-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Troubleshooting\n\n  If the step fails to set the java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n\n  [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2021-09-03T12:36:38.394272+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: cc12fd4eabb43a317d4b261f6d9010f0fe9eef3c\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed java version you want to use during the build run.\n\n      You can check [here](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) which java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select the installed java version you want to use during the build run.\n    title: Java version to be set globally for the build\n    value_options:\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable points to the file system location\n      where the JDK or JRE was installed.\n    summary: Location where the JDK or JRE was installed.\n    title: Location where the JDK or JRE was installed.\n"
  },
  {
    "path": "steps/set-java-version/1.0.2/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you set a pre-installed Java version as default on the build\n  virtual machine.\ndescription: |\n  This Step can't install any Java version. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2021-09-08T10:19:33.10276217Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: 81d4e8316656432254d74932231593241e6ba7c5\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) which java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version to be set globally for the build\n    value_options:\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable points to the file system location\n      where the JDK or JRE was installed.\n    summary: Location where the JDK or JRE was installed.\n    title: Location where the JDK or JRE was installed.\n"
  },
  {
    "path": "steps/set-java-version/1.0.3/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you set a pre-installed Java version as default on the build\n  virtual machine.\ndescription: |\n  This Step can't install any Java version. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2021-09-09T14:58:18.048447471Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: e00356140a7834f0599f8d9977c9ebdc3745c700\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) which java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version to be set globally for the build\n    value_options:\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable points to the file system location\n      where the JDK or JRE was installed.\n    summary: Location where the JDK or JRE was installed.\n    title: Location where the JDK or JRE was installed.\n"
  },
  {
    "path": "steps/set-java-version/1.1.0/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you activate pre-installed Java (JDK) version on the build\n  virtual machine.\ndescription: |\n  This Step is not supposed to install any Java version on the fly. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2022-04-14T08:25:52.406175716Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: 207ceac1601c9c46d9a0222b714ae9cf4e9aaebf\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) which java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version\n    value_options:\n    - \"17\"\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable that points to the path where\n      the JDK (Java Development Kit) is installed.\n    title: Location of the active Java installation.\n"
  },
  {
    "path": "steps/set-java-version/1.1.1/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you activate pre-installed Java (JDK) version on the build\n  virtual machine.\ndescription: |\n  This Step is not supposed to install any Java version on the fly. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2022-06-23T10:54:50.778000015Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: 97fa7591f8bf2600254bd5f8391f2f04b93b9c03\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) which java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version\n    value_options:\n    - \"17\"\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable that points to the path where\n      the JDK (Java Development Kit) is installed.\n    title: Location of the active Java installation.\n"
  },
  {
    "path": "steps/set-java-version/1.1.2/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you activate pre-installed Java (JDK) version on the build\n  virtual machine.\ndescription: |\n  This Step is not supposed to install any Java version on the fly. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2023-09-18T13:26:39.342752831Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: 6f6864513774643e95615f846466ddce2c86c07e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://stacks.bitrise.io) which Java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version\n    value_options:\n    - \"17\"\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable that points to the path where\n      the JDK (Java Development Kit) is installed.\n    title: Location of the active Java installation.\n"
  },
  {
    "path": "steps/set-java-version/1.2.0/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you activate pre-installed Java (JDK) version on the build\n  virtual machine.\ndescription: |\n  This Step is not supposed to install any Java version on the fly. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2024-02-05T15:51:04.02751468Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: 597c98127c2295678d73b4a3fbfce55fb44232ac\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://stacks.bitrise.io) which Java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version\n    value_options:\n    - \"21\"\n    - \"17\"\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable that points to the path where\n      the JDK (Java Development Kit) is installed.\n    title: Location of the active Java installation.\n"
  },
  {
    "path": "steps/set-java-version/1.2.1/step.yml",
    "content": "title: Set Java version\nsummary: This Step helps you activate pre-installed Java (JDK) version on the build\n  virtual machine.\ndescription: |\n  This Step is not supposed to install any Java version on the fly. You can only pick from the already installed versions.\n  If you want to install other Java versions, check out [Using a Java version not installed on our Android stacks](https://devcenter.bitrise.io/infrastructure/virtual-machines/#using-a-java-version-not-installed-on-our-android-stacks).\n\n  ### Configuring the Step\n  1. In the **Java version to be set globally for the build** input, select an installed Java version you wish to use during the build run.\n\n  ### Troubleshooting\n  If the Step fails to set the Java version, you can use these [scripts](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions) as a temporary workaround.\n\n  ### Useful links\n  - [Managing Java versions on Bitrise](https://devcenter.bitrise.io/infrastructure/virtual-machines/#managing-java-versions)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-set-java-version/issues\npublished_at: 2024-02-07T13:14:35.358257229Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-set-java-version.git\n  commit: 32635b32f72a9560bc9c6ee76fbdf36559a6522b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-set-java-version\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Select the installed Java version you want to use during the build run.\n\n      You can check [in system reports](https://stacks.bitrise.io) which Java versions are installed on each Bitrise stack.\n    is_required: true\n    summary: Select which pre-installed Java version you want to use during the build.\n    title: Java version\n    value_options:\n    - \"21\"\n    - \"17\"\n    - \"11\"\n    - \"8\"\n  set_java_version: \"11\"\noutputs:\n- JAVA_HOME: null\n  opts:\n    description: JAVA_HOME is an environment variable that points to the path where\n      the JDK (Java Development Kit) is installed.\n    title: Location of the active Java installation.\n"
  },
  {
    "path": "steps/set-java-version/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/set-macos-timezone/0.0.1/step.yml",
    "content": "title: Set macOS Time Zone\nsummary: Set macOS Time Zone\ndescription: Set macOS Time Zone\nwebsite: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsource_code_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsupport_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone/issues\npublished_at: 2019-08-24T17:17:32.034927-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-set-macos-timezone.git\n  commit: 916a99e41ef22fc35a9444c9578732f08be609f2\nhost_os_tags:\n- osx\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Execute `systemsetup -listtimezones` for supported time zones.\n    is_expand: true\n    is_required: true\n    title: Time Zone\n  timezone: GMT\n"
  },
  {
    "path": "steps/set-macos-timezone/0.0.2/step.yml",
    "content": "title: Set macOS Time Zone\nsummary: Set macOS Time Zone\ndescription: Set macOS Time Zone\nwebsite: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsource_code_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsupport_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone/issues\npublished_at: 2019-08-25T16:55:16.237103-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-set-macos-timezone.git\n  commit: 6c98f5ee86a1e24f64f4a48f35e65700720e3b34\nhost_os_tags:\n- osx\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Execute `systemsetup -listtimezones` for supported time zones.\n    is_expand: true\n    is_required: true\n    title: Time Zone\n  timezone: GMT\n"
  },
  {
    "path": "steps/set-macos-timezone/0.0.3/step.yml",
    "content": "title: Set macOS Time Zone\nsummary: Set macOS Time Zone\ndescription: Set macOS Time Zone\nwebsite: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsource_code_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsupport_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone/issues\npublished_at: 2019-09-03T02:21:46.21835-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-set-macos-timezone.git\n  commit: 03d89dc37b20b326acb1c8297f96d09784f059e3\nhost_os_tags:\n- osx\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Execute `systemsetup -listtimezones` for supported time zones.\n    is_expand: true\n    is_required: true\n    title: Time Zone\n  timezone: GMT\n"
  },
  {
    "path": "steps/set-macos-timezone/0.0.4/step.yml",
    "content": "title: Set macOS Time Zone\nsummary: Set macOS Time Zone\ndescription: Set macOS Time Zone\nwebsite: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsource_code_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone\nsupport_url: https://github.com/chrisfuller/bitrise-step-set-macos-timezone/issues\npublished_at: 2019-09-11T10:38:46.210804-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-set-macos-timezone.git\n  commit: 4ab04bd380c43d84c1469b13208bebbe24209701\nhost_os_tags:\n- osx\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Execute `systemsetup -listtimezones` for supported time zones.\n    is_expand: true\n    is_required: true\n    title: Time Zone\n  timezone: GMT\n"
  },
  {
    "path": "steps/set-macos-timezone/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-nuget-private-source/1.0.1/step.yml",
    "content": "title: Set NuGet private source\nsummary: Sets specified NuGet private source to the NuGet source list for the next\n  build.\ndescription: Sets specified NuGet private source to the NuGet source list for the\n  next build.\nwebsite: https://github.com/teference/steps-set-nuget-private-source\nsource_code_url: https://github.com/teference/steps-set-nuget-private-source\nsupport_url: https://github.com/teference/steps-set-nuget-private-source/issues\npublished_at: 2016-05-06T17:52:57.769773859+05:30\nsource:\n  git: https://github.com/teference/steps-set-nuget-private-source.git\n  commit: 437b0f15f8eecdb6b1488062e44547f47fc21e0f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- nuget_source_name: null\n  opts:\n    description: |\n      Name to use for specified NuGet private source in the NuGet source list.\n    is_required: true\n    summary: \"\"\n    title: NuGet private source name\n- nuget_source_path_or_url: null\n  opts:\n    description: |\n      Path or URL of the NuGet private package(s) source.\n    is_required: true\n    summary: \"\"\n    title: NuGet private source path / url\n- nuget_source_username: null\n  opts:\n    description: |\n      UserName to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source username\n- nuget_source_password: null\n  opts:\n    description: |\n      Password to be used when connecting to an authenticated source.\n    summary: \"\"\n    title: NuGet private source password\n"
  },
  {
    "path": "steps/set-nuget-private-source/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-pubspec-application-version/0.0.1/step.yml",
    "content": "title: Set application version and build number in pubspec.yaml file\nsummary: Sets application version and build number in pubspec file and returns the\n  new version info\ndescription: Sets the application version by the inputs for application version and\n  build number. The application build number is mandatory to provide for this input.\nwebsite: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsource_code_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsupport_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version/issues\npublished_at: 2022-08-26T14:48:10.674311+02:00\nsource:\n  git: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version.git\n  commit: 67c215ded9d70ba081173cceedfd2993d8ab1b90\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root dir of your Flutter project that contains *pubspec.yaml*\n      and optionally *pubspec.lock*.\n    is_required: true\n    summary: The root dir of your Flutter project\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_buildnumber: $BITRISE_BUILD_NUMBER\n  opts:\n    description: The application build number which could be used from the build on\n      bitrise.io over variable BITRISE_BUILD_NUMBER.\n    is_required: true\n    summary: Application build number could be from the build on bitrise.io from BITRISE_BUILD_NUMBER.\n    title: Application build number\n- application_version: null\n  opts:\n    description: The application version which could be empty, then it is keeped like\n      it is, or set by this input.\n    is_required: false\n    summary: The application version info as a string like 1.2.3\n    title: Application version\noutputs:\n- DART_PUBSPEC_APP_VERSION: null\n  opts:\n    description: The application version which is set in the pubspec.yaml version\n      string at the **project location**.\n    title: Flutter / Dart pubspec application version which was new set or already\n      set as input.\n- DART_PUBSPEC_APP_BUILD_NUMBER: null\n  opts:\n    description: The application build number is set in the pubspec.yaml version string\n      at the **project location**.\n    title: Flutter / Dart pubspec application build number which was set as input.\n- DART_PUBSPEC_APP_VERSION_STRING: null\n  opts:\n    description: The application version string with version+buildnumber like 1.2.3+999\n      which was set in the pubspec.yaml at the **project location**.\n    title: Flutter / Dart pubspec application version string with version+buildnumber\n      which is set in pubspec.yaml.\n"
  },
  {
    "path": "steps/set-pubspec-application-version/0.0.2/step.yml",
    "content": "title: Set application version and build number in pubspec.yaml file\nsummary: Sets application version and build number in pubspec file and returns the\n  new version info\ndescription: Sets the application version by the inputs for application version and\n  build number. The application build number is mandatory to provide for this input.\nwebsite: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsource_code_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsupport_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version/issues\npublished_at: 2022-09-01T13:29:24.450903+02:00\nsource:\n  git: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version.git\n  commit: d9a0376bab9f519de8a0017a8ee7de3dcf1eaa98\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root dir of your Flutter project that contains *pubspec.yaml*\n      and optionally *pubspec.lock*.\n    is_required: true\n    summary: The root dir of your Flutter project\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_buildnumber: $BITRISE_BUILD_NUMBER\n  opts:\n    description: The application build number which could be used from the build on\n      bitrise.io over variable BITRISE_BUILD_NUMBER.\n    is_required: true\n    summary: Application build number could be from the build on bitrise.io from BITRISE_BUILD_NUMBER.\n    title: Application build number\n- application_version: null\n  opts:\n    description: The application version which could be empty, then it is keeped like\n      it is, or set by this input.\n    is_required: false\n    summary: The application version info as a string like 1.2.3\n    title: Application version\noutputs:\n- DART_PUBSPEC_APP_VERSION: null\n  opts:\n    description: The application version which is set in the pubspec.yaml version\n      string at the **project location**.\n    title: Flutter / Dart pubspec application version which was new set or already\n      set as input.\n- DART_PUBSPEC_APP_BUILD_NUMBER: null\n  opts:\n    description: The application build number is set in the pubspec.yaml version string\n      at the **project location**.\n    title: Flutter / Dart pubspec application build number which was set as input.\n- DART_PUBSPEC_APP_VERSION_STRING: null\n  opts:\n    description: The application version string with version+buildnumber like 1.2.3+999\n      which was set in the pubspec.yaml at the **project location**.\n    title: Flutter / Dart pubspec application version string with version+buildnumber\n      which is set in pubspec.yaml.\n"
  },
  {
    "path": "steps/set-pubspec-application-version/0.0.3/step.yml",
    "content": "title: Set pubspec version and build number\nsummary: Sets application version and build number in pubspec file and returns the\n  new version info\ndescription: Sets the application version by the inputs for application version and\n  build number. The application build number and the project root are mandatory to\n  provide as inputs.\nwebsite: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsource_code_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsupport_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version/issues\npublished_at: 2022-09-06T17:01:02.181523+02:00\nsource:\n  git: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version.git\n  commit: 1b065956454934b0b899f73969891e26c8046473\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your Flutter or Dart project that contains\n      the *pubspec.yaml* file which is in general accessible over the $BITRISE_SOURCE_DIR\n      variable.\n    is_required: true\n    summary: The root directory of your Flutter or Dart project i.e. from $BITRISE_SOURCE_DIR\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_buildnumber: $BITRISE_BUILD_NUMBER\n  opts:\n    description: The application build number which could be used with variable $BITRISE_BUILD_NUMBER.\n    is_required: true\n    summary: Application build number i.e. from $BITRISE_BUILD_NUMBER.\n    title: Application build number\n- application_version: null\n  opts:\n    description: The application version which could be empty, then it is keeped like\n      it is, or set by this input.\n    is_required: false\n    summary: The application version info as a string like 1.2.3\n    title: Application version\noutputs:\n- DART_PUBSPEC_APP_VERSION: null\n  opts:\n    description: The application version which is set in the pubspec.yaml version\n      string at the **project location**.\n    title: Flutter / Dart pubspec application version which was new set or already\n      set as input.\n- DART_PUBSPEC_APP_BUILD_NUMBER: null\n  opts:\n    description: The application build number is set in the pubspec.yaml version string\n      at the **project location**.\n    title: Flutter / Dart pubspec application build number which was set as input.\n- DART_PUBSPEC_APP_VERSION_STRING: null\n  opts:\n    description: The application version string with version+buildnumber like 1.2.3+999\n      which was set in the pubspec.yaml at the **project location**.\n    title: Flutter / Dart pubspec application version string with version+buildnumber\n      which is set in pubspec.yaml.\n"
  },
  {
    "path": "steps/set-pubspec-application-version/0.1.0/step.yml",
    "content": "title: Set pubspec version and build number\nsummary: Sets application version and build number in pubspec file and returns the\n  new version info\ndescription: Sets the application version by the inputs for application version and\n  build number. The application build number and the project root are mandatory to\n  provide as inputs.\nwebsite: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsource_code_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsupport_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version/issues\npublished_at: 2025-01-07T16:25:27.169503+01:00\nsource:\n  git: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version.git\n  commit: e5cf90ea3a711ed4ee02e16420fd349fe23cb3c9\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your Flutter or Dart project that contains\n      the *pubspec.yaml* file which is in general accessible over the $BITRISE_SOURCE_DIR\n      variable.\n    is_required: true\n    summary: The root directory of your Flutter or Dart project i.e. from $BITRISE_SOURCE_DIR\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_buildnumber: $BITRISE_BUILD_NUMBER\n  opts:\n    description: The application build number which could be used with variable $BITRISE_BUILD_NUMBER.\n    is_required: true\n    summary: Application build number i.e. from $BITRISE_BUILD_NUMBER.\n    title: Application build number\n- application_version: null\n  opts:\n    description: The application version which could be empty, then it is keeped like\n      it is, or set by this input.\n    is_required: false\n    summary: The application version info as a string like 1.2.3\n    title: Application version\noutputs:\n- DART_PUBSPEC_APP_VERSION: null\n  opts:\n    description: The application version which is set in the pubspec.yaml version\n      string at the **project location**.\n    title: Flutter / Dart pubspec application version which was new set or already\n      set as input.\n- DART_PUBSPEC_APP_BUILD_NUMBER: null\n  opts:\n    description: The application build number is set in the pubspec.yaml version string\n      at the **project location**.\n    title: Flutter / Dart pubspec application build number which was set as input.\n- DART_PUBSPEC_APP_VERSION_STRING: null\n  opts:\n    description: The application version string with version+buildnumber like 1.2.3+999\n      which was set in the pubspec.yaml at the **project location**.\n    title: Flutter / Dart pubspec application version string with version+buildnumber\n      which is set in pubspec.yaml.\n"
  },
  {
    "path": "steps/set-pubspec-application-version/1.0.0/step.yml",
    "content": "title: Set pubspec version and build number\nsummary: Sets application version and build number in pubspec file and returns the\n  new version info\ndescription: Sets the application version by the inputs for application version and\n  build number. The application build number and the project root are mandatory to\n  provide as inputs.\nwebsite: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsource_code_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version\nsupport_url: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version/issues\npublished_at: 2025-01-07T16:37:40.408921+01:00\nsource:\n  git: https://github.com/milkinteractive/bitrise-step-set-pubspec-application-version.git\n  commit: 7d9059495db5db82e84fe74d97b0a94fefc01b76\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: The root directory of your Flutter or Dart project that contains\n      the *pubspec.yaml* file which is in general accessible over the $BITRISE_SOURCE_DIR\n      variable.\n    is_required: true\n    summary: The root directory of your Flutter or Dart project i.e. from $BITRISE_SOURCE_DIR\n    title: Project Location\n  project_location: $BITRISE_SOURCE_DIR\n- bitrise_buildnumber: $BITRISE_BUILD_NUMBER\n  opts:\n    description: The application build number which could be used with variable $BITRISE_BUILD_NUMBER.\n    is_required: true\n    summary: Application build number i.e. from $BITRISE_BUILD_NUMBER.\n    title: Application build number\n- application_version: null\n  opts:\n    description: The application version which could be empty, then it is keeped like\n      it is, or set by this input.\n    is_required: false\n    summary: The application version info as a string like 1.2.3\n    title: Application version\noutputs:\n- DART_PUBSPEC_APP_VERSION: null\n  opts:\n    description: The application version which is set in the pubspec.yaml version\n      string at the **project location**.\n    title: Flutter / Dart pubspec application version which was new set or already\n      set as input.\n- DART_PUBSPEC_APP_BUILD_NUMBER: null\n  opts:\n    description: The application build number is set in the pubspec.yaml version string\n      at the **project location**.\n    title: Flutter / Dart pubspec application build number which was set as input.\n- DART_PUBSPEC_APP_VERSION_STRING: null\n  opts:\n    description: The application version string with version+buildnumber like 1.2.3+999\n      which was set in the pubspec.yaml at the **project location**.\n    title: Flutter / Dart pubspec application version string with version+buildnumber\n      which is set in pubspec.yaml.\n"
  },
  {
    "path": "steps/set-pubspec-application-version/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.0/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: |-\n  Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2015-09-23T18:07:16.497575934+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: 222a32f19a63ddeace84a033fe51f3c9194d0804\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Set the Build Number / Bundle Version to this value.\n    title: Build Number\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.1/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2015-10-11T10:35:26.080982811+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: 809e1498d23cafce22b8680a67274149b8809051\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Set the Build Number / Bundle Version to this value.\n    title: Build Number\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.10/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of Bundle version in the project's Info.plist file to the specified\n  version number.\ndescription: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\n\n  If your IPA contains multiple build targets ( e.g watch app, extensions ), they would need to have the same version number as your app's main target has.<br/>\n  You need to add this step to your workflow for every build target one by one.\n\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2020-05-06T21:48:49.257851285Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 5e1ba2ee727fa4a52fae14d1109cadb346abeb8e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      **NOTE:**<br/>\n      If your IPA contains multiple build targets ( e.g watch app, extensions ), they would need to have the same version number as your app's main target has.<br/>\n      You need to add this step to your workflow for every build target one by one.\n\n      If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n    is_required: true\n    summary: Path to the given target's Info.plist file. You need to use this step\n      for each archivable target of your project.\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    title: The bundle version used in the Info.plist file\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.11/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's bundle version in the `Info.plist` file to\n  the specified version number.\ndescription: \"Set the value of your iOS app's bundle version in the `Info.plist` file\n  to the specified version number. A great\\nway to keep track of versions when submitting\n  bug reports.\\n\\nIf your IPA contains multiple build targets, they need to have the\n  same version number as your app's main target has.\\nIn that case, you need to add\n  this Step to your Workflow for each build target: if you have, say, three targets,\n  you need to have three instances of this Step in your Workflow.\\nIf there are targets\n  with different version numbers the app cannot be submitted for App Review or Beta\n  App Review.\\n\\n### Configuring the Step \\n\\n1. Set the file path to the `Info.plist`\n  file in the `Info.plist` file path input.\\n1. Add a value in the Build Number input.\n  \\n   This sets the CFBundleVersion key to the specified value in the `Info.plist`\n  file. The default value is the `$BITRISE_BUILD_NUMBER` Environment Variable.\\n1.\n  Optionally, add a value in the Version Number input. This will set the `CFBundleShortVersionString`\n  key to the specified value in the `Info.plist` file. This input is not required.\\n\\n###\n  Useful links \\n\\n- [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\\n-\n  [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\\n\\n###\n  Related Steps \\n\\n- [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\"\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2020-11-20T14:56:35.835233982Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 9a14663a47da5e8d36927b4e136d23b9f6a6576c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      **NOTE:**<br/>\n      If your IPA contains multiple build targets, they would need to have the same version number as your app's main target has.<br/>\n      You need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n      If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n    is_required: true\n    summary: Path to the given target's Info.plist file. You need to use this Step\n      for each archivable target of your project.\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n      You can find this in Xcode:\n      - Select your project in the **Project navigator**\n      - Go to the **General** tab and then the **Identity** section\n      - **Build field**\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n      You can find this in Xcode:\n      - Select your project in the **Project navigator**\n      - Go to the **General** tab and then the **Identity** section\n      - **Version field**\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    title: The bundle version used in the Info.plist file\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.12/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's bundle version in the `Info.plist` file to\n  the specified version number.\ndescription: \"Set the value of your iOS app's bundle version in the `Info.plist` file\n  to the specified version number. A great\\nway to keep track of versions when submitting\n  bug reports.\\n\\nIf your IPA contains multiple build targets, they need to have the\n  same version number as your app's main target has.\\nIn that case, you need to add\n  this Step to your Workflow for each build target: if you have, say, three targets,\n  you need to have three instances of this Step in your Workflow.\\nIf there are targets\n  with different version numbers the app cannot be submitted for App Review or Beta\n  App Review.\\n\\n### Configuring the Step \\n\\n1. In your Xcode project, set the Generate\n  Info.plist File to No, under PROJECT and TARGETS on the Build Settings tab.\\n1.\n  Manually create the `Info.plist` file and check it into source control. Make sure\n  you have all the necessary keys defined in the file.\\n1. Configure this step by\n  pointing the **Info.plist file path** input to the `Info.plist` file in the source\n  repo.\\n1. Add a value in the Build Number input. \\n   This sets the CFBundleVersion\n  key to the specified value in the `Info.plist` file. The default value is the `$BITRISE_BUILD_NUMBER`\n  Environment Variable.\\n1. Optionally, add a value in the Version Number input. This\n  will set the `CFBundleShortVersionString` key to the specified value in the `Info.plist`\n  file. This input is not required.\\n\\n### Useful links \\n\\n- [Build numbering and\n  app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\\n-\n  [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\\n\\n###\n  Related Steps \\n\\n- [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\\n-\n  [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\"\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2023-11-21T09:21:10.413646824Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: f0272f2f509fd80160677d6469703e7f87df05eb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given target's Info.plist file. You need to use this Step for each archivable target of your project.\n\n      **NOTE:**<br/>\n      If your IPA contains multiple build targets, they would need to have the same version number as your app's main target has.<br/>\n      You need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n      If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n    is_required: true\n    summary: Path to the given target's Info.plist file. You need to use this Step\n      for each archivable target of your project.\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n      You can find this in Xcode:\n      - Select your project in the **Project navigator**\n      - Go to the **General** tab and then the **Identity** section\n      - **Build field**\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n      You can find this in Xcode:\n      - Select your project in the **Project navigator**\n      - Go to the **General** tab and then the **Identity** section\n      - **Version field**\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in the Info.plist file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.2/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2016-03-03T13:33:41.223444754+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: cf0508303cb2d9144dd0076fbc3728c421f0ce0f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_required: true\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.3/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2016-04-11T10:52:48.328565432+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: 64c6c28d71df100aef23d6996b37b7ba013320c4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_required: true\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.4/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2016-08-03T13:30:51.159735976+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: 67540ab4c0810fe363ca46d11ca882a1ac44496b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- versioning\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_required: true\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.5/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2016-12-19T15:55:45.26352622+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: 7c7a72ecbbe88edfd91dfb5aa3300b9fb2c8170e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_required: true\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.7/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2018-07-12T14:19:53.199241944Z\nsource:\n  git: https://github.com/bitrise-io/steps-set-xcode-build-number.git\n  commit: 161e3b5b94e2eeb3ff7d316484217bea986b9968\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_required: true\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    title: The bundle version used in the Info.plist file\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.8/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\n\n  If your IPA contains multiple build targets ( e.g watch app, extensions ), they would need to have the same version number as your app's main target has.<br/>\n  You need to add this step to your workflow for every build target one by one.\n\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2019-05-17T12:58:49.904417433Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: b803006326613a3f005bd5037820233c1ad9d22e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      **NOTE:**<br/>\n      If your IPA contains multiple build targets ( e.g watch app, extensions ), they would need to have the same version number as your app's main target has.<br/>\n      You need to add this step to your workflow for every build target one by one.\n\n      If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n    is_required: true\n    summary: Path to the given target's Info.plist file. You need to use this step\n      for each archivable target of your project.\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    title: The bundle version used in the Info.plist file\n"
  },
  {
    "path": "steps/set-xcode-build-number/1.0.9/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: |-\n  Sets the value of Bundle version in the specified Info.plist file. A great\n  way to keep track of version when submitting bug reports.\n\n  If your IPA contains multiple build targets ( e.g watch app, extensions ), they would need to have the same version number as your app's main target has.<br/>\n  You need to add this step to your workflow for every build target one by one.\n\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\ndescription: Set the value of Bundle version in the project's Info.plist file to the\n  specified version number.\nwebsite: https://github.com/bitrise-io/set-xcode-build-number\nsource_code_url: https://github.com/bitrise-io/set-xcode-build-number\nsupport_url: https://github.com/bitrise-io/set-xcode-build-number/issues\npublished_at: 2019-10-15T09:11:52.995919755Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: c93dd8474677024f6aca4958bc5d894c93eb0831\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- xamarin\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      **NOTE:**<br/>\n      If your IPA contains multiple build targets ( e.g watch app, extensions ), they would need to have the same version number as your app's main target has.<br/>\n      You need to add this step to your workflow for every build target one by one.\n\n      If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n    is_required: true\n    summary: Path to the given target's Info.plist file. You need to use this step\n      for each archivable target of your project.\n    title: Info.plist file path\n  plist_path: null\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |\n      Set the CFBundleVersion to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Build field\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |\n      This offset will be added to `build_version` input's value.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |\n      Set the CFBundleShortVersionString to this value.\n\n      You can find this in Xcode:\n\n      - Select the your project in Project navigator\n      - Under General tab, in Identity section\n      - Version field\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    title: The bundle version used in the Info.plist file\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.0/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-02-08T13:35:48.764834347Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 57963610a6c55276178f9bf09ef976b498fe1dfb\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.1/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-02-12T11:48:39.711596748Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 1d9e8b717e998a3a1e2ba7621e894ab1cc2f9016\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.2/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-02-27T09:40:38.473047826Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: f48226b4728180e8257cd7211218dd697437ab29\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.3/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-05-01T08:03:05.256431284Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 84a689745b190eeedd86f3b449b3120ff523cfb8\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.4/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-05-08T08:23:39.703204852Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 2fbcb5125a77a68595255850dbf9e008028fc733\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.5/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-07-24T12:14:54.111114862Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 590bee606186c15e68e3954854e3222c7978f033\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.0.6/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2024-08-28T12:03:52.675471015Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: e7dfd8751816fbc2fcef992f1caa73492c32d7a7\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: This offset will be added to `build_version` input's value. It must\n      be a positive number.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.1.0/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2025-08-29T11:34:30.969679509Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 41f0d86ec87a7e23504fc0cf09992ff582800ff7\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |-\n      This offset will be added to `build_version` input's value. It must be a positive number in this case.\n\n      If you want to set the build version explicitly, set this to a negative number (e.g. -1).\n      In that case the offset is not added and the build version is set to the value of the Build Number (`build_version`) input.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.1.1/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2025-11-13T12:48:56.798464528Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: e805b75813432f17bd4332fbdbc4a2ac438b99cf\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: This will be either the CFBundleVersion in the Info.plist file or\n      the CURRENT_PROJECT_VERSION in the project file.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |-\n      This offset will be added to `build_version` input's value. It must be a positive number in this case.\n\n      If you want to set the build version explicitly, set this to a negative number (e.g. -1).\n      In that case the offset is not added and the build version is set to the value of the Build Number (`build_version`) input.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/2.2.0/step.yml",
    "content": "title: Set Xcode Project Build Number\nsummary: Set the value of your iOS app's build number to the specified version number.\ndescription: |-\n  Set the value of your iOS app's build number to the specified version number. A great way to keep track of versions\n  when submitting bug reports.\n\n  If your IPA contains multiple build targets, they need to have the same version number as your app's main target has.\n  In that case, you need to add this Step to your Workflow for each build target: if you have, say, three targets, you need to have three instances of this Step in your Workflow.\n  If there are targets with different version numbers the app cannot be submitted for App Review or Beta App Review.\n\n  ### Configuring the Step\n\n  The step can handle if versions numbers are specified in the project file (default configuration since Xcode 13) and the old style\n  where the version numbers appear in the **Info.plist** file. It can automatically detect which style is used and act accordingly.\n\n  For the simple projects you do not need to do anything because the step uses the previously defined $BITRISE_PROJECT_PATH\n  and $BITRISE_SCHEME env vars to detect the target settings.\n\n  For better customisation the step can be also instructed to look for a specific target and even for specific target configurations\n  to update the version numbers.\n\n  ### Useful links\n\n  - [Build numbering and app versioning](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/#setting-the-cfbundleversion-and-cfbundleshortversionstring-of-an-ios-app)\n  - [Current Project Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Current-Project-Version)\n  - [Marketing Version in Apple documentation](https://developer.apple.com/documentation/xcode/build-settings-reference#Marketing-Version)\n  - [CFBundleversion in Apple documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion)\n\n  ### Related Steps\n\n  - [Xcode Archive & Export for iOS](https://www.bitrise.io/integrations/steps/xcode-archive)\n  - [Set Android Manifest Version Code and Name](https://www.bitrise.io/integrations/steps/set-android-manifest-versions)\nwebsite: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsource_code_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number\nsupport_url: https://github.com/bitrise-steplib/steps-set-xcode-build-number/issues\npublished_at: 2025-11-21T14:09:32.201668644Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-set-xcode-build-number.git\n  commit: 025f0d151fcef4478efbcbcfa0d2257bb4287746\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-set-xcode-build-number\nrun_if: .IsCI\ninputs:\n- opts:\n    description: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xcode Scheme name.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Xcode Target name.\n\n      It is optional and if specified then the step will find the given target and update the version numbers for it.\n\n      If it is left empty then the step will use the scheme's default target to update the version numbers.\n    summary: Xcode Target name.\n    title: Target\n  target: null\n- configuration: null\n  opts:\n    description: |-\n      Xcode Configuration name.\n\n      It is optional and if specified then the step will only update the configuration with the given name.\n\n      If it is left empty then the step will update all of the target's configurations with the build and version number.\n    summary: Xcode Configuration name.\n    title: Configuration\n- build_version: $BITRISE_BUILD_NUMBER\n  opts:\n    description: |-\n      This will be either the CFBundleVersion in the Info.plist file or the CURRENT_PROJECT_VERSION in the project file.\n\n      If it is numeric then the step will increment it based on the `build_version_offset` input's value.\n      If the value is not numeric then the step will set the build version directly without any incrementing.\n    is_required: true\n    title: Build Number\n- build_version_offset: null\n  opts:\n    description: |-\n      This offset will be added to `build_version` input's value. It must be a positive number in this case.\n\n      If you want to set the build version explicitly, set this to a negative number (e.g. -1).\n      In that case the offset is not added and the build version is set to the value of the Build Number (`build_version`) input.\n    title: Build Number Offset\n- build_short_version_string: null\n  opts:\n    description: |-\n      This will be either the CFBundleShortVersionString in the Info.plist file or the MARKETING_VERSION in the project file.\n\n      If it is empty then the step will not modify the existing value.\n    title: Version Number\n- opts:\n    category: Debug\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XCODE_BUNDLE_VERSION: null\n  opts:\n    description: The bundle version used in either in Info.plist or project file\n    title: Xcode Bundle Version\n"
  },
  {
    "path": "steps/set-xcode-build-number/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/set-xcode-plist-value/1.0.0/step.yml",
    "content": "title: Set Xcode Plist Value\nsummary: |-\n  Sets the value of a key in the specified Info.plist file. A great\n  way to inject variables into the plist.\ndescription: Set the value of a key in the project's Info.plist file.\nwebsite: https://github.com/Reedyuk/set-xcode-plist-value\nsource_code_url: https://github.com/Reedyuk/set-xcode-plist-value\nsupport_url: https://github.com/Reedyuk/set-xcode-plist-value/issues\npublished_at: 2016-06-19T11:47:37.496457544+01:00\nsource:\n  git: https://github.com/Reedyuk/set-xcode-plist-value.git\n  commit: 23e04e8848164e5a1cf777636c522f502474492c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Path to the given project's Info.plist file.\n    is_required: true\n    title: Info.plist file path\n  plist_path: null\n- opts:\n    description: |\n      The key in the plist file you wish to set.\n    is_required: true\n    title: Plist key\n  plist_key: null\n- opts:\n    description: |\n      The value of the key in the plist file you wish to set.\n    is_required: true\n    title: Plist value\n  plist_value: null\n"
  },
  {
    "path": "steps/set-xcode-plist-value/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/share-pipeline-variable/1.0.0/step.yml",
    "content": "title: Share Pipeline variables\nsummary: Share environment variables between Pipeline Stages.\ndescription: |-\n  Share environment variables between Pipeline Stages.\n\n  Variables shared by the Step will be available in subsequent stages workflow's as [one-off env vars](https://devcenter.bitrise.io/en/builds/environment-variables.html#setting-a-custom-env-var-when-starting-a-build) as if provided manually on the website.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable/issues\npublished_at: 2023-04-11T13:36:56.653156+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable.git\n  commit: 0ebf00a05e9d686046a351992f59b68a30558e6e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nis_always_run: false\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of key - value pairs (`{key}={value}`).\n\n      The input uses a `{key}={value}` syntax.\n      The first equals sign (`=`) is the delimiter between the key and value of the environment variable.\n      A shorthand syntax of `ENV_KEY` can be used for `ENV_KEY=$ENV_KEY` when sharing an existing environment variable (ENV_KEY).\n\n      Examples:\n      ```\n      MY_ENV_KEY=my value\n      EXISTING_ENV_KEY\n      ```\n    is_required: true\n    summary: A newline (`\\n`) separated list of key - value pairs (`{key}={value}`).\n    title: Variables to share between Pipeline Stages\n  variables: null\n- app_url: $BITRISE_APP_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The app's URL on Bitrise.io.\n    title: Bitrise App URL\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The build's slug on Bitrise.io.\n    title: Bitrise Build Slug\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: API Token for the build on Bitrise.io.\n    title: Bitrise Build API Token\n"
  },
  {
    "path": "steps/share-pipeline-variable/1.1.0/step.yml",
    "content": "title: Share Pipeline variables\nsummary: Share environment variables between Pipeline Stages.\ndescription: |-\n  Share environment variables between Pipeline Stages.\n\n  Variables shared by the Step will be available in subsequent stages workflow's as [one-off env vars](https://devcenter.bitrise.io/en/builds/environment-variables.html#setting-a-custom-env-var-when-starting-a-build) as if provided manually on the website.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable/issues\npublished_at: 2023-09-08T07:50:30.035376313Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable.git\n  commit: c966900cd0c23a3f2aec1b814fc4c55cca197fad\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nis_always_run: false\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of key - value pairs (`{key}={value}`).\n\n      The input uses a `{key}={value}` syntax.\n      The first equals sign (`=`) is the delimiter between the key and value of the environment variable.\n      A shorthand syntax of `ENV_KEY` can be used for `ENV_KEY=$ENV_KEY` when sharing an existing environment variable (ENV_KEY).\n\n      Examples:\n      ```\n      MY_ENV_KEY=my value\n      EXISTING_ENV_KEY\n      ```\n    is_required: true\n    summary: A newline (`\\n`) separated list of key - value pairs (`{key}={value}`).\n    title: Variables to share between Pipeline Stages\n  variables: null\n- app_url: $BITRISE_APP_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The app's URL on Bitrise.io.\n    title: Bitrise App URL\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The build's slug on Bitrise.io.\n    title: Bitrise Build Slug\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: API Token for the build on Bitrise.io.\n    title: Bitrise Build API Token\n"
  },
  {
    "path": "steps/share-pipeline-variable/1.1.1/step.yml",
    "content": "title: Share Pipeline variables\nsummary: Share environment variables between Pipeline Stages.\ndescription: |-\n  Share environment variables between Pipeline Stages.\n\n  Variables shared by the Step will be available in subsequent stages workflow's as [one-off env vars](https://devcenter.bitrise.io/en/builds/environment-variables.html#setting-a-custom-env-var-when-starting-a-build) as if provided manually on the website.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable/issues\npublished_at: 2024-06-19T15:08:24.754515272Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable.git\n  commit: 214fdeeccafd7c3fdccde557c0f3025fe2146131\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nis_always_run: false\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of variable names or `NEW_ENV=NEW_VALUE` for declaring new variables.\n\n      The input uses a `KEY=VALUE` syntax for declaring new variables. The first `=` is the delimiter between the key and value of the environment variable.\n      A shorthand syntax of `ENV_KEY` can be used for `ENV_KEY=$ENV_KEY` when sharing an existing environment variable (ENV_KEY).\n\n      Examples:\n      ```\n      MY_ENV_VAR=my value\n      EXISTING_ENV_VAR\n      ```\n    is_required: true\n    summary: A newline (`\\n`) separated list of variable names or `NEW_ENV=NEW_VALUE`\n      for declaring new variables.\n    title: Variables to share between Pipeline Stages\n  variables: null\n- app_url: $BITRISE_APP_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The app's URL on Bitrise.io.\n    title: Bitrise App URL\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The build's slug on Bitrise.io.\n    title: Bitrise Build Slug\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: API Token for the build on Bitrise.io.\n    title: Bitrise Build API Token\n"
  },
  {
    "path": "steps/share-pipeline-variable/1.1.2/step.yml",
    "content": "title: Share Pipeline variables\nsummary: Share environment variables between Pipeline Workflows.\ndescription: |-\n  Share environment variables between Pipeline Workflows. This step works with both Pipelines and Pipelines with Stages.\n\n  Variables shared by the Step will be available in subsequent stages workflow's as [one-off env vars](https://devcenter.bitrise.io/en/builds/environment-variables.html#setting-a-custom-env-var-when-starting-a-build) as if provided manually on the website.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable/issues\npublished_at: 2025-03-18T07:33:53.449241549Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-share-pipeline-variable.git\n  commit: 5181cd6761b847d3cced8b4aed73627bce865ed9\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-share-pipeline-variable\nis_always_run: false\ninputs:\n- opts:\n    description: |-\n      A newline (`\\n`) separated list of variable names or `NEW_ENV=NEW_VALUE` for declaring new variables.\n\n      The input uses a `KEY=VALUE` syntax for declaring new variables. The first `=` is the delimiter between the key and value of the environment variable.\n      A shorthand syntax of `ENV_KEY` can be used for `ENV_KEY=$ENV_KEY` when sharing an existing environment variable (ENV_KEY).\n\n      Examples:\n      ```\n      MY_ENV_VAR=my value\n      EXISTING_ENV_VAR\n      ```\n    is_required: true\n    summary: A newline (`\\n`) separated list of variable names or `NEW_ENV=NEW_VALUE`\n      for declaring new variables.\n    title: Variables to share between Pipeline Workflows\n  variables: null\n- app_url: $BITRISE_APP_URL\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The app's URL on Bitrise.io.\n    title: Bitrise App URL\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    summary: The build's slug on Bitrise.io.\n    title: Bitrise Build Slug\n- build_api_token: $BITRISE_BUILD_API_TOKEN\n  opts:\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: API Token for the build on Bitrise.io.\n    title: Bitrise Build API Token\n"
  },
  {
    "path": "steps/share-pipeline-variable/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/sign-apk/0.9.1/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2015-12-09T17:55:36.31249557+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 7251b16474112d72cf4054289b90c5dfbdcc07fb\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/0.9.2/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-02-24T14:02:35.643487429Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: ebed88934e7e7b23eee1d2aadf584af94223ec2c\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/0.9.3/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-03-02T23:20:55.61341503+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: f191cb2cee6814d7c63504a5695985c92c0ed397\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/0.9.4/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-03-03T15:33:47.017761837+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: f75613a81d5859ab930d6b4b917f67a29f5693bc\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: null\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/0.9.5/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-04-14T14:01:10.551737042+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 31190d01cc7e955e87b585a2bb470b149df525e2\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/0.9.6/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-04-19T11:44:51.596106058+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 4cdaedf83546ed4fabf0e741b2f5f428ae8c867e\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/0.9.8/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-07-01T13:29:46.897951742+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 836c0f28b31a3cfce6c793546cac90c5bc187011\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.0.1/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-07-14T16:56:54.058897414+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 989c79b4527a1d3cff0a818cd0318a19632bce6f\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.1.0/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-09-28T14:05:20.09006183+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 1488db26fc3651a1983e5281d102a7412490d89d\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- android\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.1.1/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2016-10-14T12:06:10.644204014+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 5b31bac3c6d3722cb27b5475250c987a3365cf78\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- \"code sign\"\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.1.2/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2017-05-12T13:44:38.38476517+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 7f2f0b9d15918191509d2d1a1a75c862c96c2454\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- \"code sign\"\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.2.0/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2017-06-08T14:29:42.257279568+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 077506232e82db2dac5a880ba418439711a38139\nhost_os_tags:\n- osx-10.10\n- ubuntu\ntype_tags:\n- code-sign\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path(s) to the APK to sign.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.2.1/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2018-06-11T16:13:03.049768006+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 8c71c4045a51380d2b5e8e33023edd20a546373e\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- codesign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path(s) to the APK to sign.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.2.2/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: Sign APK.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2018-07-16T13:34:16.518568385+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: dfaae34e55597da23408d5b6a0c713179261699a\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path(s) to the APK to sign.\n\n      You can provide multiple APK paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.2.3/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: With this step, you can digitally sign your app's APK file in your workflow.\n  All you have to do is upload your keystore file in the Code signing tab of the Workflow\n  Editor.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2018-08-22T14:20:08.16959397Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: f7436831a1fadb9ea48249c68b00482034ef2982\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path(s) to the APK file to sign.\n\n      You can provide multiple APK file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n    is_required: true\n    summary: \"\"\n    title: apk path\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed apk path\n"
  },
  {
    "path": "steps/sign-apk/1.2.4/step.yml",
    "content": "title: Sign APK\nsummary: Sign APK\ndescription: With this step, you can digitally sign your app's APK file in your workflow.\n  All you have to do is upload your keystore file in the Code signing tab of the Workflow\n  Editor.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2018-11-09T12:06:17.464146743Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 80363a9611b8d37477092a51ad6d506c0b86a4f7\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: Build artifact path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    title: Bitrise signed build artifact path\n- BITRISE_APK_PATH: null\n  opts:\n    title: Bitrise signed build artifact path\n"
  },
  {
    "path": "steps/sign-apk/1.3.0/step.yml",
    "content": "title: Android Sign\nsummary: Android Sign\ndescription: With this step, you can digitally sign your app's APK file in your workflow.\n  All you have to do is upload your keystore file in the Code signing tab of the Workflow\n  Editor.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2019-05-31T13:03:16.748214575Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 8b297cca54018cf7af3ba7c5648971e8b1d8c80f\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.3.1/step.yml",
    "content": "title: Android Sign\nsummary: Android Sign\ndescription: With this step, you can digitally sign your app's APK file in your workflow.\n  All you have to do is upload your keystore file in the Code signing tab of the Workflow\n  Editor.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2019-06-11T11:35:32.760280797Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 07f6eb968af46371bd408392db59c6e8e6fea49a\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.4.0/step.yml",
    "content": "title: Android Sign\nsummary: Android Sign\ndescription: With this step, you can digitally sign your app's APK file in your workflow.\n  All you have to do is upload your keystore file in the Code signing tab of the Workflow\n  Editor.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2019-08-14T15:06:14.193054916Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: ff068384d941110fbc5723587785759da2e19890\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n"
  },
  {
    "path": "steps/sign-apk/1.4.1/step.yml",
    "content": "title: Android Sign\nsummary: Android Sign\ndescription: With this step, you can digitally sign your app's APK file in your workflow.\n  All you have to do is upload your keystore file in the Code signing tab of the Workflow\n  Editor.\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2019-08-16T11:17:20.572185717Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 3e70c00a4fa8825160ccc39611fa02061756b96b\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.4.2/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n[Android code signing using Android Sign\n  Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n[Android\n  deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n[Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n[Gradle\n  Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n[Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2020-01-09T11:51:04.941239287Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: c7a9393243444790cda9deb25f9a57d51909825f\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.4.3/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2020-02-13T12:29:04.671793449Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: f9367703d4b5c99c114830b5c79bb709780ca207\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- jarsigner_options: \"\"\n  opts:\n    description: |\n      __deprecated!__ jarsigner options are detected from the keystore\n    summary: \"\"\n    title: Additional options for jarsigner\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.5.0/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2020-09-04T09:45:18.416982003Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: fec3dff57cc4a3ebb93cbb89e531e06ee6e22a8b\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files\n    is_required: true\n    is_sensitive: false\n    summary: \"\"\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n  page_align: \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.6.0/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2020-09-15T09:58:04.210529681Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 76ac7c720742e45651ffbe7186f66539a1f7d452\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Keystore alias\n- opts:\n    description: |\n      If key password equals to keystore password, you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    summary: \"\"\n    title: Private key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    is_sensitive: false\n    summary: \"\"\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    is_sensitive: false\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.1/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2020-09-30T11:36:31.530965144Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: e6f8b899879d6cd9128be17fc55b2592a7cba435\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using apksigner instead\n      of jarsigner.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of --min-sdk-version and --max-sdk-version to decide when to apply this Signature Scheme.\n      - `v2`: Sets --v2-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets --v3-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets --v4-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of --min-sdk-version and --max-sdk-version.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: true\n  opts:\n    description: |\n      Whether to permit signing android:debuggable=\"true\" APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.10/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2022-11-29T10:41:33.348016919Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 8c963690c110d36bb328899e2c49bd4fc6498934\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using `apksigner` instead\n      of `jarsigner`.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is `app-release-bitrise-signed`.\n      Else it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.11/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the **App Settings** page, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2024-07-15T14:49:23.084952277Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: a4c00f345190a7b54d9d63e602b71b1e026a26b4\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using `apksigner` instead\n      of `jarsigner`.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is `app-release-bitrise-signed`.\n      Else it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.2/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2020-10-06T10:50:43.617725853Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 5124b4a03339bcb6f52ae562f37d2dece2d1c6cf\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using apksigner instead\n      of jarsigner.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of --min-sdk-version and --max-sdk-version to decide when to apply this Signature Scheme.\n      - `v2`: Sets --v2-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets --v3-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets --v4-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of --min-sdk-version and --max-sdk-version.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: true\n  opts:\n    description: |\n      Whether to permit signing android:debuggable=\"true\" APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.3/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2021-01-04T10:31:00.88127812Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 2b1d2061a1d1e5150e9e0b076bd511b36e55155f\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: zip\n  apt_get:\n  - name: zip\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using apksigner instead\n      of jarsigner.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of --min-sdk-version and --max-sdk-version to decide when to apply this Signature Scheme.\n      - `v2`: Sets --v2-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets --v3-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets --v4-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of --min-sdk-version and --max-sdk-version.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: true\n  opts:\n    description: |\n      Whether to permit signing android:debuggable=\"true\" APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.4/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2021-03-02T08:09:58.843752219Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 0895f1674a3fff6734029458077541c0b596caab\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: zip\n  apt_get:\n  - name: zip\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using apksigner instead\n      of jarsigner.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of --min-sdk-version and --max-sdk-version to decide when to apply this Signature Scheme.\n      - `v2`: Sets --v2-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets --v3-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets --v4-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of --min-sdk-version and --max-sdk-version.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: true\n  opts:\n    description: |\n      Whether to permit signing android:debuggable=\"true\" APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.5/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2021-05-04T11:56:55.461001254Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: c4490a0672574d5f6c55aeb32c936050d7789f6a\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\ndeps:\n  brew:\n  - name: zip\n  apt_get:\n  - name: zip\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using apksigner instead\n      of jarsigner.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of --min-sdk-version and --max-sdk-version to decide when to apply this Signature Scheme.\n      - `v2`: Sets --v2-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets --v3-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets --v4-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of --min-sdk-version and --max-sdk-version.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: true\n  opts:\n    description: |\n      Whether to permit signing android:debuggable=\"true\" APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.6/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: \"Once you have uploaded your keystore file and provided your keystore\n  credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign**\n  Step signs your APK digitally. \\nBitrise assigns Environment Variables to the uploaded\n  file and credentials, and uses those in the respective fields of the **Android Sign**\n  Step. \\nOnce the Step runs, it produces a signed APK or App Bundle which will be\n  used as the input value of the **App file path** field in the **Google Play Deploy**\n  Step.   \\n\\n### Configuring the Step\\n\\n1. Add the **Android Sign** Step after a\n  build Step in your deploy workflow.\\n2. Upload the keystore file to the **Upload\n  file** field on the **Code Signing** tab.\\n3. Provide your keystore password, keystore\n  alias and private key password to the relevant fields on the **Code Signing** tab.\\n4.\n  Run your build.\\n\\n\\n### Troubleshooting\\nMake sure you have the **Android Sign**\n  Step right after a build Steps but before **Deploy to Google Play** Step in your\n  deploy workflow.\\nIf you wish to get your Android project signed automatically,\n  use the **Android Sign** Step and do not set any gradle task for the signing, otherwise,\n  the Step will fail.\\n\\n\\n### Useful links\\n- [Android code signing using Android\n  Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\\n-\n  [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\\n\\n\\n###\n  Related Steps\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\\n- [Deploy\n  to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2021-08-05T09:25:36.587836257Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: ebfd11b238fc2bb8a955cf059ae2da3dca37ce15\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: |-\n    $BITRISE_APK_PATH\n    $BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (ex: https://URL/TO/keystore.jks).\n      For local keystores provide file path url. (ex: file://PATH/TO/keystore.jks).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using apksigner instead\n      of jarsigner.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of --min-sdk-version and --max-sdk-version to decide when to apply this Signature Scheme.\n      - `v2`: Sets --v2-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets --v3-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets --v4-signing-enabled true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of --min-sdk-version and --max-sdk-version.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: true\n  opts:\n    description: |\n      Whether to permit signing android:debuggable=\"true\" APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is \"app-release-bitrise-signed\".\n      Else it's the specified name. Do not add extensione here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.7/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2022-02-23T08:22:04.579285043Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: a7fb15061e8d49642335566d46ec6665acafb8a6\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using `apksigner` instead\n      of `jarsigner`.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is `app-release-bitrise-signed`.\n      Else it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.8/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2022-06-07T18:15:45.132809498Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 845c384eff4a5b4ab5009ea7113fe3dc79011f4e\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using `apksigner` instead\n      of `jarsigner`.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is `app-release-bitrise-signed`.\n      Else it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/1.7.9/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the Workflow Editor, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2022-08-26T13:53:11.481434665Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 99622883b486f181dfd8fa5aa8d02c5b6347225d\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: Indicates if the signature should be done using `apksigner` instead\n      of `jarsigner`.\n    is_required: true\n    title: Enables apksigner\n    value_options:\n    - \"true\"\n    - \"false\"\n  use_apk_signer: \"false\"\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If is empty then the output name is `app-release-bitrise-signed`.\n      Else it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/2.0.0/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the **App Settings** page, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2024-10-02T07:56:54.068304949Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 4a34c1b4be8e6ac74a52ae1446820fd0cef8832a\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Matching password to `keystore_url`. Do not confuse this with `key_password`!\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: Alias of key inside `keystore_url`.\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: |\n      Indicates which tool should be used for signing the app.\n\n      - `automatic`: Uses the `apksigner` tool to sign an APK and `jarsigner` tool to sign an AAB file.\n      - `apksigner`: Uses the `apksigner` tool to sign the app.\n      - `jarsigner`: Uses the `jarsigner` tool to sign the app.\n    is_required: true\n    title: Signer tool\n    value_options:\n    - automatic\n    - apksigner\n    - jarsigner\n  signer_tool: automatic\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If empty, then the output name is `app-release-bitrise-signed`.\n      Otherwise, it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/2.0.1/step.yml",
    "content": "title: Android Sign\nsummary: Signs your APK or Android App Bundle before uploading it to Google Play Store.\ndescription: |-\n  Once you have uploaded your keystore file and provided your keystore credentials on the **Code Signing** tab of the **App Settings** page, the **Android Sign** Step signs your APK digitally.\n  Bitrise assigns Environment Variables to the uploaded file and credentials, and uses those in the respective fields of the **Android Sign** Step.\n  Once the Step runs, it produces a signed APK or App Bundle which will be used as the input value of the **App file path** field in the **Google Play Deploy** Step.\n\n  ### Configuring the Step\n\n  1. Add the **Android Sign** Step after a build Step in your deploy workflow.\n  2. Upload the keystore file to the **Upload file** field on the **Code Signing** tab.\n  3. Provide your keystore password, keystore alias and private key password to the relevant fields on the **Code Signing** tab.\n  4. Run your build.\n\n  ### Troubleshooting\n  Make sure you have the **Android Sign** Step right after a build Steps but before **Deploy to Google Play** Step in your deploy workflow.\n  If you wish to get your Android project signed automatically, use the **Android Sign** Step and do not set any gradle task for the signing, otherwise, the Step will fail.\n\n  ### Useful links\n  - [Android code signing using Android Sign Step](https://devcenter.bitrise.io/code-signing/android-code-signing/android-code-signing-using-bitrise-sign-apk-step/)\n  - [Android deployment](https://devcenter.bitrise.io/deploy/android-deploy/android-deployment-index/)\n\n  ### Related Steps\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Gradle Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-sign-apk\nsource_code_url: https://github.com/bitrise-steplib/steps-sign-apk\nsupport_url: https://github.com/bitrise-steplib/steps-sign-apk/issues\npublished_at: 2025-11-13T08:25:14.247960443Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-sign-apk.git\n  commit: 79ea8bc97cd047e5acdcc14a7acbb548fef735e8\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- code-sign\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-sign-apk\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- android_app: $BITRISE_APK_PATH\\n$BITRISE_AAB_PATH\n  opts:\n    description: |-\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    is_required: true\n    summary: '`Android App Bundle (.aab)` or `Android Application Package (.apk)`'\n    title: App file path.\n- keystore_url: $BITRISEIO_ANDROID_KEYSTORE_URL\n  opts:\n    description: |-\n      For remote keystores you can provide any download location (e.g. `https://URL/TO/keystore.jks`).\n      For local keystores provide file path url. (e.g. `file://PATH/TO/keystore.jks`).\n    is_required: true\n    is_sensitive: true\n    title: Keystore url\n- keystore_password: $BITRISEIO_ANDROID_KEYSTORE_PASSWORD\n  opts:\n    description: Matching password to `keystore_url`. Do not confuse this with `key_password`!\n    is_required: true\n    is_sensitive: true\n    title: Keystore password\n- keystore_alias: $BITRISEIO_ANDROID_KEYSTORE_ALIAS\n  opts:\n    description: Alias of key inside `keystore_url`.\n    is_required: true\n    is_sensitive: true\n    title: Key alias\n- opts:\n    description: |\n      If key password equals to keystore password (not recommended), you can leave it empty.\n      Otherwise specify the private key password.\n    is_sensitive: true\n    title: Key password\n  private_key_password: $BITRISEIO_ANDROID_KEYSTORE_PRIVATE_KEY_PASSWORD\n- opts:\n    description: |\n      If enabled, it tells zipalign to use memory page alignment for stored shared object files.\n\n      - `automatic`: Enable page alignment for .so files, unless atribute `extractNativeLibs=\"true\"` is set in the AndroidManifest.xml\n      - `true`: Enable memory page alignment for .so files\n      - `false`: Disable memory page alignment for .so files\n    is_required: true\n    title: Page alignment\n    value_options:\n    - \"true\"\n    - \"false\"\n    - automatic\n  page_align: automatic\n- opts:\n    description: |\n      Indicates which tool should be used for signing the app.\n\n      - `automatic`: Uses the `apksigner` tool to sign an APK and `jarsigner` tool to sign an AAB file.\n      - `apksigner`: Uses the `apksigner` tool to sign the app.\n      - `jarsigner`: Uses the `jarsigner` tool to sign the app.\n    is_required: true\n    title: Signer tool\n    value_options:\n    - automatic\n    - apksigner\n    - jarsigner\n  signer_tool: automatic\n- opts:\n    description: |\n      If set, enforces which Signature Scheme should be used by the project.\n\n      - `automatic`: The tool uses the values of `--min-sdk-version` and `--max-sdk-version` to decide when to apply this Signature Scheme.\n      - `v2`: Sets `--v2-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v2.\n      - `v3`: Sets `--v3-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v3.\n      - `v4`: Sets `--v4-signing-enabled` true, and determines whether apksigner signs the given APK package using the APK Signature Scheme v4. This scheme produces a signature in an separate file (apk-name.apk.idsig). If true and the APK is not signed, then a v2 or v3 signature is generated based on the values of `--min-sdk-version` and `--max-sdk-version`.\n    is_required: true\n    title: APK Signature Scheme\n    value_options:\n    - automatic\n    - v2\n    - v3\n    - v4\n  signer_scheme: automatic\n- debuggable_permitted: \"true\"\n  opts:\n    description: |\n      Whether to permit signing `android:debuggable=\"true\"` APKs. Android disables some of its security protections for such apps.\n    is_required: true\n    title: Enable debuggable APKs\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |\n      If empty, then the output name is `app-release-bitrise-signed`.\n      Otherwise, it's the specified name. Do not add the file extension here.\n    summary: Name of the produced output artifact\n    title: Artifact name\n  output_name: \"\"\n- opts:\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |-\n      __This input is deprecated and will be removed on 20 August 2019, use `App file path` input instead!__\n\n      Path(s) to the build artifact file to sign (`.aab` or `.apk`).\n\n      You can provide multiple build artifact file paths separated by `|` character.\n\n      Deprecated, use `android_app` instead.\n\n      Format examples:\n\n      - `/path/to/my/app.apk`\n      - `/path/to/my/app1.apk|/path/to/my/app2.apk|/path/to/my/app3.apk`\n\n      - `/path/to/my/app.aab`\n      - `/path/to/my/app1.aab|/path/to/my/app2.apk|/path/to/my/app3.aab`\n    summary: '`Android App Bundle (.aab)` or `Android Aplication Package (.apk)`.\n      Deprecated, use `android_app` instead.'\n    title: '[DEPRECATED] Build artifact path.'\noutputs:\n- BITRISE_SIGNED_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed APK.\n      If the build generates more than one APK this output will contain the last one's path.\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_SIGNED_APK_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated APKs\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: List of the signed (and copied) APK paths\n    title: List of the signed APK paths\n- BITRISE_SIGNED_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path of the signed AAB.\n      If the build generates more than one AAB this output will contain the last one's path.\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n- BITRISE_SIGNED_AAB_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the paths of the generated AABs.\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: List of the signed (and copied) AAB paths\n    title: List of the signed AAB paths\n- BITRISE_APK_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed APK(s).\n      If multiple APKs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk`\n    summary: Path of the signed APK\n    title: Path of the signed APK\n- BITRISE_AAB_PATH: null\n  opts:\n    description: |-\n      This output will include the path(s) of the signed AAB(s).\n      If multiple AABs are provided for signing the output paths are separated with `|` character, for example, `app-armeabi-v7a-debug.aab|app-mips-debug.aab|app-x86-debug.aab`\n    summary: Path of the signed AAB\n    title: Path of the signed AAB\n"
  },
  {
    "path": "steps/sign-apk/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/slack/2.1.0/step.yml",
    "content": "title: Send a Slack message\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nsummary: |-\n  Notify your team on Slack and spice up your message with a custom sender\n  image or choose one of the awesome Emojis. You can even set different sender\n  name, image and message for builds that failed or succeeded!\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2015-08-19T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 756f39f76f94d525aaea2fc2d0c5a23799f8ec97\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- IM\n- notification\ndependencies:\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @everyone\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: null\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n"
  },
  {
    "path": "steps/slack/2.2.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2016-09-12T16:09:46.696075285+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 129d26c12090d7f7ba9461b49066fc0b73ed71e3\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- IM\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @everyone\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- formatting_mode: attachment\n  opts:\n    description: |\n      The formatting mode to use.\n\n      Slack can present the message\n      as a markdown-ish `text`, with the formatting you can\n      use in the Slack client when you chat, or can accept it\n      as an `attachment`.\n\n      The `attachment` mode supports coloring but does not\n      support the regular highlighting format, like `*bold*`\n      or `_italic_`.\n    is_expand: true\n    is_required: true\n    title: Formatting mode\n    value_options:\n    - attachment\n    - text\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.3.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2016-09-12T18:21:47.590953614+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: e8b0c061c23282c0b775b893e31a277d40e06916\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @everyone\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.4.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2017-05-09T17:40:56.840754429+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: c68cef2dbf5068b7f83e9ea676dd714a4d06d2ad\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @everyone\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.4.1/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2017-05-09T20:35:22.919619947+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 9add234a3f5d6f4fb22d7c90b1bf64c700343f4b\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @everyone\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.5.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2017-05-22T17:26:33.273863749+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: b2615bb34d61c325c3ee4e3a71accd7358977822\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @everyone\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.6.1/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2017-08-07T14:22:02.456813933+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 14a9b8c717c25266b918746f01c8712360059dd8\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @username\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    is_expand: true\n    is_required: false\n    title: Link Names\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.6.2/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2017-08-28T09:45:29.397091406+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: aece340289614c297ec354d2897ea7dd0c315e64\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @username\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    is_expand: true\n    is_required: false\n    title: Link Names\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.6.3/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2017-10-30T16:06:31.208548118+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 9fce4711a463435dda446a2f348b6406e1c48575\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @username\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise CI - OK\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise CI - ERROR\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: Type your message here\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    is_expand: true\n    is_required: false\n    title: Link Names\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.6.4/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-01-26T15:37:30.339474258+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 7c95934f46665575e243c88fdab0acb47bbb7595\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @username\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: |-\n    *Build succeeded!* :tada:\n\n    *App*\n    $BITRISE_APP_TITLE ($BITRISE_APP_URL)\n    *Build URL*\n    $BITRISE_BUILD_URL\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: |-\n    *Build failed!*\n\n    *App*\n    $BITRISE_APP_TITLE ($BITRISE_APP_URL)\n    *Build URL*\n    $BITRISE_BUILD_URL\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    is_expand: true\n    is_required: false\n    title: Link Names\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.6.5/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-01-31T16:26:36.735884039+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: ecd90cdd0b986b7fec95052c36c528729d0e6152\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      * channel example: #general\n      * username example: @username\n    is_expand: true\n    is_required: false\n    title: Target Slack channel, group or username\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    is_expand: true\n    is_required: false\n    title: The 'from' name\n- from_username_on_error: Bitrise\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The 'from' name - if the build failed\n- message: |-\n    *Build succeeded on ${BITRISE_GIT_BRANCH}!* :tada:\n\n    *App* - <$BITRISE_APP_URL|$BITRISE_APP_TITLE>\n    *Build* - <$BITRISE_BUILD_URL|#$BITRISE_BUILD_NUMBER>\n    *Workflow* - $BITRISE_TRIGGERED_WORKFLOW_ID\n    $BITRISE_PUBLIC_INSTALL_PAGE_URL\n  opts:\n    is_expand: true\n    is_required: true\n    title: The message you want to send\n- message_on_error: |-\n    *Build failed on ${BITRISE_GIT_BRANCH}!*\n\n    *App* - <$BITRISE_APP_URL|$BITRISE_APP_TITLE>\n    *Build* - <$BITRISE_BUILD_URL|#$BITRISE_BUILD_NUMBER>\n    *Workflow* - $BITRISE_TRIGGERED_WORKFLOW_ID\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: The message you want to send - if the build failed\n- color: good\n  opts:\n    description: |\n      Color of the message. You can use hex color codes,\n      or the predefined Slack color words like `good`, `warning` or `danger`.\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_expand: true\n    is_required: true\n    title: Message color\n- color_on_error: danger\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Message color\n- image_url: null\n  opts:\n    description: |\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL\n- image_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.**\n      Optionally render an image from a URL.\n      You can include GIFs.\n    is_expand: true\n    is_required: false\n    title: Image URL - if build failed\n- emoji: ':white_check_mark:'\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    is_expand: true\n    is_required: false\n    title: Emoji Icon\n- emoji_on_error: ':no_entry_sign:'\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Emoji Icon - if build failed\n- icon_url: null\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: Icon URL\n- icon_url_on_error: null\n  opts:\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    is_expand: true\n    is_required: false\n    title: Icon URL - if build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    is_expand: true\n    is_required: false\n    title: Link Names\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/slack/2.7.1/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-02-22T14:32:44.40428293+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 0e292c5b84562f4a7bb7ae0252cdcc9e893c213f\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_expand: true\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    is_expand: true\n    is_required: false\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n    Public Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/2.7.2/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-02-23T11:24:30.520615457+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 0fbf886118fce8c8d8999be29c4b37be57081187\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/2.7.3/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-06-25T12:55:33.045998895+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: bc760b7c4bc26c65e752ec0a74f80d1d01f49fda\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/2.7.4/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to register an **Incoming WebHook integration** at:\n  https://**YOURTEAMNAME**.slack.com/services\n\n  On the WebHook integration's page copy the **Webhook URL**.\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-08-31T08:13:06.671877849Z\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 7058418a996551b1c2bb296e646dfc1638b11579\nhost_os_tags:\n- osx-10.10\n- ubuntu-14.04\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_required: true\n    is_sensitive: true\n    title: Slack Webhook URL\n  webhook_url: null\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.0.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You have to create a bot with an API token at https://bitfall.slack.com/apps/manage/custom-integrations\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-10-03T12:27:36.65776816Z\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: d77fab63642cc2e89762a9ac9c9e6330f236239c\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- api_token: null\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Slack API token for your Bot\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.1.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You can either setup a **bot user with API token** or setup **Incoming WebHook integration**.\n\n  To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n\n  To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-10-09T16:02:10.101042719Z\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: 5cd9ec2addd53e71f7b2a7205abb280b2ad2e847\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.1.1/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You can either setup a **bot user with API token** or setup **Incoming WebHook integration**.\n\n  To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n\n  To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-12-14T14:37:49.553543736Z\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: efba26997c8330dabeac9f3aa05b60cdb7f03eeb\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.1.2/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You can either setup a **bot user with API token** or setup **Incoming WebHook integration**.\n\n  To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n\n  To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2018-12-18T08:50:40.827668346Z\nsource:\n  git: https://github.com/bitrise-io/steps-slack-message.git\n  commit: b1e49748fb27696d0d66a8f66f04b420c36d9e4b\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.1.3/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You can either setup a **bot user with API token** or setup **Incoming WebHook integration**.\n\n  To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n\n  To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n\n  *Don't forget to enable this Step to **Always run** if\n  you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2019-05-31T09:01:38.068185284Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 178fc8990a4118dfdd124991777a25b2917aaa57\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.1.4/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |\n  Send a [Slack](https://slack.com/) message to a channel or group.\n\n  You can either setup a **bot user with API token** or setup **Incoming WebHook integration**.\n\n  To register an **Incoming WebHook integration** visit: [https://api.slack.com/incoming-webhooks](https://api.slack.com/incoming-webhooks)\n\n  To setup a **bot with an API token** visit: [https://api.slack.com/bot-users](https://api.slack.com/bot-users)\n\n  *Don't forget to enable this Step to **Always run** if you want to get notified about failed builds as well!*\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2020-07-09T13:27:14.779851083Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: a1aaf01a9e9e04f0be4a44bc4f8ca7534a8cc85f\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n\n       Examples:\n\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required, unless providing only attachments instead.\n    title: Text of the message to send.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text of the message to send, if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally you can specify a custom icon image URL\n      which will be presented as the sender icon.\n\n      Slack recommends an image a square image,\n      which can't be larger than 128px in width nor in height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n\n      *If you specify this input, the Emoji input will be ignored!*\n    title: URL to an image to use as the icon for the message.\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: URL to an image to use as the icon for the message if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The one which should be presented as the sender of the message\n    title: the bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: the bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.1.5/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.  \\n\\n### Troubleshooting \\n\\nDon't forget to make sure that the Step runs\n  even if the build fails: you need to set it so that it runs even if a previous Step\n  failed. \\n\\nIf the Step fails, check your Slack settings, the incoming webhook or\n  the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n- [Integrating\n  with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2020-11-20T14:51:43.63256766Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 556b768a56eea08966f8f968a2d1700750070c63\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.2.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.  \\n\\n### Troubleshooting \\n\\nDon't forget to make sure that the Step runs\n  even if the build fails: you need to set it so that it runs even if a previous Step\n  failed. \\n\\nIf the Step fails, check your Slack settings, the incoming webhook or\n  the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n- [Integrating\n  with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2021-09-30T08:29:14.393475623Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: d3ce902c2159b2d41aecd3b560092d1662b0970b\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.2.1/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.  \\n\\n### Troubleshooting \\n\\nDon't forget to make sure that the Step runs\n  even if the build fails: you need to set it so that it runs even if a previous Step\n  failed. \\n\\nIf the Step fails, check your Slack settings, the incoming webhook or\n  the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n- [Integrating\n  with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2021-10-04T06:56:31.328665314Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: d992d8a7d552a49238bad03d4791efa92864689e\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.3.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.  \\n\\n### Troubleshooting \\n\\nDon't forget to make sure that the Step runs\n  even if the build fails: you need to set it so that it runs even if a previous Step\n  failed. \\n\\nIf the Step fails, check your Slack settings, the incoming webhook or\n  the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n- [Integrating\n  with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2022-04-28T15:18:51.736370264Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: eb741f92b567b58072fcad501843edb4ac804105\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n"
  },
  {
    "path": "steps/slack/3.4.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.\\n\\nNote that this step always sends a message (either to `channel` or `channel_on_error`).\n  If your use case is to send a message only on success or on failure, then you can\n  [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\\n\\n###\n  Troubleshooting \\n\\nIf the Step fails, check your Slack settings, the incoming webhook\n  or the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n-\n  [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2022-07-05T16:03:38.781796973Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 831f0aa578b692c68664629df7d1eae64981fcf9\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/3.5.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.\\n\\nNote that this step always sends a message (either to `channel` or `channel_on_error`).\n  If your use case is to send a message only on success or on failure, then you can\n  [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\\n\\n###\n  Troubleshooting \\n\\nIf the Step fails, check your Slack settings, the incoming webhook\n  or the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n-\n  [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2022-09-20T09:41:55.781440351Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: b38da2389d7fc5a09cf9b6f34db710f0c8a8ca29\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/4.0.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.\\n\\nNote that this step always sends a message (either to `channel` or `channel_on_error`).\n  If your use case is to send a message only on success or on failure, then you can\n  [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\\n\\n###\n  Troubleshooting \\n\\nIf the Step fails, check your Slack settings, the incoming webhook\n  or the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n-\n  [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2023-08-08T07:40:29.819117787Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 88a2c0726cea61995ebe17ee8ad4dad1b71d48f2\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Pipeline|${BITRISEIO_PIPELINE_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Pipeline Build|${BITRISEIO_PIPELINE_BUILD_URL}\n    View Workflow Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones when sending the slack message.\n    is_dont_change_value: true\n    summary: It uses the build state as if the Pipeline Build had finished with the\n      previous stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones.\n    is_dont_change_value: true\n    summary: It sets the build state as if the Build had finished already\n    title: Build Status\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/4.1.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either an incoming Slack\n  webhook or a Slack bot user with an API token. You can set up both on your Slack\n  account:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n- [Bot\n  user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready with\n  those, come back to Bitrise and configure the Step itself.\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.\\n\\nNote that this step always sends a message (either to `channel` or `channel_on_error`).\n  If your use case is to send a message only on success or on failure, then you can\n  [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\\n\\n###\n  Troubleshooting \\n\\nIf the Step fails, check your Slack settings, the incoming webhook\n  or the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n-\n  [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2023-11-24T15:58:57.097004146Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 73c8736f5aa35ffd921b5ed3ecfe113009ab2df7\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **Either webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (Webhook or API token is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: \"Timestamp of the message to be updated.\\n\\nWhen **Message Timestamp**\n      is provided an existing Slack message will be updated, identified by the provided\n      timestamp.  \\nExample: `\\\"1405894322.002768\\\"`.\"\n    summary: Timestamp of the message to be updated.\n    title: Message Timestamp\n  ts: null\n- opts:\n    category: If Build Failed\n    description: \"Timestamp of the message to be updated if the build failed.\\n\\nWhen\n      **Message Timestamp if the build failed** is provided an existing Slack message\n      will be updated, identified by the provided timestamp.  \\nExample: `\\\"1405894322.002768\\\"`.\"\n    summary: Timestamp of the message to be updated if the build failed.\n    title: Message Timestamp if the build failed\n  ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer if the build failed\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- footer_icon_on_error: https://github.com/bitrise-io.png?size=16\n  opts:\n    category: If Build Failed\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text if the build failed\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Pipeline|${BITRISEIO_PIPELINE_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Pipeline Build|${BITRISEIO_PIPELINE_BUILD_URL}\n    View Workflow Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones when sending the slack message.\n    is_dont_change_value: true\n    summary: It uses the build state as if the Pipeline Build had finished with the\n      previous stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones.\n    is_dont_change_value: true\n    summary: It sets the build state as if the Build had finished already\n    title: Build Status\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/4.2.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either a configured\n  Slack Integration in your workspace, an incoming Slack webhook or a Slack bot user\n  with an API token. For the former see your Workspace settings, for the latter two,\n  you can set them up in Slack:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n-\n  [Bot user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready\n  with those, come back to Bitrise and configure the Step itself:\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.\\n\\n\\nIn case of the Slack Integration usecase you can copy the ID in your\n  Workspace settings, on the Integrations page. This ID is not senstive, you can use\n  it as a step input as-is, or put it into a regular environment variable.\\n\\nNote\n  that this step always sends a message (either to `channel` or `channel_on_error`).\n  If your use case is to send a message only on success or on failure, then you can\n  [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\\n\\n###\n  Troubleshooting \\n\\nIf the Step fails, check your Slack settings, the incoming webhook\n  or the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n-\n  [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2025-01-13T15:45:57.224510574Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 2c50cbc23359d1dd1267a72c2f430f7638657984\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required)\n  workspace_slack_integration_id: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required) if the build failed\n  workspace_slack__integration_id_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (One of webhook URL, API token or workspace integration\n      ID is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: \"Timestamp of the message to be updated.\\n\\nWhen **Message Timestamp**\n      is provided an existing Slack message will be updated, identified by the provided\n      timestamp.  \\nExample: `\\\"1405894322.002768\\\"`.\"\n    summary: Timestamp of the message to be updated.\n    title: Message Timestamp\n  ts: null\n- opts:\n    category: If Build Failed\n    description: \"Timestamp of the message to be updated if the build failed.\\n\\nWhen\n      **Message Timestamp if the build failed** is provided an existing Slack message\n      will be updated, identified by the provided timestamp.  \\nExample: `\\\"1405894322.002768\\\"`.\"\n    summary: Timestamp of the message to be updated if the build failed.\n    title: Message Timestamp if the build failed\n  ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer if the build failed\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- footer_icon_on_error: https://github.com/bitrise-io.png?size=16\n  opts:\n    category: If Build Failed\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text if the build failed\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Pipeline|${BITRISEIO_PIPELINE_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Pipeline Build|${BITRISEIO_PIPELINE_BUILD_URL}\n    View Workflow Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones when sending the slack message.\n    is_dont_change_value: true\n    summary: It uses the build state as if the Pipeline Build had finished with the\n      previous stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones.\n    is_dont_change_value: true\n    summary: It sets the build state as if the Build had finished already\n    title: Build Status\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/4.2.1/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: \"\\nSend a [Slack](https://slack.com/) message to a Slack user, a group,\n  or a channel. Create and customize the messages however you see fit. Among other\n  things, you can:\\n\\n- Set a different text for failed and successful builds.\\n-\n  Add an icon and/or emojis to your messages. \\n- Set the bot user's name for the\n  messages.\\n- Linkify channel names and usernames.\\n- Add and customize attachments.\n  \\n\\n### Configuring the Step \\n\\nTo use this Step, you need either a configured\n  Slack Integration in your workspace, an incoming Slack webhook or a Slack bot user\n  with an API token. For the former see your Workspace settings, for the latter two,\n  you can set them up in Slack:\\n\\n- [Incoming webhooks](https://api.slack.com/incoming-webhooks).\\n-\n  [Bot user with an API token](https://api.slack.com/bot-users).\\n\\nOnce you're ready\n  with those, come back to Bitrise and configure the Step itself:\\n\\n1. Create a [Secret\n  Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either\n  your Slack webhook URL or your Slack API token.\\n1. Add the Secret to either the\n  **Slack Webhook URL** or the **Slack API token** input.\\n1. Toggle the **Run if\n  previous Step failed** option on - you should see a white checkmark on green background\n  next to it. This allows Slack messages to be sent for failed builds, too.\\n1. In\n  the **Target Slack channel, group or username**, set where the Slack message should\n  be sent. \\n1. Customize your messages as you'd like. For the details, see the respective\n  inputs.\\n\\n\\nIn case of the Slack Integration usecase you can copy the ID in your\n  Workspace settings, on the Integrations page. This ID is not senstive, you can use\n  it as a step input as-is, or put it into a regular environment variable.\\n\\nNote\n  that this step always sends a message (either to `channel` or `channel_on_error`).\n  If your use case is to send a message only on success or on failure, then you can\n  [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\\n\\n###\n  Troubleshooting \\n\\nIf the Step fails, check your Slack settings, the incoming webhook\n  or the API token, and your Slack channel permissions. \\n\\n### Useful links \\n\\n-\n  [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\\n-\n  [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\\n\\n###\n  Related Steps \\n\\n- [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\\n-\n  [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\"\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2025-01-14T09:28:50.256167501Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: aa015f68e383dea921957ecb858c8005c1b73e55\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required)\n  workspace_slack_integration_id: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required) if the build failed\n  workspace_slack__integration_id_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (One of webhook URL, API token or workspace integration\n      ID is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: \"Timestamp of the message to be updated.\\n\\nWhen **Message Timestamp**\n      is provided an existing Slack message will be updated, identified by the provided\n      timestamp.  \\nExample: `\\\"1405894322.002768\\\"`.\"\n    summary: Timestamp of the message to be updated.\n    title: Message Timestamp\n  ts: null\n- opts:\n    category: If Build Failed\n    description: \"Timestamp of the message to be updated if the build failed.\\n\\nWhen\n      **Message Timestamp if the build failed** is provided an existing Slack message\n      will be updated, identified by the provided timestamp.  \\nExample: `\\\"1405894322.002768\\\"`.\"\n    summary: Timestamp of the message to be updated if the build failed.\n    title: Message Timestamp if the build failed\n  ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer if the build failed\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- footer_icon_on_error: https://github.com/bitrise-io.png?size=16\n  opts:\n    category: If Build Failed\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text if the build failed\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Pipeline|${BITRISEIO_PIPELINE_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Pipeline Build|${BITRISEIO_PIPELINE_BUILD_URL}\n    View Workflow Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones when sending the slack message.\n    is_dont_change_value: true\n    summary: It uses the build state as if the Pipeline Build had finished with the\n      previous stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones.\n    is_dont_change_value: true\n    summary: It sets the build state as if the Build had finished already\n    title: Build Status\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/4.2.2/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |2-\n\n  Send a [Slack](https://slack.com/) message to a Slack user, a group, or a channel. Create and customize the messages however you see fit. Among other things, you can:\n\n  - Set a different text for failed and successful builds.\n  - Add an icon and/or emojis to your messages.\n  - Set the bot user's name for the messages.\n  - Linkify channel names and usernames.\n  - Add and customize attachments.\n\n  ### Configuring the Step\n\n  To use this Step, you need either a configured [Slack Integration in your workspace](https://devcenter.bitrise.io/en/workspaces/workspace-slack-integration.html), an incoming Slack webhook or a Slack bot user with an API token. For the former see your Workspace settings, for the latter two, you can set them up in Slack:\n\n  - [Incoming webhooks](https://api.slack.com/incoming-webhooks).\n  - [Bot user with an API token](https://api.slack.com/bot-users).\n\n  Once you're ready with those, come back to Bitrise and configure the Step itself:\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either your Slack webhook URL or your Slack API token.\n  1. Add the Secret to either the **Slack Webhook URL** or the **Slack API token** input.\n  1. Toggle the **Run if previous Step failed** option on - you should see a white checkmark on green background next to it. This allows Slack messages to be sent for failed builds, too.\n  1. In the **Target Slack channel, group or username**, set where the Slack message should be sent.\n  1. Customize your messages as you'd like. For the details, see the respective inputs.\n\n  In case of the Slack Integration usecase you can copy the ID in your Workspace settings, on the Integrations page. This ID is not senstive, you can use it as a step input as-is, or put it into a regular environment variable.\n\n  Note that this step always sends a message (either to `channel` or `channel_on_error`). If your use case is to send a message only on success or on failure, then you can [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\n\n  ### Troubleshooting\n\n  If the Step fails, check your Slack settings, the incoming webhook or the API token, and your Slack channel permissions.\n\n  ### Useful links\n\n  - [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\n  - [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\n\n  ### Related Steps\n\n  - [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\n  - [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2025-05-28T14:10:41.056294105Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: 46b180f629fc44a3c0056439dd5f4a2429cb46ce\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required)\n  workspace_slack_integration_id: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required) if the build failed\n  workspace_slack__integration_id_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (One of webhook URL, API token or workspace integration\n      ID is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: |-\n      Timestamp of the message to be updated.\n\n      When **Message Timestamp** is provided an existing Slack message will be updated, identified by the provided timestamp.\n      Example: `\"1405894322.002768\"`.\n    summary: Timestamp of the message to be updated.\n    title: Message Timestamp\n  ts: null\n- opts:\n    category: If Build Failed\n    description: |-\n      Timestamp of the message to be updated if the build failed.\n\n      When **Message Timestamp if the build failed** is provided an existing Slack message will be updated, identified by the provided timestamp.\n      Example: `\"1405894322.002768\"`.\n    summary: Timestamp of the message to be updated if the build failed.\n    title: Message Timestamp if the build failed\n  ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer if the build failed\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- footer_icon_on_error: https://github.com/bitrise-io.png?size=16\n  opts:\n    category: If Build Failed\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text if the build failed\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Pipeline|${BITRISEIO_PIPELINE_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Pipeline Build|${BITRISEIO_PIPELINE_BUILD_URL}\n    View Workflow Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones when sending the slack message.\n    is_dont_change_value: true\n    summary: It uses the build state as if the Pipeline Build had finished with the\n      previous stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones.\n    is_dont_change_value: true\n    summary: It sets the build state as if the Build had finished already\n    title: Build Status\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/4.3.0/step.yml",
    "content": "title: Send a Slack message\nsummary: Send a [Slack](https://slack.com/) message to a channel or group.\ndescription: |-\n  Send a [Slack](https://slack.com/) message to a Slack user, a group, or a channel. Create and customize the messages however you see fit. Among other things, you can:\n\n  - Set a different text for failed and successful builds.\n  - Add an icon and/or emojis to your messages.\n  - Set the bot user's name for the messages.\n  - Linkify channel names and usernames.\n  - Add and customize attachments.\n\n  ### Configuring the Step\n\n  To use this Step, you need either a configured [Slack Integration in your workspace](https://devcenter.bitrise.io/en/workspaces/workspace-slack-integration.html), an incoming Slack webhook or a Slack bot user with an API token. For the former see your Workspace settings, for the latter two, you can set them up in Slack:\n\n  - [Incoming webhooks](https://api.slack.com/incoming-webhooks).\n  - [Bot user with an API token](https://api.slack.com/bot-users).\n\n  Once you're ready with those, come back to Bitrise and configure the Step itself:\n\n  1. Create a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/) for either your Slack webhook URL or your Slack API token.\n  1. Add the Secret to either the **Slack Webhook URL** or the **Slack API token** input.\n  1. Toggle the **Run if previous Step failed** option on - you should see a white checkmark on green background next to it. This allows Slack messages to be sent for failed builds, too.\n  1. In the **Target Slack channel, group or username**, set where the Slack message should be sent.\n  1. Customize your messages as you'd like. For the details, see the respective inputs.\n\n  In case of the Slack Integration usecase you can copy the ID in your Workspace settings, on the Integrations page. This ID is not senstive, you can use it as a step input as-is, or put it into a regular environment variable.\n\n  Note that this step always sends a message (either to `channel` or `channel_on_error`). If your use case is to send a message only on success or on failure, then you can [run the entire step conditionally](https://devcenter.bitrise.io/en/steps-and-workflows/introduction-to-steps/enabling-or-disabling-a-step-conditionally.html).\n\n  ### Troubleshooting\n\n  If the Step fails, check your Slack settings, the incoming webhook or the API token, and your Slack channel permissions.\n\n  ### Useful links\n\n  - [Integrating with Slack](https://devcenter.bitrise.io/builds/configuring-notifications/#integrating-with-slack)\n  - [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments)\n\n  ### Related Steps\n\n  - [Send email with Mailgun](https://www.bitrise.io/integrations/steps/email-with-mailgun)\n  - [Post Jira Comment](https://www.bitrise.io/integrations/steps/post-jira-comment-with-build-details)\nwebsite: https://github.com/bitrise-io/steps-slack-message\nsource_code_url: https://github.com/bitrise-io/steps-slack-message\nsupport_url: https://github.com/bitrise-io/steps-slack-message/issues\npublished_at: 2026-02-24T15:41:51.327660838Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-slack-message.git\n  commit: d63a406dbbcc21ed07b44a007337cb38ef4f6a8c\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/slack/4.3.0/bin/slack-darwin-amd64\n    hash: sha256-6d556398fb8b292b277233f9cafab2e0d6ec384b9dbbf01c991d0dda356f2cc2\n  darwin-arm64:\n    storage_uri: steps/slack/4.3.0/bin/slack-darwin-arm64\n    hash: sha256-1777b2473a4ba02c50d1800f0fffcb8cc1f150bcb54ff5ac4f0f56c426492a6c\n  linux-amd64:\n    storage_uri: steps/slack/4.3.0/bin/slack-linux-amd64\n    hash: sha256-b6bdbe9873da810b3a27d7295b5168a596c260559222989072e701eebde58aaa\n  linux-arm64:\n    storage_uri: steps/slack/4.3.0/bin/slack-linux-arm64\n    hash: sha256-e662f7d8e77e192b907a51f2645aa2e0959156f7e86a2d383230b6ebc136d6ed\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-slack-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- is_debug_mode: \"no\"\n  opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required)\n  webhook_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register an **Incoming WebHook integration** visit: https://api.slack.com/incoming-webhooks\n    is_required: false\n    is_sensitive: true\n    title: Slack Webhook URL (Webhook or API token is required) if the build failed\n  webhook_url_on_error: null\n- opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required)\n  workspace_slack_integration_id: null\n- opts:\n    category: If Build Failed\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n      To register a **Workspace Slack Integration** see the Integration page in your Workspace settings\n    is_required: false\n    is_sensitive: false\n    title: Workspace Slack Integration ID (Integration ID, Webhook or API token is\n      required) if the build failed\n  workspace_slack__integration_id_on_error: null\n- api_token: null\n  opts:\n    description: |\n      **One of workspace\\_integration\\_id, webhook\\_url or api\\_token input is required.**\n\n      To setup a **bot with an API token** visit: https://api.slack.com/bot-users\n    is_required: false\n    is_sensitive: true\n    title: Slack API token (One of webhook URL, API token or workspace integration\n      ID is required)\n- channel: null\n  opts:\n    description: |\n      Can be an encoded ID, or the channel's name.\n       Examples:\n       * channel ID: C024BE91L\n       * channel: #general\n       * username: @username\n    title: Target Slack channel, group or username\n- channel_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      * channel example: #general\n      * username example: @username\n    title: Target Slack channel, group or username if the build failed\n- opts:\n    description: |\n      Text of the message to send.\n      Required unless you wish to send attachments only.\n    title: Text of the message.\n  text: null\n- blocks: null\n  opts:\n    description: |\n      Payload of Block Kit to send. Please check the format guideline [https://api.slack.com/methods/chat.postMessage#arg_blocks](https://api.slack.com/methods/chat.postMessage#arg_blocks)\n    title: Block Kit payload\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text of the message if the build failed\n  text_on_error: null\n- emoji: null\n  opts:\n    description: |\n      Optionally you can specify a Slack emoji as the sender\n      icon. You can use the Ghost icon for example\n      if you specify `:ghost:` here as an input.\n      **If you specify an Icon URL then this Emoji input will be ignored!**\n    title: Emoji to use as the icon for the message\n- emoji_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      **This option will be used if the build failed.** If you\n      leave this option empty then the default one will be used.\n    title: Emoji to use as the icon for the message if the build failed\n- icon_url: https://github.com/bitrise-io.png\n  opts:\n    description: |\n      Optionally, you can specify a custom icon image URL\n      which will be presented as the sender icon.\n      Slack recommends an image a square image,\n      which can't be larger than 128px in either width or height,\n      and it must be smaller than 64K in size.\n      Slack custom emoji guideline: [https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons](https://slack.zendesk.com/hc/en-us/articles/202931348-Using-emoji-and-emoticons)\n      If you specify this input, the **Emoji** input will be ignored!\n    title: Message icon\n- icon_url_on_error: https://github.com/bitrise-io.png\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message icon if the build failed\n- link_names: \"yes\"\n  opts:\n    description: |\n      Linkify names in the message such as `@slackbot` or `#random`\n    title: Linkify channel names and usernames?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- from_username: Bitrise\n  opts:\n    description: |\n      The username of the bot user which will be presented as the sender of the message\n    title: The bot's username for the message\n- from_username_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The bot's username for the message if the build failed\n- opts:\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread).\n    title: Thread Timestamp\n  thread_ts: null\n- opts:\n    category: If Build Failed\n    description: Sends the message as a reply to the message with the given ts if\n      set (in a thread) if the build failed.\n    title: Thread Timestamp if the build failed\n  thread_ts_on_error: null\n- opts:\n    description: |-\n      Timestamp of the message to be updated.\n\n      When **Message Timestamp** is provided an existing Slack message will be updated, identified by the provided timestamp.\n      Example: `\"1405894322.002768\"`.\n    summary: Timestamp of the message to be updated.\n    title: Message Timestamp\n  ts: null\n- opts:\n    category: If Build Failed\n    description: |-\n      Timestamp of the message to be updated if the build failed.\n\n      When **Message Timestamp if the build failed** is provided an existing Slack message will be updated, identified by the provided timestamp.\n      Example: `\"1405894322.002768\"`.\n    summary: Timestamp of the message to be updated if the build failed.\n    title: Message Timestamp if the build failed\n  ts_on_error: null\n- opts:\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast: \"no\"\n- opts:\n    category: If Build Failed\n    description: Used in conjunction with thread_ts and indicates whether reply should\n      be made visible to everyone in the channel or conversation\n    title: Reply Broadcast if the build failed\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reply_broadcast_on_error: \"no\"\n- color: '#3bc3a3'\n  opts:\n    description: |\n      Color is used to color the border along the left side of the attachment.\n      Can either be one of good, warning, danger, or any hex color code (eg. #439FE0).\n      You can find more info about the color and other text formatting\n      in [Slack's documentation](https://api.slack.com/docs/message-attachments).\n    is_required: true\n    title: Message color\n- color_on_error: '#f0741f'\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Message color if the build failed\n- opts:\n    description: An optional text that appears above the attachment block.\n    title: An optional text that appears above the attachment block.\n  pretext: '*Build Succeeded!*'\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: An optional text that appears above the attachment block if the build failed\n  pretext_on_error: '*Build Failed!*'\n- author_name: $GIT_CLONE_COMMIT_AUTHOR_NAME\n  opts:\n    description: A small text used to display the author's name.\n    title: A small text used to display the author's name.\n- opts:\n    description: Title is displayed as larger, bold text near the top of a attachment.\n    title: The title of the attachment\n  title: $GIT_CLONE_COMMIT_MESSAGE_SUBJECT\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: The title of the attachment if the build failed\n  title_on_error: null\n- opts:\n    description: A URL that will hyperlink the title.\n    title: A URL that will hyperlink the title.\n  title_link: null\n- message: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    description: |\n      Text is the main text of the attachment, and can contain standard message markup.\n      The content will automatically collapse if it contains 700+ characters or 5+ linebreaks,\n      and will display a \"Show more...\" link to expand the content.\n    title: Text is the main text of the attachment\n- message_on_error: $GIT_CLONE_COMMIT_MESSAGE_BODY\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Text is the main text of the attachment if the build failed\n- image_url: null\n  opts:\n    description: |\n      A URL to an image file that will be displayed inside the attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      Large images will be resized to a maximum width of 400px or a maximum height of 500px.\n    title: A URL to an image file that will be displayed inside the attachment\n- image_url_on_error: null\n  opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Image URL if build failed\n- opts:\n    description: |\n      A URL to an image file that will be displayed as a thumbnail on the right side of a attachment.\n\n      Supported formats: GIF, JPEG, PNG, and BMP.\n      The thumbnail's longest dimension will be scaled down to 75px.\n    title: A URL to an image file that will be displayed as a thumbnail\n  thumb_url: null\n- opts:\n    category: If Build Failed\n    description: |\n      This option will be used if the build failed. If you\n      leave this option empty then the default one will be used.\n    title: Thumbnail if the build failed\n  thumb_url_on_error: null\n- footer: Bitrise\n  opts:\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer\n- footer_on_error: Bitrise\n  opts:\n    category: If Build Failed\n    description: |\n      The footer adds some brief text to help contextualize and identify an attachment.\n\n      Limited to 300 characters.\n    title: Footer adds some brief text as footer if the build failed\n- footer_icon: https://github.com/bitrise-io.png?size=16\n  opts:\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text\n- footer_icon_on_error: https://github.com/bitrise-io.png?size=16\n  opts:\n    category: If Build Failed\n    description: |\n      Renders a small icon beside the footer text\n      It will be scaled down to 16px by 16px.\n    title: Renders a small icon beside the footer text if the build failed\n- opts:\n    description: Show the current time as part of the attachment's footer?\n    title: Show the current time as part of the attachment's footer?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  timestamp: \"yes\"\n- fields: |\n    App|${BITRISE_APP_TITLE}\n    Branch|${BITRISE_GIT_BRANCH}\n    Pipeline|${BITRISEIO_PIPELINE_TITLE}\n    Workflow|${BITRISE_TRIGGERED_WORKFLOW_ID}\n  opts:\n    description: |\n      Fields separated by newlines and each field contains a `title` and a `value`.\n      The `title` and the `value` fields are separated by a pipe `|` character.\n\n      The *title* shown as a bold heading above the `value` text.\n      The *value* is the text value of the field.\n\n      Supports multiline text with escaped newlines. Example: `Release notes| - Line1 \\n -Line2`.\n\n      Empty lines and lines without a separator are omitted.\n    title: A list of fields to be displayed in a table inside the attachment\n- buttons: |\n    View App|${BITRISE_APP_URL}\n    View Pipeline Build|${BITRISEIO_PIPELINE_BUILD_URL}\n    View Workflow Build|${BITRISE_BUILD_URL}\n    Install Page|${BITRISE_PUBLIC_INSTALL_PAGE_URL}\n  opts:\n    description: |\n      Buttons separated by newlines and each field contains a `text` and a `url`.\n      The `text` and the `url` fields are separated by a pipe `|` character.\n      Empty lines and lines without a separator are omitted.\n\n      The *text* is the label for the button.\n      The *url* is the fully qualified http or https url to deliver users to.\n      An attachment may contain 1 to 5 buttons.\n    title: A list of buttons attached to the message as link buttons\n- opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones when sending the slack message.\n    is_dont_change_value: true\n    summary: It uses the build state as if the Pipeline Build had finished with the\n      previous stage (if applicable)\n    title: Pipeline Build Status\n  pipeline_build_status: $BITRISEIO_PIPELINE_BUILD_STATUS\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    description: |\n      This status will be used to help choosing between _on_error inputs and normal ones.\n    is_dont_change_value: true\n    summary: It sets the build state as if the Build had finished already\n    title: Build Status\n- opts:\n    description: Will export the created thread's timestamp to the environment with\n      the supplied name (if not already in thread)\n    is_required: false\n    is_sensitive: false\n    title: The newly created thread timestamp environment variable name\n  output_thread_ts: null\n"
  },
  {
    "path": "steps/slack/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/smart-qa/0.0.1/step.yml",
    "content": "title: SmartQA\nsummary: |\n  SmartQA E2E test step.\ndescription: |\n  Deploy build to SmartQA. (https://smart-qa.io)\nwebsite: https://github.com/Levetty/bitrise-step-smartqa\nsource_code_url: https://github.com/Levetty/bitrise-step-smartqa\nsupport_url: https://github.com/Levetty/bitrise-step-smartqa/issues\npublished_at: 2021-03-21T20:33:43.550291+09:00\nsource:\n  git: https://github.com/Levetty/bitrise-step-smartqa.git\n  commit: 5ac7d12e24f37c0578b142918392c8fab672326c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/Levetty/bitrise-step-smartqa\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Path to your .app file.\n    is_expand: true\n    is_required: true\n    summary: Your application build path.\n    title: Build Path\n- api_key: null\n  opts:\n    description: |\n      Access token to access SmartQA API.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API Key.\n    title: API KEY\n"
  },
  {
    "path": "steps/smart-qa/0.0.2/step.yml",
    "content": "title: SmartQA\nsummary: |\n  SmartQA E2E test step.\ndescription: |\n  Deploy build to SmartQA. (https://smart-qa.io)\nwebsite: https://github.com/Levetty/bitrise-step-smartqa\nsource_code_url: https://github.com/Levetty/bitrise-step-smartqa\nsupport_url: https://github.com/Levetty/bitrise-step-smartqa/issues\npublished_at: 2021-05-31T14:33:41.32784+09:00\nsource:\n  git: https://github.com/Levetty/bitrise-step-smartqa.git\n  commit: 8696f17256863d09120dcf63c697348870b4a645\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/Levetty/bitrise-step-smartqa\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: $BITRISE_APP_DIR_PATH\n  opts:\n    description: |\n      Path to your .app directory.\n    is_expand: true\n    is_required: true\n    summary: Your application build path.\n    title: Build Path\n- api_key: null\n  opts:\n    description: |\n      Access token to access SmartQA API.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your API Key.\n    title: API KEY\n"
  },
  {
    "path": "steps/smart-qa/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/sms-text-message/2.0.0/step.yml",
    "content": "title: Twilio SMS Text Message Sender\nsummary: |-\n  You can stay up-to-date about the status of your builds even if you don't\n  have an internet connection all day. Send an SMS to your phone and you can\n  keep an eye on the status of your builds even with a good old Nokia 3310.\ndescription: |-\n  SMS Text Message Sender using [https://www.twilio.com/](https://www.twilio.com/)\n\n  To use their service you have to register first.\n  It is possible to register a trial account for free.\n\n  **Important!**\n\n  [Info about recipient charging](https://www.twilio.com/help/faq/sms/when-i-send-an-sms-message-through-twilio-does-the-recipient-of-my-sms-message-get-charged)\nwebsite: https://github.com/bitrise-io/steps-sms-text-message\nsource_code_url: https://github.com/bitrise-io/steps-sms-text-message\nsupport_url: https://github.com/bitrise-io/steps-sms-text-message/issues\npublished_at: 2015-09-08T21:16:16.284838376+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-sms-text-message.git\n  commit: ad56aeb56afb269fa1151504ebbafc1d3d0c181b\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- account_sid: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Twilio Account SID\n- auth_token: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Twilio account authentication token\n- from_number: \"\"\n  opts:\n    description: |-\n      Your Twilio sender number,\n      in E.164 format [http://en.wikipedia.org/wiki/E.164](http://en.wikipedia.org/wiki/E.164)\n      (i.e. without hyphens)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Twilio SMS From number\n- opts:\n    description: |\n      Receiver's phone number,\n      in E.164 format [http://en.wikipedia.org/wiki/E.164](http://en.wikipedia.org/wiki/E.164)\n      (i.e. without hyphens)\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: Send SMS To number (only one allowed)\n  to_number: \"\"\n- message: \"\"\n  opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: SMS message\n- opts:\n    description: \"\"\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: SMS media\n  sms_media: \"\"\n"
  },
  {
    "path": "steps/sms-text-message/2.0.1/step.yml",
    "content": "title: Twilio SMS Text Message Sender\nsummary: |-\n  You can stay up-to-date about the status of your builds even if you don't\n  have an internet connection all day. Send an SMS to your phone and you can\n  keep an eye on the status of your builds even with a good old Nokia 3310.\ndescription: |-\n  SMS Text Message Sender using [https://www.twilio.com/](https://www.twilio.com/)\n\n  To use their service you have to register first.\n  It is possible to register a trial account for free.\n\n  **Important!**\n\n  [Info about recipient charging](https://www.twilio.com/help/faq/sms/when-i-send-an-sms-message-through-twilio-does-the-recipient-of-my-sms-message-get-charged)\nwebsite: https://github.com/bitrise-io/steps-sms-text-message\nsource_code_url: https://github.com/bitrise-io/steps-sms-text-message\nsupport_url: https://github.com/bitrise-io/steps-sms-text-message/issues\npublished_at: 2018-08-31T08:51:32.638334562Z\nsource:\n  git: https://github.com/bitrise-io/steps-sms-text-message.git\n  commit: 00b53c9c076826cb0e57379084beac839b9b43ba\nhost_os_tags:\n- osx-10.9\n- osx-10.10\ntype_tags:\n- notification\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- account_sid: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Twilio Account SID\n- auth_token: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Twilio account authentication token\n- from_number: \"\"\n  opts:\n    description: |-\n      Your Twilio sender number,\n      in E.164 format [http://en.wikipedia.org/wiki/E.164](http://en.wikipedia.org/wiki/E.164)\n      (i.e. without hyphens)\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Twilio SMS From number\n- opts:\n    description: |\n      Receiver's phone number,\n      in E.164 format [http://en.wikipedia.org/wiki/E.164](http://en.wikipedia.org/wiki/E.164)\n      (i.e. without hyphens)\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: Send SMS To number (only one allowed)\n  to_number: \"\"\n- message: \"\"\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: SMS message\n- opts:\n    description: \"\"\n    is_expand: true\n    summary: \"\"\n    title: SMS media\n  sms_media: \"\"\n"
  },
  {
    "path": "steps/sms-text-message/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/snyk/0.1.0/step.yml",
    "content": "title: Test with Snyk\nsummary: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows\ndescription: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows.\n  By utilizing this step, you will be able to test your project dependencies for vulnerabilities during builds and use Snyk to monitor your projects\n  for new vulnerabilities.\n  This step uses Snyk as an external service and requires your authentication token.\nwebsite: https://github.com/pilvikala/bitrise-step-snyk\nsource_code_url: https://github.com/pilvikala/bitrise-step-snyk\nsupport_url: https://github.com/pilvikala/bitrise-step-snyk/issues\npublished_at: 2022-08-21T10:28:02.500264652+03:00\nsource:\n  git: https://github.com/pilvikala/bitrise-step-snyk.git\n  commit: 288a3ed705c9fbbc23ff5fc1fd8666c13d768533\nproject_type_tags:\n- android\n- ios\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- auth_token: $SNYK_AUTH_TOKEN\n  opts:\n    description: |\n      Your Snyk authentication token (see https://app.snyk.io/account).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Snyk Authentication Token\n    title: Auth Token\n- command: test\n  opts:\n    description: |\n      This is the CLI command to run with Snyk.\n\n      Default value: `test`\n    is_required: false\n    summary: Snyk CLI command to run\n    title: Command\n- opts:\n    description: |\n      Only report vulnerabilities of the provided level or higher (low/medium/high/critical).\n\n      Default is low.\n    summary: Only report vulnerabilities of the provided level or higher.\n    title: Severity threshold\n    value_options:\n    - low\n    - medium\n    - high\n    - critical\n  severity_threshold: low\n- fail_on_issues: \"yes\"\n  opts:\n    description: |\n      Specifies whether to fail the build or not based on the results found by Snyk.\n\n      Snyk by default returns an error code from the test command. This may break your Bitrise workflow. By specifying `no`, the build can continue even if vulnerabilities are found.\n    summary: Specifies whether to fail the build or not based on the results found\n      by Snyk.\n    title: Fail on issues\n    value_options:\n    - \"yes\"\n    - \"no\"\n- monitor: \"no\"\n  opts:\n    description: |\n      If enabled, imports the snapshot of dependencies to Snyk for continuous monitoring after a successful test.\n\n      Set this value to `yes` to import the snapshot of dependencies to Snyk after a successful test. Snyk will then start monitoring the dependencies for new vulnerabilities and alert when a new vulnerability is discovered.\n    summary: If enabled, imports the snapshot of dependencies to Snyk for continuous\n      monitoring after a successful test.\n    title: Monitor (import to Snyk)\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    summary: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    title: Target file\n  target_file: null\n- opts:\n    description: |\n      Name of the Snyk organisation name, under which this project should be tested and monitored.\n\n      If omitted the default organization will be used.\n    summary: Name of the Snyk organisation name, under which this project should be\n      tested and monitored.\n    title: Organization\n  organization: null\n- additional_arguments: null\n  opts:\n    description: Refer to the Snyk CLI help page for information on additional arguments.\n    summary: Refer to the Snyk CLI help page for information on additional arguments.\n    title: Additional arguments\n"
  },
  {
    "path": "steps/snyk/1.0.0/step.yml",
    "content": "title: Test with Snyk\nsummary: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows\ndescription: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows.\n  By utilizing this step, you will be able to test your project dependencies for vulnerabilities during builds and use Snyk to monitor your projects\n  for new vulnerabilities.\n  This step uses Snyk as an external service and requires your authentication token.\nwebsite: https://github.com/pilvikala/bitrise-step-snyk\nsource_code_url: https://github.com/pilvikala/bitrise-step-snyk\nsupport_url: https://github.com/pilvikala/bitrise-step-snyk/issues\npublished_at: 2022-09-09T09:33:51.404198+03:00\nsource:\n  git: https://github.com/pilvikala/bitrise-step-snyk.git\n  commit: 9149d400e67361eda0ab8e8ba086b29feabd30fe\nproject_type_tags:\n- android\n- ios\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- auth_token: $SNYK_AUTH_TOKEN\n  opts:\n    description: |\n      Your Snyk authentication token (see https://app.snyk.io/account).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Snyk Authentication Token\n    title: Auth Token\n- command: test\n  opts:\n    description: |\n      This is the CLI command to run with Snyk.\n\n      Default value: `test`\n    is_required: false\n    summary: Snyk CLI command to run\n    title: Command\n- opts:\n    description: |\n      Only report vulnerabilities of the provided level or higher (low/medium/high/critical).\n\n      Default is low.\n    summary: Only report vulnerabilities of the provided level or higher.\n    title: Severity threshold\n    value_options:\n    - low\n    - medium\n    - high\n    - critical\n  severity_threshold: low\n- fail_on_issues: \"yes\"\n  opts:\n    description: |\n      Specifies whether to fail the build or not based on the results found by Snyk.\n\n      Snyk by default returns an error code from the test command. This may break your Bitrise workflow. By specifying `no`, the build can continue even if vulnerabilities are found.\n    summary: Specifies whether to fail the build or not based on the results found\n      by Snyk.\n    title: Fail on issues\n    value_options:\n    - \"yes\"\n    - \"no\"\n- create_report: \"no\"\n  opts:\n    description: |\n      Specifies whether to create an HTML report.\n\n      If set to `yes`, an HTML report will be created and available as a build artifact\n    summary: Specifies whether to create an HTML report\n    title: Create HTML Report\n    value_options:\n    - \"yes\"\n    - \"no\"\n- monitor: \"no\"\n  opts:\n    description: |\n      If enabled, imports the snapshot of dependencies to Snyk for continuous monitoring after a successful test.\n\n      Set this value to `yes` to import the snapshot of dependencies to Snyk after a successful test. Snyk will then start monitoring the dependencies for new vulnerabilities and alert when a new vulnerability is discovered.\n    summary: If enabled, imports the snapshot of dependencies to Snyk for continuous\n      monitoring after a successful test.\n    title: Monitor (import to Snyk)\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    summary: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    title: Target file\n  target_file: null\n- opts:\n    description: |\n      Name of the Snyk organisation name, under which this project should be tested and monitored.\n\n      If omitted the default organization will be used.\n    summary: Name of the Snyk organisation name, under which this project should be\n      tested and monitored.\n    title: Organization\n  organization: null\n- additional_arguments: null\n  opts:\n    description: Refer to the Snyk CLI help page for information on additional arguments.\n    summary: Refer to the Snyk CLI help page for information on additional arguments.\n    title: Additional arguments\n"
  },
  {
    "path": "steps/snyk/1.0.1/step.yml",
    "content": "title: Test with Snyk\nsummary: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows\ndescription: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows.\n  By utilizing this step, you will be able to test your project dependencies for vulnerabilities during builds and use Snyk to monitor your projects\n  for new vulnerabilities.\n  This step uses Snyk as an external service and requires your authentication token.\nwebsite: https://github.com/pilvikala/bitrise-step-snyk\nsource_code_url: https://github.com/pilvikala/bitrise-step-snyk\nsupport_url: https://github.com/pilvikala/bitrise-step-snyk/issues\npublished_at: 2023-02-24T11:49:50.783223+02:00\nsource:\n  git: https://github.com/pilvikala/bitrise-step-snyk.git\n  commit: 14729197de3ec3521173e920e0a5ff7a6774990f\nproject_type_tags:\n- android\n- ios\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- auth_token: $SNYK_AUTH_TOKEN\n  opts:\n    description: |\n      Your Snyk authentication token (see https://app.snyk.io/account).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Snyk Authentication Token\n    title: Auth Token\n- command: test\n  opts:\n    description: |\n      This is the CLI command to run with Snyk.\n\n      Default value: `test`\n    is_required: false\n    summary: Snyk CLI command to run\n    title: Command\n- opts:\n    description: |\n      Only report vulnerabilities of the provided level or higher (low/medium/high/critical).\n\n      Default is low.\n    summary: Only report vulnerabilities of the provided level or higher.\n    title: Severity threshold\n    value_options:\n    - low\n    - medium\n    - high\n    - critical\n  severity_threshold: low\n- fail_on_issues: \"yes\"\n  opts:\n    description: |\n      Specifies whether to fail the build or not based on the results found by Snyk.\n\n      Snyk by default returns an error code from the test command. This may break your Bitrise workflow. By specifying `no`, the build can continue even if vulnerabilities are found.\n    summary: Specifies whether to fail the build or not based on the results found\n      by Snyk.\n    title: Fail on issues\n    value_options:\n    - \"yes\"\n    - \"no\"\n- create_report: \"no\"\n  opts:\n    description: |\n      Specifies whether to create an HTML report.\n\n      If set to `yes`, an HTML report will be created and available as a build artifact\n    summary: Specifies whether to create an HTML report\n    title: Create HTML Report\n    value_options:\n    - \"yes\"\n    - \"no\"\n- monitor: \"no\"\n  opts:\n    description: |\n      If enabled, imports the snapshot of dependencies to Snyk for continuous monitoring after a successful test.\n\n      Set this value to `yes` to import the snapshot of dependencies to Snyk after a successful test. Snyk will then start monitoring the dependencies for new vulnerabilities and alert when a new vulnerability is discovered.\n    summary: If enabled, imports the snapshot of dependencies to Snyk for continuous\n      monitoring after a successful test.\n    title: Monitor (import to Snyk)\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    summary: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    title: Target file\n  target_file: null\n- opts:\n    description: |\n      Name of the Snyk organisation name, under which this project should be tested and monitored.\n\n      If omitted the default organization will be used.\n    summary: Name of the Snyk organisation name, under which this project should be\n      tested and monitored.\n    title: Organization\n  organization: null\n- additional_arguments: null\n  opts:\n    description: Refer to the Snyk CLI help page for information on additional arguments.\n    summary: Refer to the Snyk CLI help page for information on additional arguments.\n    title: Additional arguments\n"
  },
  {
    "path": "steps/snyk/1.0.2/step.yml",
    "content": "title: Test with Snyk\nsummary: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows\ndescription: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows.\n  By utilizing this step, you will be able to test your project dependencies for vulnerabilities during builds and use Snyk to monitor your projects\n  for new vulnerabilities.\n  This step uses Snyk as an external service and requires your authentication token.\nwebsite: https://github.com/pilvikala/bitrise-step-snyk\nsource_code_url: https://github.com/pilvikala/bitrise-step-snyk\nsupport_url: https://github.com/pilvikala/bitrise-step-snyk/issues\npublished_at: 2023-03-16T10:27:40.208568+02:00\nsource:\n  git: https://github.com/pilvikala/bitrise-step-snyk.git\n  commit: 2f2b4b9bc4b5decc638409568d8cbf171cc9bf18\nproject_type_tags:\n- android\n- ios\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- auth_token: $SNYK_AUTH_TOKEN\n  opts:\n    description: |\n      Your Snyk authentication token (see https://app.snyk.io/account).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Snyk Authentication Token\n    title: Auth Token\n- command: test\n  opts:\n    description: |\n      This is the CLI command to run with Snyk.\n\n      Default value: `test`\n    is_required: false\n    summary: Snyk CLI command to run\n    title: Command\n- opts:\n    description: |\n      Only report vulnerabilities of the provided level or higher (low/medium/high/critical).\n\n      Default is low.\n    summary: Only report vulnerabilities of the provided level or higher.\n    title: Severity threshold\n    value_options:\n    - low\n    - medium\n    - high\n    - critical\n  severity_threshold: low\n- fail_on_issues: \"yes\"\n  opts:\n    description: |\n      Specifies whether to fail the build or not based on the results found by Snyk.\n\n      Snyk by default returns an error code from the test command. This may break your Bitrise workflow. By specifying `no`, the build can continue even if vulnerabilities are found.\n    summary: Specifies whether to fail the build or not based on the results found\n      by Snyk.\n    title: Fail on issues\n    value_options:\n    - \"yes\"\n    - \"no\"\n- create_report: \"no\"\n  opts:\n    description: |\n      Specifies whether to create an HTML report.\n\n      If set to `yes`, an HTML report will be created and available as a build artifact\n    summary: Specifies whether to create an HTML report\n    title: Create HTML Report\n    value_options:\n    - \"yes\"\n    - \"no\"\n- monitor: \"no\"\n  opts:\n    description: |\n      If enabled, imports the snapshot of dependencies to Snyk for continuous monitoring after a successful test.\n\n      Set this value to `yes` to import the snapshot of dependencies to Snyk after a successful test. Snyk will then start monitoring the dependencies for new vulnerabilities and alert when a new vulnerability is discovered.\n    summary: If enabled, imports the snapshot of dependencies to Snyk for continuous\n      monitoring after a successful test.\n    title: Monitor (import to Snyk)\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    summary: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    title: Target file\n  target_file: null\n- opts:\n    description: |\n      Name of the Snyk organisation name, under which this project should be tested and monitored.\n\n      If omitted the default organization will be used.\n    summary: Name of the Snyk organisation name, under which this project should be\n      tested and monitored.\n    title: Organization\n  organization: null\n- additional_arguments: null\n  opts:\n    description: Refer to the Snyk CLI help page for information on additional arguments.\n    summary: Refer to the Snyk CLI help page for information on additional arguments.\n    title: Additional arguments\n"
  },
  {
    "path": "steps/snyk/1.0.3/step.yml",
    "content": "title: Test with Snyk\nsummary: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows\ndescription: |\n  Bitrise Snyk Step incorporates Snyk into your Bitrise workflows.\n  By utilizing this step, you will be able to test your project dependencies for vulnerabilities during builds and use Snyk to monitor your projects\n  for new vulnerabilities.\n  This step uses Snyk as an external service and requires your authentication token.\nwebsite: https://github.com/pilvikala/bitrise-step-snyk\nsource_code_url: https://github.com/pilvikala/bitrise-step-snyk\nsupport_url: https://github.com/pilvikala/bitrise-step-snyk/issues\npublished_at: 2023-04-13T08:28:04.786317+03:00\nsource:\n  git: https://github.com/pilvikala/bitrise-step-snyk.git\n  commit: ff48d92f158fdd14266231f6071d128dcad6c588\nproject_type_tags:\n- android\n- ios\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ninputs:\n- auth_token: $SNYK_AUTH_TOKEN\n  opts:\n    description: |\n      Your Snyk authentication token (see https://app.snyk.io/account).\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Snyk Authentication Token\n    title: Auth Token\n- command: test\n  opts:\n    description: |\n      This is the CLI command to run with Snyk.\n\n      Default value: `test`\n    is_required: false\n    summary: Snyk CLI command to run\n    title: Command\n- opts:\n    description: |\n      Only report vulnerabilities of the provided level or higher (low/medium/high/critical).\n\n      Default is low.\n    summary: Only report vulnerabilities of the provided level or higher.\n    title: Severity threshold\n    value_options:\n    - low\n    - medium\n    - high\n    - critical\n  severity_threshold: low\n- fail_on_issues: \"yes\"\n  opts:\n    description: |\n      Specifies whether to fail the build or not based on the results found by Snyk.\n\n      Snyk by default returns an error code from the test command. This may break your Bitrise workflow. By specifying `no`, the build can continue even if vulnerabilities are found.\n    summary: Specifies whether to fail the build or not based on the results found\n      by Snyk.\n    title: Fail on issues\n    value_options:\n    - \"yes\"\n    - \"no\"\n- create_report: \"no\"\n  opts:\n    description: |\n      Specifies whether to create an HTML report.\n\n      If set to `yes`, an HTML report will be created and available as a build artifact\n    summary: Specifies whether to create an HTML report\n    title: Create HTML Report\n    value_options:\n    - \"yes\"\n    - \"no\"\n- monitor: \"no\"\n  opts:\n    description: |\n      If enabled, imports the snapshot of dependencies to Snyk for continuous monitoring after a successful test.\n\n      Set this value to `yes` to import the snapshot of dependencies to Snyk after a successful test. Snyk will then start monitoring the dependencies for new vulnerabilities and alert when a new vulnerability is discovered.\n    summary: If enabled, imports the snapshot of dependencies to Snyk for continuous\n      monitoring after a successful test.\n    title: Monitor (import to Snyk)\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    summary: The path to the manifest file to be used by Snyk. Should be provided\n      if non-standard.\n    title: Target file\n  target_file: null\n- opts:\n    description: |\n      Name of the Snyk organisation name, under which this project should be tested and monitored.\n\n      If omitted the default organization will be used.\n    summary: Name of the Snyk organisation name, under which this project should be\n      tested and monitored.\n    title: Organization\n  organization: null\n- additional_arguments: null\n  opts:\n    description: Refer to the Snyk CLI help page for information on additional arguments.\n    summary: Refer to the Snyk CLI help page for information on additional arguments.\n    title: Additional arguments\n"
  },
  {
    "path": "steps/snyk/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/sofy-upload/0.0.3/step.yml",
    "content": "title: Sofy upload\nsummary: |\n  Uploads your build to Sofy.\ndescription: |\n  Uploads your build to Sofy.\n  You are required to provide the Build Path and Subscription key.\nwebsite: https://github.com/SOFYAIOFFICIAL/bitrise-step-sofy-upload\nsource_code_url: https://github.com/SOFYAIOFFICIAL/bitrise-step-sofy-upload\nsupport_url: https://github.com/SOFYAIOFFICIAL/bitrise-step-sofy-upload/issues\npublished_at: 2021-07-17T16:55:22.933276+05:00\nsource:\n  git: https://github.com/SOFYAIOFFICIAL/bitrise-step-sofy-upload.git\n  commit: 3115e6860ec6d09d1d3826f6ce4f428009f1fe8f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n      - The Xcode build for simulator Step generates a .app file at `$BITRISE_APP_DIR_PATH`\n      - The Xcode Archive & Export for iOS Step generates a ipa file at `$BITRISE_IPA_PATH`\n      - The Android Build Step generates apk file at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build Path\n- opts:\n    description: |\n      Find your subscription key by logging into Sofy, going to Account Settings --> API Key section.\n    is_required: true\n    is_sensitive: true\n    title: Subscription Key\n  subscription_key: null\n"
  },
  {
    "path": "steps/sofy-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/sofy-upload-bitrise-step/0.0.2/step.yml",
    "content": "title: Sofy app upload\nsummary: |\n  Uploads your build to Sofy.\ndescription: |\n  Uploads your build to Sofy.\n  You are required to provide the Build Path and Subscription key.\nwebsite: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step\nsource_code_url: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step\nsupport_url: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step/issues\npublished_at: 2023-11-10T14:52:20.601767+05:00\nsource:\n  git: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step.git\n  commit: bd2ecbad78b33a9ed668ec10e39dab3a183d4396\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.ipa`, or `.apk` path.\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n      - The Xcode Archive & Export for iOS Step generates a ipa file at `$BITRISE_IPA_PATH`\n      - The Android Build Step generates apk file at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.ipa`, or `.apk` path.\n    title: Build Path\n- opts:\n    description: |\n      Find your subscription key by logging into Sofy, going to Account Settings --> API Key section.\n    is_required: true\n    is_sensitive: true\n    title: Subscription Key\n  subscription_key: null\n- application_guid: null\n  opts:\n    description: |\n      Unique identifier for the application (Optional).\n    is_required: false\n    title: Application Guid\n- certificate_name: null\n  opts:\n    description: |\n      Your Application certificate name (optional)\n    is_required: false\n    title: Certificate Name\n"
  },
  {
    "path": "steps/sofy-upload-bitrise-step/0.0.4/step.yml",
    "content": "title: Sofy-app-upload-bitrise-step\nsummary: |\n  Uploads your build to Sofy.\ndescription: |\n  Uploads your build to Sofy.\n  You are required to provide the Build Path and Subscription key.\nwebsite: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step\nsource_code_url: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step\nsupport_url: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step/issues\npublished_at: 2023-11-29T23:39:51.28768+05:00\nsource:\n  git: https://github.com/SOFYDEVELOPER/sofy-app-upload-bitrise-step.git\n  commit: 70f9eaacff60c48920336740052ae89b2bad8f56\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.ipa`, or `.apk` path.\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n      - The Xcode Archive & Export for iOS Step generates a ipa file at `$BITRISE_IPA_PATH`\n      - The Android Build Step generates apk file at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.ipa`, or `.apk` path.\n    title: Build Path\n- opts:\n    description: |\n      Find your subscription key by logging into Sofy, going to Account Settings --> API Key section.\n    is_required: true\n    is_sensitive: true\n    title: Subscription Key\n  subscription_key: null\n- application_guid: null\n  opts:\n    description: |\n      Unique identifier for the application (Optional).\n    is_required: false\n    title: Application Guid\n- certificate_name: null\n  opts:\n    description: |\n      Your Application certificate name (optional)\n    is_required: false\n    title: Certificate Name\n"
  },
  {
    "path": "steps/sofy-upload-bitrise-step/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/sonarqube-msbuild-scanner/1.0.0/step.yml",
    "content": "title: SonarQube MSBuild Scanner\nsummary: |\n  Step for running SonarQube MSBuild Scanner CLI.\ndescription: |\n  Step for running SonarQube MSBuild Scanner CLI.\nwebsite: https://github.com/tbrushwyler/bitrise-step-sonarqube-msbuild-scanner\nsource_code_url: https://github.com/tbrushwyler/bitrise-step-sonarqube-msbuild-scanner\nsupport_url: https://github.com/tbrushwyler/bitrise-step-sonarqube-msbuild-scanner/issues\npublished_at: 2019-01-18T10:49:37.164573-05:00\nsource:\n  git: https://github.com/tbrushwyler/bitrise-step-sonarqube-msbuild-scanner.git\n  commit: 51530e8d46158bb8f1471ab0b649c7720314f127\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- xamarin\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\n  apt_get:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.5.0.1761\n- opts:\n    description: Specifies the key of the analyzed project in SonarQube.\n    is_required: true\n    title: Key of the analyzed project in SonarQube.\n  sonarqube_project_key: null\n- opts:\n    description: Specifies the name of the analyzed project in SonarQube. Adding this\n      argument will overwrite the project name in SonarQube if it already exists.\n    is_required: false\n    title: Name of the analyzed project in SonarQube.\n  sonarqube_project_name: null\n- opts:\n    description: Specifies the version of your project.\n    is_required: false\n    title: Version of your project in SonarQube.\n  sonarqube_project_version: null\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.analysis.mode=preview\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Scanner parameters for the `begin` step\n  scanner_begin_properties: null\n- opts:\n    description: |-\n      Commands to run between \"begin\" and \"end\" steps.\n      You may want to build your project, execute unit tests, and generate code coverage data.\n\n      Example:\n      ```\n      msbuild $BITRISE_PROJECT_PATH /t:Rebuild\n      ```\n    title: Build commands.\n  scanner_build_commands: null\n- opts:\n    description: |-\n      See [documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+MSBuild)\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.login=TOKEN_HERE\n      sonar.password=PASSWORD_HERE\n      ```\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    title: Scanner parameters for the `end` step\n  scanner_end_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printd to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-msbuild-scanner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/sonarqube-quality-gate/step-info.yml",
    "content": "maintainer: community"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.0/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIt's an error to both have that file and specify properties\n  here at the same time.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2017-04-28T00:42:28.882075063Z\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 7cc72d937e9465a7c62b023228d73925ae896d97\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.0.1.733\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n        sonar.sources=.\n        sonar.login=TOKEN_HERE\n        #environment variables are evaluated\n        sonar.projectKey=$BITRISE_APP_TITLE\n        sonar.host.url=https://sonar.example.test\n        sonar.analysis.mode=preview\n        sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.1/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIt's an error to both have that file and specify properties\n  here at the same time.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2017-06-04T22:32:52.352769673Z\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: cbb441b82f37ee60ca229ecb3d93d22b727d078d\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.0.3.778\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n        sonar.sources=.\n        sonar.login=TOKEN_HERE\n        #environment variables are evaluated\n        sonar.projectKey=$BITRISE_APP_TITLE\n        sonar.host.url=https://sonar.example.test\n        sonar.analysis.mode=preview\n        sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.10/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[Getting\n  Started](https://docs.sonarsource.com/sonarqube/latest/#getting-started).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarsource.com/sonarqube/latest/devops-platform-integration/github-integration/).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarscanner/)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2023-10-17T13:02:19.585423+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 266741a6e7731b8265b52e124197f6833ab76d17\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Scanner CLI version to be used. Step will fail if invalid or non-existent is specified.\n\n      `latest` can be used to use the latest available scanner\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.6.2.2472\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      In addition, debug logging will be enabled for SonarQube (by adding the -X argument).\n\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.11/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[Getting\n  Started](https://docs.sonarsource.com/sonarqube/latest/#getting-started).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarsource.com/sonarqube/latest/devops-platform-integration/github-integration/).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarscanner/)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2025-02-09T23:30:56.843701+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 0962019301febca1f64ca37fa8aa3706b1a40b95\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Scanner CLI version to be used. Step will fail if invalid or non-existent is specified.\n\n      `latest` can be used to use the latest available scanner\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.6.2.2472\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- opts:\n    description: |-\n      See [alternatives to sonar-project.properties](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/scanners/sonarscanner/#sonar-project-properties) documentation\n      before changing this value.\n\n      Specify the path to the project configuration file through the `-Dproject.settings=` argument.\n    is_required: true\n    title: Path of project configuration file\n  project_settings_path: sonar-project.properties\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      In addition, debug logging will be enabled for SonarQube (by adding the -X argument).\n\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.12/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[Getting\n  Started](https://docs.sonarsource.com/sonarqube/latest/#getting-started).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarsource.com/sonarqube/latest/devops-platform-integration/github-integration/).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarscanner/)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2026-05-11T20:10:53.080179+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 89a1028fe641057edd62a7a725aa8e22cefcf3b0\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Scanner CLI version to be used. Step will fail if invalid or non-existent is specified.\n\n      `latest` can be used to use the latest available scanner\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.6.2.2472\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- opts:\n    description: |-\n      See [alternatives to sonar-project.properties](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/scanners/sonarscanner/#sonar-project-properties) documentation\n      before changing this value.\n\n      Specify the path to the project configuration file through the `-Dproject.settings=` argument.\n    is_required: true\n    title: Path of project configuration file\n  project_settings_path: sonar-project.properties\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      In addition, debug logging will be enabled for SonarQube (by adding the -X argument).\n\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.2/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2018-02-10T16:24:49.824003928+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: b006f0c6a9f79b8666e34e327f58b55d282f5f5a\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.0.3.778\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.analysis.mode=preview\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.3/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2018-05-23T20:03:42.537177681+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 746e5a759b0b859cb4ba36aa8b5e4be99fd68044\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.2.0.1227\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.analysis.mode=preview\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.4/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2018-08-21T03:24:40.13518426+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: da2b842998f5b30a3db26d1b9d91b0ad73a9b3e2\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.2.0.1227\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.analysis.mode=preview\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.5/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2018-10-10T13:58:34.436402102+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 7e84de1e2bea96782ad74fb586be5316add20b76\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.2.0.1227\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.analysis.mode=preview\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.6/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2019-04-30T02:30:06.467410913+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 4a10cf1ca326347f50e19f806c8e73f75ad19727\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 3.3.0.1492\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.7/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2020-05-19T13:49:36.479543+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 21124ebffed8689c04b8f9e420fcf01aed278e20\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  apt_get:\n  - name: unzip\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Scanner CLI version to be used. Step will fail if invalid or non-existent\n      is specified.\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.3.0.2102\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      In addition, debug logging will be enabled for SonarQube (by adding the -X argument).\n\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.8/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2021-08-24T11:15:38.246838+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 0de979cd167456c80705cbcbf1f12bd74e53a38a\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Scanner CLI version to be used. Step will fail if invalid or non-existent is specified.\n\n      `latest` can be used to use the latest available scanner\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.6.2.2472\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      In addition, debug logging will be enabled for SonarQube (by adding the -X argument).\n\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/1.0.9/step.yml",
    "content": "title: SonarQube Scanner\nsummary: Runs SonarQube Scanner CLI\ndescription: \"This step provides only a **scanner** (client) which needs SonarQube\n  **server** to work.\\nIf you haven't access to server check out this tutorial: \\n[how\n  to get started in two minutes](https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes).\\nLocal\n  server can be spawned in previous script step. \\nSee [test of this step](https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/blob/master/bitrise.yml)\n  \\nfor sample step implementation.\\n\\nAnalysis result can be saved to file (specified\n  via `sonar.report.export.path` property) or send directly by server e.g.\\nto [GitHub\n  PullRequest comment](https://docs.sonarqube.org/display/PLUG/GitHub+Plugin).\\n\\nScanner\n  properties can be provided via `sonar-project.properties` file in the workspace\n  root directory or typed in input below.\\nSee [SonarQube Scanner documentation](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner)\n  \\nfor more details.\\n\\nIf both file and properties are specified, they will be merged\n  by appending properties to the file.\"\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner/issues\npublished_at: 2021-09-03T01:13:04.073022+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-sonarqube-scanner.git\n  commit: 3fee20be446130d5be114bee8ef0917ba3274053\ntype_tags:\n- utility\ndeps:\n  brew:\n  - name: unzip\n  - name: wget\n  - name: curl\n  apt_get:\n  - name: unzip\n  - name: wget\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |-\n      Scanner CLI version to be used. Step will fail if invalid or non-existent is specified.\n\n      `latest` can be used to use the latest available scanner\n    is_required: true\n    title: Scanner CLI version\n  scanner_version: 4.6.2.2472\n- opts:\n    description: |-\n      See [analysis parameters](https://docs.sonarqube.org/display/SONAR/Analysis+Parameters) documentation\n      for list of possible options.\n\n      Example:\n      ```\n      sonar.sources=.\n      sonar.java.binaries=build/classes/kotlin/main\n      sonar.login=TOKEN_HERE\n      #environment variables are evaluated\n      sonar.projectKey=$BITRISE_APP_TITLE\n      sonar.host.url=https://sonar.example.test\n      sonar.report.export.path=sonar-report.json\n      ```\n    is_expand: true\n    is_required: false\n    title: Scanner parameters in Java properties format\n  scanner_properties: null\n- is_debug: \"false\"\n  opts:\n    description: |-\n      Whether trace of shell commands should be printed to a build log.\n      In addition, debug logging will be enabled for SonarQube (by adding the -X argument).\n\n      Options:\n      * \"true\"\n      * \"false\" (default)\n    is_expand: false\n    title: Print all executed shell commands to a build log?\n    value_options:\n    - \"true\"\n    - \"false\"\n"
  },
  {
    "path": "steps/sonarqube-scanner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/stamp-appicon-with-version-number/1.1.0/step.yml",
    "content": "title: Stamp AppIcon with version number\nsummary: |\n  This script will use ImageMagick to stamp the version number to all icons.\ndescription: |\n  Stamps version \"version(build number)\" to the bottom of the icon.\nwebsite: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\nsource_code_url: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\nsupport_url: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number/issues\npublished_at: 2018-09-13T23:12:56.00796207+03:00\nsource:\n  git: https://github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number.git\n  commit: b5990967adeb4690554aa3436cfc4b5647eadd2e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/ollitapa/bitrise-step-stamp-appicon-with-version-number\ndeps:\n  brew:\n  - name: imagemagick\n  apt_get:\n  - name: imagemagick\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"true\"\ninputs:\n- opts:\n    description: |\n      Relative path to icons for example `Project/General.xcassets/AppIcon.appiconset`\n    is_expand: true\n    is_required: true\n    summary: Relative path to icons\n    title: Path to icons of the project\n    value_options: []\n  stamp_path_to_icons: null\n- opts:\n    description: |\n      Version number or string for example 0.1 or Dev\n    is_expand: true\n    is_required: true\n    summary: Version number or string\n    title: Version number or string\n    value_options: []\n  stamp_version: null\n- opts:\n    description: |\n      Build number to stamp on the icon. Defaults to BITRISE_BUILD_NUMBER\n    is_expand: true\n    is_required: true\n    summary: Build number to stamp on the icon\n    title: Build number to stamp on the icon\n    value_options: []\n  stamp_build_number: $BITRISE_BUILD_NUMBER\n- foreground_color: white\n  opts:\n    description: |\n      Foreground color (text color) of the stamp. Defaults to \"white\"\n    is_expand: true\n    is_required: true\n    summary: Foreground color of the stamp\n    title: Foreground color of the stamp\n    value_options: []\n- background_color: '#0008'\n  opts:\n    description: |\n      Background color of the stamp. Defaults to translucent black\n    is_expand: true\n    is_required: true\n    summary: Background color of the stamp\n    title: Background color of the stamp\n    value_options: []\n"
  },
  {
    "path": "steps/stamp-appicon-with-version-number/step-info.yml",
    "content": "maintainer: community\ndeprecate_notes: This step is a duplicate of \"bitrise-step-stamp-appicon-with-version-number\". Please use that step ID instead.\nremoval_date: 2025-09-31\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.0/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully\ndescription: Start Android emulator and wait till it's booted fully\nwebsite: https://github.com/bitrise-io/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-io/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-io/steps-start-android-emulator/issues\npublished_at: 2015-10-29T17:25:42.008578447Z\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: cd02fa5143cb3fe90f2b91a98d88b30f6c98415a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: false\n    title: Emulator to boot\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.1/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully\ndescription: Start Android emulator and wait till it's booted fully\nwebsite: https://github.com/bitrise-io/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-io/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-io/steps-start-android-emulator/issues\npublished_at: 2015-10-29T19:14:05.497393131Z\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 786eb7074098c0c042cb65439f05bf9e66a9fb82\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: true\n    title: Emulator to boot\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.2/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully\ndescription: Start Android emulator and wait till it's booted fully\nwebsite: https://github.com/bitrise-io/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-io/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-io/steps-start-android-emulator/issues\npublished_at: 2015-12-05T09:38:31.251987686+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: aa07583d65af7c68d6fce309951c126416f21555\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: true\n    title: Emulator to boot\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_expand: true\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.3/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2015-12-17T16:13:57.800712019+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-start-android-emulator.git\n  commit: fdb9e432bb1bfe69c6a584dfce1b4ec52a9fbc2d\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: true\n    title: Emulator to boot\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_expand: true\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.4/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2015-12-18T15:48:17.319765163+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 8b82b3eb202c312c3939a1627c8bddb00b2937d5\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: true\n    title: Emulator to boot\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_expand: true\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.5/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2016-01-27T15:21:14.539726848+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 26372f7d75e3e143a9fa7bedf195c293db9a1d3c\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: true\n    title: Emulator to boot\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_expand: true\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/0.9.7/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2016-02-02T18:01:42.502135352+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: c9c9bc0a85a285800e78e0428d395faca6883ba1\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_required: true\n    title: Emulator to boot\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.0.0/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2016-02-09T15:07:22.840862214+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: bb1e5a1e09a28b17f7d5dc795a2eac4e8281ed56\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: null\n  opts:\n    description: |\n      Emulator to boot\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: 320x480\n    title: Emulator skin\n  skin: null\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.0.1/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2016-02-11T12:45:45.261569509+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 2db42c117cda2336b8df4c285f02ebd79ebccebc\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `320x480`.\n    title: Emulator skin\n  skin: null\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.0.2/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2016-05-09T11:48:05.85743972+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: f8d76369b477e9a7c0bf393aba137360dbc95c91\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- opts:\n    description: |-\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: Additional options for emulator call\n  other_options: \"\"\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.1.0/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2016-08-24T11:57:43.677164381+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: d8cbd0d2d72c972371d9107523673640648333ba\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-audio -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.1.1/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and - optionally - wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2017-02-13T16:21:26.810881735+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 5edf124060b2499dde86b7062acc9b626aedaffd\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-start-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: If this option is false, the step will not wait for the emulator\n      to finish boot\n    is_required: true\n    title: Wait for emulator boot\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_boot: \"true\"\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.2.0/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and - optionally - wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2017-03-22T14:56:25.978098441+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 37c40ad79c5ee8eac92b44ce93df7b96fa9744b2\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-start-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: If this option is false, the step will not wait for the emulator\n      to finish boot\n    is_required: true\n    title: Wait for emulator boot\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_boot: \"true\"\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.2.1/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and - optionally - wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2017-03-29T16:05:05.569825997+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 2d53e954bc7ea1d0fbde9fdda6e64e6a1b301de9\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-start-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: If this option is false, the step will not wait for the emulator\n      to finish boot\n    is_required: true\n    title: Wait for emulator boot\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_boot: \"true\"\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.3.0/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and - optionally - wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2017-05-08T17:29:53.987386472+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 0afd501af36228ca04e2ff9882cc8bb13ce3c740\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-start-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: If this option is false, the step will not wait for the emulator\n      to finish boot\n    is_required: true\n    title: Wait for emulator boot\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_boot: \"true\"\n- boot_timeout: \"1600\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.3.1/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and - optionally - wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2017-05-16T12:27:17.435719403+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: 7cd9fe0ce1e8b0a4446f49234855d7fbf3aadde8\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-start-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: If this option is false, the step will not wait for the emulator\n      to finish boot\n    is_required: true\n    title: Wait for emulator boot\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_boot: \"true\"\n- boot_timeout: \"1600\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/1.3.2/step.yml",
    "content": "title: Start Android emulator\nsummary: Start Android emulator and wait till it's booted fully.\ndescription: Start Android emulator and - optionally - wait till it's booted fully.\nwebsite: https://github.com/bitrise-steplib/steps-start-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-start-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-start-android-emulator/issues\npublished_at: 2017-11-20T08:38:46.023508482+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-start-android-emulator.git\n  commit: a53248552fe6262fee734053640060c57c34a246\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-start-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_name: $BITRISE_EMULATOR_NAME\n  opts:\n    description: |\n      Emulator AVD image name to boot.\n    is_required: true\n    title: Emulator to boot\n- opts:\n    description: |\n      Use this input to specify an emulator skin.\n      Value example: `768x1280`.\n    title: Emulator skin\n  skin: 768x1280\n- emulator_options: -no-boot-anim -no-window\n  opts:\n    description: These flags will be added to the emulator command.\n    title: Specify emulator command's flags\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n- opts:\n    description: If this option is false, the step will not wait for the emulator\n      to finish boot\n    is_required: true\n    title: Wait for emulator boot\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_boot: \"true\"\n- boot_timeout: \"1600\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- opts:\n    description: |-\n      This options is deprecated please use `emulator_options` instead.\n\n      Options added to the end of the emulator call.\n\n      Example:\n      `-dpi-device 165 -no-cache`\n    title: '[Deprecated!] Additional options for emulator call'\n  other_options: \"\"\noutputs:\n- BITRISE_EMULATOR_SERIAL: null\n  opts:\n    description: Booted emulator serial\n    title: Emulator serial\n"
  },
  {
    "path": "steps/start-android-emulator/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, use [AVD Manager](https://github.com/bitrise-steplib/steps-avd-manager) Step instead.\nmaintainer: bitrise\nremoval_date: \"2019-08-25\"\n"
  },
  {
    "path": "steps/steps-app-gallery-reports/0.9.0/step.yml",
    "content": "title: Huawei AppGallery Connect Reports\nsummary: Gets the different Reports from AppGallery Connect for a specific published\n  app.\ndescription: |-\n  Gets the next reports from AppGallery Connect:\n  - Download and Installation Report\n  - In-app Payment Report\n  - Paid Download Report\n  - Installation Failure Data Report\n\n  This step is based on [AppGallery Connect Reports](https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-References/agcapi-appdownloadexport)\nwebsite: https://github.com/ferPrieto/steps-app-gallery-reports\nsource_code_url: https://github.com/ferPrieto/steps-app-gallery-reports\nsupport_url: https://github.com/ferPrieto/steps-app-gallery-reports/issues\npublished_at: 2021-03-06T00:13:45.025487Z\nsource:\n  git: https://github.com/ferPrieto/steps-app-gallery-reports.git\n  commit: 6c74a96cdf30aa2ce82f753ae6f33a702e644916\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- xamarin\n- react-native\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- huawei_app_id: null\n  opts:\n    category: Required Config\n    description: App ID can be found in the `App information` section in App Gallery\n      Connect.\n    is_expand: true\n    is_required: true\n    title: App ID\n- huawei_client_id: null\n  opts:\n    category: Required Config\n    description: Client ID generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    title: Client ID\n- huawei_client_secret: null\n  opts:\n    category: Required Config\n    description: Key Secret generated in `AppGallery Connect -> Users and permissions\n      -> API key -> Connect API -> API client`\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Key\n- download_installation_language: en-US\n  opts:\n    category: Download and Installation\n    description: Query language. The report title is displayed in different languages.\n      Only simplified Chinese (zh-CN), English (en-US), and Russian (ru-RU) are supported.\n    is_expand: true\n    is_required: false\n    title: Language\n- download_installation_start_time: null\n  opts:\n    category: Download and Installation\n    description: Query start time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: Start Time\n- download_installation_end_time: null\n  opts:\n    category: Download and Installation\n    description: Query end time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: End Time\n- download_installation_export_type: CSV\n  opts:\n    category: Download and Installation\n    description: Format of an exported file. The options are as follows CSV, EXCEL.\n    is_expand: true\n    is_required: false\n    title: Export Type\n    value_options:\n    - CSV\n    - EXCEL\n- in_app_payment_language: en-US\n  opts:\n    category: In-App Payment\n    description: Query language. The report title is displayed in different languages.\n      Only simplified Chinese (zh-CN), English (en-US), and Russian (ru-RU) are supported.\n    is_expand: true\n    is_required: false\n    title: Language\n- in_app_payment_start_time: null\n  opts:\n    category: In-App Payment\n    description: Query start time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: Start Time\n- in_app_payment_end_time: null\n  opts:\n    category: In-App Payment\n    description: Query end time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: End Time\n- in_app_payment_export_type: CSV\n  opts:\n    category: In-App Payment\n    description: Format of an exported file. The options are as follows CSV, EXCEL.\n    is_expand: true\n    is_required: false\n    title: Export Type\n    value_options:\n    - CSV\n    - EXCEL\n- in_app_payment_currency: EUR\n  opts:\n    category: In-App Payment\n    description: Currency code. Only CNY, EUR, USD, GBP, and JPY are supported.\n    is_expand: true\n    is_required: false\n    title: Currency\n    value_options:\n    - CNY\n    - EUR\n    - USD\n    - GBP\n    - JPY\n- opts:\n    category: Paid Download\n    description: Domain name related to the region of the app payment.\n    is_expand: true\n    is_required: false\n    title: Domain\n    value_options:\n    - China\n    - Europe\n    - Asia Pacific\n    - Russia\n  paid_download_domain: Europe\n- opts:\n    category: Paid Download\n    description: Query language. The report title is displayed in different languages.\n      Only simplified Chinese (zh-CN), English (en-US), and Russian (ru-RU) are supported.\n    is_expand: true\n    is_required: false\n    title: Language\n  paid_download_language: en-US\n- opts:\n    category: Paid Download\n    description: Query start time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: Start Time\n  paid_download_start_time: null\n- opts:\n    category: Paid Download\n    description: Query end time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: End Time\n  paid_download_end_time: null\n- opts:\n    category: Paid Download\n    description: This parameter is mandatory in Paid Download Reports. Available country\n      IDs https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agcapi-reference-countrycode\n    is_expand: true\n    is_required: false\n    title: Country Id\n  paid_download_country_id: null\n- installation_failure_data_language: en-US\n  opts:\n    category: Installation Failure Data\n    description: Query language. The report title is displayed in different languages.\n      Only simplified Chinese (zh-CN), English (en-US), and Russian (ru-RU) are supported.\n    is_expand: true\n    is_required: false\n    title: Language\n- installation_failure_data_start_time: null\n  opts:\n    category: Installation Failure Data\n    description: Query start time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: Start Time\n- installation_failure_data_end_time: null\n  opts:\n    category: Installation Failure Data\n    description: Query end time in UTC time. The format is YYYYMMDD. The interval\n      between startTime and EndTime cannot exceed 180 days.\n    is_expand: true\n    is_required: false\n    title: End Time\n- opts:\n    category: Debug\n    description: |\n      If debug=yes the step will print debug infos\n    title: Show debug logs?\n    value_options:\n    - \"no\"\n    - \"yes\"\n  show_debug_logs: \"no\"\noutputs:\n- DOWNLOAD_INSTALLATION_REPORT_LINK: null\n  opts:\n    category: Download and Installation\n    is_dont_change_value: false\n    title: Download and Installation Report Link\n- IN_APP_PAYMENT_REPORT_REPORT_LINK: null\n  opts:\n    category: In-App Payment\n    is_dont_change_value: false\n    title: In-App Payment Report Link\n- PAID_DOWNLOAD_REPORT_LINK: null\n  opts:\n    category: Paid Download\n    is_dont_change_value: false\n    title: Paid Download Report Link\n- INSTALLATION_FAILURE_DATA_REPORT_LINK: null\n  opts:\n    category: Installation Failure Data\n    is_dont_change_value: false\n    title: Installation Failure Data Report Link\n"
  },
  {
    "path": "steps/steps-app-gallery-reports/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/steps-chatwork-message/0.0.1/step.yml",
    "content": "title: steps-chatwork-message\nsummary: |\n  Send a Chatwork message\ndescription: |\n  Send a Chatwork message from your Bitrise build!\nwebsite: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsource_code_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsupport_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message/issues\npublished_at: 2019-08-01T14:01:11.774741+09:00\nsource:\n  git: https://github.com/monolithic-adam/bitrise-step-chatwork-message.git\n  commit: 669711074ac5119ea42d903ddeff276435e779e9\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/monolithic-adam/bitrise-step-chatwork-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_token: null\n  opts:\n    description: |\n      **An api\\_token input is required.**\n\n      To get your **API token** visit: https://www.chatwork.com/service/packages/chatwork/subpackages/api/token.php\n    is_required: true\n    is_sensitive: true\n    title: Chatwork API Token\n- opts:\n    description: |\n      **An room\\_id input is required.**\n\n      To get your **Room ID** look at the #!rid in your URL\n    is_required: true\n    is_sensitive: true\n    title: Chatwork Room ID\n  room_id: null\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    is_required: true\n    title: Build Status\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_required: true\n    title: App Title\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch\n- git_message: $BITRISE_GIT_MESSAGE\n  opts:\n    title: Git Message\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    title: Build URL\n"
  },
  {
    "path": "steps/steps-chatwork-message/0.0.2/step.yml",
    "content": "title: Send a Chatwork message\nsummary: |\n  Send a Chatwork message\ndescription: |\n  Send a Chatwork message from your Bitrise build!\nwebsite: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsource_code_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsupport_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message/issues\npublished_at: 2019-09-26T08:04:39.302499+09:00\nsource:\n  git: https://github.com/monolithic-adam/bitrise-step-chatwork-message.git\n  commit: 2ed0a7a18fe659f1ace25e6b85586dfc6188508a\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/monolithic-adam/bitrise-step-chatwork-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_token: null\n  opts:\n    description: |\n      **An api\\_token input is required.**\n\n      To get your **API token** visit: https://www.chatwork.com/service/packages/chatwork/subpackages/api/token.php\n    is_required: true\n    is_sensitive: true\n    title: Chatwork API Token\n- opts:\n    description: |\n      **An room\\_id input is required.**\n\n      To get your **Room ID** look at the #!rid in your URL\n    is_required: true\n    is_sensitive: true\n    title: Chatwork Room ID\n  room_id: null\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    is_required: true\n    title: Build Status\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_required: true\n    title: App Title\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch\n- git_message: $BITRISE_GIT_MESSAGE\n  opts:\n    title: Git Message\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    title: Bitrise Build URL\n- install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n  opts:\n    title: Install Page URL\n"
  },
  {
    "path": "steps/steps-chatwork-message/0.0.3/step.yml",
    "content": "title: Send a Chatwork message\nsummary: |\n  Send a Chatwork message\ndescription: |\n  Send a Chatwork message from your Bitrise build!\nwebsite: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsource_code_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsupport_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message/issues\npublished_at: 2019-10-11T09:42:56.644067+09:00\nsource:\n  git: https://github.com/monolithic-adam/bitrise-step-chatwork-message.git\n  commit: 40cfdbdc3a25e2e0c79f7fe4955df60ca7a6d1be\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/monolithic-adam/bitrise-step-chatwork-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_token: null\n  opts:\n    description: |\n      **An api_token input is required.**\n\n      To get your **API token** visit: https://www.chatwork.com/service/packages/chatwork/subpackages/api/token.php\n    is_required: true\n    is_sensitive: true\n    title: Chatwork API Token\n- opts:\n    description: |\n      **An room_id input is required.**\n\n      To get your **Room ID** look at the #!rid in your URL or in the group chat setting screen.\n      For more information visit: https://help.chatwork.com/hc/ja/articles/360000142942-%E3%83%AB%E3%83%BC%E3%83%A0ID%E3%82%92%E7%A2%BA%E8%AA%8D%E3%81%99%E3%82%8B\n    is_required: true\n    is_sensitive: true\n    title: Chatwork Room ID\n  room_id: null\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    is_required: true\n    title: Build Status\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_required: true\n    title: App Title\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch\n- git_message: $BITRISE_GIT_MESSAGE\n  opts:\n    title: Git Message\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    title: Bitrise Build URL\n- install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n  opts:\n    title: Install Page URL\n"
  },
  {
    "path": "steps/steps-chatwork-message/0.0.4/step.yml",
    "content": "title: Send a Chatwork message\nsummary: |\n  Send a Chatwork message\ndescription: |\n  Send a Chatwork message from your Bitrise build!\nwebsite: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsource_code_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message\nsupport_url: https://github.com/monolithic-adam/bitrise-step-chatwork-message/issues\npublished_at: 2019-12-27T14:27:59.775816+09:00\nsource:\n  git: https://github.com/monolithic-adam/bitrise-step-chatwork-message.git\n  commit: 10e226d42dd376cf2fc1ff494e30195b8b10acce\ntype_tags:\n- notification\ntoolkit:\n  go:\n    package_name: github.com/monolithic-adam/bitrise-step-chatwork-message\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\ninputs:\n- api_token: null\n  opts:\n    description: |\n      **An api_token input is required.**\n\n      To get your **API token** visit: https://www.chatwork.com/service/packages/chatwork/subpackages/api/token.php\n    is_required: true\n    is_sensitive: true\n    title: Chatwork API Token\n- opts:\n    description: |\n      **An room_id input is required.**\n\n      To get your **Room ID** look at the #!rid in your URL or in the group chat setting screen.\n      For more information visit: https://help.chatwork.com/hc/ja/articles/360000142942-%E3%83%AB%E3%83%BC%E3%83%A0ID%E3%82%92%E7%A2%BA%E8%AA%8D%E3%81%99%E3%82%8B\n    is_required: true\n    is_sensitive: true\n    title: Chatwork Room ID\n  room_id: null\n- chatwork_message: $CHATWORK_MESSAGE\n  opts:\n    description: |\n      If you want to send your own custom message instead of the default build status override it here.\n    title: Message to send to Chatwork\n- build_status: $BITRISE_BUILD_STATUS\n  opts:\n    is_required: true\n    title: Build Status\n- app_title: $BITRISE_APP_TITLE\n  opts:\n    is_required: true\n    title: App Title\n- git_branch: $BITRISE_GIT_BRANCH\n  opts:\n    title: Git Branch\n- git_message: $BITRISE_GIT_MESSAGE\n  opts:\n    title: Git Message\n- build_url: $BITRISE_BUILD_URL\n  opts:\n    title: Bitrise Build URL\n- install_page_url: $BITRISE_PUBLIC_INSTALL_PAGE_URL\n  opts:\n    title: Install Page URL\n"
  },
  {
    "path": "steps/steps-chatwork-message/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/swift-environment-variable-injector/0.1.0/step.yml",
    "content": "title: Swift Environment Variable Injector\nsummary: |\n  Step to inject static values from environment variables into Swift code files before compilation and Continuous deployment allowing us to not expose our production keys and values in statically in our code and store sensitive values safe.\ndescription: \"This step allows us to inject CI pipelines environment variables values\n  into Swift code static values before compilation and Continuous deployment to a\n  specific environment(Development, Testing or Production) where we can define the\n  values injected for each build and deployment e.g. a API url that the App uses and\n  is different for each environment. \\nAlso it allows us to not expose our production\n  keys and values in statically in our code.\\nFor more info, check out the Swift [Variable\n  Injector Project](https://github.com/LucianoPAlmeida/variable-injector) on github.\\n\"\nwebsite: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsource_code_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsupport_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector/issues\npublished_at: 2018-11-06T21:29:19.217608321-02:00\nsource:\n  git: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector.git\n  commit: 39e6e9380f65ced03af78d99860eee6c973a4182\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Variable Injector version to be used. Step will fail if invalid or\n      non-existent is specified.\n    is_required: true\n    title: Swift Variable Injector Version\n  variable_injector_version: 0.2.0\n- files: null\n  opts:\n    description: |\n      All the file paths separated by a white space.\n      The files will be visited by the [variable-injector](https://github.com/LucianoPAlmeida/variable-injector).\n      If there are literals matching the ENV_VAR pattern and the environment variable name is defined on the current workflow it will replace with it value.\n    is_expand: true\n    is_required: true\n    summary: The paths for the files which you be checked and have the values replaced\n      if it's aplicable.\n    title: Paths of the Swift files\n- opts:\n    description: \"All the names paths separated by a white space.\\nIf a string literal\n      on this files matches the environment variable pattern $(ENV_VAR) but is not\n      a ENV var to be replaced we can just ignore it. \\n\"\n    is_expand: true\n    is_required: false\n    summary: The variable names that will be ignored by the variable injector.\n    title: Environment Variable Names to ignore\n  vars_to_ignore: null\n- opts:\n    description: |\n      All injectictions variables and values logged. Also the output files content.\n    is_expand: true\n    is_required: false\n    summary: Indicates if the injection should print logs.\n    title: Verbose mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/swift-environment-variable-injector/0.1.1/step.yml",
    "content": "title: Swift Environment Variable Injector\nsummary: |\n  Step to inject static values from environment variables into Swift code files before compilation and Continuous deployment allowing us to not expose our production keys and values in statically in our code and store sensitive values safe.\ndescription: \"This step allows us to inject CI pipelines environment variables values\n  into Swift code static values before compilation and Continuous deployment to a\n  specific environment(Development, Testing or Production) where we can define the\n  values injected for each build and deployment e.g. a API url that the App uses and\n  is different for each environment. \\nAlso it allows us to not expose our production\n  keys and values in statically in our code.\\nFor more info, check out the Swift [Variable\n  Injector Project](https://github.com/LucianoPAlmeida/variable-injector) on github.\\n\"\nwebsite: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsource_code_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsupport_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector/issues\npublished_at: 2019-04-23T23:18:33.567900249-03:00\nsource:\n  git: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector.git\n  commit: 126cfbdfdc3719b2eb9dcbc80c6037e881404592\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Variable Injector version to be used. Step will fail if invalid or\n      non-existent is specified.\n    is_required: true\n    title: Swift Variable Injector Version\n  variable_injector_version: 0.2.1\n- files: null\n  opts:\n    description: |\n      All the file paths separated by a white space.\n      The files will be visited by the [variable-injector](https://github.com/LucianoPAlmeida/variable-injector).\n      If there are literals matching the ENV_VAR pattern and the environment variable name is defined on the current workflow it will replace with it value.\n    is_expand: true\n    is_required: true\n    summary: The paths for the files which you be checked and have the values replaced\n      if it's aplicable.\n    title: Paths of the Swift files\n- opts:\n    description: \"All the names paths separated by a white space.\\nIf a string literal\n      on this files matches the environment variable pattern $(ENV_VAR) but is not\n      a ENV var to be replaced we can just ignore it. \\n\"\n    is_expand: true\n    is_required: false\n    summary: The variable names that will be ignored by the variable injector.\n    title: Environment Variable Names to ignore\n  vars_to_ignore: null\n- opts:\n    description: |\n      All injectictions variables and values logged. Also the output files content.\n    is_expand: true\n    is_required: false\n    summary: Indicates if the injection should print logs.\n    title: Verbose mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/swift-environment-variable-injector/0.1.2/step.yml",
    "content": "title: Swift Environment Variable Injector\nsummary: |\n  Step to inject static values from environment variables into Swift code files before compilation and Continuous deployment allowing us to not expose our production keys and values in statically in our code and store sensitive values safe.\ndescription: \"This step allows us to inject CI pipelines environment variables values\n  into Swift code static values before compilation and Continuous deployment to a\n  specific environment(Development, Testing or Production) where we can define the\n  values injected for each build and deployment e.g. a API url that the App uses and\n  is different for each environment. \\nAlso it allows us to not expose our production\n  keys and values in statically in our code.\\nFor more info, check out the Swift [Variable\n  Injector Project](https://github.com/LucianoPAlmeida/variable-injector) on github.\\n\"\nwebsite: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsource_code_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsupport_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector/issues\npublished_at: 2022-10-11T23:56:23.567900249-03:00\nsource:\n  git: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector.git\n  commit: 6bbf82860e7373e3706ba5c722e0f3111892327f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Variable Injector version to be used. Step will fail if invalid or\n      non-existent is specified.\n    is_required: true\n    title: Swift Variable Injector Version\n  variable_injector_version: 0.2.1\n- files: null\n  opts:\n    description: |\n      All the file paths separated by a white space.\n      The files will be visited by the [variable-injector](https://github.com/LucianoPAlmeida/variable-injector).\n      If there are literals matching the ENV_VAR pattern and the environment variable name is defined on the current workflow it will replace with it value.\n    is_expand: true\n    is_required: true\n    summary: The paths for the files which you be checked and have the values replaced\n      if it's applicable.\n    title: Paths of the Swift files\n- opts:\n    description: \"All the names paths separated by a white space.\\nIf a string literal\n      on this files matches the environment variable pattern $(ENV_VAR) but is not\n      a ENV var to be replaced we can just ignore it. \\n\"\n    is_expand: true\n    is_required: false\n    summary: The variable names that will be ignored by the variable injector.\n    title: Environment Variable Names to ignore\n  vars_to_ignore: null\n- opts:\n    description: |\n      All injections variables and values logged. Also the output files content.\n    is_expand: true\n    is_required: false\n    summary: Indicates if the injection should print logs.\n    title: Verbose mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/swift-environment-variable-injector/0.1.3/step.yml",
    "content": "title: Swift Environment Variable Injector\nsummary: |\n  Step to inject static values from environment variables into Swift code files before compilation and Continuous deployment allowing us to not expose our production keys and values in statically in our code and store sensitive values safe.\ndescription: \"This step allows us to inject CI pipelines environment variables values\n  into Swift code static values before compilation and Continuous deployment to a\n  specific environment(Development, Testing or Production) where we can define the\n  values injected for each build and deployment e.g. a API url that the App uses and\n  is different for each environment. \\nAlso it allows us to not expose our production\n  keys and values in statically in our code.\\nFor more info, check out the Swift [Variable\n  Injector Project](https://github.com/LucianoPAlmeida/variable-injector) on github.\\n\"\nwebsite: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsource_code_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector\nsupport_url: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector/issues\npublished_at: 2022-11-09T09:01:30.261901568-03:00\nsource:\n  git: https://github.com/LucianoPAlmeida/bitrise-step-swift-environment-variable-injector.git\n  commit: d476ab9dbd4c7cbb5fb8cc6362d6969f8c659049\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: wget\n  - name: unzip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: Variable Injector version to be used. Step will fail if invalid or\n      non-existent is specified.\n    is_required: true\n    title: Swift Variable Injector Version\n  variable_injector_version: 0.2.1\n- files: null\n  opts:\n    description: |\n      All the file paths separated by a white space.\n      The files will be visited by the [variable-injector](https://github.com/LucianoPAlmeida/variable-injector).\n      If there are literals matching the ENV_VAR pattern and the environment variable name is defined on the current workflow it will replace with it value.\n    is_expand: true\n    is_required: true\n    summary: The paths for the files which you be checked and have the values replaced\n      if it's applicable.\n    title: Paths of the Swift files\n- opts:\n    description: \"All the names paths separated by a white space.\\nIf a string literal\n      on this files matches the environment variable pattern $(ENV_VAR) but is not\n      a ENV var to be replaced we can just ignore it. \\n\"\n    is_expand: true\n    is_required: false\n    summary: The variable names that will be ignored by the variable injector.\n    title: Environment Variable Names to ignore\n  vars_to_ignore: null\n- opts:\n    description: |\n      All injections variables and values logged. Also the output files content.\n    is_expand: true\n    is_required: false\n    summary: Indicates if the injection should print logs.\n    title: Verbose mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\n"
  },
  {
    "path": "steps/swift-environment-variable-injector/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/swift-package-manager-build-for-mac/0.0.1/step.yml",
    "content": "title: Swift Package Manager Build for Mac\nsummary: |\n  Runs Build on your macOS project with Swift Package Manager\ndescription: |\n  Runs Swift Package Manager's `swift build` action for macOS app projects.\nwebsite: https://github.com/kitasuke/bitrise-step-swift-package-manager-build-for-mac\nsource_code_url: https://github.com/kitasuke/bitrise-step-swift-package-manager-build-for-mac\nsupport_url: https://github.com/kitasuke/bitrise-step-swift-package-manager-build-for-mac/issues\npublished_at: 2019-03-19T00:58:00.147077+09:00\nsource:\n  git: https://github.com/kitasuke/bitrise-step-swift-package-manager-build-for-mac.git\n  commit: b6842ac60b082e18db4d7864c474433b1dd61faf\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/kitasuke/bitrise-step-swift-package-manager-build-for-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: ./.build\n  opts:\n    description: |\n      A build path, relative to the working directory.\n    is_expand: true\n    is_required: true\n    title: Build path\n- configuration: debug\n  opts:\n    description: |\n      Two build configurations, Debug (default) and Release.\n    title: Configuration\n    value_options:\n    - debug\n    - release\n- build_tests: \"no\"\n  opts:\n    description: |\n      Build both source and test targets\n    title: Build tests\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_sandbox: \"no\"\n  opts:\n    description: |\n      Disable using the sandbox when executing subprocesses\n    title: Disable sandbox\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EXECUTABLE_PATH: null\n  opts:\n    title: The executable path\n"
  },
  {
    "path": "steps/swift-package-manager-build-for-mac/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/swift-package-manager-test-for-mac/0.0.1/step.yml",
    "content": "title: Swift Package Manager Test for Mac\nsummary: |\n  Runs Test on your macOS project with Swift Package Manager\ndescription: |\n  Runs Swift Package Manager's `swift test` action for macOS app projects.\nwebsite: https://github.com/kitasuke/bitrise-step-swift-package-manager-test-for-mac\nsource_code_url: https://github.com/kitasuke/bitrise-step-swift-package-manager-test-for-mac\nsupport_url: https://github.com/kitasuke/bitrise-step-swift-package-manager-test-for-mac/issues\npublished_at: 2019-03-19T00:53:57.002409+09:00\nsource:\n  git: https://github.com/kitasuke/bitrise-step-swift-package-manager-test-for-mac.git\n  commit: c41e9cb4f8225207c7961519a219a5145f12dec7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/kitasuke/bitrise-step-swift-package-manager-test-for-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: ./.build\n  opts:\n    description: |\n      A build path, relative to the working directory.\n    is_expand: true\n    is_required: true\n    title: Build Path\n- is_skip_build: \"no\"\n  opts:\n    description: |\n      Should skip building the test target?\n    title: Skip build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_parallel: \"no\"\n  opts:\n    description: |\n      Should run the tests in parallel?\n    title: Parallel test\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/swift-package-manager-test-for-mac/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/swift-package-manager-xcodeproj-for-mac/0.0.1/step.yml",
    "content": "title: Swift Package Manager Xcodeproj for Mac\nsummary: |\n  Runs Generate Xcode project on your macOS project with Swift Package Manager\ndescription: |\n  Runs Swift Package Manager's `swift package generate-xcodeproj` action for macOS app projects.\nwebsite: https://github.com/kitasuke/bitrise-step-swift-package-manager-xcodeproj-for-mac\nsource_code_url: https://github.com/kitasuke/bitrise-step-swift-package-manager-xcodeproj-for-mac\nsupport_url: https://github.com/kitasuke/bitrise-step-swift-package-manager-xcodeproj-for-mac/issues\npublished_at: 2019-03-19T01:03:53.105517+09:00\nsource:\n  git: https://github.com/kitasuke/bitrise-step-swift-package-manager-xcodeproj-for-mac.git\n  commit: dc3e70c725c02f9a81eed3e61be84dd65681ceee\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/kitasuke/bitrise-step-swift-package-manager-xcodeproj-for-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path where the Xcode project should be generated\n    is_expand: true\n    is_required: true\n    title: Output path\n  output: .\n- enable_code_coverage: \"no\"\n  opts:\n    description: |\n      Enable code coverage in the generated project\n    title: Enable code coverage\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Path to xcconfig file to override\n    is_expand: true\n    is_required: false\n    title: Path to xcconfig file\n  xcconfig_overrides: \"\"\n"
  },
  {
    "path": "steps/swift-package-manager-xcodeproj-for-mac/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/swiftformat/0.1.0/step.yml",
    "content": "title: |-\n  SwiftFormat\nsummary: |\n  Runs SwiftFormat lint on the project\ndescription: |\n  Runs SwiftFormat on the project to verify formatted code\n  For more information about SwiftFormat please visit: https://github.com/nicklockwood/SwiftFormat\nwebsite: https://github.com/dmiluski/bitrise-step-swiftformat\nsource_code_url: https://github.com/dmiluski/bitrise-step-swiftformat\nsupport_url: https://github.com/dmiluski/bitrise-step-swiftformat/issues\npublished_at: 2020-04-09T10:32:19-07:00\nsource:\n  git: https://github.com/dmiluski/bitrise-step-swiftformat.git\n  commit: f131b2235ed2e2773822f3799141c6526ef5157f\nhost_os_tags:\n  - osx-10.10\n  - ubuntu-16.04\nproject_type_tags:\n  - ios\n  - macos\ntype_tags:\n  - utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftformat\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n  - formatting_path: null\n    opts:\n      category: Config\n      description: \"\"\n      is_required: true\n      title: \"Select the path where SwiftFormat should lint\"\n      summary: \"\"\n  - format_config_file: $BITRISE_SOURCE_DIR/.swiftformat\n    opts:\n      category: Config\n      description: |-\n        If you use a custom format configuration for Bitrise, you can specify the path here.\n      is_required: false\n      summary: \"\"\n      title: \"Format configuration file\"\n"
  },
  {
    "path": "steps/swiftformat/step-info.yml",
    "content": "maintainer: community"
  },
  {
    "path": "steps/swiftlint/0.1.1/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2017-09-09T16:47:46.577521+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: 9de7bb250035f464ae226a7ac3d0fcd586a879f2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\n"
  },
  {
    "path": "steps/swiftlint/0.10.1/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2020-07-27T10:06:56.623354+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: fb36f6fb3a5d51f73369c088b88ac9023d365af3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_range: all\n  opts:\n    category: Config\n    description: Take the git diff and only lint those files\n    is_required: true\n    summary: \"\"\n    title: Select option for range of Swiftlint\n    value_options:\n    - all\n    - changed\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - csv\n    - checkstyle\n    - emoji\n    - github-actions-logging\n    - html\n    - json\n    - junit\n    - markdown\n    - sonarqube\n    - xcode\n  reporter: xcode\n- opts:\n    category: Config\n    description: Use strict mode when linting (i.e. warnings become errors)\n    is_required: false\n    summary: \"\"\n    title: Use strict mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  strict: \"no\"\n- opts:\n    category: Config\n    description: Don't print status logs like 'Linting ' & 'Done linting'\n    is_required: false\n    summary: \"\"\n    title: Use quiet mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  quiet: \"no\"\noutputs:\n- SWIFTLINT_REPORT: null\n  opts:\n    category: Output\n    description: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings. This is useful when you want to pass it somewhere\n      else, for example on a Slack channel.\n    is_dont_change_value: true\n    summary: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings.\n    title: A Swiftlint report\n- SWIFTLINT_REPORT_PATH: null\n  opts:\n    category: Output\n    description: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the `$BITRISE_DEPLOY_DIR` with the generated report file name.\n      The file name depends on the reporter that was selected, for example for the\n      `junit` reporter, the generated file name will be `swiftlint_report.xml`, and\n      for the `html` reporter it will be `swiftlint_report.html`). This is useful\n      if you want to have this report in a separate file and do something with it,\n      for example upload to S3.\n    is_dont_change_value: true\n    summary: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the $BITRISE_DEPLOY_DIR with the generated report file name.\n    title: A Swiftlint report path\n"
  },
  {
    "path": "steps/swiftlint/0.2.1/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2017-09-27T17:14:45.524673+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: 60dc0f830de8ae78bbadf0daa1ef6463b1f73fcc\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: $BITRISE_SOURCE_DIR\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: 'If you use a custom linting configuration for Bitrise, you can specify\n      the path here. '\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n\n"
  },
  {
    "path": "steps/swiftlint/0.3.0/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2017-10-05T13:55:09.466210838+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: a0bc3edfc70a63f25d81c1971792a3526924063b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: $BITRISE_SOURCE_DIR\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: 'If you use a custom linting configuration for Bitrise, you can specify\n      the path here. '\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - xcode\n    - json\n    - csv\n    - checkstyle\n    - junit\n    - emoji\n  reporter: xcode\n"
  },
  {
    "path": "steps/swiftlint/0.3.1/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2017-10-13T10:05:52.995108629+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: e3a1dee2888e1864476a0526d8db2fbe73c7e7fb\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: 'If you use a custom linting configuration for Bitrise, you can specify\n      the path here. '\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - xcode\n    - json\n    - csv\n    - checkstyle\n    - junit\n    - emoji\n  reporter: xcode\n"
  },
  {
    "path": "steps/swiftlint/0.4.0/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2017-11-18T19:41:59.509442+01:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: 76bb95d97a4ea0ba2ebd03c0477c0342c2eeabe0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - xcode\n    - json\n    - csv\n    - checkstyle\n    - junit\n    - emoji\n  reporter: xcode\n- opts:\n    category: Config\n    description: Use strict mode when linting (i.e. warnings become errors)\n    is_required: false\n    summary: \"\"\n    title: Use strict mode\n    value_options:\n    - true\n    - false\n  strict: false\n"
  },
  {
    "path": "steps/swiftlint/0.4.2/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2017-11-18T22:54:29.053729+01:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: 48315ba5abea226bfb3ada4787128eece0c9eeb4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - xcode\n    - json\n    - csv\n    - checkstyle\n    - junit\n    - emoji\n  reporter: xcode\n- opts:\n    category: Config\n    description: Use strict mode when linting (i.e. warnings become errors)\n    is_required: false\n    summary: \"\"\n    title: Use strict mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  strict: \"no\"\n"
  },
  {
    "path": "steps/swiftlint/0.6.0/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2020-04-28T08:41:27.264122+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: a7cb74e722a3fea3abbaae9c23bdd8d1645eda46\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_range: all\n  opts:\n    category: Config\n    description: Take the git diff and only lint those files\n    is_required: true\n    summary: \"\"\n    title: Select option for range of Swiftlint\n    value_options:\n    - all\n    - changed\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - csv\n    - checkstyle\n    - emoji\n    - github-actions-logging\n    - html\n    - json\n    - junit\n    - markdown\n    - sonarqube\n    - xcode\n  reporter: xcode\n- opts:\n    category: Config\n    description: Use strict mode when linting (i.e. warnings become errors)\n    is_required: false\n    summary: \"\"\n    title: Use strict mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  strict: \"no\"\noutputs:\n- SWIFTLINT_REPORT: null\n  opts:\n    category: Output\n    description: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings. This is useful when you want to pass it somewhere\n      else, for example on a Slack channel.\n    is_dont_change_value: true\n    summary: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings.\n    title: A Swiftlint report\n- SWIFTLINT_REPORT_PATH: null\n  opts:\n    category: Output\n    description: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the `$BITRISE_DEPLOY_DIR` with the generated report file name.\n      The file name depends on the reporter that was selected, for example for the\n      `junit` reporter, the generated file name will be `swiftlint_report.xml`, and\n      for the `html` reporter it will be `swiftlint_report.html`). This is useful\n      if you want to have this report in a separate file and do something with it,\n      for example upload to S3.\n    is_dont_change_value: true\n    summary: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the $BITRISE_DEPLOY_DIR with the generated report file name.\n    title: A Swiftlint report path\n"
  },
  {
    "path": "steps/swiftlint/0.7.0/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2020-05-02T12:12:26.542206+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: 7a42e0cce43e38cccab539ebc4f95c6458c49458\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_range: all\n  opts:\n    category: Config\n    description: Take the git diff and only lint those files\n    is_required: true\n    summary: \"\"\n    title: Select option for range of Swiftlint\n    value_options:\n    - all\n    - changed\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - csv\n    - checkstyle\n    - emoji\n    - github-actions-logging\n    - html\n    - json\n    - junit\n    - markdown\n    - sonarqube\n    - xcode\n  reporter: xcode\n- opts:\n    category: Config\n    description: Use strict mode when linting (i.e. warnings become errors)\n    is_required: false\n    summary: \"\"\n    title: Use strict mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  strict: \"no\"\n- opts:\n    category: Config\n    description: Don't print status logs like 'Linting ' & 'Done linting'\n    is_required: false\n    summary: \"\"\n    title: Use quiet mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  quiet: \"no\"\noutputs:\n- SWIFTLINT_REPORT: null\n  opts:\n    category: Output\n    description: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings. This is useful when you want to pass it somewhere\n      else, for example on a Slack channel.\n    is_dont_change_value: true\n    summary: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings.\n    title: A Swiftlint report\n- SWIFTLINT_REPORT_PATH: null\n  opts:\n    category: Output\n    description: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the `$BITRISE_DEPLOY_DIR` with the generated report file name.\n      The file name depends on the reporter that was selected, for example for the\n      `junit` reporter, the generated file name will be `swiftlint_report.xml`, and\n      for the `html` reporter it will be `swiftlint_report.html`). This is useful\n      if you want to have this report in a separate file and do something with it,\n      for example upload to S3.\n    is_dont_change_value: true\n    summary: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the $BITRISE_DEPLOY_DIR with the generated report file name.\n    title: A Swiftlint report path\n"
  },
  {
    "path": "steps/swiftlint/0.8.0/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Runs Swiftlint on the project\ndescription: |\n  Runs Swiftlint on the project to provide clean code\n  For more information about Swiftlint please visit: https://github.com/realm/SwiftLint/\nwebsite: https://github.com/kimdv/bitrise-step-swiftlint\nsource_code_url: https://github.com/kimdv/bitrise-step-swiftlint\nsupport_url: https://github.com/kimdv/bitrise-step-swiftlint/issues\npublished_at: 2020-07-27T10:06:56.623354+02:00\nsource:\n  git: https://github.com/kimdv/bitrise-step-swiftlint.git\n  commit: fb964570c2de14a7e82b65c031cb3fb77a720c0d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    category: Config\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_range: all\n  opts:\n    category: Config\n    description: Take the git diff and only lint those files\n    is_required: true\n    summary: \"\"\n    title: Select option for range of Swiftlint\n    value_options:\n    - all\n    - changed\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    category: Config\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    category: Config\n    description: Sets the reporter style when printing violations or errors.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - csv\n    - checkstyle\n    - emoji\n    - github-actions-logging\n    - html\n    - json\n    - junit\n    - markdown\n    - sonarqube\n    - xcode\n  reporter: xcode\n- opts:\n    category: Config\n    description: Use strict mode when linting (i.e. warnings become errors)\n    is_required: false\n    summary: \"\"\n    title: Use strict mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  strict: \"no\"\n- opts:\n    category: Config\n    description: Don't print status logs like 'Linting ' & 'Done linting'\n    is_required: false\n    summary: \"\"\n    title: Use quiet mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  quiet: \"no\"\noutputs:\n- SWIFTLINT_REPORT: null\n  opts:\n    category: Output\n    description: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings. This is useful when you want to pass it somewhere\n      else, for example on a Slack channel.\n    is_dont_change_value: true\n    summary: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings.\n    title: A Swiftlint report\n- SWIFTLINT_REPORT_PATH: null\n  opts:\n    category: Output\n    description: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the `$BITRISE_DEPLOY_DIR` with the generated report file name.\n      The file name depends on the reporter that was selected, for example for the\n      `junit` reporter, the generated file name will be `swiftlint_report.xml`, and\n      for the `html` reporter it will be `swiftlint_report.html`). This is useful\n      if you want to have this report in a separate file and do something with it,\n      for example upload to S3.\n    is_dont_change_value: true\n    summary: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the $BITRISE_DEPLOY_DIR with the generated report file name.\n    title: A Swiftlint report path\n"
  },
  {
    "path": "steps/swiftlint/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/swiftlint-extended/1.0.0/step.yml",
    "content": "title: Swiftlint\nsummary: |\n  Generates swiftlint reports in different formats, compatible with Bitrise test reports add-on\ndescription: |\n  This step generates the swiftlint report and saves it to a file in the bitrise deploy folder. It produces 2 environment variables, one with the report and the other one with the path to the report file. The first variable is useful if you want to p pass your report directly to somewhere, for example a Slack channel. The second variable is useful if you want to process the report file further, for example upload it to S3 or attach it to a pull request. Finally, this step is compatible with the Bitrise test reports add-on, so in case the linting fails, you can easily see the details there.\nwebsite: https://github.com/lawicko/bitrise-step-swiftlint\nsource_code_url: https://github.com/lawicko/bitrise-step-swiftlint\nsupport_url: https://github.com/lawicko/bitrise-step-swiftlint/issues\npublished_at: 2020-05-07T11:15:19.326789+02:00\nsource:\n  git: https://github.com/lawicko/bitrise-step-swiftlint.git\n  commit: a875b43bc88c36ddc45fc291692bab07b78f50e6\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: swiftlint\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- linting_path: null\n  opts:\n    description: \"\"\n    is_required: true\n    summary: \"\"\n    title: Select the path where Swiftlint should lint\n- lint_config_file: $BITRISE_SOURCE_DIR/.swiftlint.yml\n  opts:\n    description: If you use a custom linting configuration for Bitrise, you can specify\n      the path here.\n    is_required: false\n    summary: \"\"\n    title: Linting configuration file\n- opts:\n    description: Sets the reporter type when printing violations or errors.\n    summary: \"\"\n    title: Select the reporter type\n    value_options:\n    - checkstyle\n    - csv\n    - emoji\n    - github-actions-logging\n    - html\n    - json\n    - junit\n    - markdown\n    - sonarqube\n    - xcode\n  reporter: xcode\n- opts:\n    description: When using the strict mode, the warnings will become errors.\n    is_required: false\n    summary: \"\"\n    title: Select yest if you want to use the strict mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  strict: \"no\"\n- opts:\n    description: This will be used as a report file name. Please don't put the extension\n      here. The extension will be determined depending on the reporter that you choose.\n      The default is `swiftlint_report`.\n    is_required: true\n    summary: The report file name, without extension.\n    title: The report file name, without extension.\n  report_file: swiftlint_report\noutputs:\n- SWIFTLINT_REPORT: null\n  opts:\n    description: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings. This is useful when you want to pass it somewhere\n      else, for example on a Slack channel.\n    is_dont_change_value: true\n    summary: The generated Swiftlint report. May be empty if the Swiftlint succeeded\n      with 0 errors or warnings. This is useful when you want to pass it somewhere\n      else, for example on a Slack channel.\n    title: A Swiftlint report\n- SWIFTLINT_REPORT_PATH: null\n  opts:\n    description: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the `$BITRISE_DEPLOY_DIR` with the `report_file` you provide\n      as one of the inputs to this step. The file name depends on the reporter that\n      was selected, for example for the `junit` reporter, the generated file name\n      will have the extension `xml`, and for the `html` reporter it will be `html`).\n      This is useful if you want to have this report in a separate file and do something\n      with it, for example upload to S3.\n    is_dont_change_value: true\n    summary: The path to the generated Swiftlint report (by default, it is created\n      by concatenating the `$BITRISE_DEPLOY_DIR` with the `report_file` you provide\n      as one of the inputs to this step. The file name depends on the reporter that\n      was selected, for example for the `junit` reporter, the generated file name\n      will have the extension `xml`, and for the `html` reporter it will be `html`).\n      This is useful if you want to have this report in a separate file and do something\n      with it, for example upload to S3.\n    title: A Swiftlint report path\n"
  },
  {
    "path": "steps/swiftlint-extended/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/telegram-notifier/1.0.0/step.yml",
    "content": "title: Telegram Notifier\nsummary: |\n  Notify Telegram groups about build status\ndescription: |\n  This plugin let's you notify about build status on your Telegram groups\nwebsite: https://github.com/munirwanis/bitrise-step-telegram-notifier\nsource_code_url: https://github.com/munirwanis/bitrise-step-telegram-notifier\nsupport_url: https://github.com/munirwanis/bitrise-step-telegram-notifier/issues\npublished_at: 2017-10-31T13:25:11.222148-02:00\nsource:\n  git: https://github.com/munirwanis/bitrise-step-telegram-notifier.git\n  commit: 7b954855740fb70abcfdd9ba355b5f9242a42897\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: false\nrun_if: \"\"\ninputs:\n- TELEGRAM_BOT_TOKEN: $TELEGRAM_BOT_TOKEN\n  opts:\n    description: |\n      Your bot token\n      You can also set it as a Secret with the name `TELEGRAM_BOT_TOKEN`\n    is_required: true\n    title: Telegram Bot Token\n- TELEGRAM_CHAT_ID: $TELEGRAM_CHAT_ID\n  opts:\n    description: |\n      The chat you want to send the message\n      You can also set it as a Secret with the name `TELEGRAM_CHAT_ID`\n    is_required: true\n    title: Chat ID\n"
  },
  {
    "path": "steps/telegram-notifier/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/telegram-notify/1.0.2/step.yml",
    "content": "title: Send Telegram Message\nsummary: |\n  Notify telegram group or chat on builds status.\ndescription: |\n  This step will send a message to the provided [telegram](https://core.telegram.org/bots) chat.\n  Includes the build status and download URL. You can also add a custom message to be sent with the notification.\n  This step always runs, no matter if build succeded or failed.\nwebsite: https://github.com/mcaldas/bitrise-step-telegram-notify\nsource_code_url: https://github.com/mcaldas/bitrise-step-telegram-notify\nsupport_url: https://github.com/mcaldas/bitrise-step-telegram-notify/issues\npublished_at: 2018-10-28T01:28:51.556107627+03:00\nsource:\n  git: https://github.com/mcaldas/bitrise-step-telegram-notify.git\n  commit: 1213396f97138fcd4dcb64e6a19266ce66e28843\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The bot token.\n      Can also be taken from env var `TELEGRAM_BOT_TOKEN`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Bot Token\n  telegram_bot_token: $TELEGRAM_BOT_TOKEN\n- opts:\n    description: |\n      The id of the chat notifications will be sent to.\n      Can also be taken from env var `TELEGRAM_CHAT_ID`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Chat ID\n  telegram_chat_id: $TELEGRAM_CHAT_ID\n- download_url: $DOWNLOAD_URL\n  opts:\n    description: |\n      The url where artifacts can be downloaded.\n    is_required: true\n    title: Download URL\n- custom_message: $CUSTOM_MESSAGE\n  opts:\n    description: \"Any info you would like to append to the message. \\nIt is sent both\n      on succeeded and failed builds.\\n\"\n    is_expand: true\n    is_required: false\n    title: Custom message\n"
  },
  {
    "path": "steps/telegram-notify/1.0.3/step.yml",
    "content": "title: Send Telegram Message\nsummary: |\n  Notify telegram group or chat on builds status.\ndescription: |\n  This step will send a message to the provided [telegram](https://core.telegram.org/bots) chat.\n  Includes the build status and download URL. You can also add a custom message to be sent with the notification.\n  This step always runs, no matter if build succeded or failed.\nwebsite: https://github.com/mcaldas/bitrise-step-telegram-notify\nsource_code_url: https://github.com/mcaldas/bitrise-step-telegram-notify\nsupport_url: https://github.com/mcaldas/bitrise-step-telegram-notify/issues\npublished_at: 2018-11-01T00:22:10.739270328+02:00\nsource:\n  git: https://github.com/mcaldas/bitrise-step-telegram-notify.git\n  commit: 6799db07780e5907f0a30646ba7a65663ed8abc5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The bot token.\n      Can also be taken from env var `TELEGRAM_BOT_TOKEN`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Bot Token\n  telegram_bot_token: $TELEGRAM_BOT_TOKEN\n- opts:\n    description: |\n      The id of the chat notifications will be sent to.\n      Can also be taken from env var `TELEGRAM_CHAT_ID`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Chat ID\n  telegram_chat_id: $TELEGRAM_CHAT_ID\n- download_url: $DOWNLOAD_URL\n  opts:\n    description: |\n      The url where artifacts can be downloaded.\n    is_required: true\n    title: Download URL\n- custom_message: $CUSTOM_MESSAGE\n  opts:\n    description: \"Any info you would like to append to the message. \\nIt is sent both\n      on succeeded and failed builds.\\n\"\n    is_expand: true\n    is_required: false\n    title: Custom message\n"
  },
  {
    "path": "steps/telegram-notify/1.0.5/step.yml",
    "content": "title: Send Telegram Message\nsummary: |\n  Notify telegram group or chat on builds status.\ndescription: |\n  This step will send a message to the provided [telegram](https://core.telegram.org/bots) chat.\n  Includes the build status and download URL. You can also add a custom message to be sent with the notification.\n  This step always runs, no matter if build succeded or failed.\nwebsite: https://github.com/mcaldas/bitrise-step-telegram-notify\nsource_code_url: https://github.com/mcaldas/bitrise-step-telegram-notify\nsupport_url: https://github.com/mcaldas/bitrise-step-telegram-notify/issues\npublished_at: 2019-02-02T00:27:06.060346+02:00\nsource:\n  git: https://github.com/mcaldas/bitrise-step-telegram-notify.git\n  commit: a34bfeb6c68e4b33e42e67242bb91a729ca5f373\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The bot token.\n      Can also be taken from env var `TELEGRAM_BOT_TOKEN`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Bot Token\n  telegram_bot_token: $TELEGRAM_BOT_TOKEN\n- opts:\n    description: |\n      The id of the chat notifications will be sent to.\n      Can also be taken from env var `TELEGRAM_CHAT_ID`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Chat ID\n  telegram_chat_id: $TELEGRAM_CHAT_ID\n- download_url: $DOWNLOAD_URL\n  opts:\n    description: |\n      The url where artifacts can be downloaded.\n    is_required: true\n    title: Download URL\n- custom_message: $CUSTOM_MESSAGE\n  opts:\n    description: \"Any info you would like to append to the message. \\nIt is sent both\n      on succeeded and failed builds.\\n\"\n    is_expand: true\n    is_required: false\n    title: Custom message\n"
  },
  {
    "path": "steps/telegram-notify/2.0.0/step.yml",
    "content": "title: Send Telegram Message\nsummary: |\n  Notify telegram group or chat on builds status.\ndescription: |\n  This step will send a message to the provided [telegram](https://core.telegram.org/bots) chat.\n  Includes the build status and download URL. You can also add a custom message to be sent with the notification.\n  This step always runs, no matter if build succeded or failed.\nwebsite: https://github.com/mcaldas/bitrise-step-telegram-notify\nsource_code_url: https://github.com/mcaldas/bitrise-step-telegram-notify\nsupport_url: https://github.com/mcaldas/bitrise-step-telegram-notify/issues\npublished_at: 2023-06-21T02:14:41.127136+03:00\nsource:\n  git: https://github.com/mcaldas/bitrise-step-telegram-notify.git\n  commit: 005b37095c54b49ca57aea339b7a831fb845ed3d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: \"\"\ninputs:\n- link_previews_enabled: \"no\"\n  opts:\n    title: Enable Link Previews\n    value_options:\n    - \"no\"\n    - \"yes\"\n- opts:\n    description: |\n      The bot token.\n      Can also be taken from env var `TELEGRAM_BOT_TOKEN`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Bot Token\n  telegram_bot_token: $TELEGRAM_BOT_TOKEN\n- opts:\n    description: |\n      The id of the chat notifications will be sent to.\n      Can also be taken from env var `TELEGRAM_CHAT_ID`\n    is_required: true\n    is_sensitive: true\n    title: Telegram Chat ID\n  telegram_chat_id: $TELEGRAM_CHAT_ID\n- download_url: $DOWNLOAD_URL\n  opts:\n    description: |\n      The url where artifacts can be downloaded.\n    is_required: true\n    title: Download URL\n- custom_message: $CUSTOM_MESSAGE\n  opts:\n    description: \"Any info you would like to append to the message. \\nIt is sent both\n      on succeeded and failed builds.\\nYou can also include newlines in the message\n      by using \\\\\\\\n.\\n\"\n    is_expand: true\n    is_required: false\n    title: Custom message\n"
  },
  {
    "path": "steps/telegram-notify/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/testfairy-deploy/2.0.0/step.yml",
    "content": "title: TestFairy Deploy\ndescription: |-\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nsummary: |-\n  Deploy your awesome App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments and let the TestFairy do it's magic.\nwebsite: https://github.com/bitrise-io/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-io/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-io/steps-testfairy-deploy/issues\npublished_at: 2015-09-08T11:55:41.183669292+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-testfairy-deploy.git\n  commit: a73fa5cff8293b50e4d2fef2fe3fb5b0695d1a9f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- testfairy\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n      You can find your API key under the settings menu.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: TestFairy API key\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: dSYM path\n- opts:\n    description: |-\n      Tester Groups that will be notified when the app is ready.\n      Setup groups in your TestFairy account testers page.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Comments\n"
  },
  {
    "path": "steps/testfairy-deploy/2.0.1/step.yml",
    "content": "title: TestFairy Deploy\nsummary: |-\n  Deploy your awesome App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments and let the TestFairy do it's magic.\ndescription: |-\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-io/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-io/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-io/steps-testfairy-deploy/issues\npublished_at: 2015-11-03T13:56:21.768108995+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-testfairy-deploy.git\n  commit: f3b7cc5ef9d7e02c93b89281a0a29c54bdfc4744\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n      You can find your API key under the settings menu.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: TestFairy API key\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: dSYM path\n- opts:\n    description: |-\n      Tester Groups that will be notified when the app is ready.\n      Setup groups in your TestFairy account testers page.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy/2.1.1/step.yml",
    "content": "title: TestFairy Deploy\nsummary: Deploy your App to TestFairy.\ndescription: |-\n  Deploy your App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments.\n\n\n  **NOTE** To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-io/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-io/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-io/steps-testfairy-deploy/issues\npublished_at: 2018-07-05T10:03:29.978485034+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-testfairy-deploy.git\n  commit: 6c777f397d545e73b6b3153df5514faa266d7834\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n\n\n      **NOTE** You can find your API key under the settings menu.\n    is_required: true\n    summary: TestFairy API key\n    title: TestFairy API key\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_required: true\n    summary: IPA path\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    summary: dSYM path\n    title: dSYM path\n- opts:\n    description: \"Tester Groups that will be notified when the app is ready.\\nSetup\n      groups in your TestFairy account testers page.   \"\n    summary: Tester groups\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: Email notification\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: Recording duration\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: Video recording\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: Comments\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy/2.2.0/step.yml",
    "content": "title: TestFairy Deploy\nsummary: Deploy your App to TestFairy.\ndescription: |-\n  Deploy your awesome App to Testfairy easily, making use of multiple configuration options.\n\n  * Set tester groups to be notified\n  * Enable email notification for the build\n  * Enable in-app notification of new versions\n  * Set recording duration\n  * Enable or disable video recording\n  * Add your comments\n\n  Once you're done setting up, you can simply let TestFairy do its magic!\n\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-io/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-io/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-io/steps-testfairy-deploy/issues\npublished_at: 2018-08-31T08:05:43.545997413Z\nsource:\n  git: https://github.com/bitrise-io/steps-testfairy-deploy.git\n  commit: ec185517d2e99f7cbb2b73e8b468dc7e7148f017\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n\n\n      **NOTE** You can find your API key under the settings menu.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: TestFairy API key\n    title: TestFairy API key\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_required: true\n    summary: IPA path\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    summary: dSYM path\n    title: dSYM path\n- opts:\n    description: \"Tester Groups that will be notified when the app is ready.\\nSetup\n      groups in your TestFairy account testers page.   \"\n    summary: Tester groups\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: Email notification\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: Recording duration\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: Video recording\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: Comments\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy/2.3.0/step.yml",
    "content": "title: TestFairy Deploy\nsummary: Deploy your App to TestFairy.\ndescription: |-\n  Deploy your awesome App to Testfairy easily, making use of multiple configuration options.\n\n  * Set tester groups to be notified\n  * Enable email notification for the build\n  * Enable in-app notification of new versions\n  * Set recording duration\n  * Enable or disable video recording\n  * Add your comments\n\n  Once you're done setting up, you can simply let TestFairy do its magic!\n\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy/issues\npublished_at: 2019-06-05T08:24:22.724043029Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy.git\n  commit: 262cc373a916b093c4db1d62dcbdb98ba004da6d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n\n\n      **NOTE** You can find your API key under the settings menu.\n    is_required: true\n    is_sensitive: true\n    summary: TestFairy API key\n    title: TestFairy API key\n- opts:\n    description: If you are using a private cloud endpoint for TestFairy, specify\n      it here\n    summary: Private cloud endpoint for TestFairy\n    title: Private cloud endpoint\n  server_endpoint: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_required: true\n    summary: IPA path\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    summary: dSYM path\n    title: dSYM path\n- opts:\n    description: \"Tester Groups that will be notified when the app is ready.\\nSetup\n      groups in your TestFairy account testers page.   \"\n    summary: Tester groups\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: Email notification\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: Recording duration\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: Video recording\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: Comments\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy/2.3.1/step.yml",
    "content": "title: TestFairy Deploy\nsummary: Deploy your App to TestFairy.\ndescription: |-\n  Deploy your awesome App to Testfairy easily, making use of multiple configuration options.\n\n  * Set tester groups to be notified\n  * Enable email notification for the build\n  * Enable in-app notification of new versions\n  * Set recording duration\n  * Enable or disable video recording\n  * Add your comments\n\n  Once you're done setting up, you can simply let TestFairy do its magic!\n\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy/issues\npublished_at: 2020-10-14T15:08:42.313605849Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy.git\n  commit: 0a7696dafbac7b20f1272911133d674f87493657\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n\n\n      **NOTE** You can find your API key under the settings menu.\n    is_required: true\n    is_sensitive: true\n    summary: TestFairy API key\n    title: TestFairy API key\n- opts:\n    description: If you are using a private cloud endpoint for TestFairy, specify\n      it here\n    summary: Private cloud endpoint for TestFairy\n    title: Private cloud endpoint\n  server_endpoint: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_required: true\n    summary: IPA path\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    summary: dSYM path\n    title: dSYM path\n- opts:\n    description: \"Tester Groups that will be notified when the app is ready.\\nSetup\n      groups in your TestFairy account testers page.   \"\n    summary: Tester groups\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: Email notification\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: Recording duration\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: Video recording\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: Comments\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy/2.3.2/step.yml",
    "content": "title: TestFairy Deploy\nsummary: Deploy your App to TestFairy.\ndescription: |-\n  Deploy your awesome App to Testfairy easily, making use of multiple configuration options.\n\n  * Set tester groups to be notified\n  * Enable email notification for the build\n  * Enable in-app notification of new versions\n  * Set recording duration\n  * Enable or disable video recording\n  * Add your comments\n\n  Once you're done setting up, you can simply let TestFairy do its magic!\n\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy/issues\npublished_at: 2020-10-15T14:45:56.595888763Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy.git\n  commit: b0f601944f0594c84093e615227425702f211c68\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n\n\n      **NOTE** You can find your API key under the settings menu.\n    is_required: true\n    is_sensitive: true\n    summary: TestFairy API key\n    title: TestFairy API key\n- opts:\n    description: If you are using a private cloud endpoint for TestFairy, specify\n      it here\n    summary: Private cloud endpoint for TestFairy\n    title: Private cloud endpoint\n  server_endpoint: \"\"\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: Path for the IPA to upload to TestFairy.\n    is_required: true\n    summary: IPA path\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: Path for the dSYM to upload to TestFairy.\n    summary: dSYM path\n    title: dSYM path\n- opts:\n    description: \"Tester Groups that will be notified when the app is ready.\\nSetup\n      groups in your TestFairy account testers page.   \"\n    summary: Tester groups\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: Email notification\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: Recording duration\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: Video recording\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: Comments\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/testfairy-deploy-android/1.0.0/step.yml",
    "content": "title: TestFairy Deploy Android\nsummary: |-\n  Deploy your awesome App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments and let the TestFairy do it's magic.\ndescription: |-\n  Deploy your awesome App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments and let the TestFairy do it's magic.\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android/issues\npublished_at: 2016-02-22T07:34:58.706705979-03:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy-android.git\n  commit: 789231b5d8c3b2c630bcbb6c52755d676acc1c78\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- testfairy\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: \"\"\n  opts:\n    description: |-\n      API key from TestFairy.\n      You can find your API key under the settings menu.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    summary: \"\"\n    title: TestFairy API key\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: Path for the APK to upload to TestFairy.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: APK path\n- opts:\n    description: |-\n      Tester Groups that will be notified when the app is ready.\n      Setup groups in your TestFairy account testers page.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- icon_watermark: \"off\"\n  opts:\n    description: Sets Icon Watermark.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Icon Watermark\n    value_options:\n    - \"on\"\n    - \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    summary: \"\"\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL_ANDROID: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy-android/1.0.1/step.yml",
    "content": "title: TestFairy Deploy Android\nsummary: |-\n  Deploy your awesome App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments and let the TestFairy do it's magic.\ndescription: |-\n  Deploy your awesome App to TestFairy, set Tester Groups to be notified,\n  enable email notification for the build, enable in-app notification of new\n  version, set recording duration, set if video recording is enabled and add\n  your comments and let the TestFairy do it's magic.\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android/issues\npublished_at: 2016-04-11T16:25:41.039830686+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy-android.git\n  commit: dbb18e85481c7b9e23fc681f6b4fee77ea8ccf32\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $TEST_FAIRY_API_KEY\n  opts:\n    description: |-\n      API key from TestFairy.\n      You can find your API key under the settings menu.\n    is_required: true\n    summary: \"\"\n    title: TestFairy API key\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: Path for the APK to upload to TestFairy.\n    is_required: true\n    summary: \"\"\n    title: APK path\n- opts:\n    description: |-\n      Tester Groups that will be notified when the app is ready.\n      Setup groups in your TestFairy account testers page.\n    summary: \"\"\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: \"\"\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: \"\"\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: \"\"\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- icon_watermark: \"off\"\n  opts:\n    description: Sets Icon Watermark.\n    summary: \"\"\n    title: Icon Watermark\n    value_options:\n    - \"on\"\n    - \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: \"\"\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL_ANDROID: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy-android/1.0.3/step.yml",
    "content": "title: TestFairy Deploy Android\nsummary: Deploy your awesome App to TestFairy.\ndescription: |-\n  Deploy your awesome App to Testfairy easily, making use of multiple configuration options.\n\n  * Set tester groups to be notified\n  * Enable email notification for the build\n  * Enable in-app notification of new versions\n  * Set recording duration\n  * Enable or disable video recording\n  * Add your comments\n\n  Once you're done setting up, you can simply let TestFairy do its magic!\n\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android/issues\npublished_at: 2018-08-31T11:15:58.990371126Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy-android.git\n  commit: 1b57d100739c7c3d581f4b78fd56afc397b17c60\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $TEST_FAIRY_API_KEY\n  opts:\n    description: |-\n      API key from TestFairy.\n      You can find your API key under the settings menu.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: TestFairy API key\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: Path for the APK to upload to TestFairy.\n    is_required: true\n    summary: \"\"\n    title: APK path\n- opts:\n    description: |-\n      Tester Groups that will be notified when the app is ready.\n      Setup groups in your TestFairy account testers page.\n    summary: \"\"\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: \"\"\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: \"\"\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: \"\"\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- icon_watermark: \"off\"\n  opts:\n    description: Sets Icon Watermark.\n    summary: \"\"\n    title: Icon Watermark\n    value_options:\n    - \"on\"\n    - \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: \"\"\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL_ANDROID: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy-android/1.0.4/step.yml",
    "content": "title: TestFairy Deploy Android\nsummary: Deploy your awesome App to TestFairy.\ndescription: |-\n  Deploy your awesome App to Testfairy easily, making use of multiple configuration options.\n\n  * Set tester groups to be notified\n  * Enable email notification for the build\n  * Enable in-app notification of new versions\n  * Set recording duration\n  * Enable or disable video recording\n  * Add your comments\n\n  Once you're done setting up, you can simply let TestFairy do its magic!\n\n  To use this step you have to register\n  an account on [TestFairy.com](http://testfairy.com/).\nwebsite: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsource_code_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android\nsupport_url: https://github.com/bitrise-steplib/steps-testfairy-deploy-android/issues\npublished_at: 2020-10-14T14:29:39.683328957Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-testfairy-deploy-android.git\n  commit: ba3d725f309424528cf795ff2e99b4b28286ed10\nhost_os_tags:\n- osx-10.10\n- ubuntu\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- api_key: $TEST_FAIRY_API_KEY\n  opts:\n    description: |-\n      API key from TestFairy.\n      You can find your API key under the settings menu.\n    is_required: true\n    is_sensitive: true\n    summary: \"\"\n    title: TestFairy API key\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: Path for the APK to upload to TestFairy.\n    is_required: true\n    summary: \"\"\n    title: APK path\n- opts:\n    description: |-\n      Tester Groups that will be notified when the app is ready.\n      Setup groups in your TestFairy account testers page.\n    summary: \"\"\n    title: Tester groups\n  tester_groups: \"\"\n- notify: \"off\"\n  opts:\n    description: Sets if should email testers about new version.\n    summary: \"\"\n    title: Email notification\n    value_options:\n    - \"on\"\n    - \"off\"\n- auto_update: \"off\"\n  opts:\n    description: |-\n      If auto update is on all users will be prompt to update\n      to this build next time they run the app.\n    summary: \"\"\n    title: Auto update\n    value_options:\n    - \"on\"\n    - \"off\"\n- max_test_duration: 10m\n  opts:\n    description: Maximum session recording length, eg 20m or 1h. Maximum 24h.\n    summary: \"\"\n    title: Recording duration\n- opts:\n    description: Sets if video recording is enabled for this build.\n    summary: \"\"\n    title: Video recording\n    value_options:\n    - \"on\"\n    - wifi\n    - \"off\"\n  video_recording: \"off\"\n- icon_watermark: \"off\"\n  opts:\n    description: Sets Icon Watermark.\n    summary: \"\"\n    title: Icon Watermark\n    value_options:\n    - \"on\"\n    - \"off\"\n- comment: \"\"\n  opts:\n    description: Comment text will be included in the email sent to testers.\n    summary: \"\"\n    title: Comments\noutputs:\n- TESTFAIRY_PUBLIC_INSTALL_PAGE_URL_ANDROID: null\n  opts:\n    description: Public Install Page's URL\n    title: Public Install Page URL\n"
  },
  {
    "path": "steps/testfairy-deploy-android/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/testingbot-upload-app/0.0.1/step.yml",
    "content": "title: TestingBot App Upload\nsummary: |\n  Uploads your APK or IPA to TestingBot for mobile app testing.\ndescription: |\n  Uploads your APK or IPA to TestingBot for mobile app testing. You can find more information on https://testingbot.com\nwebsite: https://github.com/testingbot/bitrise-step-testingbot-app-upload\nsource_code_url: https://github.com/testingbot/bitrise-step-testingbot-app-upload\nsupport_url: https://github.com/testingbot/bitrise-step-testingbot-app-upload/issues\npublished_at: 2021-03-25T13:38:48.923785+01:00\nsource:\n  git: https://github.com/testingbot/bitrise-step-testingbot-app-upload.git\n  commit: 9cf3095969e1183046bbf1ccc0eab3f8737354af\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_ipa_filepath: null\n  opts:\n    description: |\n      The app file you want to upload to TestingBot, usually $BITRISE\\_APK\\_PATH or $BITRISE\\_IPA\\_PATH.\n    is_expand: true\n    is_required: true\n    summary: Location of the IPA or APK that you want to upload.\n    title: Location of the IPA or APK\n- opts:\n    description: |\n      You can find the key in the TestingBot member area.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The key to authenticate with TestingBot.\n    title: TestingBot Key\n  testingbot_key: null\n- opts:\n    description: |\n      You can find the secret in the TestingBot member area.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: The secret to authenticate with TestingBot.\n    title: TestingBot Secret\n  testingbot_secret: null\n"
  },
  {
    "path": "steps/testingbot-upload-app/step-info.yml",
    "content": "maintainer: community"
  },
  {
    "path": "steps/testlio-upload/0.1.0/step.yml",
    "content": "title: |-\n  Testlio Upload\nsummary: |\n  Uploads IPA to Testlio\ndescription: |\n  Uploads IPA to Testlio for validation to work around 2fa restrictions of\n  app distribution through AppStoreConnect\nwebsite: https://github.com/dmiluski/bitrise-step-testlio-upload\nsource_code_url: https://github.com/dmiluski/bitrise-step-testlio-upload\nsupport_url: https://github.com/dmiluski/bitrise-step-testlio-upload/issues\npublished_at: 2020-10-25T15:00:01.19267+01:00\nsource:\n  git: https://github.com/dmiluski/bitrise-step-testlio-upload.git\n  commit: 8af4c8f8d91f623fff8c77ffa2729412015cc296\n\nproject_type_tags:\n  - ios\n  - macos\n\ntype_tags:\n  - deploy\n  - test\n\nis_always_run: false\nis_skippable: false\n\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\ninputs:\n  - ipa_path: $BITRISE_IPA_PATH\n    opts:\n      description: |-\n        Path to your IPA file to be deployed.\n      is_required: true\n      title: IPA path\n  - testlio_api_token:\n    opts:\n      description: |\n        Authentication to the API is performed via ​JWT​.\n      is_required: true\n      is_sensitive: true\n      summary: Your Testlio API token\n      title: Testlio API Token\n\n  - testlio_collection_id:\n    opts:\n      description: |\n        Identifier of the collection\n      is_required: true\n      is_sensitive: false\n      summary: Your Testlio Collection ID\n      title: Testlio Collection ID\n\n  - testlio_app_name:\n    opts:\n      description: |\n        Application name used for submission\n      is_required: true\n      is_sensitive: false\n      summary: Your Testlio App name\n      title: Testlio App name\n"
  },
  {
    "path": "steps/testlio-upload/step-info.yml",
    "content": "maintainer: community"
  },
  {
    "path": "steps/testproject-run/0.2.0/step.yml",
    "content": "title: Run a TestProject job\nsummary: Run a TestProject job\ndescription: Run a [TestProject](https://testproject.io/) job\nwebsite: https://github.com/sca-organization/bitrise-testproject-run\nsource_code_url: https://github.com/sca-organization/bitrise-testproject-run\nsupport_url: https://github.com/sca-organization/bitrise-testproject-run/issues\npublished_at: 2022-04-07T23:20:28.86163+10:00\nsource:\n  git: https://github.com/sca-organization/bitrise-testproject-run.git\n  commit: a490981f29f3f9afa597946a74cc6910bb67faef\nproject_type_tags:\n- ios\n- android\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This can be found in the [Integrations](https://app.testproject.io/#/integrations/api) tab.\n      You can either create a new one or use an existing one.\n      To create an API Key:\n        -> API\n        -> Create API Key\n      To use an existing Key:\n        -> [API Key]\n        -> Copy\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your TestProject API key\n    title: TestProject API key\n  testproject_api_key: null\n- opts:\n    description: \"This can be found in TestProject's Project tab:\\n  -> My Projects\\n\n      \\ -> [Project] \\n  -> ... (Meatball menu)\\n  -> Copy ID\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Your TestProject project id\n    title: TestProject project id\n  testproject_project_id: null\n- opts:\n    description: \"This can be found in the Project tab:\\n   -> My Projects\\n   ->\n      [Project] \\n   -> Test & Jobs \\n   -> [Job] \\n   -> ... (Meatball menu)\\n   ->\n      Copy ID\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Your TestProject job id\n    title: TestProject job id\n  testproject_job_id: null\n"
  },
  {
    "path": "steps/testproject-run/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/testproject-upload/0.1.0/step.yml",
    "content": "title: Upload a file to TestProject\nsummary: Upload an IPA/APK file to TestProject\ndescription: Upload an IPA/APK file to TestProject\nwebsite: https://github.com/sca-organization/bitrise-testproject-upload\nsource_code_url: https://github.com/sca-organization/bitrise-testproject-upload\nsupport_url: https://github.com/sca-organization/bitrise-testproject-upload/issues\npublished_at: 2022-03-25T09:58:05.470422+11:00\nsource:\n  git: https://github.com/sca-organization/bitrise-testproject-upload.git\n  commit: 443a186e3b459909615197d8af1fd27b0f21942d\nproject_type_tags:\n- ios\n- android\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  apt_get:\n  - name: jq\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      This can be found in the Integrations tab.\n      You can either create a new one or use an existing one.\n      To create an API Key:\n        -> API\n        -> Create API Key\n      To use an existing Key:\n        -> [API Key]\n        -> Copy\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Your TestProject API key\n    title: TestProject API key\n  testproject_api_key: null\n- opts:\n    description: \"This can be found in TestProject's Project tab:\\n  -> My Projects\\n\n      \\ -> [Project] \\n  -> ... \\n  -> Copy ID\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Your TestProject project id\n    title: TestProject project id\n  testproject_project_id: null\n- opts:\n    description: \"This can be found in TestProject's Project tab:\\n  -> My Projects\n      \\n  -> [Project] \\n  -> Applications \\n  -> [Application] \\n  -> ... \\n  ->\n      Copy ID\\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Your TestProject app id\n    title: TestProject app id\n  testproject_app_id: null\n- opts:\n    description: \"This can be found in TestProject's Project tab:\\n   -> My Projects\\n\n      \\  -> [Project] \\n   -> Test & Jobs \\n   -> [Job] \\n   -> ... \\n   -> Copy ID\\n\"\n    is_expand: true\n    is_required: false\n    is_sensitive: false\n    summary: Your TestProject job id\n    title: TestProject job id\n  testproject_job_id: null\n- apk_ipa_filepath: $BITRISE_IPA_PATH\n  opts:\n    description: |\n      This usually gets generated by the the \"Gradle Runner\" or \"XCode Archive & Export\" step\n      The app file you want to upload to TestProject, usually $BITRISE\\_APK\\_PATH or $BITRISE\\_IPA\\_PATH.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Path of the IPA or APK that you want to upload.\n    title: Path of the IPA or APK\n"
  },
  {
    "path": "steps/testproject-upload/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/theappspajamas-service-account-key-installer/0.0.3/step.yml",
    "content": "title: TheAppsPajamas Service Account Key Installer\nsummary: Installs a service account key to your pipeline before build time\ndescription: |\n  Installs a service account key to your pipeline before build time\nwebsite: https://www.theappspajamas.com\nsource_code_url: https://github.com/TheAppsPajamas/bitrise-step-theappspajamas-service-account-key-installer\nsupport_url: https://www.theappspajamas.com/support\npublished_at: 2019-03-06T06:50:24.706568Z\nsource:\n  git: https://github.com/TheAppsPajamas/bitrise-step-theappspajamas-service-account-key-installer.git\n  commit: 80e22d5ceb95d51d1a1ddbf93074aaa5042a9c6a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- xamarin\ntype_tags:\n- access-control\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    is_sensitive: true\n    summary: TheAppsPajamas Service Account Key.\n    title: TheAppsPajamas Service Account Key\n  service_account_key: null\n- bitrise_source_dir: $BITRISE_SOURCE_DIR\n  opts:\n    title: Bitrise source dir\noutputs:\n- TAP_SECURITY_PATH: null\n  opts:\n    title: The path tapsecurity.json was installed at\n"
  },
  {
    "path": "steps/theappspajamas-service-account-key-installer/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/timestamp/0.9.1/step.yml",
    "content": "title: Generate timestamps\ndescription: |-\n  Generates current timestamp\nsummary: |-\n  Need some time? This step helps by giving you the current time\n  in two formats! ISO_DATETIME and even UNIX_TIMESTAMP! What more could a mere\n  mortal ask for?\nwebsite: https://github.com/bitrise-io/steps-timestamp\nsource_code_url: https://github.com/bitrise-io/steps-timestamp\nsupport_url: https://github.com/bitrise-io/steps-timestamp/issues\npublished_at: 2015-08-20T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-timestamp.git\n  commit: 97f1ac0d48e1450cb71f0dd6dc28f76e88c49c35\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\ndependencies:\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\noutputs:\n- UNIX_TIMESTAMP: null\n  opts:\n    title: unix style\n- ISO_DATETIME: null\n  opts:\n    title: iso 8601 (RFC3339Nano)\n"
  },
  {
    "path": "steps/timestamp/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/translized/1.0.2/step.yml",
    "content": "title: Translized\nsummary: |\n  Download your localization files from Translized directly from your pipeline.\ndescription: |\n  Download your localization files from Translized directly from your pipeline. Configuration file .translized.yml should exist in a root directory. More details about file and how to create it can be found here: https://docs.translized.com/docs/cli/configuration/\nwebsite: https://github.com/translized/bitrise-step-translized\nsource_code_url: https://github.com/translized/bitrise-step-translized\nsupport_url: https://github.com/translized/bitrise-step-translized/issues\npublished_at: 2024-01-31T16:34:58.622688+01:00\nsource:\n  git: https://github.com/translized/bitrise-step-translized.git\n  commit: 5fb63670a2b63e8a5bf17a613bcb9a5c375ca9c5\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\n"
  },
  {
    "path": "steps/translized/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.1/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2017-11-30T18:52:13.942591+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: afd115783cd51ce413cb1038710a0b0397b7136e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: \"\"\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.2/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2018-03-05T01:39:04.785657774+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: 425bd841945fa7c07a59d9b7555f7763d561ff4b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.3/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2018-04-19T20:19:51.021037858+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: 0953b49153e231543d1704a1ee676fd946126e16\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.4/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2018-06-26T15:31:29.110550345+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: f1499b9224bb0f2199b9a36fac12c76f589fa331\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.5/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2018-09-06T03:30:57.438119402+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: ef069eac3abc70e90147f15c90b7106d90f1703e\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.6/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2018-09-07T00:35:17.779774568+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: ce58d2452e5da7ab776923df1ad76a9e9afb7831\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.7/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2019-04-29T22:35:55.179541+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: eba20985271605baa7993ea03b359890341e17d3\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\n- branch_repo_owner: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's source repo owner login\n    title: Pull Request source repo owner\n- branch_dest_repo_owner: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's destination repo owner login\n    title: Pull Request destination repo owner\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/0.0.8/step.yml",
    "content": "title: Trigger Bitrise workflow\nsummary: |\n  Triggers a workflow on bitrise.io with specified parameters.\ndescription: |\n  The main purpose of this step is to trigger another workflow process of the same app, with the same build parameters, to achieve\n  multiple workflows that all start on the same trigger. Optionally, we would like to do this in parallel and with different necessity of checks.\n\n  For example: unit tests require a PR status check but mutation tests do not.\n  However you can also provide modified build parameters, different Bitrise app and/or choose the same workflow.\n\n  All the parameters except the workflow ID have default values equal to those in a current build. The workflow ID needs to be specified explicitly\n  to avoid accidental infinite recursive triggers of the same build.\n  You can use `$BITRISE_TRIGGERED_WORKFLOW_ID` environment variable to get current workflow ID.\n\n  See [devcenter](http://devcenter.bitrise.io/api/build-trigger/#build-params) for more information about build parameters.\n  Specifying [environment variables](http://devcenter.bitrise.io/api/build-trigger/#specify-environment-variables) is not supported by this step.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow/issues\npublished_at: 2019-11-05T19:34:01.749425+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow.git\n  commit: b8c689efd6c4e611c9feb89ba95c277778d84943\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-trigger-bitrise-workflow\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- app_slug: $BITRISE_APP_SLUG\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Bitrise App Slug. You can view your App's Slug on the `Code` tab of the\n      app.\n    title: Bitrise App Slug\n- api_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Build trigger API Token. You can view and regenerate your App's API Token\n      on the `Code` tab of the app.\n    title: Build trigger API Token\n- branch: $BITRISE_GIT_BRANCH\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The (Source) Branch to build. In the case of a standard git commit, this\n      is the branch of the commit. In case of a Pull Request build this is the source\n      branch, the one the PR was started from.\n    title: (Source) Branch to build\n- opts:\n    is_expand: true\n    is_required: false\n    title: git Tag to build\n  tag: $BITRISE_GIT_TAG\n- commit_hash: $BITRISE_GIT_COMMIT\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit hash to build\n- commit_message: $BITRISE_GIT_MESSAGE\n  opts:\n    is_expand: true\n    is_required: false\n    title: git commit message (or build's message)\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Force the use of the specified workflow ID. If empty, then the workflow\n      will be selected, based on the project's [Trigger Map](http://devcenter.bitrise.io/webhooks/trigger-map/)\n      config.\n    title: Workflow ID\n  workflow_id: null\n- branch_dest: $BITRISEIO_GIT_BRANCH_DEST\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      Used only in the case of Pull Request builds: this is the destination/target branch of the Pull Request, and the one the PR will be merged into.\n    title: Pull request destination branch\n- opts:\n    is_expand: true\n    is_required: false\n    summary: Pull Request ID on the source code hosting system (e.g. the PR number\n      on GitHub).\n    title: Pull Request ID\n  pull_request_id: $PULL_REQUEST_ID\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The repository URL from where the Pull Request is sent. E.g. if it's\n      created from a fork this should be the fork's URL.\n    title: Pull Request repository URL\n  pull_request_repository_url: $BITRISEIO_PULL_REQUEST_REPOSITORY_URL\n- opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      The pre-merge branch: if the source code hosting system supports & provides the pre-merged state of the PR on a special \"merge branch\" (ref). Probably only GitHub supports this.\n    title: Pull Request pre-merge branch\n  pull_request_merge_branch: $BITRISEIO_PULL_REQUEST_MERGE_BRANCH\n- opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's \"head branch\" (refs/), if the source code hosting\n      system supports & provides this. This special git ref should point to the source\n      of the Pull Request. Supported by GitHub and GitLab.\n    title: Pull Request head branch\n  pull_request_head_branch: $BITRISEIO_PULL_REQUEST_HEAD_BRANCH\n- exported_environment_variable_names: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: |\n      `|` separated names of environment variables to export from current environment to triggered workflow, without leading `$`.\n    title: Names of environment variables to export\n- branch_repo_owner: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's source repo owner login\n    title: Pull Request source repo owner\n- branch_dest_repo_owner: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: The Pull Request's destination repo owner login\n    title: Pull Request destination repo owner\noutputs:\n- TRIGGERED_BUILD_SLUG: null\n  opts:\n    description: Triggered build slug\n    summary: \"\"\n    title: Triggered build slug\n- TRIGGERED_BUILD_NUMBER: null\n  opts:\n    description: Triggered build number\n    summary: \"\"\n    title: Triggered build number\n- TRIGGERED_BUILD_URL: null\n  opts:\n    description: Triggered build URL\n    summary: \"\"\n    title: Triggered build URL\n- TRIGGERED_WORKFLOW_ID: null\n  opts:\n    description: Triggered workflow ID\n    summary: \"\"\n    title: Triggered workflow ID\n"
  },
  {
    "path": "steps/trigger-bitrise-workflow/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.0.1/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2019-11-08T17:07:49.648179+01:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: 3eb40e3a38118f95037883ab5015fdeb6440883d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for auth with TryoutApps\n  shaman_token: null\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman file\n  shaman_config_path: ./.shaman.yml\n- file_path: ${BITRISE_IPA_PATH}\n  opts:\n    description: |\n      By default, this value is set to BITRISE_IPA_PATH\n    is_required: true\n    title: Path to the file that have to be uploaded\n- changelog_message: ${TAG_MESSAGE}\n  opts:\n    description: |\n      By default, this message is taken from the TAG_MESSAGE.\n      If you don't use tag message or tag deploy approach, you can\n      remove this message from the deploy step.\n    is_required: false\n    title: Message used for setting the changelog\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.0.4/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2019-12-02T15:12:06.72745+01:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: 8192d50a1b282dd2239c8283d47e636df8578eec\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for auth with TryoutApps\n  shaman_token: null\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman file\n  shaman_config_path: ./.shaman.yml\n- file_path: ${BITRISE_IPA_PATH}\n  opts:\n    is_required: true\n    title: Path to the file that have to be uploaded\n- changelog_message: null\n  opts:\n    category: Config\n    description: |\n      If you are using tag based deployment, you can store changelog in \"${TAG_MESSAGE}\" global variable and then use it here.\n\n      If you don't use tag message or tag deploy approach, you can remove this message from the deploy step.\n    is_required: false\n    title: Message used for setting the changelog\n- opts:\n    category: Config\n    description: |\n      Release name used only if ZIP is uploaded to TryoutApps.\n    is_required: false\n    title: Release name (ZIP platform only)\n  release_name: null\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.0.5/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2019-12-12T13:23:25.733749+01:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: 2f1fea9e153dfbe92e3cf3c91f634eb687639b82\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for authentication with TryoutApps\n  shaman_token: null\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman.yml file\n  shaman_config_path: ./.shaman.yml\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- file_path: null\n  opts:\n    category: Config\n    description: |\n      By default, this value is read from shaman.yml file. If you need to use a custom path, you can set it here.\n    is_required: false\n    title: Path to the file that have to be uploaded\n- changelog_message: null\n  opts:\n    category: Config\n    description: \"A message that can be used as a changelog, you can store value from\n      tag/commit/script in a custom global variable (e.g. \\\"${TAG_MESSAGE}\\\") and\n      then use it here.       \\n\"\n    is_required: false\n    title: Message used for setting the change log\n- opts:\n    category: Config\n    description: |\n      Release name used only if ZIP is uploaded to TryoutApps.\n    is_required: false\n    title: Release name (ZIP platform only)\n  release_name: null\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.0.7/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2023-10-10T17:23:33.14036+02:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: ce0c22c65ec703435e3eb74e16a30f15c383b1c2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for authentication with TryoutApps\n  shaman_token: null\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman.yml file\n  shaman_config_path: ./.shaman.yml\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- file_path: null\n  opts:\n    category: Config\n    description: |\n      By default, this value is read from shaman.yml file. If you need to use a custom path, you can set it here.\n    is_required: false\n    title: Path to the file that is to be uploaded\n- changelog_message: null\n  opts:\n    category: Config\n    description: \"A message that can be used as a changelog, you can store value from\n      tag/commit/script in a custom global variable (e.g. \\\"${TAG_MESSAGE}\\\") and\n      then use it here.       \\n\"\n    is_required: false\n    title: Message used for setting the change log\n- opts:\n    category: Config\n    description: |\n      Release name used only if ZIP is uploaded to TryoutApps.\n    is_required: false\n    title: Release name (ZIP platform only)\n  release_name: null\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.0.8/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2023-10-27T10:24:51.718998+02:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: 72b557fd37a7bdc0f703600169b964038119feae\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for authentication with TryoutApps\n  shaman_token: null\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman.yml file\n  shaman_config_path: ./.shaman.yml\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- file_path: null\n  opts:\n    category: Config\n    description: |\n      By default, this value is read from shaman.yml file. If you need to use a custom path, you can set it here.\n    is_required: false\n    title: Path to the file that is to be uploaded\n- changelog_message: null\n  opts:\n    category: Config\n    description: \"A message that can be used as a changelog, you can store value from\n      tag/commit/script in a custom global variable (e.g. \\\"${TAG_MESSAGE}\\\") and\n      then use it here.       \\n\"\n    is_required: false\n    title: Message used for setting the change log\n- opts:\n    category: Config\n    description: |\n      Release name used only if ZIP is uploaded to TryoutApps.\n    is_required: false\n    title: Release name (ZIP platform only)\n  release_name: null\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.0.9/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2024-03-06T12:02:48.592734+01:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: e1f9c5a9979bdec0462914332fe045bcb4b7b954\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for authentication with TryoutApps\n  shaman_token: null\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman.yml file\n  shaman_config_path: ./.shaman.yml\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- file_path: null\n  opts:\n    category: Config\n    description: |\n      By default, this value is read from shaman.yml file. If you need to use a custom path, you can set it here.\n    is_required: false\n    title: Path to the file that is to be uploaded\n- changelog_message: null\n  opts:\n    category: Config\n    description: \"A message that can be used as a changelog, you can store value from\n      tag/commit/script in a custom global variable (e.g. \\\"${TAG_MESSAGE}\\\") and\n      then use it here.       \\n\"\n    is_required: false\n    title: Message used for setting the change log\n- opts:\n    category: Config\n    description: |\n      Release name used only if ZIP is uploaded to TryoutApps.\n    is_required: false\n    title: Release name (ZIP platform only)\n  release_name: null\n- opts:\n    category: Config\n    description: |\n      When set, a specific Ruby version will be installed on the machine. Otherwise, the default version from the machine will be used.\n    is_required: false\n    title: Ruby version\n  ruby_version: null\n"
  },
  {
    "path": "steps/tryoutapps-shaman/1.1.0/step.yml",
    "content": "title: TryoutApps Shaman\nsummary: |\n  Uploads apps to Infinum's TryoutApps\ndescription: |\n  Uploads apps to Infinum's TryoutApps using shaman deploy script.\n  Only one build at the time can be uploaded.\nwebsite: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsource_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy\nsupport_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/issues\npublished_at: 2025-02-19T15:27:44.972402+01:00\nsource:\n  git: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy.git\n  commit: 128c8da25ccf8e53874c383eb7b662411dec458f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\n- flutter\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Get your user token from https://[TENANT].tryoutapps.com/users/me\n      \\n\"\n    is_required: true\n    is_sensitive: true\n    title: Token used for authentication with TryoutApps\n  shaman_token: null\n- opts:\n    description: |\n      By default, this value is set to './.shaman.yml'\n    is_required: true\n    title: Path to the shaman.yml file\n  shaman_config_path: ./.shaman.yml\n- environment_name: null\n  opts:\n    description: |\n      Name defined in shaman.yml\n    is_required: true\n    title: Deploy environment name\n- file_path: null\n  opts:\n    category: Config\n    description: |\n      By default, this value is read from shaman.yml file. If you need to use a custom path, you can set it here.\n    is_required: false\n    title: Path to the file that is to be uploaded\n- changelog_message: null\n  opts:\n    category: Config\n    description: \"A message that can be used as a changelog, you can store value from\n      tag/commit/script in a custom global variable (e.g. \\\"${TAG_MESSAGE}\\\") and\n      then use it here.       \\n\"\n    is_required: false\n    title: Message used for setting the change log\n- opts:\n    category: Config\n    description: |\n      Release name used only if ZIP is uploaded to TryoutApps.\n    is_required: false\n    title: Release name (ZIP platform only)\n  release_name: null\n- gemfile_path: null\n  opts:\n    category: Config\n    description: |\n      When set, it specifies a local Gemfile used for installing Shaman. If not set, a default Gemfile is generated.\n    is_required: false\n    title: Path to a local Gemfile\n"
  },
  {
    "path": "steps/tryoutapps-shaman/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/tslint/0.0.4/step.yml",
    "content": "title: Run tslint command\nsummary: Runs `tslint` with the given args.\ndescription: Runs `tslint` with the given args.\nwebsite: https://github.com/ibratoev/steps-tslint\nsource_code_url: https://github.com/ibratoev/steps-tslint\nsupport_url: https://github.com/ibratoev/steps-tslint/issues\npublished_at: 2017-03-29T18:28:08.540610584+03:00\nsource:\n  git: https://github.com/ibratoev/steps-tslint.git\n  commit: 8f24c81dfb3d65b4129f1d44591eca7af13d44c0\nhost_os_tags:\n- osx\n- ubuntu\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to the `tslint` executable.\n    title: '`tslint` executable path'\n  path: tslint\n- opts:\n    description: |\n      The version of `tslint` to install if not available.\n    title: Version\n  version: latest\n- opts:\n    description: |\n      The TypeScript version to install if not available.\n    title: TypeScript version\n  typescript_version: latest\n- args: '\"**/*.ts\" -e \"**/node_modules/**\"'\n  opts:\n    description: Arguments are added to the `tslint` command.\n    title: Arguments for running `tslint`\n"
  },
  {
    "path": "steps/tslint/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/tuist/0.1.0/step.yml",
    "content": "title: Run Tuist\nsummary: |\n  Describe, maintain, and interact with Xcode projects at a large scale.\ndescription: |\n  Tuist is a CLI tool to scale up modular Xcode projects. It abstracts away the intricacies of .xcodeproj by providing a declarative API to describe the projects, and provides workflows to make developers productive.\nwebsite: https://github.com/tuist/bitrise-step-tuist\nsource_code_url: https://github.com/tuist/bitrise-step-tuist\nsupport_url: https://github.com/tuist/bitrise-step-tuist/issues\npublished_at: 2021-12-29T16:56:50.145022+01:00\nsource:\n  git: https://github.com/tuist/bitrise-step-tuist.git\n  commit: 90021dace37349f3fd64239b0dd1139ae050965f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- command: The Tuist command to execute\n  opts:\n    description: |\n      Use this input to set the command that will be executed.\n    is_expand: true\n    is_required: true\n    summary: The command to execute. For example \"generate\".\n    title: Command\n    value_options: []\n"
  },
  {
    "path": "steps/tuist/0.2.1/step.yml",
    "content": "title: tuist\nsummary: |\n  Run Tuist from Bitrise's CI environment\ndescription: |\n  Run Tuist from Bitrise's CI environment\nwebsite: https://github.com/tuist/bitrise-step-tuist\nsource_code_url: https://github.com/tuist/bitrise-step-tuist\nsupport_url: https://github.com/tuist/bitrise-step-tuist/issues\npublished_at: 2022-12-27T09:28:59.073185+01:00\nsource:\n  git: https://github.com/tuist/bitrise-step-tuist.git\n  commit: d5f672b0870dfaa7ee4cf4d5625b809262e6f6cd\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- command: The Tuist command to execute\n  opts:\n    description: |\n      Use this input to set the command that will be executed.\n    is_expand: true\n    is_required: true\n    summary: The command to execute. For example \"generate\".\n    title: Command\n    value_options: []\n"
  },
  {
    "path": "steps/tuist/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/twitter-message/0.0.4/step.yml",
    "content": "title: Send twitter message\nsummary: Update a [Twitter](https://twitter.com/) account status.\ndescription: |\n  This step is used to update a twitter account status.\n\n  For that you need to create a twitter application here : [https://apps.twitter.com](https://apps.twitter.com)\n\n  **Use the same credentials as the account you want to update !**\n\n  And get the four important information in your app : **Consumer Key (API Key)** / **Consumer Secret (API Secret)** / **Access Token** / **Access Token Secret**\n\n  Find all the error code list [here](https://developer.twitter.com/en/docs/basics/response-codes)\nwebsite: https://github.com/kawaiseb/bitrise-step-twitter-message\nsource_code_url: https://github.com/kawaiseb/bitrise-step-twitter-message\nsupport_url: https://github.com/kawaiseb/bitrise-step-twitter-message/issues\npublished_at: 2018-02-26T17:44:25.1386+01:00\nsource:\n  git: https://github.com/kawaiseb/bitrise-step-twitter-message.git\n  commit: c0dd15b45cb773be98405331ad4583963b1bc89e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Your application's Consumer Key and Secret are used to authenticate requests to the Twitter Platform.\n\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Consumer Key (API Key)\n  tw_consumer_key: null\n- opts:\n    description: |\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Consumer Secret (API Secret)\n  tw_consumer_secret: null\n- opts:\n    description: |\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Access Token Secret\n  tw_access_token_secret: null\n- opts:\n    description: |\n      This access token can be used to make API requests on your own account's behalf.\n      Do not share your access token secret with anyone.\n\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Access Token\n  tw_access_token_key: null\n- opts:\n    description: \"The screen name, handle, or alias that this user identifies themselves\n      with. \\n\\n**screen_names** are unique but subject to change. Use id_str as a\n      user identifier whenever possible. \\n\\nTypically a maximum of 15 characters\n      long, but some historical accounts may exist with longer names\\n\"\n    is_expand: true\n    is_required: true\n    summary: null\n    title: Screen name where to post\n  tw_screen_name: null\n- opts:\n    is_required: true\n    summary: null\n    title: Text to post on twitter\n  tw_status: null\n- opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode ?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  tw_debug_mode: \"no\"\n"
  },
  {
    "path": "steps/twitter-message/1.0.2/step.yml",
    "content": "title: Send twitter message\nsummary: Update a [Twitter](https://twitter.com/) account status.\ndescription: |\n  This step is used to update a twitter account status.\n\n  For that you need to create a twitter application here : [https://apps.twitter.com](https://apps.twitter.com)\n\n  **Use the same credentials as the account you want to update !**\n\n  And get the four important information in your app : **Consumer Key (API Key)** / **Consumer Secret (API Secret)** / **Access Token** / **Access Token Secret**\n\n  Find all the error code list [here](https://developer.twitter.com/en/docs/basics/response-codes)\nwebsite: https://github.com/kawaiseb/bitrise-step-twitter-message\nsource_code_url: https://github.com/kawaiseb/bitrise-step-twitter-message\nsupport_url: https://github.com/kawaiseb/bitrise-step-twitter-message/issues\npublished_at: 2018-03-27T14:23:41.566631+02:00\nsource:\n  git: https://github.com/kawaiseb/bitrise-step-twitter-message.git\n  commit: f58cf3822d0aa693126e9150bf482a382af1df94\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Your application's Consumer Key and Secret are used to authenticate requests to the Twitter Platform.\n\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Consumer Key (API Key)\n  tw_consumer_key: null\n- opts:\n    description: |\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Consumer Secret (API Secret)\n  tw_consumer_secret: null\n- opts:\n    description: |\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Access Token Secret\n  tw_access_token_secret: null\n- opts:\n    description: |\n      This access token can be used to make API requests on your own account's behalf.\n      Do not share your access token secret with anyone.\n\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Access Token\n  tw_access_token_key: null\n- opts:\n    description: \"The screen name, handle, or alias that this user identifies themselves\n      with. \\n\\n**screen_names** are unique but subject to change. Use id_str as a\n      user identifier whenever possible. \\n\\nTypically a maximum of 15 characters\n      long, but some historical accounts may exist with longer names\\n\"\n    is_expand: true\n    is_required: true\n    summary: null\n    title: Screen name where to post\n  tw_screen_name: null\n- opts:\n    is_required: true\n    summary: null\n    title: Text to post on twitter\n  tw_status: null\n- opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode ?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  tw_debug_mode: \"no\"\n"
  },
  {
    "path": "steps/twitter-message/1.0.4/step.yml",
    "content": "title: Send twitter message\nsummary: Update a [Twitter](https://twitter.com/) account status.\ndescription: |\n  This step is used to update a twitter account status.\n\n  For that you need to create a twitter application here : [https://apps.twitter.com](https://apps.twitter.com)\n\n  **Use the same credentials as the account you want to update !**\n\n  And get the four important information in your app : **Consumer Key (API Key)** / **Consumer Secret (API Secret)** / **Access Token** / **Access Token Secret**\n\n  Find all the error code list [here](https://developer.twitter.com/en/docs/basics/response-codes)\nwebsite: https://github.com/kawaiseb/bitrise-step-twitter-message\nsource_code_url: https://github.com/kawaiseb/bitrise-step-twitter-message\nsupport_url: https://github.com/kawaiseb/bitrise-step-twitter-message/issues\npublished_at: 2018-04-17T14:40:31.496937+02:00\nsource:\n  git: https://github.com/kawaiseb/bitrise-step-twitter-message.git\n  commit: b08f1c24c016e08559ce8c94b80da4553391ffe3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- notification\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Your application's Consumer Key and Secret are used to authenticate requests to the Twitter Platform.\n\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Consumer Key (API Key)\n  tw_consumer_key: null\n- opts:\n    description: |\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Consumer Secret (API Secret)\n  tw_consumer_secret: null\n- opts:\n    description: |\n      This access token can be used to make API requests on your own account's behalf.\n      Do not share your access token secret with anyone.\n\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Access Token\n  tw_access_token_key: null\n- opts:\n    description: |\n      You will find the key in your [twitter application](https://apps.twitter.com/) inside the *Keys and Access Tokens* section.\n    is_required: true\n    title: Access Token Secret\n  tw_access_token_secret: null\n- opts:\n    description: \"The screen name, handle, or alias that this user identifies themselves\n      with. \\n\\n**screen_names** are unique but subject to change. Use id_str as a\n      user identifier whenever possible. \\n\\nTypically a maximum of 15 characters\n      long, but some historical accounts may exist with longer names\\n\"\n    is_expand: true\n    is_required: true\n    summary: null\n    title: Screen name where to post\n  tw_screen_name: null\n- opts:\n    is_required: true\n    summary: null\n    title: Text to post on twitter\n  tw_status: null\n- opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode ?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  tw_debug_mode: \"no\"\n"
  },
  {
    "path": "steps/twitter-message/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/unzip/0.0.3/step.yml",
    "content": "title: Unzip\nsummary: |\n  Unzip an archive into a directory\ndescription: |\n  This step takes a zip file as input and unzips its content to a directory.\nwebsite: https://github.com/digitalrmdy/bitrise-step-unzip\nsource_code_url: https://github.com/digitalrmdy/bitrise-step-unzip\nsupport_url: https://github.com/digitalrmdy/bitrise-step-unzip/issues\npublished_at: 2019-10-30T12:44:21.044492+01:00\nsource:\n  git: https://github.com/digitalrmdy/bitrise-step-unzip.git\n  commit: b17cf58927a3993e80a370f026369f404381beaa\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- archive_path: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Path to your ZIP file.\n    title: Archive path\n- opts:\n    is_expand: true\n    is_required: true\n    summary: Path to the directory where your ZIP file should be unpacked.\n    title: Output path\n  output_path: null\n"
  },
  {
    "path": "steps/unzip/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/update-gitops-repository/0.1.2/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github Personal Access Token must be provided with access to the repository.\n  A temporary SSH key will automatically be added to the repository to push\n  changes. It will also be automatically deleted once the step terminated.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2021-01-13T12:35:20.13584+01:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: c98048d90f53baa497e1434252fc843b96987007\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github SSH URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: Input values for the Go template files as key-value pairs.\n    title: Input values for the Go template files\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: \"\"\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/0.1.3/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github Personal Access Token must be provided with access to the repository.\n  A temporary SSH key will automatically be added to the repository to push\n  changes. It will also be automatically deleted once the step terminated.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2021-01-26T17:12:09.391603891Z\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: a3166c56dcc91e7142a27a9bcb693db35345e2ad\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github SSH URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: \"\"\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.0.0/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2022-01-26T15:07:13.569872+01:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 09e44f866a338424ee3b04426d9552fa5e62ad65\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: \"\"\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.0.1/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2022-03-28T15:34:00.010742+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 2d004a5ead883609aaf48ededa9b8ad14971d894\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: \"\"\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.0/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2022-08-05T18:33:31.827511+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 46245ff2a3e7b7267f3fc63cd2104ec67e53c256\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.10/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-08-07T16:42:50.296938+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 5d04a90ad6c7a679b0176832a3b3f05415d0da3a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.11/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-08-30T14:43:41.665576+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 88bc497da9869946e6b21b44c7e2bf19ba8ffe05\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.2/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2023-03-10T16:25:39.375101+01:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 9bdaefba75322e78fa9889dbab772216be0fc028\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.3/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2023-03-31T12:55:05.760458+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: bc1e7ec9bb34f23632e1ab429bc2162a5b45de35\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.4/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2023-05-17T15:23:18.148457+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: b8bf0714aba3c37376b9d3fd5b360d1ff6d5bbb1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.5/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2023-06-09T15:14:22.818556+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: fd8ef88709a2d339f6026f217379f2d837063e8c\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.6/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2023-12-22T15:52:13.116728+01:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 83dc53d85375b31b20aa10bc51086fc5741d13c2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.7/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-01-03T13:13:20.530193+01:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 9b1dd29be6751baa799d14c42903d91e609655b9\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.8/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-03-19T11:20:33.661228+01:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 2118818ba9acd9b4d822251fb71acea84e62312e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/1.1.9/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-04-26T11:22:13.816339+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 1466be59338031f96605d6267e6f1fd16a8302e2\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/2.0.0/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-09-16T11:14:58.889457+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 25035b812e5e340d20ae174ce321baaa76efbab1\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\n- opts:\n    category: Replacer mode\n    description: \"There are situations when simple templating is not sufficient. \\nReplacer\n      mode enables matching & replacing values based on a key+delimiter combination,\\nacross\n      multiple files.\\n\"\n    title: Key-value matching mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  replacer_mode: false\n- delimiter: =\n  opts:\n    category: Replacer mode\n    description: \"Indicates the delimiter between key and value.\\nFor example in \\\"key=value\\\",\n      \\\"=\\\" is the delimiter. \\nRequired when \\\"Replacer mode\\\" is enabled.\\n\"\n    title: Delimiter\n- files: null\n  opts:\n    category: Replacer mode\n    description: |\n      List of files to scan for matching key-value pairs.\n      Required when \"Replacer mode\" is enabled.\n    title: Files\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/2.0.1/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-09-16T15:53:35.016529+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: a88c5a56a5ba24588b61769619564ad03fd3e832\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    is_required: true\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\n- opts:\n    category: Replacer mode\n    description: \"There are situations when simple templating is not sufficient. \\nReplacer\n      mode enables matching & replacing values based on a key+delimiter combination,\\nacross\n      multiple files.\\n\"\n    title: Key-value matching mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  replacer_mode: false\n- delimiter: =\n  opts:\n    category: Replacer mode\n    description: \"Indicates the delimiter between key and value.\\nFor example in \\\"key=value\\\",\n      \\\"=\\\" is the delimiter. \\nRequired when \\\"Replacer mode\\\" is enabled.\\n\"\n    title: Delimiter\n- files: null\n  opts:\n    category: Replacer mode\n    description: |\n      List of files to scan for matching key-value pairs.\n      Required when \"Replacer mode\" is enabled.\n    title: Files\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/2.0.3/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-09-18T12:00:14.992151+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: 222d8d00f9f069fa3c8155070a02478c6037c8fe\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\n- opts:\n    category: Replacer mode\n    description: \"There are situations when simple templating is not sufficient. \\nReplacer\n      mode enables matching & replacing values based on a key+delimiter combination,\\nacross\n      multiple files.\\n\"\n    title: Key-value matching mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  replacer_mode: false\n- delimiter: =\n  opts:\n    category: Replacer mode\n    description: \"Indicates the delimiter between key and value.\\nFor example in \\\"key=value\\\",\n      \\\"=\\\" is the delimiter. \\nRequired when \\\"Replacer mode\\\" is enabled.\\n\"\n    title: Delimiter\n- files: null\n  opts:\n    category: Replacer mode\n    description: |\n      List of files to scan for matching key-value pairs.\n      Required when \"Replacer mode\" is enabled.\n    title: Files\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/2.0.4/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2024-10-07T13:39:43.996566+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: d562a2f7a34d7d6dc5fad2ed146c9a536ea227f3\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\n- opts:\n    category: Replacer mode\n    description: \"There are situations when simple templating is not sufficient. \\nReplacer\n      mode enables matching & replacing values based on a key+delimiter combination,\\nacross\n      multiple files.\\n\"\n    title: Key-value matching mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  replacer_mode: false\n- delimiter: =\n  opts:\n    category: Replacer mode\n    description: \"Indicates the delimiter between key and value.\\nFor example in \\\"key=value\\\",\n      \\\"=\\\" is the delimiter. \\nRequired when \\\"Replacer mode\\\" is enabled.\\n\"\n    title: Delimiter\n- files: null\n  opts:\n    category: Replacer mode\n    description: |\n      List of files to scan for matching key-value pairs.\n      Required when \"Replacer mode\" is enabled.\n    title: Files\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/2.0.5/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2025-05-20T15:25:08.500092+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: aad03fcef73ce2cfac20ded181a18d48fb886b21\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deploy_path: \"\"\n  opts:\n    title: Path to place rendered templates inside the repository\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Templates\n    description: |-\n      Input values for the Go template files as key-value pairs in YAML format.\n\n      For example:\n\n      ```\n      my-key1: my value 1\n      my-key2: my value 2\n      ```\n    title: Input values for the Go template files in YAML format\n  values: null\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\n- opts:\n    category: Replacer mode\n    description: \"There are situations when simple templating is not sufficient. \\nReplacer\n      mode enables matching & replacing values based on a key+delimiter combination,\\nacross\n      multiple files.\\n\"\n    title: Key-value matching mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  replacer_mode: false\n- delimiter: =\n  opts:\n    category: Replacer mode\n    description: \"Indicates the delimiter between key and value.\\nFor example in \\\"key=value\\\",\n      \\\"=\\\" is the delimiter. \\nRequired when \\\"Replacer mode\\\" is enabled.\\n\"\n    title: Delimiter\n- files: null\n  opts:\n    category: Replacer mode\n    description: |\n      List of files to scan for matching key-value pairs.\n      Required when \"Replacer mode\" is enabled.\n    title: Files\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/3.0.0/step.yml",
    "content": "title: Update GitOps repository\nsummary: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\ndescription: |\n  Updates files of a GitOps repository either by pushing changes directly to a\n  given folder of a given branch or by opening a pull request to it.\n  URL of the pull request is exposed as an output in the latter case.\n  Updated files are go templates rendered by substituting given values.\n  A Github username and Personal Access Token must be provided with access to the repository.\nwebsite: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsource_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository\nsupport_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues\npublished_at: 2025-12-12T16:53:09.689839+02:00\nsource:\n  git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git\n  commit: bc3bc4b5a9422c7d46106e585a5a4b4f677a0933\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- deploy\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/bitrise-step-update-gitops-repository\ndeps:\n  brew:\n  - name: git\n  apt_get:\n  - name: git\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- deploy_repository_url: \"\"\n  opts:\n    is_required: true\n    title: Github HTTPS URL of the repository to deploy to\n- deployments: \"\"\n  opts:\n    description: |-\n      Configure one or more deployments to update in a single commit.\n      Each deployment must have a path and values. In replacer mode, files must also be specified.\n\n      For template mode:\n\n      ```yaml\n      - path: package-foo\n        values:\n          repository: example.com/repo/package-foo\n          tag: v1.0.0\n      - path: package-bar\n        values:\n          repository: example.com/repo/package-bar\n          tag: v1.0.0\n      ```\n\n      For replacer mode (include files to scan):\n\n      ```yaml\n      - path: my-service\n        files:\n          - config.yaml\n        values:\n          us.gcr.io/my-project/my-service: v1.0.0\n      ```\n    is_required: true\n    title: Deployment configurations\n- deploy_token: $DEPLOY_TOKEN\n  opts:\n    is_required: true\n    is_sensitive: true\n    title: Personal Access Token to interact with Github API\n- deploy_user: \"\"\n  opts:\n    is_required: true\n    title: Github username associated with the Personal Access Token\n- deploy_branch: master\n  opts:\n    is_required: true\n    title: Branch of the repository to deploy to\n- commit_message: bitrise ci integration\n  opts:\n    is_required: true\n    title: Commit message of pushed changes\n- opts:\n    category: Templates\n    description: |-\n      Path to the folder containing Go template files.\n      Required in template mode (when replacer_mode is false).\n    title: Path to Go templates folder\n  templates_folder_path: deployments/helm\n- opts:\n    category: Pull Request\n    description: |\n      Open a pull request instead of pushing\n      changes directly to the given branch.\n    title: Open a pull request\n    value_options:\n    - \"true\"\n    - \"false\"\n  pull_request: false\n- opts:\n    category: Pull Request\n    title: Title of the opened pull request\n  pull_request_title: \"\"\n- opts:\n    category: Pull Request\n    title: Body of the opened pull request\n  pull_request_body: 'Source commit: https://github.com/$BITRISEIO_GIT_REPOSITORY_OWNER/$BITRISEIO_GIT_REPOSITORY_SLUG/commit/$BITRISE_GIT_COMMIT'\n- opts:\n    category: Replacer mode\n    description: \"There are situations when simple templating is not sufficient. \\nReplacer\n      mode enables matching & replacing values based on a key+delimiter combination,\\nacross\n      multiple files specified in each deployment's 'files' field.\\n\"\n    is_required: true\n    title: Key-value matching mode\n    value_options:\n    - \"true\"\n    - \"false\"\n  replacer_mode: false\n- delimiter: =\n  opts:\n    category: Replacer mode\n    description: \"Indicates the delimiter between key and value.\\nFor example in \\\"key=value\\\",\n      \\\"=\\\" is the delimiter. \\nRequired when \\\"Replacer mode\\\" is enabled.\\n\"\n    title: Delimiter\noutputs:\n- PR_URL: null\n  opts:\n    description: |\n      URL of opened pull request. Will be emitted in pull request mode.\n    title: URL of opened pull request\n"
  },
  {
    "path": "steps/update-gitops-repository/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/update-jira-issue-field/1.0.0/step.yml",
    "content": "title: Update JIRA issues field\nsummary: |\n  Updates a JIRA issues field like `Fix version` or `Links`. Existing value is overwritten.\ndescription: |\n  See [What is an issue](https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html) for more information.\n  Any field available in issue edit screen can be updated.\n  Multiple issues can be specified, all of them are updated in the same way.\n  Field value may be removed by specyfying new ewmpty value.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field/issues\npublished_at: 2017-11-13T21:33:33.042785+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field.git\n  commit: 56ec218d0eae362be048a25f6c7b94bcd23bbb40\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- jira_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: JIRA user (or bot) login.\n    title: JIRA username\n- jira_password: null\n  opts:\n    description: |\n      See [API tokens documentation](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)\n      for more information about API tokens.\n    is_expand: true\n    is_required: true\n    summary: JIRA user (or bot) password or token.\n    title: JIRA user password\n- jira_instance_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL e.g. `https://example.atlassian.net`.\n    title: JIRA instance URL\n- issue_id_or_key_list: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Issues numeric ids e.g. `100000` or keys e.g. `FOO-123`, separated by\n      `|`. At least one element has to be specified. White spaces are trimmed.\n    title: List of issue ids or keys\n- field_key: null\n  opts:\n    description: |\n      Available field keys are available in metadata for editing an issue. See [Get edit issue meta](https://docs.atlassian.com/jira/REST/cloud/#api/2/issue-getEditIssueMeta)\n      documentation for more information.\n    is_expand: true\n    is_required: true\n    summary: Field in terms of API e.g. `reporter` or `customfield_11300`.\n    title: Field key\n- field_value: null\n  opts:\n    description: |\n      Existing field value if any will be overwritten by this value. May be empty.\n    is_expand: true\n    is_required: false\n    summary: New value to be written into the field. May be empty.\n    title: Field value\n"
  },
  {
    "path": "steps/update-jira-issue-field/1.0.1/step.yml",
    "content": "title: Update JIRA issues field\nsummary: |\n  Updates a JIRA [issues](https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html) field like `Fix version` or `Links`. Existing value is overwritten.\ndescription: |\n  Updates a JIRA [issues](https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html) fields like `Fix version` or `Links`.\n\n  User specified in `jira_username` input must have `Edit Issue` permission granted.\n  See [Managing project permissions](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) for more information.\n\n  Any field available on the issue edit screen can be updated. Multiple issues can be specified, all of them are updated in the same way.\n\n  Field value may be removed by specifying new empty value.\n\n  Either basic (password/token) or cookie-based authentication can be used. Thus either `jira_username` with `jira_password` or `jira_cookie` inputs must be specified.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field/issues\npublished_at: 2018-03-04T04:19:29.284686289+01:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field.git\n  commit: 0b2d11a9033661c196b7ed295ab023d23457fb7b\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- jira_username: null\n  opts:\n    is_expand: true\n    is_required: false\n    summary: JIRA user (or bot) login. Ignored if `jira_cookie` is specified.\n    title: JIRA username\n- jira_password: null\n  opts:\n    description: |\n      See [API tokens documentation](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)\n      for more information about API tokens.\n    is_expand: true\n    is_required: false\n    summary: JIRA user (or bot) password or token. Ignored if `jira_cookie` is specified.\n    title: JIRA user password\n- jira_cookie: null\n  opts:\n    description: |\n      See [Cookie-based auth for REST APIs](https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-cookie-based-authentication/)\n      for more information about cookie-based auth.\n    is_expand: true\n    is_required: false\n    summary: JIRA user (or bot) authentication cookie.\n    title: JIRA authentication cookie\n- jira_instance_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL e.g. `https://example.atlassian.net`.\n    title: JIRA instance URL\n- issue_id_or_key_list: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Issues numeric ids e.g. `100000` or keys e.g. `FOO-123`, separated by\n      `|`. At least one element has to be specified. White spaces are trimmed.\n    title: List of issue ids or keys\n- field_key: null\n  opts:\n    description: |\n      Available field keys are available in metadata for editing an issue. See [Get edit issue meta](https://docs.atlassian.com/jira/REST/cloud/#api/2/issue-getEditIssueMeta)\n      documentation for more information.\n    is_expand: true\n    is_required: true\n    summary: Field in terms of API e.g. `reporter` or `customfield_11300`.\n    title: Field key\n- field_value: null\n  opts:\n    description: |\n      Existing field value if any will be overwritten by this value. May be empty.\n    is_expand: true\n    is_required: false\n    summary: New value to be written into the field. May be empty.\n    title: Field value\n"
  },
  {
    "path": "steps/update-jira-issue-field/1.0.2/step.yml",
    "content": "title: Update JIRA issues field\nsummary: |\n  Updates a JIRA [issues](https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html) field like `Fix version` or `Links`. Existing value is overwritten.\ndescription: |\n  Updates a JIRA [issues](https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html) fields like `Fix version` or `Links`.\n\n  User specified in `jira_username` input must have `Edit Issue` permission granted.\n  See [Managing project permissions](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) for more information.\n\n  Any field available on the issue edit screen can be updated. Multiple issues can be specified, all of them are updated in the same way.\n\n  Field value may be removed by specifying new empty value.\n\n  Either basic (password/token) or cookie-based authentication can be used. Thus either `jira_username` with `jira_password` or `jira_cookie` inputs must be specified.\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field/issues\npublished_at: 2018-09-09T02:10:55.322246776+02:00\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field.git\n  commit: 95aa07f335f60b4fd22a94eb938b5e2d814ab870\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/DroidsOnRoids/bitrise-step-update-jira-issue-field\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- jira_username: null\n  opts:\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: JIRA user (or bot) login. Ignored if `jira_cookie` is specified.\n    title: JIRA username\n- jira_password: null\n  opts:\n    description: |\n      See [API tokens documentation](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)\n      for more information about API tokens.\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: JIRA user (or bot) password or token. Ignored if `jira_cookie` is specified.\n    title: JIRA user password\n- jira_cookie: null\n  opts:\n    description: |\n      See [Cookie-based auth for REST APIs](https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-cookie-based-authentication/)\n      for more information about cookie-based auth.\n    is_expand: true\n    is_required: false\n    is_sensitive: true\n    summary: JIRA user (or bot) authentication cookie.\n    title: JIRA authentication cookie\n- jira_instance_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: JIRA instance URL e.g. `https://example.atlassian.net`.\n    title: JIRA instance URL\n- issue_id_or_key_list: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Issues numeric ids e.g. `100000` or keys e.g. `FOO-123`, separated by\n      `|`. At least one element has to be specified. White spaces are trimmed.\n    title: List of issue ids or keys\n- field_key: null\n  opts:\n    description: |\n      Available field keys are available in metadata for editing an issue. See [Get edit issue meta](https://docs.atlassian.com/jira/REST/cloud/#api/2/issue-getEditIssueMeta)\n      documentation for more information.\n    is_expand: true\n    is_required: true\n    summary: Field in terms of API e.g. `reporter` or `customfield_11300`.\n    title: Field key\n- field_value: null\n  opts:\n    description: |\n      Existing field value if any will be overwritten by this value. May be empty.\n    is_expand: true\n    is_required: false\n    summary: New value to be written into the field. May be empty.\n    title: Field value\n"
  },
  {
    "path": "steps/update-jira-issue-field/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/update-jira-release-status/0.0.1/step.yml",
    "content": "title: Jira Release Status Update\nsummary: Updates the release status in Jira, marking it for release. The step includes\n  the option to set the release as a draft.\ndescription: This step automates Jira release management by updating the release status.\n  It allows seamless marking of a release for deployment, with an optional draft setting.\n  Ensure your Jira instance details, release ID, authentication token, and other necessary\n  inputs are correctly configured for smooth integration with your CI/CD workflows.\nwebsite: https://github.com/Ahmadalsofi/bitrise-step-update-jira-release\nsource_code_url: https://github.com/Ahmadalsofi/bitrise-step-update-jira-release\nsupport_url: https://github.com/Ahmadalsofi/bitrise-step-update-jira-release/issues\npublished_at: 2024-02-01T23:08:09.006209+03:00\nsource:\n  git: https://github.com/Ahmadalsofi/bitrise-step-update-jira-release-status.git\n  commit: 9a4d87219533557f02246f5b68025d81f64bfcba\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: true\nrun_if: \"\"\ninputs:\n- jira_username: \"\"\n  opts:\n    description: |\n      Your Jira username is required for authenticating Jira API requests. Ensure that you provide the correct username associated with your Jira account.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Provide your Jira username for authentication.\n    title: Jira Username\n- jira_token: \"\"\n  opts:\n    description: |\n      The API token is used to authenticate and authorize the Jira API requests. You can generate a token in your Jira account settings.\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Provide the API token for authenticating with Jira.\n    title: Jira API Token\n- jira_url: \"\"\n  opts:\n    description: |\n      The Jira URL is the base URL of your Jira instance, excluding any specific paths. Make sure to include the protocol (e.g., https://) and any necessary port information.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Provide the base URL of your Jira instance.\n    title: Jira URL\n- jira_release_id: \"\"\n  opts:\n    description: |\n      The Jira Release ID is a required input that specifies the unique identifier associated with the Jira release.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Provide the unique identifier for the Jira release.\n    title: Jira Release ID\n- opts:\n    description: |\n      Set this input to 'true' if you want to mark the Jira release as completed, or 'false' otherwise.\n    is_expand: true\n    is_required: true\n    is_sensitive: false\n    summary: Specify whether to mark the Jira release as completed.\n    title: Mark Release as Completed\n    value_options:\n    - \"true\"\n    - \"false\"\n  release_status: \"true\"\n- opts:\n    description: |\n      The Release Date is an optional input that allows you to specify the date associated with the Jira release. This field can be left empty if not applicable.\n    is_expand: true\n    is_required: false\n    is_sensitive: false\n    summary: Provide the release date for the Jira release.\n    title: Release Date (Optional)\n  release_date: \"\"\noutputs:\n- JIRA_RELEASE_UPDATE_SUCCESS: null\n  opts:\n    summary: Indicates whether the Jira release update was successful or failed.\n    title: Jira Release Update Status\n"
  },
  {
    "path": "steps/update-jira-release-status/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/update-xcode-project-provisioning/1.0.0/step.yml",
    "content": "title: Update Xcode Project Provisioning\nsummary: |\n  Updates Xcode's project file signing config to use a specific certificate and provisioning profile\ndescription: |\n  Updates Xcode's project file signing config to use a specific certificate and provisioning profile\nwebsite: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning\nsource_code_url: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning.git\nsupport_url: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning/issues\npublished_at: 2020-03-03T23:07:22.000457-05:00\nsource:\n  git: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning.git\n  commit: 89ddef54f6072bca950708ca608d77b50694618b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Your project.xcodeproj file path. (e.g. MyAwesomeProject/MyAwesomeProject.xcodeproj)\n      \\ \\nProvide `.xcodeproj` path even if using `.xcworkspace`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: Your project.xcodeproj file path.\n    title: Xcode project.xcodeproj Path\n    value_options: []\n  xcode_xcodeproj_file: null\n- opts:\n    description: |\n      The target name of your Xcode project. (e.g. MyAwesomeProject)\n    is_expand: true\n    is_required: true\n    summary: Project Target Name\n    title: Project Target\n    value_options: []\n  project_target: null\n- code_sign_style: Automatic\n  opts:\n    description: \"The **CODE__SIGN__STYLE** value will be replaced.  \\nValue either\n      `Automatic` or `Manual`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **CODE__SIGN__STYLE** value will be replaced.\n    title: Code Sign Style\n    value_options:\n    - Automatic\n    - Manual\n- development_team: null\n  opts:\n    description: \"The **configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n      \\ \\nLeft blank means `None`.\\n\"\n    is_expand: true\n    is_required: false\n    summary: The **configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n    title: Development Team\n    value_options: []\n- code_sign_identity: null\n  opts:\n    description: \"The **configurations** of **CODE__SIGN__IDENTITY** value will be\n      replaced.   \\nValue will be `iPhone Developer`, `iPhone Distribution` or others.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **configurations** of **CODE__SIGN__IDENTITY** value will be replaced.\n    title: Code Sign Identity\n    value_options: []\n- opts:\n    description: \"The **configurations** of **PROVISIONING__PROFILE__SPECIFIER** value\n      will be replaced.  \\nPlease specify the provisioning profile name which is same\n      as one created at **Certificates, Identifiers & Profiles** at **Apple Developer\n      Program**.  \\nDon't forget to upload that provisioning profile file.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **configurations** of **PROVISIONING__PROFILE__SPECIFIER** value\n      will be replaced.\n    title: Provisioning Profile Specifier\n    value_options: []\n  provisioning_profile_specifier: null\n- dry_run: \"no\"\n  opts:\n    description: |\n      If set this value `yes`, it will Dry-run this steps to preview the signing settings.\n    is_expand: true\n    is_required: true\n    summary: If set this value `yes`, it will Dry-run this steps to preview the signing\n      settings.\n    title: Dry-run preview (settings preview)\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/update-xcode-project-provisioning/1.1.0/step.yml",
    "content": "title: Update Xcode Project Provisioning\nsummary: |\n  Updates Xcode's project file signing config to use a specific certificate and provisioning profile\ndescription: |\n  Updates Xcode's project file signing config to use a specific certificate and provisioning profile\nwebsite: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning\nsource_code_url: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning.git\nsupport_url: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning/issues\npublished_at: 2020-03-27T17:25:06.338444-04:00\nsource:\n  git: https://github.com/cupojoe/bitrise-step-update-xcode-project-provisioning.git\n  commit: 32a8d7724164f230fbb1f9efca10d96da9f43ea7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- utility\n- code-sign\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: \"Your project.xcodeproj file path. (e.g. MyAwesomeProject/MyAwesomeProject.xcodeproj)\n      \\ \\nProvide `.xcodeproj` path even if using `.xcworkspace`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: Your project.xcodeproj file path.\n    title: Xcode project.xcodeproj Path\n    value_options: []\n  xcode_xcodeproj_file: null\n- opts:\n    description: |\n      The target name of your Xcode project. (e.g. MyAwesomeProject)\n    is_expand: true\n    is_required: true\n    summary: Project Target Name\n    title: Project Target\n    value_options: []\n  project_target: null\n- code_sign_style: Automatic\n  opts:\n    description: \"The **CODE__SIGN__STYLE** value will be replaced.  \\nValue either\n      `Automatic` or `Manual`.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **CODE__SIGN__STYLE** value will be replaced.\n    title: Code Sign Style\n    value_options:\n    - Automatic\n    - Manual\n- development_team: null\n  opts:\n    description: \"The **configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n      \\ \\nLeft blank means `None`.\\n\"\n    is_expand: true\n    is_required: false\n    summary: The **configurations** of **DEVELOPMENT_TEAM** value will be replaced.\n    title: Development Team\n    value_options: []\n- code_sign_identity: null\n  opts:\n    description: \"The **configurations** of **CODE__SIGN__IDENTITY** value will be\n      replaced.   \\nValue will be `iPhone Developer`, `iPhone Distribution` or others.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **configurations** of **CODE__SIGN__IDENTITY** value will be replaced.\n    title: Code Sign Identity\n    value_options: []\n- opts:\n    description: \"The **configurations** of **PROVISIONING__PROFILE__SPECIFIER** value\n      will be replaced.  \\nPlease specify the provisioning profile name which is same\n      as one created at **Certificates, Identifiers & Profiles** at **Apple Developer\n      Program**.  \\nDon't forget to upload that provisioning profile file.\\n\"\n    is_expand: true\n    is_required: true\n    summary: The **configurations** of **PROVISIONING__PROFILE__SPECIFIER** value\n      will be replaced.\n    title: Provisioning Profile Specifier\n    value_options: []\n  provisioning_profile_specifier: null\n- dry_run: \"no\"\n  opts:\n    description: |\n      If set this value `yes`, it will Dry-run this steps to preview the signing settings.\n    is_expand: true\n    is_required: true\n    summary: If set this value `yes`, it will Dry-run this steps to preview the signing\n      settings.\n    title: Dry-run preview (settings preview)\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/update-xcode-project-provisioning/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/upload-gradle-github-dependencies/0.1.0/step.yml",
    "content": "title: Upload Gradle Dependencies\nsummary: |\n  Uploads gradle dependencies to Github Dependency Graph\ndescription: |\n  This step uses the Github Dependency Graph Gradle plugin in order to generate a comprehensive dependency\n  graph for this project, and uploads it to Github using the Github Dependency Submission REST API.\nwebsite: https://github.com/esteluk/bitrise-step-upload-gradle-github-dependencies\nsource_code_url: https://github.com/esteluk/bitrise-step-upload-gradle-github-dependencies\nsupport_url: https://github.com/esteluk/bitrise-step-upload-gradle-github-dependencies/issues\npublished_at: 2024-08-13T22:28:28.760366+01:00\nsource:\n  git: https://github.com/esteluk/bitrise-step-upload-gradle-github-dependencies.git\n  commit: 22b0325f719cab801ec4abbfcd68e98fb72de845\nproject_type_tags:\n- android\ntype_tags:\n- artifact-info\ntoolkit:\n  go:\n    package_name: github.com/esteluk/bitrise-step-upload-gradle-github-dependencies\ninputs:\n- gradlew_path: $GRADLEW_PATH\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      The path should be relative to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- github_token: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Access token used to authenticate with the Github API\n    title: Github Access Token\n- included_projects: null\n  opts:\n    category: Filtering dependencies\n    is_expand: true\n    summary: A regex of projects whose dependencies should be included in the dependency\n      graph. Defaults to include all projects.\n    title: Included projects\n- excluded_projects: null\n  opts:\n    category: Filtering dependencies\n    is_expand: true\n    summary: A regex of projects whose dependencies should be excluded in the dependency\n      graph. Defaults to exclude no projects.\n    title: Excluded projects\n- included_configurations: null\n  opts:\n    category: Filtering dependencies\n    is_expand: true\n    summary: A regex of configurations whose dependencies should be included in the\n      dependency graph. Defaults to include all configurations.\n    title: Included configurations\n- excluded_configurations: null\n  opts:\n    category: Filtering dependencies\n    is_expand: true\n    summary: A regex of configurations whose dependencies should be excluded in the\n      dependency graph. Defaults to exclude no configurations.\n    title: Excluded configurations\n- opts:\n    category: Controlling dependency scope\n    description: \"Dependencies in Github's dependency graph can be identified as having\n      either a Runtime or a Development scope,\\nthis helps us to identify those dependencies\n      that are only used within eg. a project's test harness. \\n\"\n    is_expand: true\n    is_required: false\n    summary: A regex of projects whose dependencies should be given a runtime scope\n      in the dependency graph. Defaults to include all projects.\n    title: Runtime included projects\n  runtime_included_projects: null\n- opts:\n    category: Controlling dependency scope\n    is_expand: true\n    summary: A regex of projects whose dependencies that do not provide runtime scoped\n      dependencies. Defaults to exclude no projects.\n    title: Runtime excluded projects\n  runtime_excluded_projects: null\n- opts:\n    category: Controlling dependency scope\n    is_expand: true\n    summary: A regex of configurations whose dependencies should be given a runtime\n      scope in the dependency graph. Defaults to include all configurations.\n    title: Runtime included configurations\n  runtime_included_configurations: null\n- opts:\n    category: Controlling dependency scope\n    is_expand: true\n    summary: A regex of configurations whose dependencies that do not provide runtime\n      scoped dependencies. Defaults to exclude no configurations.\n    title: Runtime excluded configurations\n  runtime_excluded_configurations: null\n- github_job_correlator: $BITRISE_TRIGGERED_WORKFLOW_ID\n  opts:\n    category: Github\n    is_expand: true\n    is_required: true\n    summary: Populates the `job.correlator` property in the Submission API. Can be\n      used to associate a number of submissions together.\n    title: Github Dependency Graph Job Correlator\n- github_job_id: $BITRISE_BUILD_SLUG\n  opts:\n    category: Github\n    is_expand: true\n    is_required: true\n    summary: The ID of the job that creates this dependency graph\n    title: Github Dependency Graph Job ID\n- github_graph_ref: refs/heads/$BITRISE_GIT_BRANCH\n  opts:\n    category: Github\n    is_expand: true\n    is_required: true\n    summary: Reference to the repository branch that triggered this snapshot.\n    title: Github Dependency Graph Ref\n- github_graph_sha: $GIT_CLONE_COMMIT_HASH\n  opts:\n    category: Github\n    description: |\n      The SHA of the commit to check.\n    is_dont_change_value: true\n    is_expand: true\n    is_required: false\n    summary: The SHA of the commit to check.\n    title: Github Commit SHA-1 Hash\n- github_graph_workspace: $BITRISE_SOURCE_DIR\n  opts:\n    category: Github\n    is_expand: true\n    is_required: true\n    summary: The root directory of the repository\n    title: Github Dependency Graph Workspace\n- github_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n  opts:\n    category: Github repo\n    description: |\n      The name of the owner of the GitHub repository.\n    is_expand: true\n    is_required: false\n    summary: The name of the GitHub repository.\n    title: GitHub repository owner\n- github_repo: $BITRISEIO_GIT_REPOSITORY_SLUG\n  opts:\n    category: Github repo\n    description: |\n      The name of the GitHub repository.\n    is_expand: true\n    is_required: false\n    summary: The name of the GitHub repository.\n    title: GitHub repository\noutputs:\n- GITHUB_DEPENDENCY_GRAPH: null\n  opts:\n    summary: The dependency graph that is submitted to Github\n    title: Path to Github dependency graph\n"
  },
  {
    "path": "steps/upload-gradle-github-dependencies/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/upload-to-sauce-labs/0.0.1/step.yml",
    "content": "#\n# A couple of useful guides & docs:\n#\n# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs\n# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md\n# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md\n# - Bitrise docs: http://devcenter.bitrise.io/\n# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/\n\ntitle: |-\n  Upload to Sauce Labs\nsummary: |\n  Upload an APK/AAB/IPA/ZIP artifact to Sauce Labs.\ndescription: |\n  Upload your build file to Sauce Labs for remote device testing.\n  Requires an APK, AAB, IPA, or ZIP file within the workflow, Sauce Labs username, access key, and file name.\n  You can optionally provide a build path and request url.\n\n  Required fields are:\n  - sauce_username\n  - sauce_access_key\n  - sauce_app_name\n\n  Optional fields are:\n  - artifact_path\n  - data_center_url\nwebsite: https://github.com/camseda/bitrise-step-upload-to-sauce-labs\nsource_code_url: https://github.com/camseda/bitrise-step-upload-to-sauce-labs\nsupport_url: https://github.com/camseda/bitrise-step-upload-to-sauce-labs/issues\npublished_at: 2024-03-26T12:38:22.13670071+02:00\nsource:\n  git: https://github.com/camseda/bitrise-step-upload-to-sauce-labs.git\n  commit: 291be42de92c3c1fe0ed1823969690640d19ae37\nproject_type_tags:\n  - ios\n  - android\n\ntype_tags:\n  - deploy\n\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\n\ndeps:\n  brew:\n    - name: git\n  apt_get:\n    - name: git\n\ntoolkit:\n  bash:\n    entry_file: step.sh\n\ninputs:\n  - sauce_username: $SAUCE_USERNAME\n    opts:\n      title: Sauce Labs username\n      summary: Your Sauce Labs username\n      description: The username given to your Sauce Labs account.\n      is_required: true\n      is_sensitive: true\n  - sauce_access_key: $SAUCE_ACCESS_KEY\n    opts:\n      title: Sauce Labs Access Key\n      summary: Your Sauce Labs Access Key\n      description: The secure key used to access your Sauce Labs account.\n      is_required: true\n      is_sensitive: true\n  - sauce_app_name: $SAUCE_APP_NAME\n    opts:\n      title: Sauce Labs App Name\n      summary: Your Sauce Labs application name and extension.\n      description: |\n        This is translated to the File Name in Sauce Labs (and must include the file extension). The extension is used to automatically set the `artifact_path`.\n\n        Sauce Lab's File Name can be used to activate a specific app with the `filename` flag in your Capabilities\n        rather than using the File ID automatically generated on upload - `storage:filename=<fileName>.<ext>`.\n        A JavaScript example would be: `caps['app'] = 'storage:filename=TestApplication.apk';`\n      is_required: true\n  - artifact_path:\n    opts:\n      title: The absolute APK, AAB, IPA, or ZIP path\n      summary: Leave empty to use an automatically generated artifact_path.\n      description: |\n        Generated automatically based on the Sauce Lab application's name set in `sauce_app_name`.\n        The extension will be used to gather the `BITRISE_APK_PATH`, `BITRISE_AAB_PATH`, `BITRISE_IPA_PATH`, or `BITRISE_XCARCHIVE_ZIP_PATH`.\n\n        If you're uploading a file in a format other than .apk, .aab, .ipa, or .zip, you will need to provide a value for `artifact_path`.\n      is_required: false\n  - data_center_url:\n    opts:\n      title: Request / data center URL\n      summary: App storage URL containing the location of your data center\n      description: |\n        If using the ES East or Europe data center, provide the desired URL for the POST request.\n        This step will default to US West (https://api.us-west-1.saucelabs.com/v1/storage/upload) otherwise.\n      is_required: false"
  },
  {
    "path": "steps/upload-to-sauce-labs/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/urls-scanner/1.0.7/step.yml",
    "content": "title: Mobile apps URL scanner\nsummary: |\n  Scan source code to extract all HTTP/HTTPS URLs and execute an analysis of those URLs with SSLLabs\ndescription: |\n  Scan source code to extract all HTTP/HTTPS URLs and execute an analysis of those URLs with SSLLabs\nwebsite: https://github.com/odemolliens/bitrise-step-urls-scanner\nsource_code_url: https://github.com/odemolliens/bitrise-step-urls-scanner\nsupport_url: https://github.com/odemolliens/bitrise-step-urls-scanner/issues\npublished_at: 2021-04-07T15:38:08.541902+02:00\nsource:\n  git: https://github.com/odemolliens/bitrise-step-urls-scanner.git\n  commit: e60a617c33eaa4eb192698dd4f7f2a770b2191b5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: ssllabs-scan\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Define the list of domains like this: google.com;apple.com;flutter.com;bitrise.io (using ; as separator).\n      The list set by default can help you to remove URLs that are only used from a development perspective.\n    is_expand: true\n    is_required: false\n    summary: Analyze HTTPS URLs with SSLLabs and generate a report for each domain\n    title: Analyze HTTPS URLs with SSLLabs\n    value_options:\n    - \"yes\"\n    - \"no\"\n  ssl_labs_scan: \"no\"\n- black_list: apache.org;cloudflare.com;bintray.com;w3.org;apple-mapkit.com;apple.com;mzstatic.com;mozilla.org;github.io;github.com;youtube.com;withgoogle.com;android.com;google.com;jitpack.io;microsoft.com;firebaseio.com\n  opts:\n    description: |\n      Define the list of domains like this: google.com;apple.com;flutter.com;bitrise.io (using ; as separator).\n      The list set by default can help you to remove URLs that are only used from a development perspective.\n    is_expand: true\n    is_required: false\n    summary: List of domains that will not be analyzed by SSLLabs\n    title: HTTPS Domains blacklisted\n"
  },
  {
    "path": "steps/urls-scanner/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/veracode-security/1.0.3/step.yml",
    "content": "title: Veracode Security\nsummary: |\n  This step uploads your app to Veracode Security for app security testing.\ndescription: |\n  This setp uploads your app to Veracode Security for app security testing.\nwebsite: https://github.com/ryanphillipthomas/veracode-security\nsource_code_url: https://github.com/ryanphillipthomas/veracode-security\nsupport_url: https://github.com/ryanphillipthomas/veracode-security/issues\npublished_at: 2021-02-26T23:05:16.184332-05:00\nsource:\n  git: https://github.com/ryanphillipthomas/veracode-security.git\n  commit: cb654f5f2c4b2a1a18a5a211e1720e80b79ef359\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Your Veracode API Credentials ID\n      [https://help.veracode.com/r/c_api_credentials3](https://help.veracode.com/r/c_api_credentials3)\n    is_required: true\n    is_sensitive: true\n    title: Veracode API Credentials ID\n  veracode_api_id: null\n- opts:\n    description: |-\n      Your Veracode API Secret Key\n      [https://help.veracode.com/r/c_api_credentials3](https://help.veracode.com/r/c_api_credentials3)\n    is_required: true\n    is_sensitive: true\n    title: Veracode API Secret Key\n  veracode_api_secret: null\n- opts:\n    description: |-\n      Your Veracode Application ID\n      [https://help.veracode.com/r/r_applications_info](https://help.veracode.com/r/r_applications_info)\n    is_required: true\n    title: Veracode Application ID\n  veracode_app_id: null\n- file_upload_path: null\n  opts:\n    is_required: true\n    title: File Upload Path\n- auto_scan: \"yes\"\n  opts:\n    description: |-\n      Automatically starts a staic scan after pre-scan is complete\n      [https://help.veracode.com/r/r_applications_info](https://help.veracode.com/r/r_applications_info)\n    is_required: true\n    title: Auto Scan\n    value_options:\n    - \"no\"\n    - \"yes\"\n"
  },
  {
    "path": "steps/veracode-security/1.0.4/step.yml",
    "content": "title: Veracode Security\nsummary: |\n  This step uploads your app to Veracode Security for app security testing.\ndescription: |\n  This setp uploads your app to Veracode Security for app security testing.\nwebsite: https://github.com/ryanphillipthomas/veracode-security\nsource_code_url: https://github.com/ryanphillipthomas/veracode-security\nsupport_url: https://github.com/ryanphillipthomas/veracode-security/issues\npublished_at: 2021-05-25T08:18:15.173015-04:00\nsource:\n  git: https://github.com/ryanphillipthomas/veracode-security.git\n  commit: 1d29e240d8604312edc88f5c02ce966a25d2a975\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\n- android\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Your Veracode API Credentials ID\n      [https://help.veracode.com/r/c_api_credentials3](https://help.veracode.com/r/c_api_credentials3)\n    is_required: true\n    is_sensitive: true\n    title: Veracode API Credentials ID\n  veracode_api_id: null\n- opts:\n    description: |-\n      Your Veracode API Secret Key\n      [https://help.veracode.com/r/c_api_credentials3](https://help.veracode.com/r/c_api_credentials3)\n    is_required: true\n    is_sensitive: true\n    title: Veracode API Secret Key\n  veracode_api_secret: null\n- opts:\n    description: |-\n      Your Veracode Application ID\n      [https://help.veracode.com/r/r_applications_info](https://help.veracode.com/r/r_applications_info)\n    is_required: true\n    title: Veracode Application ID\n  veracode_app_id: null\n- file_upload_path: null\n  opts:\n    is_required: true\n    title: File Upload Path\n- auto_scan: \"true\"\n  opts:\n    description: |-\n      Automatically starts a staic scan after pre-scan is complete\n      [https://help.veracode.com/r/r_applications_info](https://help.veracode.com/r/r_applications_info)\n    is_required: true\n    title: Auto Scan\n    value_options:\n    - \"false\"\n    - \"true\"\n"
  },
  {
    "path": "steps/veracode-security/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/version-extractor-android/0.3.0/step.yml",
    "content": "title: Get versionName and versionCode on Android\nsummary: |\n  Extract the versionName and the versionCode on an Android project using a Gradle task\ndescription: |\n  Extracts the version name and the version code from the Android project. It is useful if the versionName and versionCode values are defined somewhere else. Therefore, this step uses a Gradle task to print these two values. It supports only Groovy files for now.\nwebsite: https://github.com/vladimirpetrovski/bitrise-step-version-extractor-android\nsource_code_url: https://github.com/vladimirpetrovski/bitrise-step-version-extractor-android\nsupport_url: https://github.com/vladimirpetrovski/bitrise-step-version-extractor-android/issues\npublished_at: 2020-05-13T17:58:05.089605+02:00\nsource:\n  git: https://github.com/vladimirpetrovski/bitrise-step-version-extractor-android.git\n  commit: b07f737f632568fa7a64001f4d63652c1282b21e\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_gradle_path: $BITRISE_SOURCE_DIR/app/build.gradle\n  opts:\n    is_required: true\n    summary: Path to the app's build.gradle file where the versionCode and versionName\n      are defined.\n    title: Path to the build.gradle file\n- gradlew_path: ./gradlew\n  opts:\n    category: Config\n    description: |\n      Using a Gradle Wrapper (gradlew) is required, as the wrapper ensures\n      that the right Gradle version is installed and used for the build.\n      You can find more information about the Gradle Wrapper (gradlew),\n      and about how you can generate one\n      in the official guide at: [https://docs.gradle.org/current/userguide/gradle_wrapper.html](https://docs.gradle.org/current/userguide/gradle_wrapper.html).\n      **The path should be relative** to the repository root. For example, `./gradlew`,\n      or if it is in a sub directory, `./sub/dir/gradlew`.\n    is_required: true\n    title: gradlew file path\n- opts:\n    description: |\n      Define a build variant if you need get a specific version defined in a flavor, for example: `Flavor1Debug`. If it is not defined, by default extracts the version from the `defaultConfig` section in the `build.gradle` file.\n    is_required: false\n    summary: Set a custom variant, in case you need to print the version name and\n      version code for a specific build.\n    title: Build variant\n  variant: \"\"\noutputs:\n- EXTRACTED_ANDROID_VERSION_NAME: null\n  opts:\n    summary: The extracted versionName value usually located in the app's `build.gradle`\n      file.\n    title: Extracted versionName value\n- EXTRACTED_ANDROID_VERSION_CODE: null\n  opts:\n    summary: The extracted versionCode value located in the app's `build.gradle` file.\n    title: Extracted versionCode value\n"
  },
  {
    "path": "steps/version-extractor-android/step-info.yml",
    "content": "maintainer: community\ndeprecate_notes: This step is no longer maintained by its author.\n"
  },
  {
    "path": "steps/version-pre-release-info/1.0.0/step.yml",
    "content": "title: Version pre-release info\nsummary: Generate version containing pre-release information (`v1.0.0-alpha.1`, `2.4.1.beta+2`,\n  `v2.0-rc.3`) based on git tags.\ndescription: |-\n  This step extends version provided as a parameter (`Version number`) with a pre-release identifier (`Pre-release identifier`, e.g. `alpha`, `beta`, `rc`)\n  and a pre-release number. The pre-release number is automatically incremented based on the existing git tags.\n  If there are no tags for the provided version, pre-release number is set to the initial value (`Pre-release initial value`).\n  Pre-release information is exported to the following environment variables:\n  - **APP_PRE_RELEASE_INFO** (e.g. `rc.3`)\n  - **APP_VERSION_WITH_PRE_RELEASE_INFO** (e.g. `v2.0-rc.3`)\n\n  You can use these environment variables in next steps (e.g. when creating a git tag).\nwebsite: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsource_code_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsupport_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info/issues\npublished_at: 2016-06-23T00:36:33.245617403+02:00\nsource:\n  git: https://github.com/pmkowal/bitrise-step-version-pre-release-info.git\n  commit: 36159c82db7995ce0010887ed042f6de82e994a2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- versioning\n- pre-release\n- git\n- tag\n- alpha\n- beta\n- rc\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      e.g.: `1.0.0`\n    is_required: true\n    title: Version number\n  version_number: $XPI_VERSION\n- opts:\n    description: |\n      e.g.: `alpha`, `beta`, `rc`\n    is_required: true\n    title: Pre-release identifier\n  pre_release_identifier: beta\n- opts:\n    description: |\n      If there are no tags, pre-release number is set to this value\n    is_required: true\n    title: Pre-release initial value\n  pre_release_initial_value: 1\n- opts:\n    description: |\n      e.g. [v]2.0-rc.3\n    is_required: false\n    title: Version prefix\n  pre_release_version_prefix: v\n- opts:\n    description: |\n      e.g. 2.0[-]rc.3\n    is_required: false\n    title: Pre-release identifier prefix\n  pre_release_identifier_prefix: '-'\n- opts:\n    description: |\n      e.g. 2.0-rc[.]3\n    is_required: false\n    title: Pre-release number prefix\n  pre_release_number_prefix: .\noutputs:\n- APP_VERSION_PRE_RELEASE_INFO: null\n  opts:\n    title: Pre-release info (e.g. `rc.3`)\n- APP_VERSION_WITH_PRE_RELEASE_INFO: null\n  opts:\n    title: Version number containing pre-release info (e.g. `v2.0-rc.3`)\n"
  },
  {
    "path": "steps/version-pre-release-info/1.0.1/step.yml",
    "content": "title: Version pre-release info\nsummary: Generate version containing pre-release information (`v1.0.0-alpha.1`, `2.4.1.beta+2`,\n  `v2.0-rc.3`) based on git tags.\ndescription: |-\n  This step extends version provided as a parameter (`Version number`) with a pre-release identifier (`Pre-release identifier`, e.g. `alpha`, `beta`, `rc`)\n  and a pre-release number. The pre-release number is automatically incremented based on the existing git tags.\n  If there are no tags for the provided version, pre-release number is set to the initial value (`Pre-release initial value`).\n  Pre-release information is exported to the following environment variables:\n  - **APP_PRE_RELEASE_INFO** (e.g. `rc.3`)\n  - **APP_VERSION_WITH_PRE_RELEASE_INFO** (e.g. `v2.0-rc.3`)\n\n  You can use these environment variables in next steps (e.g. when creating a git tag).\nwebsite: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsource_code_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsupport_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info/issues\npublished_at: 2016-06-23T16:52:19.896234346+02:00\nsource:\n  git: https://github.com/pmkowal/bitrise-step-version-pre-release-info.git\n  commit: 3fabb2fe0956209f167c44a20887f3358e7345f9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- versioning\n- pre-release\n- git\n- tag\n- alpha\n- beta\n- rc\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      e.g.: `1.0.0`\n    is_required: true\n    title: Version number\n  version_number: $XPI_VERSION\n- opts:\n    description: |\n      e.g.: `alpha`, `beta`, `rc`\n    is_required: true\n    title: Pre-release identifier\n  pre_release_identifier: beta\n- opts:\n    description: |\n      If there are no tags, pre-release number is set to this value\n    is_required: true\n    title: Pre-release initial value\n  pre_release_initial_value: 1\n- opts:\n    description: |\n      e.g. [v]2.0-rc.3\n    is_required: false\n    title: Version prefix\n  version_prefix: v\n- opts:\n    description: |\n      e.g. 2.0[-]rc.3\n    is_required: false\n    title: Pre-release identifier prefix\n  pre_release_identifier_prefix: '-'\n- opts:\n    description: |\n      e.g. 2.0-rc[.]3\n    is_required: false\n    title: Pre-release number prefix\n  pre_release_number_prefix: .\noutputs:\n- APP_VERSION_PRE_RELEASE_INFO: null\n  opts:\n    title: Pre-release info (e.g. `rc.3`)\n- APP_VERSION_WITH_PRE_RELEASE_INFO: null\n  opts:\n    title: Version number containing pre-release info (e.g. `v2.0-rc.3`)\n"
  },
  {
    "path": "steps/version-pre-release-info/1.0.2/step.yml",
    "content": "title: Version pre-release info\nsummary: Generate version containing pre-release information (`v1.0.0-alpha.1`, `2.4.1.beta+2`,\n  `v2.0-rc.3`) based on git tags.\ndescription: |-\n  This step extends version provided as a parameter (`Version number`) with a pre-release identifier (`Pre-release identifier`, e.g. `alpha`, `beta`, `rc`)\n  and a pre-release number. The pre-release number is automatically incremented based on the existing git tags.\n  If there are no tags for the provided version, pre-release number is set to the initial value (`Pre-release initial value`).\n  Pre-release information is exported to the following environment variables:\n  - **APP_PRE_RELEASE_INFO** (e.g. `rc.3`)\n  - **APP_VERSION_WITH_PRE_RELEASE_INFO** (e.g. `v2.0-rc.3`)\n\n  You can use these environment variables in next steps (e.g. when creating a git tag).\nwebsite: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsource_code_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info\nsupport_url: https://github.com/pmkowal/bitrise-step-version-pre-release-info/issues\npublished_at: 2016-07-05T23:55:57.96339176+02:00\nsource:\n  git: https://github.com/pmkowal/bitrise-step-version-pre-release-info.git\n  commit: 1970cb90c321f19f808dfdac82be953bc22a8eea\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      e.g.: `1.0.0`\n    is_required: true\n    title: Version number\n  version_number: $XPI_VERSION\n- opts:\n    description: |\n      e.g.: `alpha`, `beta`, `rc`\n    is_required: true\n    title: Pre-release identifier\n  pre_release_identifier: beta\n- opts:\n    description: |\n      If there are no tags, pre-release number is set to this value\n    is_required: true\n    title: Pre-release initial value\n  pre_release_initial_value: 1\n- opts:\n    description: |\n      e.g. [v]2.0-rc.3\n    is_required: false\n    title: Version prefix\n  version_prefix: v\n- opts:\n    description: |\n      e.g. 2.0[-]rc.3\n    is_required: false\n    title: Pre-release identifier prefix\n  pre_release_identifier_prefix: '-'\n- opts:\n    description: |\n      e.g. 2.0-rc[.]3\n    is_required: false\n    title: Pre-release number prefix\n  pre_release_number_prefix: .\noutputs:\n- APP_VERSION_PRE_RELEASE_INFO: null\n  opts:\n    title: Pre-release info (e.g. `rc.3`)\n- APP_VERSION_WITH_PRE_RELEASE_INFO: null\n  opts:\n    title: Version number containing pre-release info (e.g. `v2.0-rc.3`)\n"
  },
  {
    "path": "steps/version-pre-release-info/step-info.yml",
    "content": "maintainer: community\nremoval_date: 2025-09-31\ndeprecate_notes: This step is a duplicate of \"bitrise-step-version-pre-release-info\". Please use that step ID instead.\n"
  },
  {
    "path": "steps/versionbox-deploy/0.0.2/step.yml",
    "content": "title: VersionBox Application Deployment\nsummary: |\n  Deploy your builded application as a new version to VersionBox.io store!\ndescription: \"VersionBox is an inHouse application store for enterprises. (https://versionbox.io)\\nYou\n  can manage, distribute and analyze your iOS or Android app from VersionBox web panel.\\n\\nUse\n  this step to entegrate your VersionBox deployment with Bitrise.\\nIt will automatically\n  deploy your generated IPA or APK file to VersionBox on build. \\n\\nAll you need is\n  an app key, and an api token from VersionBox!\"\nwebsite: https://github.com/loopdigital/bitrise-step-versionbox-deploy\nsource_code_url: https://github.com/loopdigital/bitrise-step-versionbox-deploy\nsupport_url: https://github.com/loopdigital/bitrise-step-versionbox-deploy/issues\npublished_at: 2018-08-08T14:33:58.167514067+03:00\nsource:\n  git: https://github.com/loopdigital/bitrise-step-versionbox-deploy.git\n  commit: e40cdcfdcca25ba6fd87c2a0a4b49eea54abf99f\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: VersionBox Application Key\n  vb_app_key: null\n- opts:\n    is_expand: true\n    is_required: true\n    title: VersionBox User API Token\n  vb_api_token: null\n- opts:\n    description: Absolute path of the IPA or APK file generated on build.\n    is_expand: true\n    is_required: true\n    title: File Path\n  vb_file_path: null\n- opts:\n    is_expand: true\n    title: Version description text to display on VersionBox.\n  vb_version_description: null\n"
  },
  {
    "path": "steps/versionbox-deploy/0.0.3/step.yml",
    "content": "title: VersionBox Application Deployment\nsummary: |\n  Deploy your builded application as a new version to VersionBox.io store!\ndescription: \"VersionBox is an inHouse application store for enterprises. (https://versionbox.io)\\nYou\n  can manage, distribute and analyze your iOS or Android app from VersionBox web panel.\\n\\nUse\n  this step to integrate your VersionBox deployment with Bitrise.\\nIt will automatically\n  deploy your generated IPA or APK file to VersionBox on build. \\n\\nAll you need is\n  an APP KEY and an API TOKEN from VersionBox!\\n\"\nwebsite: https://github.com/loopdigital/bitrise-step-versionbox-deploy\nsource_code_url: https://github.com/loopdigital/bitrise-step-versionbox-deploy\nsupport_url: https://github.com/loopdigital/bitrise-step-versionbox-deploy/issues\npublished_at: 2018-08-10T15:21:54.609158093+03:00\nsource:\n  git: https://github.com/loopdigital/bitrise-step-versionbox-deploy.git\n  commit: 783048d252aeba231fca1a491c35735ccd9e5682\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- deploy\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: VersionBox Application Key\n  vb_app_key: null\n- opts:\n    is_expand: true\n    is_required: true\n    title: VersionBox User API Token\n  vb_api_token: null\n- opts:\n    description: Absolute path of the IPA or APK file generated on build.\n    is_expand: true\n    is_required: true\n    title: File Path\n  vb_file_path: null\n- opts:\n    category: Additional\n    description: Mark the version as live after deployment.\n    is_expand: true\n    is_required: false\n    title: Mark as Live\n    value_options:\n    - \"yes\"\n    - \"no\"\n  vb_mark_live: \"no\"\n- opts:\n    category: Additional\n    description: Publish the version when deployment complete.\n    is_expand: true\n    is_required: false\n    title: Publish the Version\n    value_options:\n    - \"no\"\n    - \"yes\"\n  vb_auto_publish: \"no\"\n- opts:\n    category: Description\n    description: Version description text to display on VersionBox.\n    is_expand: true\n    is_required: false\n    title: Version Description\n  vb_version_description: null\n- opts:\n    category: Description\n    description: Your version description will be automatically generated from commits\n      between last two git tags. (Generated description will overwrite the Version\n      Description field above.)\n    is_expand: true\n    is_required: false\n    title: Copy Description From Tag Commits\n    value_options:\n    - \"yes\"\n    - \"no\"\n  vb_description_from_commit: \"no\"\n- opts:\n    category: Description\n    description: Absolute path of the currently cloned repository on VM. (Only necessary\n      if Description From Commits is desired.)\n    is_expand: true\n    is_required: false\n    title: Cloned Repository Path\n  vb_cloned_repository_path: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/versionbox-deploy/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/0.9.4/step.yml",
    "content": "title: '[PRIVATE-BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-08-29T14:56:04.7709296+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: bc244460a363d8734c6f65a83a4d6fb6f9ec90ab\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: instrumentation\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: null\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    title: Environment Variables\n- download_test_results: false\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - false\n    - true\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/0.9.5/step.yml",
    "content": "title: '[PRIVATE-BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-08-29T16:10:38.209158028+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 29c5e563013b653d9ad8d936f0680437c1ed89f7\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: instrumentation\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: null\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    title: Environment Variables\n- download_test_results: false\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - false\n    - true\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/0.9.6/step.yml",
    "content": "title: '[PRIVATE-BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-09-25T19:16:38.093885924+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 2238a2c48a54b3451b12d904ba76a5e323966ddb\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: null\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    title: Environment Variables\n- download_test_results: false\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - false\n    - true\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/0.9.7/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-09-27T12:17:52.892226331+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: d832dfff68d364078428575ab41d40bce40cf2e3\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: null\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    title: Environment Variables\n- download_test_results: false\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - false\n    - true\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/0.9.8/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-10-20T15:56:53.114282287+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 188d8a221e16f55197fdf05ec9012980c3e6cf46\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: false\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - false\n    - true\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    title: Environment Variables\n- download_test_results: false\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - false\n    - true\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/0.9.9/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-12-12T16:41:50.998745602+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 551db279e4a14199c5ec88d8b8fbffb8ad825d02\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so wou won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: false\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - false\n    - true\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=\"/sdcard/tempDir/coverage.ec\"\n      ```\n    title: Environment Variables\n- download_test_results: false\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - false\n    - true\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.0.0/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2017-12-21T13:36:39.523074691+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 57195b997579e76e46ff2eefbc5fe7bcad403498\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      Test targets\n    summary: Test targets\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.0.1/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2018-02-02T13:44:27.021494233+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: c6403584716a574ba8492ec12835b5527870d20c\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,text\n      password_resource,password,text\n      loginbtn_resource,,click\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    is_required: true\n    summary: |\n      Test result files like video or test cases results won't be downloaded. Use this input if you have set `directories_to_pull` input and you have files generated in the test.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.0.2/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2018-04-26T14:49:29.335395854+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: dd5d0fdf32eed2d8dbcf3b5b2adc87733749ef0d\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: $ADDON_VDTESTING_API_URL\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.0.3/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2018-08-31T12:06:26.142508457Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 1fcfced408a10f50fdfd7574e5ce35eb38c8afdb\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬──────────┬────────────────────┬─────────────┬────────────────┬\n      │   MODEL_ID  │   MAKE   │     MODEL_NAME     │  RESOLUTION │ OS_VERSION_IDS │\n      ├─────────────┼──────────┼────────────────────┼─────────────┼────────────────┼\n      │ Nexus4      │ LG       │ Nexus 4            │ 1280 x 768  │ 19,21,22       │\n      │ Nexus10     │ Samsung  │ Nexus 10           │ 2560 x 1600 │ 19,21,22       │\n      │ Nexus5      │ LG       │ Nexus 5            │ 1920 x 1080 │ 19,21,22,23    │\n      │ Nexus5X     │ LG       │ Nexus 5X           │ 1920 x 1080 │ 23,24,25,26    │\n      │ Nexus6      │ Motorola │ Nexus 6            │ 2560 x 1440 │ 21,22,23,24,25 │\n      │ Nexus6P     │ Google   │ Nexus 6P           │ 2560 x 1440 │ 23,24,25,26    │\n      │ Nexus7      │ ASUS     │ Nexus 7 (2012)     │ 1280 x 800  │ 19,21,22       │\n      │ Nexus9      │ HTC      │ Nexus 9            │ 2048 x 1536 │ 21,22,23,24,25 │\n      │ NexusLowRes │ Generic  │ Low-res MDPI phone │  640 x 360  │ 23,24,25,26    │\n      └─────────────┴──────────┴────────────────────┴─────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.0.5/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2018-11-16T14:15:41.276185059Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: db754cee62484b1d76f099f1ca5ae977a7646e55\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬───────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS  │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼───────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22          │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22          │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23       │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26       │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25    │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27    │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22          │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26       │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25    │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴───────────────────┴──────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬───────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS  │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼───────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22          │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22          │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23       │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26       │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25    │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27    │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22          │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26       │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25    │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴───────────────────┴──────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.0.6/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2019-08-08T07:23:55.139363217Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: d117c3e4a3b9f1ff194aa7b1ed5e18328d24519b\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io.addons.required:\n  - addon_id:\"addons-firebase-testlab\": null\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: true\n    summary: |\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬───────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS  │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼───────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22          │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22          │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23       │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26       │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25    │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27    │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22          │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26       │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25    │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴───────────────────┴──────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬───────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS  │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼───────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22          │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22          │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23       │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26       │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25    │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27    │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22          │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26       │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25    │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴───────────────────┴──────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- app_package_id: null\n  opts:\n    description: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    summary: |\n      The Java package of the application under test (leave empty to get it extracted from the APK manifest).\n    title: App package ID\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_package_id: null\n  opts:\n    category: Instrumentation Test\n    description: The Java package name of the instrumentation test (leave empty to\n      get it extracted from the APK manifest).\n    summary: The Java package name of the instrumentation test (leave empty to get\n      it extracted from the APK manifest).\n    title: Test package ID\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- environment_variables: null\n  opts:\n    category: Debug\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.1/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2019-09-05T11:46:20.311221394Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: e4a6b0556535b3dcbf3f2883790ec658c0e9f1fb\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test. By default `android-build` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n\n      Can specify an apk (`$BITRISE_APK_PATH`) or aab bundle as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app (apk or aab) to test.\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬───────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS  │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼───────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22          │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22          │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23       │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26       │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25    │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27    │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22          │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26       │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25    │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴───────────────────┴──────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬───────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS  │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼───────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22          │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22          │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23       │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26       │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25    │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27    │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22          │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26       │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25    │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴───────────────────┴──────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n\n      Files should be seperated by newline.\n      For example:\n\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.10/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step collects the built\n  APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests,\n  the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to\n  run UI tests on them.\\n\\nThe available test types are instrumentation, robo, gameloop.\n  \\n\\n### Configuring the Step \\n\\nYou can read [our detailed guide about using the\n  Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with\n  other Bitrise Steps. Here we'll go over the configuration options of the Step. \\n\\n1.\n  Make sure the **App path** input points to the path of the APK or AAB file of your\n  app. If you use our **Android Build** or **Android Build for UI Testing** Steps,\n  you don't need to change the default value. \\n1. Add the devices you want the tests\n  to run on in the **Test devices** input. \\n\\n   You need to set the device ID, the\n  version, the orientation, and the language. Read the input description for more\n  information and available devices.\\n1. Choose a test type. \\n   \\n   The available\n  options are:\\n   - instrumentation\\n   - robo\\n   - gameloop\\n\\nFor detailed configuration\n  options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n  \\n\\nYou can also export the results of the Step to the Test reports add-on. All\n  you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\\n\\n###\n  Troubleshooting\\n\\nIf you get the **Build already exists** error, it is because\n  you have more than one instance of the Step in your Workflow. This doesn't work\n  as Bitrise sends the build slug to Firebase and having the Step more than once in\n  the same Workflow results in sending the same build slug multiple times. \\n\\n\\n###\n  Useful links\\n\\n- [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\\n-\n  [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\\n\\n###\n  Related Steps \\n\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2024-05-31T07:46:45.904909856Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: f6fabdd35a2e6e2736c462ff31c48fff59f01d13\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\\n│\n      AmatiTvEmulator     │ Google   │ Google TV Amati                          │\n      VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\\n│ AndroidTablet270dpi\n      │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720\n      \\ │ 30                      │                  │\\n│ GoogleTvEmulator    │ Google\n      \\  │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │\n      beta=30          │\\n│ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │\n      VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ MediumTablet.arm\n      \\   │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x\n      1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ Nexus10             │\n      Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600\n      │ 19,21,22                │ deprecated=19    │\\n│ Nexus4              │ LG       │\n      Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus5              │ LG       │ Nexus\n      5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │\n      deprecated=19    │\\n│ Nexus5X             │ LG       │ Nexus 5X                                 │\n      VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\\n│ Nexus6\n      \\             │ Motorola │ Nexus 6                                  │ VIRTUAL\n      │ 2560 x 1440 │ 21,22,23,24,25          │                  │\\n│ Nexus6P             │\n      Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440\n      │ 23,24,25,26,27          │                  │\\n│ Nexus7              │ Asus\n      \\    │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus7_clone_16_9   │ Generic  │ Nexus7\n      clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │\n      beta             │\\n│ Nexus9              │ HTC      │ Nexus 9                                  │\n      VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\\n│ NexusLowRes\n      \\        │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640\n      x 360  │ 23,24,25,26,27,28,29,30 │                  │\\n│ Pixel2              │\n      Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080\n      │ 26,27,28,29,30          │                  │\\n│ Pixel2.arm          │ Google\n      \\  │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33\n      \\   │ preview=33, beta │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                      │                  │\\n│ SmallPhone.arm\n      \\     │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280\n      x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      \\    \\n```\\n\"\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\n      │       MODEL_ID      │   MAKE   │                MODEL_NAME                │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\n      ├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\n      │ AmatiTvEmulator     │ Google   │ Google TV Amati                          │ VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\n      │ AndroidTablet270dpi │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720  │ 30                      │                  │\n      │ GoogleTvEmulator    │ Google   │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │ beta=30          │\n      │ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ MediumTablet.arm    │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Nexus10             │ Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │ deprecated=19    │\n      │ Nexus4              │ LG       │ Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22                │ deprecated=19    │\n      │ Nexus5              │ LG       │ Nexus 5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │ deprecated=19    │\n      │ Nexus5X             │ LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\n      │ Nexus6              │ Motorola │ Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │                  │\n      │ Nexus6P             │ Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │                  │\n      │ Nexus7              │ Asus     │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22                │ deprecated=19    │\n      │ Nexus7_clone_16_9   │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta             │\n      │ Nexus9              │ HTC      │ Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\n      │ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │                  │\n      │ Pixel2              │ Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │                  │\n      │ Pixel2.arm          │ Google   │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Pixel3              │ Google   │ Pixel 3                                  │ VIRTUAL │ 2160 x 1080 │ 30                      │                  │\n      │ SmallPhone.arm      │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      └─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.11/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step collects the built\n  APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests,\n  the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to\n  run UI tests on them.\\n\\nThe available test types are instrumentation, robo, gameloop.\n  \\n\\n### Configuring the Step \\n\\nYou can read [our detailed guide about using the\n  Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with\n  other Bitrise Steps. Here we'll go over the configuration options of the Step. \\n\\n1.\n  Make sure the **App path** input points to the path of the APK or AAB file of your\n  app. If you use our **Android Build** or **Android Build for UI Testing** Steps,\n  you don't need to change the default value. \\n1. Add the devices you want the tests\n  to run on in the **Test devices** input. \\n\\n   You need to set the device ID, the\n  version, the orientation, and the language. Read the input description for more\n  information and available devices.\\n1. Choose a test type. \\n   \\n   The available\n  options are:\\n   - instrumentation\\n   - robo\\n   - gameloop\\n\\nFor detailed configuration\n  options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n  \\n\\nYou can also export the results of the Step to the Test reports add-on. All\n  you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\\n\\n###\n  Troubleshooting\\n\\nIf you get the **Build already exists** error, it is because\n  you have more than one instance of the Step in your Workflow. This doesn't work\n  as Bitrise sends the build slug to Firebase and having the Step more than once in\n  the same Workflow results in sending the same build slug multiple times. \\n\\n\\n###\n  Useful links\\n\\n- [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\\n-\n  [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\\n\\n###\n  Related Steps \\n\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2024-06-04T08:48:35.811961878Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 4fdef165bbcdbd89095b87b56a38b680dc8278e5\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\\n│\n      AmatiTvEmulator     │ Google   │ Google TV Amati                          │\n      VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\\n│ AndroidTablet270dpi\n      │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720\n      \\ │ 30                      │                  │\\n│ GoogleTvEmulator    │ Google\n      \\  │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │\n      beta=30          │\\n│ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │\n      VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ MediumTablet.arm\n      \\   │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x\n      1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ Nexus10             │\n      Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600\n      │ 19,21,22                │ deprecated=19    │\\n│ Nexus4              │ LG       │\n      Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus5              │ LG       │ Nexus\n      5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │\n      deprecated=19    │\\n│ Nexus5X             │ LG       │ Nexus 5X                                 │\n      VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\\n│ Nexus6\n      \\             │ Motorola │ Nexus 6                                  │ VIRTUAL\n      │ 2560 x 1440 │ 21,22,23,24,25          │                  │\\n│ Nexus6P             │\n      Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440\n      │ 23,24,25,26,27          │                  │\\n│ Nexus7              │ Asus\n      \\    │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus7_clone_16_9   │ Generic  │ Nexus7\n      clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │\n      beta             │\\n│ Nexus9              │ HTC      │ Nexus 9                                  │\n      VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\\n│ NexusLowRes\n      \\        │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640\n      x 360  │ 23,24,25,26,27,28,29,30 │                  │\\n│ Pixel2              │\n      Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080\n      │ 26,27,28,29,30          │                  │\\n│ Pixel2.arm          │ Google\n      \\  │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33\n      \\   │ preview=33, beta │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                      │                  │\\n│ SmallPhone.arm\n      \\     │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280\n      x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      \\    \\n```\\n\"\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\n      │       MODEL_ID      │   MAKE   │                MODEL_NAME                │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\n      ├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\n      │ AmatiTvEmulator     │ Google   │ Google TV Amati                          │ VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\n      │ AndroidTablet270dpi │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720  │ 30                      │                  │\n      │ GoogleTvEmulator    │ Google   │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │ beta=30          │\n      │ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ MediumTablet.arm    │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Nexus10             │ Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │ deprecated=19    │\n      │ Nexus4              │ LG       │ Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22                │ deprecated=19    │\n      │ Nexus5              │ LG       │ Nexus 5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │ deprecated=19    │\n      │ Nexus5X             │ LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\n      │ Nexus6              │ Motorola │ Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │                  │\n      │ Nexus6P             │ Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │                  │\n      │ Nexus7              │ Asus     │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22                │ deprecated=19    │\n      │ Nexus7_clone_16_9   │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta             │\n      │ Nexus9              │ HTC      │ Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\n      │ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │                  │\n      │ Pixel2              │ Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │                  │\n      │ Pixel2.arm          │ Google   │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Pixel3              │ Google   │ Pixel 3                                  │ VIRTUAL │ 2160 x 1080 │ 30                      │                  │\n      │ SmallPhone.arm      │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      └─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.12/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step collects the built\n  APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests,\n  the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to\n  run UI tests on them.\\n\\nThe available test types are instrumentation, robo, gameloop.\n  \\n\\n### Configuring the Step \\n\\nYou can read [our detailed guide about using the\n  Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with\n  other Bitrise Steps. Here we'll go over the configuration options of the Step. \\n\\n1.\n  Make sure the **App path** input points to the path of the APK or AAB file of your\n  app. If you use our **Android Build** or **Android Build for UI Testing** Steps,\n  you don't need to change the default value. \\n1. Add the devices you want the tests\n  to run on in the **Test devices** input. \\n\\n   You need to set the device ID, the\n  version, the orientation, and the language. Read the input description for more\n  information and available devices.\\n1. Choose a test type. \\n   \\n   The available\n  options are:\\n   - instrumentation\\n   - robo\\n   - gameloop\\n\\nFor detailed configuration\n  options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n  \\n\\nYou can also export the results of the Step to the Test reports add-on. All\n  you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\\n\\n###\n  Troubleshooting\\n\\nIf you get the **Build already exists** error, it is because\n  you have more than one instance of the Step in your Workflow. This doesn't work\n  as Bitrise sends the build slug to Firebase and having the Step more than once in\n  the same Workflow results in sending the same build slug multiple times. \\n\\n\\n###\n  Useful links\\n\\n- [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\\n-\n  [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\\n\\n###\n  Related Steps \\n\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2024-07-24T10:13:07.894448096Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 6e407ab299beaac436099cfd7b267ac787c76c17\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬────────────────────────────┬─────────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │       OS_VERSION_IDS       │   TAGS  │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼────────────────────────────┼─────────┤\\n│\n      AmatiTvEmulator     │ Google   │ Google TV Amati                          │\n      VIRTUAL │ 1080 x 1920 │ 29                         │ beta=29 │\\n│ AndroidTablet270dpi\n      │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720\n      \\ │ 30                         │         │\\n│ GoogleTvEmulator    │ Google   │\n      Google TV                                │ VIRTUAL │  720 x 1280 │ 30                         │\n      beta=30 │\\n│ MediumPhone.arm     │ Generic  │ Medium Phone, 6.4in/16cm (Arm)\n      \\          │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,34 │         │\\n│\n      MediumTablet.arm    │ Generic  │ Medium Tablet, 10in/25cm (Arm)           │\n      VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34 │         │\\n│ Nexus5X             │\n      LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080\n      │ 24,25,26                   │         │\\n│ Nexus6              │ Motorola │\n      Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 24,25                      │\n      \\        │\\n│ Nexus6P             │ Google   │ Nexus 6P                                 │\n      VIRTUAL │ 2560 x 1440 │ 24,25,26,27                │         │\\n│ Nexus7_clone_16_9\n      \\  │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x\n      720  │ 24,25,26                   │ beta    │\\n│ Nexus9              │ HTC      │\n      Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 24,25                      │\n      \\        │\\n│ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │\n      VIRTUAL │  640 x 360  │ 24,25,26,27,28,29,30       │         │\\n│ Pixel2              │\n      Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080\n      │ 26,27,28,29,30             │         │\\n│ Pixel2.arm          │ Google   │\n      Pixel 2 (Arm)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33\n      \\   │         │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                         │         │\\n│ SmallPhone.arm\n      \\     │ Generic  │ Small Phone, 4.7in/12cm (Arm)            │ VIRTUAL │ 1280\n      x 720  │ 26,27,28,29,30,31,32,33,34 │         │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴────────────────────────────┴─────────┘\n      \\   \\n```\\n\"\n    is_required: true\n    summary: \"Format:\\nOne device configuration per line and the parameters are separated\n      with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬────────────────────────────┬─────────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │       OS_VERSION_IDS       │   TAGS  │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼────────────────────────────┼─────────┤\\n│\n      AmatiTvEmulator     │ Google   │ Google TV Amati                          │\n      VIRTUAL │ 1080 x 1920 │ 29                         │ beta=29 │\\n│ AndroidTablet270dpi\n      │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720\n      \\ │ 30                         │         │\\n│ GoogleTvEmulator    │ Google   │\n      Google TV                                │ VIRTUAL │  720 x 1280 │ 30                         │\n      beta=30 │\\n│ MediumPhone.arm     │ Generic  │ Medium Phone, 6.4in/16cm (Arm)\n      \\          │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,34 │         │\\n│\n      MediumTablet.arm    │ Generic  │ Medium Tablet, 10in/25cm (Arm)           │\n      VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34 │         │\\n│ Nexus5X             │\n      LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080\n      │ 24,25,26                   │         │\\n│ Nexus6              │ Motorola │\n      Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 24,25                      │\n      \\        │\\n│ Nexus6P             │ Google   │ Nexus 6P                                 │\n      VIRTUAL │ 2560 x 1440 │ 24,25,26,27                │         │\\n│ Nexus7_clone_16_9\n      \\  │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x\n      720  │ 24,25,26                   │ beta    │\\n│ Nexus9              │ HTC      │\n      Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 24,25                      │\n      \\        │\\n│ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │\n      VIRTUAL │  640 x 360  │ 24,25,26,27,28,29,30       │         │\\n│ Pixel2              │\n      Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080\n      │ 26,27,28,29,30             │         │\\n│ Pixel2.arm          │ Google   │\n      Pixel 2 (Arm)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33\n      \\   │         │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                         │         │\\n│ SmallPhone.arm\n      \\     │ Generic  │ Small Phone, 4.7in/12cm (Arm)            │ VIRTUAL │ 1280\n      x 720  │ 26,27,28,29,30,31,32,33,34 │         │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴────────────────────────────┴─────────┘\n      \\  \\n```\\n\"\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.13/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2025-06-04T12:54:11.886078733Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 31cd491b33e1d55ef5d84f5c8b5c16af3c80c123\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬───────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │         OS_VERSION_IDS        │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼───────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                            │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                            │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                            │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,34,35 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35 │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33       │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35 │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴───────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬───────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │         OS_VERSION_IDS        │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼───────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                            │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                            │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                            │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,34,35 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35 │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33       │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35 │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴───────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- num_flaky_test_attempts: \"0\"\n  opts:\n    category: Debug\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.2/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2020-02-27T11:56:44.431161827Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 02a4aaf447177ea130e0a1b335361d4d0d29c6d5\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test. By default `android-build` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n\n      Can specify an apk (`$BITRISE_APK_PATH`) or aab bundle as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app (apk or aab) to test.\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬──────────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS     │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼──────────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22             │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22             │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23          │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26          │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25       │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27       │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22             │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26          │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25       │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28,29 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28,29          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴──────────────────────┴──────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬──────────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │   OS_VERSION_IDS     │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼──────────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22             │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22             │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23          │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26          │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25       │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27       │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22             │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26          │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25       │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28,29 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28,29          │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴──────────────────────┴──────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n\n      Files should be seperated by newline.\n      For example:\n\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.3/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. Available test types are instrumentation, robo, gameloop.\n  The minimal setup of this step would be to select test type. If you selected instrumentation, don't forget to set __Test APK path__\n  under the __Instrumentation Test__ group as well.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2021-03-26T11:56:58.73494095Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 17560aad2e4b672e523e11ab1097782ac4c3d182\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test. By default `android-build` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n\n      Can specify an apk (`$BITRISE_APK_PATH`) or aab bundle as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app (apk or aab) to test.\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬─────────────────────────┬─────────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │      OS_VERSION_IDS     │   TAGS  │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼─────────────────────────┼─────────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22                │         │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22                │         │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23             │         │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26             │         │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25          │         │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27          │         │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22                │         │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26             │ beta    │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25          │         │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28,29,30 │ beta=30 │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28,29,30          │ beta=30 │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴─────────────────────────┴─────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────────┬─────────────────────────┬─────────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │  RESOLUTION │      OS_VERSION_IDS     │   TAGS  │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────────┼─────────────────────────┼─────────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ 2560 x 1600 │ 19,21,22                │         │\n      │ Nexus4            │ LG       │ Nexus 4                             │ 1280 x 768  │ 19,21,22                │         │\n      │ Nexus5            │ LG       │ Nexus 5                             │ 1920 x 1080 │ 19,21,22,23             │         │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ 1920 x 1080 │ 23,24,25,26             │         │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ 2560 x 1440 │ 21,22,23,24,25          │         │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ 2560 x 1440 │ 23,24,25,26,27          │         │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ 1280 x 800  │ 19,21,22                │         │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ 1280 x 720  │ 23,24,25,26             │ beta    │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ 2048 x 1536 │ 21,22,23,24,25          │         │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │  640 x 360  │ 23,24,25,26,27,28,29,30 │ beta=30 │\n      │ Pixel2            │ Google   │ Pixel 2                             │ 1920 x 1080 │ 26,27,28,29,30          │ beta=30 │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────────┴─────────────────────────┴─────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n\n      Files should be seperated by newline.\n      For example:\n\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.4/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step doesn't build anything,\n  it collects the built APK from `$BITRISE_APK_PATH` (and in case of instrumentation\n  tests, the test APK from `$BITRISE_TEST_APK_PATH`).\\n\\nAvailable test types are\n  instrumentation, robo, gameloop. The minimal setup of this Step would be to select\n  a test type. If you selected instrumentation, don't forget to set the __Test APK\n  path__\\nunder the __Instrumentation Test__ group as well. To create the two required\n  APKs, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n  Step (before this Step).  \"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2021-05-04T14:19:10.858363812Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 07be2c76f44edc29e8b2caafa55f58c2b060d651\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬─────────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │   TAGS  │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼─────────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │         │\n      │ Nexus4            │ LG       │ Nexus 4                             │ VIRTUAL │ 1280 x 768  │ 19,21,22                │         │\n      │ Nexus5            │ LG       │ Nexus 5                             │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │         │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │         │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │         │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │         │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ VIRTUAL │ 1280 x 800  │ 19,21,22                │         │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta    │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │         │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │ beta=30 │\n      │ Pixel2            │ Google   │ Pixel 2                             │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │ beta=30 │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴─────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬─────────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │   TAGS  │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼─────────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │         │\n      │ Nexus4            │ LG       │ Nexus 4                             │ VIRTUAL │ 1280 x 768  │ 19,21,22                │         │\n      │ Nexus5            │ LG       │ Nexus 5                             │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │         │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │         │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │         │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │         │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ VIRTUAL │ 1280 x 800  │ 19,21,22                │         │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta    │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │         │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │ beta=30 │\n      │ Pixel2            │ Google   │ Pixel 2                             │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │ beta=30 │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴─────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n\n      Files should be seperated by newline.\n      For example:\n\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.5/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step doesn't build anything,\n  it collects the built APK from `$BITRISE_APK_PATH` (and in case of instrumentation\n  tests, the test APK from `$BITRISE_TEST_APK_PATH`).\\n\\nAvailable test types are\n  instrumentation, robo, gameloop. The minimal setup of this Step would be to select\n  a test type. If you selected instrumentation, don't forget to set the __Test APK\n  path__\\nunder the __Instrumentation Test__ group as well. To create the two required\n  APKs, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n  Step (before this Step).  \"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2021-05-26T12:34:28.9957039Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 9331d16a028e7042f10b9880b7fc15a2f8fdc0b5\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬─────────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │   TAGS  │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼─────────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │         │\n      │ Nexus4            │ LG       │ Nexus 4                             │ VIRTUAL │ 1280 x 768  │ 19,21,22                │         │\n      │ Nexus5            │ LG       │ Nexus 5                             │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │         │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │         │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │         │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │         │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ VIRTUAL │ 1280 x 800  │ 19,21,22                │         │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta    │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │         │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │ beta=30 │\n      │ Pixel2            │ Google   │ Pixel 2                             │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │ beta=30 │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴─────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬─────────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │   TAGS  │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼─────────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │         │\n      │ Nexus4            │ LG       │ Nexus 4                             │ VIRTUAL │ 1280 x 768  │ 19,21,22                │         │\n      │ Nexus5            │ LG       │ Nexus 5                             │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │         │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │         │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │         │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │         │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ VIRTUAL │ 1280 x 800  │ 19,21,22                │         │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta    │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │         │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │ beta=30 │\n      │ Pixel2            │ Google   │ Pixel 2                             │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │ beta=30 │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴─────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n\n      Files should be seperated by newline.\n      For example:\n\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.6/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for Android'\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step doesn't build anything,\n  it collects the built APK from `$BITRISE_APK_PATH` (and in case of instrumentation\n  tests, the test APK from `$BITRISE_TEST_APK_PATH`).\\n\\nAvailable test types are\n  instrumentation, robo, gameloop. The minimal setup of this Step would be to select\n  a test type. If you selected instrumentation, don't forget to set the __Test APK\n  path__\\nunder the __Instrumentation Test__ group as well. To create the two required\n  APKs, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n  Step (before this Step).  \"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2022-03-11T15:49:27.068647866Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 49b65da3e84664a43d3b5b410eaa07fc0696690b\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌───────────────────┬──────────┬─────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────┐\\n│\n      \\     MODEL_ID     │   MAKE   │              MODEL_NAME             │   FORM\n      \\ │  RESOLUTION │      OS_VERSION_IDS     │ TAGS │\\n├───────────────────┼──────────┼─────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────┤\\n│\n      Nexus10           │ Samsung  │ Nexus 10                            │ VIRTUAL\n      │ 2560 x 1600 │ 19,21,22                │      │\\n│ Nexus4            │ LG       │\n      Nexus 4                             │ VIRTUAL │ 1280 x 768  │ 19,21,22                │\n      \\     │\\n│ Nexus5            │ LG       │ Nexus 5                             │\n      VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │      │\\n│ Nexus5X           │\n      LG       │ Nexus 5X                            │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26\n      \\            │      │\\n│ Nexus6            │ Motorola │ Nexus 6                             │\n      VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │      │\\n│ Nexus6P           │\n      Google   │ Nexus 6P                            │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27\n      \\         │      │\\n│ Nexus7            │ Asus     │ Nexus 7 (2012)                      │\n      VIRTUAL │ 1280 x 800  │ 19,21,22                │      │\\n│ Nexus7_clone_16_9\n      │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ VIRTUAL │ 1280 x 720  │ 23,24,25,26\n      \\            │ beta │\\n│ Nexus9            │ HTC      │ Nexus 9                             │\n      VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │      │\\n│ NexusLowRes       │\n      Generic  │ Low-resolution MDPI phone           │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30\n      │      │\\n│ Pixel2            │ Google   │ Pixel 2                             │\n      VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │      │\\n│ Pixel3            │\n      Google   │ Pixel 3                             │ VIRTUAL │ 2160 x 1080 │ 30\n      \\                     │      │\\n└───────────────────┴──────────┴─────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────┘\n      \\       \\n```\\n\"\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────────┬──────────┬─────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────┐\n      │      MODEL_ID     │   MAKE   │              MODEL_NAME             │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │ TAGS │\n      ├───────────────────┼──────────┼─────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────┤\n      │ Nexus10           │ Samsung  │ Nexus 10                            │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │      │\n      │ Nexus4            │ LG       │ Nexus 4                             │ VIRTUAL │ 1280 x 768  │ 19,21,22                │      │\n      │ Nexus5            │ LG       │ Nexus 5                             │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │      │\n      │ Nexus5X           │ LG       │ Nexus 5X                            │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │      │\n      │ Nexus6            │ Motorola │ Nexus 6                             │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │      │\n      │ Nexus6P           │ Google   │ Nexus 6P                            │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │      │\n      │ Nexus7            │ Asus     │ Nexus 7 (2012)                      │ VIRTUAL │ 1280 x 800  │ 19,21,22                │      │\n      │ Nexus7_clone_16_9 │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta │\n      │ Nexus9            │ HTC      │ Nexus 9                             │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │      │\n      │ NexusLowRes       │ Generic  │ Low-resolution MDPI phone           │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │      │\n      │ Pixel2            │ Google   │ Pixel 2                             │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │      │\n      │ Pixel3            │ Google   │ Pixel 3                             │ VIRTUAL │ 2160 x 1080 │ 30                      │      │\n      └───────────────────┴──────────┴─────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n\n      For example:\n\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n\n      For example, you could use the following parameter for custom login:\n\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n\n      Files should be seperated by newline.\n      For example:\n\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n\n      For example:\n\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.7/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step collects the built\n  APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests,\n  the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to\n  run UI tests on them.\\n\\nThe available test types are instrumentation, robo, gameloop.\n  \\n\\n### Configuring the Step \\n\\nYou can read [our detailed guide about using the\n  Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with\n  other Bitrise Steps. Here we'll go over the configuration options of the Step. \\n\\n1.\n  Make sure the **App path** input points to the path of the APK or AAB file of your\n  app. If you use our **Android Build** or **Android Build for UI Testing** Steps,\n  you don't need to change the default value. \\n1. Add the devices you want the tests\n  to run on in the **Test devices** input. \\n\\n   You need to set the device ID, the\n  version, the orientation, and the language. Read the input description for more\n  information and available devices.\\n1. Choose a test type. \\n   \\n   The available\n  options are:\\n   - instrumentation\\n   - robo\\n   - gameloop\\n\\nFor detailed configuration\n  options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n  \\n\\nYou can also export the results of the Step to the Test reports add-on. All\n  you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\\n\\n###\n  Troubleshooting\\n\\nIf you get the **Build already exists** error, it is because\n  you have more than one instance of the Step in your Workflow. This doesn't work\n  as Bitrise sends the build slug to Firebase and having the Step more than once in\n  the same Workflow results in sending the same build slug multiple times. \\n\\n\\n###\n  Useful links\\n\\n- [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\\n-\n  [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\\n\\n###\n  Related Steps \\n\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2022-06-14T10:24:20.929105661Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: eeedc86985f9fdb73505f522ad717efa49dc5d76\nproject_type_tags:\n- android\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │      OS_VERSION_IDS     │ TAGS │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────┤\\n│\n      AndroidTablet270dpi │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │\n      VIRTUAL │ 1600 x 720  │ 30                      │      │\\n│ Nexus10             │\n      Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600\n      │ 19,21,22                │      │\\n│ Nexus4              │ LG       │ Nexus\n      4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22                │\n      \\     │\\n│ Nexus5              │ LG       │ Nexus 5                                  │\n      VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │      │\\n│ Nexus5X             │\n      LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080\n      │ 23,24,25,26             │      │\\n│ Nexus6              │ Motorola │ Nexus\n      6                                  │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25\n      \\         │      │\\n│ Nexus6P             │ Google   │ Nexus 6P                                 │\n      VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │      │\\n│ Nexus7              │\n      Asus     │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │\n      19,21,22                │      │\\n│ Nexus7_clone_16_9   │ Generic  │ Nexus7\n      clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │\n      beta │\\n│ Nexus9              │ HTC      │ Nexus 9                                  │\n      VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │      │\\n│ NexusLowRes         │\n      Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640 x 360  │\n      23,24,25,26,27,28,29,30 │      │\\n│ Pixel2              │ Google   │ Pixel 2\n      \\                                 │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │\n      \\     │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                      │      │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────┘\n      \\      \\n```\\n\"\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────┐\n      │       MODEL_ID      │   MAKE   │                MODEL_NAME                │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │ TAGS │\n      ├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────┤\n      │ AndroidTablet270dpi │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720  │ 30                      │      │\n      │ Nexus10             │ Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │      │\n      │ Nexus4              │ LG       │ Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22                │      │\n      │ Nexus5              │ LG       │ Nexus 5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │      │\n      │ Nexus5X             │ LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │      │\n      │ Nexus6              │ Motorola │ Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │      │\n      │ Nexus6P             │ Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │      │\n      │ Nexus7              │ Asus     │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22                │      │\n      │ Nexus7_clone_16_9   │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta │\n      │ Nexus9              │ HTC      │ Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │      │\n      │ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │      │\n      │ Pixel2              │ Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │      │\n      │ Pixel3              │ Google   │ Pixel 3                                  │ VIRTUAL │ 2160 x 1080 │ 30                      │      │\n      └─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.8/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step collects the built\n  APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests,\n  the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to\n  run UI tests on them.\\n\\nThe available test types are instrumentation, robo, gameloop.\n  \\n\\n### Configuring the Step \\n\\nYou can read [our detailed guide about using the\n  Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with\n  other Bitrise Steps. Here we'll go over the configuration options of the Step. \\n\\n1.\n  Make sure the **App path** input points to the path of the APK or AAB file of your\n  app. If you use our **Android Build** or **Android Build for UI Testing** Steps,\n  you don't need to change the default value. \\n1. Add the devices you want the tests\n  to run on in the **Test devices** input. \\n\\n   You need to set the device ID, the\n  version, the orientation, and the language. Read the input description for more\n  information and available devices.\\n1. Choose a test type. \\n   \\n   The available\n  options are:\\n   - instrumentation\\n   - robo\\n   - gameloop\\n\\nFor detailed configuration\n  options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n  \\n\\nYou can also export the results of the Step to the Test reports add-on. All\n  you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\\n\\n###\n  Troubleshooting\\n\\nIf you get the **Build already exists** error, it is because\n  you have more than one instance of the Step in your Workflow. This doesn't work\n  as Bitrise sends the build slug to Firebase and having the Step more than once in\n  the same Workflow results in sending the same build slug multiple times. \\n\\n\\n###\n  Useful links\\n\\n- [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\\n-\n  [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\\n\\n###\n  Related Steps \\n\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2022-12-02T09:34:03.200215888Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 68703efde1005866fcaeb6b717515085aa2d8c41\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n    is_required: true\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\\n│\n      AmatiTvEmulator     │ Google   │ Google TV Amati                          │\n      VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\\n│ AndroidTablet270dpi\n      │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720\n      \\ │ 30                      │                  │\\n│ GoogleTvEmulator    │ Google\n      \\  │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │\n      beta=30          │\\n│ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │\n      VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ MediumTablet.arm\n      \\   │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x\n      1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ Nexus10             │\n      Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600\n      │ 19,21,22                │ deprecated=19    │\\n│ Nexus4              │ LG       │\n      Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus5              │ LG       │ Nexus\n      5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │\n      deprecated=19    │\\n│ Nexus5X             │ LG       │ Nexus 5X                                 │\n      VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\\n│ Nexus6\n      \\             │ Motorola │ Nexus 6                                  │ VIRTUAL\n      │ 2560 x 1440 │ 21,22,23,24,25          │                  │\\n│ Nexus6P             │\n      Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440\n      │ 23,24,25,26,27          │                  │\\n│ Nexus7              │ Asus\n      \\    │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus7_clone_16_9   │ Generic  │ Nexus7\n      clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │\n      beta             │\\n│ Nexus9              │ HTC      │ Nexus 9                                  │\n      VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\\n│ NexusLowRes\n      \\        │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640\n      x 360  │ 23,24,25,26,27,28,29,30 │                  │\\n│ Pixel2              │\n      Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080\n      │ 26,27,28,29,30          │                  │\\n│ Pixel2.arm          │ Google\n      \\  │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33\n      \\   │ preview=33, beta │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                      │                  │\\n│ SmallPhone.arm\n      \\     │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280\n      x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      \\    \\n```\\n\"\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\n      │       MODEL_ID      │   MAKE   │                MODEL_NAME                │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\n      ├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\n      │ AmatiTvEmulator     │ Google   │ Google TV Amati                          │ VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\n      │ AndroidTablet270dpi │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720  │ 30                      │                  │\n      │ GoogleTvEmulator    │ Google   │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │ beta=30          │\n      │ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ MediumTablet.arm    │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Nexus10             │ Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │ deprecated=19    │\n      │ Nexus4              │ LG       │ Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22                │ deprecated=19    │\n      │ Nexus5              │ LG       │ Nexus 5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │ deprecated=19    │\n      │ Nexus5X             │ LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\n      │ Nexus6              │ Motorola │ Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │                  │\n      │ Nexus6P             │ Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │                  │\n      │ Nexus7              │ Asus     │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22                │ deprecated=19    │\n      │ Nexus7_clone_16_9   │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta             │\n      │ Nexus9              │ HTC      │ Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\n      │ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │                  │\n      │ Pixel2              │ Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │                  │\n      │ Pixel2.arm          │ Google   │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Pixel3              │ Google   │ Pixel 3                                  │ VIRTUAL │ 2160 x 1080 │ 30                      │                  │\n      │ SmallPhone.arm      │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      └─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.1.9/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: \"Run Android UI tests on virtual devices. This Step collects the built\n  APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests,\n  the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to\n  run UI tests on them.\\n\\nThe available test types are instrumentation, robo, gameloop.\n  \\n\\n### Configuring the Step \\n\\nYou can read [our detailed guide about using the\n  Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with\n  other Bitrise Steps. Here we'll go over the configuration options of the Step. \\n\\n1.\n  Make sure the **App path** input points to the path of the APK or AAB file of your\n  app. If you use our **Android Build** or **Android Build for UI Testing** Steps,\n  you don't need to change the default value. \\n1. Add the devices you want the tests\n  to run on in the **Test devices** input. \\n\\n   You need to set the device ID, the\n  version, the orientation, and the language. Read the input description for more\n  information and available devices.\\n1. Choose a test type. \\n   \\n   The available\n  options are:\\n   - instrumentation\\n   - robo\\n   - gameloop\\n\\nFor detailed configuration\n  options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n  \\n\\nYou can also export the results of the Step to the Test reports add-on. All\n  you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\\n\\n###\n  Troubleshooting\\n\\nIf you get the **Build already exists** error, it is because\n  you have more than one instance of the Step in your Workflow. This doesn't work\n  as Bitrise sends the build slug to Firebase and having the Step more than once in\n  the same Workflow results in sending the same build slug multiple times. \\n\\n\\n###\n  Useful links\\n\\n- [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\\n-\n  [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\\n\\n###\n  Related Steps \\n\\n- [Android Build](https://www.bitrise.io/integrations/steps/android-build)\\n-\n  [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\\n-\n  [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2023-03-29T12:23:36.683132868Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: cdd9f624138fcbccca5b855c5aecd151d96cca01\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: \"Format:\\nOne device configuration per line and the parameters are\n      separated with `,` in the order of: `deviceID,version,language,orientation`\\n\\nFor\n      example:\\n`NexusLowRes,24,en,portrait`\\n\\n`NexusLowRes,24,en,landscape`\\n\\nAvailable\n      devices and its versions:\\n```\\n┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\\n│\n      \\      MODEL_ID      │   MAKE   │                MODEL_NAME                │\n      \\  FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\\n├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\\n│\n      AmatiTvEmulator     │ Google   │ Google TV Amati                          │\n      VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\\n│ AndroidTablet270dpi\n      │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720\n      \\ │ 30                      │                  │\\n│ GoogleTvEmulator    │ Google\n      \\  │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │\n      beta=30          │\\n│ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │\n      VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ MediumTablet.arm\n      \\   │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x\n      1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n│ Nexus10             │\n      Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600\n      │ 19,21,22                │ deprecated=19    │\\n│ Nexus4              │ LG       │\n      Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus5              │ LG       │ Nexus\n      5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │\n      deprecated=19    │\\n│ Nexus5X             │ LG       │ Nexus 5X                                 │\n      VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\\n│ Nexus6\n      \\             │ Motorola │ Nexus 6                                  │ VIRTUAL\n      │ 2560 x 1440 │ 21,22,23,24,25          │                  │\\n│ Nexus6P             │\n      Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440\n      │ 23,24,25,26,27          │                  │\\n│ Nexus7              │ Asus\n      \\    │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22\n      \\               │ deprecated=19    │\\n│ Nexus7_clone_16_9   │ Generic  │ Nexus7\n      clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │\n      beta             │\\n│ Nexus9              │ HTC      │ Nexus 9                                  │\n      VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\\n│ NexusLowRes\n      \\        │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640\n      x 360  │ 23,24,25,26,27,28,29,30 │                  │\\n│ Pixel2              │\n      Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080\n      │ 26,27,28,29,30          │                  │\\n│ Pixel2.arm          │ Google\n      \\  │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33\n      \\   │ preview=33, beta │\\n│ Pixel3              │ Google   │ Pixel 3                                  │\n      VIRTUAL │ 2160 x 1080 │ 30                      │                  │\\n│ SmallPhone.arm\n      \\     │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280\n      x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\\n└─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      \\    \\n```\\n\"\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `NexusLowRes,24,en,portrait`\n\n      `NexusLowRes,24,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────┬──────────┬──────────────────────────────────────────┬─────────┬─────────────┬─────────────────────────┬──────────────────┐\n      │       MODEL_ID      │   MAKE   │                MODEL_NAME                │   FORM  │  RESOLUTION │      OS_VERSION_IDS     │       TAGS       │\n      ├─────────────────────┼──────────┼──────────────────────────────────────────┼─────────┼─────────────┼─────────────────────────┼──────────────────┤\n      │ AmatiTvEmulator     │ Google   │ Google TV Amati                          │ VIRTUAL │ 1080 x 1920 │ 29                      │ beta=29          │\n      │ AndroidTablet270dpi │ Generic  │ Generic 720x1600 Android tablet @ 270dpi │ VIRTUAL │ 1600 x 720  │ 30                      │                  │\n      │ GoogleTvEmulator    │ Google   │ Google TV                                │ VIRTUAL │  720 x 1280 │ 30                      │ beta=30          │\n      │ MediumPhone.arm     │ Generic  │ MediumPhone (ARM)                        │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ MediumTablet.arm    │ Generic  │ MediumTablet (ARM)                       │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Nexus10             │ Samsung  │ Nexus 10                                 │ VIRTUAL │ 2560 x 1600 │ 19,21,22                │ deprecated=19    │\n      │ Nexus4              │ LG       │ Nexus 4                                  │ VIRTUAL │ 1280 x 768  │ 19,21,22                │ deprecated=19    │\n      │ Nexus5              │ LG       │ Nexus 5                                  │ VIRTUAL │ 1920 x 1080 │ 19,21,22,23             │ deprecated=19    │\n      │ Nexus5X             │ LG       │ Nexus 5X                                 │ VIRTUAL │ 1920 x 1080 │ 23,24,25,26             │                  │\n      │ Nexus6              │ Motorola │ Nexus 6                                  │ VIRTUAL │ 2560 x 1440 │ 21,22,23,24,25          │                  │\n      │ Nexus6P             │ Google   │ Nexus 6P                                 │ VIRTUAL │ 2560 x 1440 │ 23,24,25,26,27          │                  │\n      │ Nexus7              │ Asus     │ Nexus 7 (2012)                           │ VIRTUAL │ 1280 x 800  │ 19,21,22                │ deprecated=19    │\n      │ Nexus7_clone_16_9   │ Generic  │ Nexus7 clone, DVD 16:9 aspect ratio      │ VIRTUAL │ 1280 x 720  │ 23,24,25,26             │ beta             │\n      │ Nexus9              │ HTC      │ Nexus 9                                  │ VIRTUAL │ 2048 x 1536 │ 21,22,23,24,25          │                  │\n      │ NexusLowRes         │ Generic  │ Low-resolution MDPI phone                │ VIRTUAL │  640 x 360  │ 23,24,25,26,27,28,29,30 │                  │\n      │ Pixel2              │ Google   │ Pixel 2                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30          │                  │\n      │ Pixel2.arm          │ Google   │ Pixel 2 (ARM)                            │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      │ Pixel3              │ Google   │ Pixel 3                                  │ VIRTUAL │ 2160 x 1080 │ 30                      │                  │\n      │ SmallPhone.arm      │ Generic  │ SmallPhone (ARM)                         │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,32,33    │ preview=33, beta │\n      └─────────────────────┴──────────┴──────────────────────────────────────────┴─────────┴─────────────┴─────────────────────────┴──────────────────┘\n      ```\n    title: Test devices\n  test_devices: NexusLowRes,24,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    description: null\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- num_flaky_test_attempts: 0\n  opts:\n    category: Debug\n    description: |\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: \"\"\n    title: Number of times a test execution is reattempted\n- obb_files_list: \"\"\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: \"A list of paths that will be downloaded from the device's storage\n      after the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be available\n      on the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    summary: \"A list of paths that will be downloaded from the device's storage after\n      the test is complete. \\n\\nFor example\\n\\n```\\n/sdcard/tempDir1\\n/data/tempDir2\\n```\\n\\nIf\n      `download_test_results` input is set to `false` then these files will be downloaded\n      to the dashboard only. To have them downloaded set that input to `true` as well.\\n\"\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run and\n      the files you downloaded from the device (if you have set `directories_to_pull`\n      input as well) will be downloaded. Otherwise, no any file will be downloaded.\n      \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: \"\"\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.2.0/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2025-08-13T07:38:46.350931766Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 1ad7c52cb2b91cbb53e4df6a80bf5cfcfb66629f\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTv.arm            │ Google  │ Google TV, 1280x720 @ 213dpi (Arm)             │ VIRTUAL │  720 x 1280 │ 31                               │ preview=31             │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTv.arm            │ Google  │ Google TV, 1280x720 @ 213dpi (Arm)             │ VIRTUAL │  720 x 1280 │ 31                               │ preview=31             │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- num_flaky_test_attempts: \"0\"\n  opts:\n    category: Debug\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.2.1/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2025-09-12T12:05:52.084561122Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: de37a8255e20d21f11e362a21d07c343a6f1acb0\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.3.0/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2025-10-01T09:37:07.038472856Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 240cbccd00696133578d2d0ef998aec855287bb6\nproject_type_tags:\n- android\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.3.1/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2025-11-10T13:49:19.719629553Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 6ccc0ef5af78356f7d1566c8d1a718c1f48e9daa\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.3.2/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2026-01-13T15:02:21.698362999Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: adfe1b04beeb61750d97fa369f4ca98f24dd5377\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.2/bin/virtual-device-testing-for-android-darwin-amd64\n    hash: sha256-5f06bac9aba03103ffdcaffb978bd50f4e357b0482ac98287bf01bae1926378e\n  darwin-arm64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.2/bin/virtual-device-testing-for-android-darwin-arm64\n    hash: sha256-86ccdbb6af87ee36cc25093ca90075d4f4596de17ae8c044831bf58b592331bb\n  linux-amd64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.2/bin/virtual-device-testing-for-android-linux-amd64\n    hash: sha256-a7d62f587db8cace8bd6aec877438c592e21ad63066da548abada3c0b532e63a\n  linux-arm64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.2/bin/virtual-device-testing-for-android-linux-arm64\n    hash: sha256-c3e5e9e9ebc3ab0347e0df7dc295ac2c2106b077c7a331a462549dedbd40626a\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.3.3/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2026-04-27T13:02:59.299435594Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 7882726316c9cea81d62cc4fa8fa1d8e9e7b1e25\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.3/bin/virtual-device-testing-for-android-darwin-amd64\n    hash: sha256-fbb81456b4aa08cab07f609a0a6f4c838899984e6edbd7b72d0caf157feafbad\n  darwin-arm64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.3/bin/virtual-device-testing-for-android-darwin-arm64\n    hash: sha256-4c8a7f54d6d961975fe5240c702bc6f18727f61b5ceec9d5a47bded491441d63\n  linux-amd64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.3/bin/virtual-device-testing-for-android-linux-amd64\n    hash: sha256-bca756ea983957d329b61172ec9a0c15deb9b118c09fcce1a24aff8eb993e36f\n  linux-arm64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.3/bin/virtual-device-testing-for-android-linux-arm64\n    hash: sha256-4464774899f0d4aed23f36a1981f263cb9341da390dd5bb8d523d0ccfea26664\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/1.3.4/step.yml",
    "content": "title: Virtual Device Testing for Android\nsummary: Run Android UI tests on virtual devices\ndescription: |-\n  Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the `$BITRISE_APK_PATH` and in case of instrumentation tests, the `$BITRISE_TEST_APK_PATH` Environment Variables and uses Firebase Test Lab to run UI tests on them.\n\n  The available test types are instrumentation, robo, gameloop.\n\n  ### Configuring the Step\n\n  You can read [our detailed guide about using the Step](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html) with other Bitrise Steps. Here we'll go over the configuration options of the Step.\n\n  1. Make sure the **App path** input points to the path of the APK or AAB file of your app. If you use our **Android Build** or **Android Build for UI Testing** Steps, you don't need to change the default value.\n  1. Add the devices you want the tests to run on in the **Test devices** input.\n\n     You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.\n  1. Choose a test type.\n\n     The available options are:\n     - instrumentation\n     - robo\n     - gameloop\n\n  For detailed configuration options related to the different test types, please check out the [full guide](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html).\n\n  You can also export the results of the Step to the Test reports add-on. All you need to do is to add a **Deploy to Bitrise.io** Step to the end of your Workflow.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  - [Device testing for Android](https://devcenter.bitrise.io/en/testing/device-testing-for-android.html)\n  - [Test reports](https://devcenter.bitrise.io/en/testing/test-reports.html)\n\n  ### Related Steps\n\n  - [Android Build](https://www.bitrise.io/integrations/steps/android-build)\n  - [Android Build for UI Testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues\npublished_at: 2026-05-08T11:39:52.863070657Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android.git\n  commit: 9ee2899cf4a3b6736a49a0ff284d572bf29c6223\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.4/bin/virtual-device-testing-for-android-darwin-amd64\n    hash: sha256-85dd0b0230a3059e0a6f6a5193697c7f870d1724f95fbe269bf14f439b07504c\n  darwin-arm64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.4/bin/virtual-device-testing-for-android-darwin-arm64\n    hash: sha256-e82e39b0f8719a4320ea7148ff07ca5d4a349be11c838d6dde625f87412527b8\n  linux-amd64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.4/bin/virtual-device-testing-for-android-linux-amd64\n    hash: sha256-b14b7919344ab52b8fd67d6b6d90adef18af8a732beb5b5a9dae631be1134873\n  linux-arm64:\n    storage_uri: steps/virtual-device-testing-for-android/1.3.4/bin/virtual-device-testing-for-android-linux-arm64\n    hash: sha256-6956da7c8f2f5e1ac25950ac4a1dd51368a4256eef66bdf995908fe921e78592\nproject_type_tags:\n- android\n- cordova\n- flutter\n- ionic\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-android\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- app_path: $BITRISE_APK_PATH\n  opts:\n    description: |\n      The path to the app to test (APK or AAB). By default `android-build` and `android-build-for-ui-testing` Steps export the `BITRISE_APK_PATH` Env Var, so you won't need to change this input.\n      Can specify an APK (`$BITRISE_APK_PATH`) or AAB (Android App Bundle) as input (`$BITRISE_AAB_PATH`).\n\n      If nothing is specified then the Step will use a default empty Application APK. This will help the library instrumentation tests as it can be used as a shell where the tests will be running.\n    summary: |\n      The path to the app to test (APK or AAB).\n    title: App path\n- opts:\n    description: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    is_required: true\n    summary: |\n      The type of your test you want to run on the devices. Find more properties below in the selected test type's group.\n    title: Test type\n    value_options:\n    - instrumentation\n    - robo\n    - gameloop\n  test_type: robo\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n      `MediumPhone.arm,33,en,portrait`\n\n      `MediumTablet.arm,23,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────────────────┬─────────┬────────────────────────────────────────────────┬─────────┬─────────────┬──────────────────────────────────┬────────────────────────┐\n      │         MODEL_ID        │   MAKE  │                   MODEL_NAME                   │   FORM  │  RESOLUTION │          OS_VERSION_IDS          │          TAGS          │\n      ├─────────────────────────┼─────────┼────────────────────────────────────────────────┼─────────┼─────────────┼──────────────────────────────────┼────────────────────────┤\n      │ AmatiTvEmulator         │ Google  │ Google TV Amati                                │ VIRTUAL │ 1080 x 1920 │ 29                               │ beta=29, deprecated=29 │\n      │ AndroidTablet270dpi.arm │ Generic │ Generic 720x1600 Android tablet @ 270dpi (Arm) │ VIRTUAL │ 1600 x 720  │ 30                               │                        │\n      │ GoogleTvEmulator        │ Google  │ Google TV                                      │ VIRTUAL │  720 x 1280 │ 30                               │ beta=30, deprecated=30 │\n      │ MediumPhone.arm         │ Generic │ Medium Phone, 6.4in/16cm (Arm)                 │ VIRTUAL │ 2400 x 1080 │ 26,27,28,29,30,31,32,33,35,36,34 │                        │\n      │ MediumTablet.arm        │ Generic │ Medium Tablet, 10.05in/25cm (Arm)              │ VIRTUAL │ 2560 x 1600 │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      │ Pixel2.arm              │ Google  │ Pixel 2 (Arm)                                  │ VIRTUAL │ 1920 x 1080 │ 26,27,28,29,30,31,32,33          │                        │\n      │ SmallPhone.arm          │ Generic │ Small Phone, 4.65in/12cm (Arm)                 │ VIRTUAL │ 1280 x 720  │ 26,27,28,29,30,31,32,33,34,35    │                        │\n      └─────────────────────────┴─────────┴────────────────────────────────────────────────┴─────────┴─────────────┴──────────────────────────────────┴────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: MediumPhone.arm,33,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Instrumentation Test\n    description: The path to the APK that contains instrumentation tests. To build\n      this, you can run the [Build for UI testing](https://bitrise.io/integrations/steps/android-build-for-ui-testing)\n      Step (before this Step).\n    summary: The path to the APK that contains instrumentation tests\n    title: Test APK path\n  test_apk_path: $BITRISE_TEST_APK_PATH\n- inst_test_runner_class: null\n  opts:\n    category: Instrumentation Test\n    description: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    summary: The fully-qualified Java class name of the instrumentation test runner\n      (leave empty to use the last name extracted from the APK manifest).\n    title: Test runner class\n- inst_test_targets: null\n  opts:\n    category: Instrumentation Test\n    description: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    summary: |\n      A list of one or more instrumentation test targets to be run (default: all targets). Each target must be fully qualified with the package name or class name, in one of these formats:\n      - `package package_name`\n      - `class package_name.class_name`\n      - `class package_name.class_name#method_name`\n      For example:\n      `class com.my.company.app.MyTargetClass,class com.my.company.app.MyOtherTargetClass`\n    title: |\n      Test targets, seperated with the \",\" character.\n- inst_use_orchestrator: \"false\"\n  opts:\n    category: Instrumentation Test\n    description: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    is_required: true\n    summary: |\n      The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not.\n    title: Use Orchestrator\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Robo Test\n    description: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    summary: The initial activity used to start the app during a robo test. (leave\n      empty to get it extracted from the APK manifest)\n    title: Initial activity\n  robo_initial_activity: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    summary: |\n      The maximum depth of the traversal stack a robo test can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity(leave empty to use the default value: `50`)\n    title: Max depth\n  robo_max_depth: null\n- opts:\n    category: Robo Test\n    description: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    summary: |\n      The maximum number of steps/actions a robo test can execute(leave empty to use the default value: `no limit`).\n    title: Max steps\n  robo_max_steps: null\n- opts:\n    category: Robo Test\n    description: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    summary: |\n      To complete text fields in your app, use robo-directives and provide a comma-separated list of key-value pairs, where the key is the Android resource name of the target UI element, and the value is the text string. EditText fields are supported but not text fields in WebView UI elements.\n      For example, you could use the following parameter for custom login:\n      ```\n      username_resource,username,ENTER_TEXT\n      password_resource,password,ENTER_TEXT\n      loginbtn_resource,,SINGLE_CLICK\n      ```\n      One directive per line, the parameters are separated with `,` character. For example: `ResourceName,InputText,ActionType`\n    title: Robo directives\n  robo_directives: null\n- opts:\n    category: Robo Test\n    summary: A path to a JSON file with a sequence of recorded actions Robo should\n      perform before the Robo crawl.\n    title: Robo scenario file path\n  robo_scenario_file: null\n- loop_scenarios: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario numbers which will be run as part of the test (default: all scenarios).\n      A maximum of 1024 scenarios may be specified in one test matrix.\n      Format: int,[int,...]\n      For example:\n      ```\n      1,2\n      ```\n    summary: 'A list of game-loop scenario numbers which will be run as part of the\n      test (default: all scenarios).'\n    title: Loop scenarios\n- loop_scenario_labels: null\n  opts:\n    category: Game Loop Test\n    description: |\n      A list of game-loop scenario labels (default: None).\n      Each game-loop scenario may be labeled in the APK manifest file with one or more arbitrary strings, creating logical groupings (e.g. GPU_COMPATIBILITY_TESTS).\n    summary: 'A list of game-loop scenario labels (default: None).'\n    title: Loop scenario labels\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    is_required: true\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min), the maximum is 3600 (60 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: \"900\"\n- obb_files_list: null\n  opts:\n    category: Test setup\n    description: |\n      A list of one or two Android OBB file names which will be copied to each test device before the tests will run (default: None).\n      Each OBB file name must conform to the format as specified by Android (e.g. [main|patch].0300110.com.example.android.obb) and will be installed into `[shared-storage]/Android/obb/[package-name]/` on the test device.\n      Files should be seperated by newline.\n      For example:\n      ```\n      main.0300110.com.example.android.obb\n      patch.0300110.com.example.android.obb\n      ```\n    summary: Upload OBB files before tests will run\n    title: OBB files\n- auto_google_login: \"false\"\n  opts:\n    category: Test setup\n    description: |-\n      Automatically log into the test device using a preconfigured Google\n      account before beginning the test.\n    is_required: true\n    summary: Add preconfigured Google account before tests will run\n    title: Add preconfigured Google account\n    value_options:\n    - \"false\"\n    - \"true\"\n- environment_variables: null\n  opts:\n    category: Test setup\n    description: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    summary: |\n      One variable per line, key and value seperated by `=`\n      For example:\n      ```\n      coverage=true\n      coverageFile=/sdcard/tempDir/coverage.ec\n      ```\n    title: Environment Variables\n- directories_to_pull: null\n  opts:\n    category: Debug\n    description: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be available on the dashboard only. To have them downloaded set that input to `true` as well.\n    summary: |\n      A list of paths that will be downloaded from the device's storage after the test is complete.\n\n      For example\n\n      ```\n      /sdcard/tempDir1\n      /data/tempDir2\n      ```\n\n      If `download_test_results` input is set to `false` then these files will be downloaded to the dashboard only. To have them downloaded set that input to `true` as well.\n    title: Directories to pull\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run and the files you downloaded from the device (if you have set `directories_to_pull` input as well) will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- opts:\n    category: Debug\n    is_required: true\n    summary: |\n      If set to `true` will enable verbose level logging.\n    title: Verbose log\n    value_options:\n    - \"false\"\n    - \"true\"\n  use_verbose_log: \"false\"\n- apk_path: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    is_required: false\n    summary: |\n      Deprecated. Use 'App path' input instead of this one.\n      The path to the APK you want the tests run with. By default `gradle-runner` step exports `BITRISE_APK_PATH` env, so you won't need to change this input.\n    title: APK path\n- app_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the App manifest.\n      The Java package of the application under test.\n    title: App package ID\n- inst_test_package_id: null\n  opts:\n    category: Deprecated\n    description: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    summary: |\n      Deprecated: If not specified will be automatically extracted from the Test App manifest.\n      The Java package name of the instrumentation test.\n    title: Test package ID\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: \"\"\n  opts:\n    summary: The directory containing the downloaded files if you have set `directories_to_pull`\n      and `download_test_results` inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-android/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.0/step.yml",
    "content": "title: '[BETA] Virtual Device Testing for iOS'\nsummary: Run iOS XCUItests on virtual devices\ndescription: |-\n  Run iOS XCUItests on virtual devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2018-09-03T13:57:56.813175595Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 64b8e9fd2e0ad1232b88f3e2979291163bb5485f\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: null\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────┬────────────────────────┬────────────────┬\n      │   MODEL_ID    │       MODEL_NAME       │ OS_VERSION_IDS │\n      ├───────────────┼────────────────────────┼────────────────┼\n      │  ipad5        │  iPad (5th generation) │      11.2      │\n      │  ipadmini4    │  iPad mini 4           │      11.2      │\n      │  ipadpro_105  │  iPad Pro (10.5-inch)  │      11.2      │\n      │  iphone6s     │  iPhone 6s             │    10.3,11.2   │\n      │  iphone6splus │  iPhone 6s Plus        │    9.0,9.1     │\n      │  iphone7      │  iPhone 7              │      11.2      │\n      │  iphone7plus  │  iPhone 7 Plus         │      11.2      │\n      │  iphone8      │  iPhone 8              │      11.2      │\n      │  iphone8plus  │  iPhone 8 Plus         │      11.2      │\n      │  iphonese     │  iPhone SE             │      11.2      │\n      │  iphonex      │  iPhone X              │      11.2      │\n      └───────────────┴────────────────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────┬────────────────────────┬────────────────┬\n      │   MODEL_ID    │       MODEL_NAME       │ OS_VERSION_IDS │\n      ├───────────────┼────────────────────────┼────────────────┼\n      │  ipad5        │  iPad (5th generation) │      11.2      │\n      │  ipadmini4    │  iPad mini 4           │      11.2      │\n      │  ipadpro_105  │  iPad Pro (10.5-inch)  │      11.2      │\n      │  iphone6s     │  iPhone 6s             │    10.3,11.2   │\n      │  iphone6splus │  iPhone 6s Plus        │    9.0,9.1     │\n      │  iphone7      │  iPhone 7              │      11.2      │\n      │  iphone7plus  │  iPhone 7 Plus         │      11.2      │\n      │  iphone8      │  iPhone 8              │      11.2      │\n      │  iphone8plus  │  iPhone 8 Plus         │      11.2      │\n      │  iphonese     │  iPhone SE             │      11.2      │\n      │  iphonex      │  iPhone X              │      11.2      │\n      └───────────────┴────────────────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run will\n      be downloaded. Otherwise, no any file will be downloaded. \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.1/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on virtual devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2018-09-11T14:26:23.706926363Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 0e3c12d6194acb147f64f6dfbe9388320b309319\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: null\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────┬────────────────────────┬────────────────┬\n      │   MODEL_ID    │       MODEL_NAME       │ OS_VERSION_IDS │\n      ├───────────────┼────────────────────────┼────────────────┼\n      │  ipad5        │  iPad (5th generation) │      11.2      │\n      │  ipadmini4    │  iPad mini 4           │      11.2      │\n      │  ipadpro_105  │  iPad Pro (10.5-inch)  │      11.2      │\n      │  iphone6s     │  iPhone 6s             │    10.3,11.2   │\n      │  iphone6splus │  iPhone 6s Plus        │    9.0,9.1     │\n      │  iphone7      │  iPhone 7              │      11.2      │\n      │  iphone7plus  │  iPhone 7 Plus         │      11.2      │\n      │  iphone8      │  iPhone 8              │      11.2      │\n      │  iphone8plus  │  iPhone 8 Plus         │      11.2      │\n      │  iphonese     │  iPhone SE             │      11.2      │\n      │  iphonex      │  iPhone X              │      11.2      │\n      └───────────────┴────────────────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────┬────────────────────────┬────────────────┬\n      │   MODEL_ID    │       MODEL_NAME       │ OS_VERSION_IDS │\n      ├───────────────┼────────────────────────┼────────────────┼\n      │  ipad5        │  iPad (5th generation) │      11.2      │\n      │  ipadmini4    │  iPad mini 4           │      11.2      │\n      │  ipadpro_105  │  iPad Pro (10.5-inch)  │      11.2      │\n      │  iphone6s     │  iPhone 6s             │    10.3,11.2   │\n      │  iphone6splus │  iPhone 6s Plus        │    9.0,9.1     │\n      │  iphone7      │  iPhone 7              │      11.2      │\n      │  iphone7plus  │  iPhone 7 Plus         │      11.2      │\n      │  iphone8      │  iPhone 8              │      11.2      │\n      │  iphone8plus  │  iPhone 8 Plus         │      11.2      │\n      │  iphonese     │  iPhone SE             │      11.2      │\n      │  iphonex      │  iPhone X              │      11.2      │\n      └───────────────┴────────────────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run will\n      be downloaded. Otherwise, no any file will be downloaded. \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.10/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2019-10-15T09:12:03.800354559Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: e1aea675397e4d0356286a0eb7d7fd233945be3d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │           TAGS           │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2          │\n      │ iphone6     │ iPhone 6              │ 11.4                │ deprecated=11.4          │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3,11.2     │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ default, deprecated=11.2 │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1           │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1           │                          │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │           TAGS           │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2          │\n      │ iphone6     │ iPhone 6              │ 11.4                │ deprecated=11.4          │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3,11.2     │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ default, deprecated=11.2 │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1           │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1           │                          │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.11/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2020-03-23T15:51:27.003710777Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: f967ab04cae3a5107e81d303e591acd9b963b827\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,12.3,en,portrait`\n\n      `iphone7,12.3,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS               │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2                  │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2                  │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2                  │\n      │ iphone11    │ iPhone 11             │ 13.3                │                                  │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3                │                                  │\n      │ iphone6     │ iPhone 6              │ 11.4,12.2           │ deprecated=11.4                  │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3, deprecated=11.2 │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2                  │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ deprecated=11.2, default         │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonexr    │ iPhone XR             │ 13.2                │                                  │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1,12.3      │                                  │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1,12.3      │                                  │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,12.3,en,portrait`\n\n      `iphone7,12.3,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS               │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2                  │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2                  │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2                  │\n      │ iphone11    │ iPhone 11             │ 13.3                │                                  │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3                │                                  │\n      │ iphone6     │ iPhone 6              │ 11.4,12.2           │ deprecated=11.4                  │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3, deprecated=11.2 │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2                  │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ deprecated=11.2, default         │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonexr    │ iPhone XR             │ 13.2                │                                  │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1,12.3      │                                  │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1,12.3      │                                  │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,12.3,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.12/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2020-05-29T10:58:24.884925448Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 801c27b98f6eb2504b8bf6d7b73aada47f37e5bb\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,12.3,en,portrait`\n\n      `iphone7,12.3,en,landscape`\n\n      Available devices and its versions:\n      ```\n      +-------------+-----------------------+---------------------+----------------------------------+\n      |   MODEL_ID  |          NAME         |    OS_VERSION_IDS   |               TAGS               |\n      +-------------+-----------------------+---------------------+----------------------------------+\n      | ipad5       | iPad (5th generation) | 11.2,12.0           | deprecated=11.2                  |\n      | ipadmini4   | iPad mini 4           | 11.2,12.0           | deprecated=11.2                  |\n      | ipadpro_105 | iPad Pro (10.5-inch)  | 11.2                | deprecated=11.2                  |\n      | iphone11    | iPhone 11             | 13.3                |                                  |\n      | iphone11pro | iPhone 11 Pro         | 13.3                |                                  |\n      | iphone6     | iPhone 6              | 11.4                | deprecated=11.4                  |\n      | iphone6s    | iPhone 6s             | 10.3,11.2,11.4,12.0 | deprecated=10.3, deprecated=11.2 |\n      | iphone7     | iPhone 7              | 11.2,11.4,12.0,12.3 | deprecated=11.2                  |\n      | iphone7plus | iPhone 7 Plus         | 11.2,11.4,12.0      | deprecated=11.2                  |\n      | iphone8     | iPhone 8              | 11.2,11.4,12.0      | deprecated=11.2, default         |\n      | iphone8plus | iPhone 8 Plus         | 11.2,11.4,12.0,12.3 | deprecated=11.2                  |\n      | iphonese    | iPhone SE             | 11.2,11.4,12.0,12.3 | deprecated=11.2                  |\n      | iphonex     | iPhone X              | 11.2,11.4,12.0,12.3 | deprecated=11.2                  |\n      | iphonexr    | iPhone XR             | 13.2                |                                  |\n      | iphonexs    | iPhone XS             | 12.0,12.1,12.3      |                                  |\n      | iphonexsmax | iPhone XS Max         | 12.0,12.1,12.3      |                                  |\n      +-------------+-----------------------+---------------------+----------------------------------+\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,12.3,en,portrait`\n\n      `iphone7,12.3,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS               │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2                  │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2                  │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2                  │\n      │ iphone11    │ iPhone 11             │ 13.3                │                                  │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3                │                                  │\n      │ iphone6     │ iPhone 6              │ 11.4,12.2           │ deprecated=11.4                  │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3, deprecated=11.2 │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2                  │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ deprecated=11.2, default         │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0,12.3 │ deprecated=11.2                  │\n      │ iphonexr    │ iPhone XR             │ 13.2                │                                  │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1,12.3      │                                  │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1,12.3      │                                  │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,12.3,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.13/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2021-03-26T11:59:06.449315352Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 3325539af816f51fc5ae3e2b6c176d3658f17ae5\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,12.3,en,portrait`\n\n      `iphone7,12.3,en,landscape`\n\n      Available devices and its versions:\n      ```\n      +-------------+-----------------------+--------------------------+---------------------------------------------------+\n      |   MODEL_ID  |          NAME         |      OS_VERSION_IDS      |                       TAGS                        |\n      +-------------+-----------------------+--------------------------+---------------------------------------------------+\n      | ipad5       │ iPad (5th generation) │ 11.2,12.0,14.1           │ deprecated=11.2, deprecated=12.0                  |\n      | ipadmini4   │ iPad mini 4           │ 11.2,12.0,14.1           │ deprecated=11.2                                   │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                     │ deprecated=11.2                                   │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6                │                                                   │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.1                │                                                   │\n      │ iphone6     │ iPhone 6              │ 11.4                     │ deprecated=11.4                                   │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0      │ deprecated=10.3, deprecated=11.2, deprecated=11.4 │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0,12.3      │ deprecated=11.2, deprecated=11.4                  │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0,14.1      │ deprecated=11.2                                   │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.4,13.6,14.1 │ deprecated=11.2, default                          │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0,12.3      │ deprecated=11.2, deprecated=11.4                  │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0,12.3      │ deprecated=11.2, deprecated=11.4, deprecated=12.3 │\n      │ iphonex     │ iPhone X              │ 11.2,11.4                │ deprecated=11.2, deprecated=11.4                  │\n      │ iphonexr    │ iPhone XR             │ 13.2                     │                                                   │\n      │ iphonexs    │ iPhone XS             │ 12.0                     │                                                   │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1,12.3           |                                                   |\n      +-------------+-----------------------+--------------------------+---------------------------------------------------+\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,12.3,en,portrait`\n\n      `iphone7,12.3,en,landscape`\n\n      Available devices and its versions:\n      ```\n      +-------------+-----------------------+--------------------------+---------------------------------------------------+\n      |   MODEL_ID  |          NAME         |      OS_VERSION_IDS      |                       TAGS                        |\n      +-------------+-----------------------+--------------------------+---------------------------------------------------+\n      | ipad5       │ iPad (5th generation) │ 11.2,12.0,14.1           │ deprecated=11.2, deprecated=12.0                  |\n      | ipadmini4   │ iPad mini 4           │ 11.2,12.0,14.1           │ deprecated=11.2                                   │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                     │ deprecated=11.2                                   │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6                │                                                   │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.1                │                                                   │\n      │ iphone6     │ iPhone 6              │ 11.4                     │ deprecated=11.4                                   │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0      │ deprecated=10.3, deprecated=11.2, deprecated=11.4 │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0,12.3      │ deprecated=11.2, deprecated=11.4                  │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0,14.1      │ deprecated=11.2                                   │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.4,13.6,14.1 │ deprecated=11.2, default                          │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0,12.3      │ deprecated=11.2, deprecated=11.4                  │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0,12.3      │ deprecated=11.2, deprecated=11.4, deprecated=12.3 │\n      │ iphonex     │ iPhone X              │ 11.2,11.4                │ deprecated=11.2, deprecated=11.4                  │\n      │ iphonexr    │ iPhone XR             │ 13.2                     │                                                   │\n      │ iphonexs    │ iPhone XS             │ 12.0                     │                                                   │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1,12.3           |                                                   |\n      +-------------+-----------------------+--------------------------+---------------------------------------------------+\n      ```\n    title: Test devices\n  test_devices: iphone7,12.3,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.2/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on virtual devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2018-10-08T13:35:17.304201411Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 0880b56ddab45cc144d87fb57198b5895b267558\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────┬────────────────────────┬────────────────┬\n      │   MODEL_ID    │       MODEL_NAME       │ OS_VERSION_IDS │\n      ├───────────────┼────────────────────────┼────────────────┼\n      │  ipad5        │  iPad (5th generation) │      11.2      │\n      │  ipadmini4    │  iPad mini 4           │      11.2      │\n      │  ipadpro_105  │  iPad Pro (10.5-inch)  │      11.2      │\n      │  iphone6s     │  iPhone 6s             │    10.3,11.2   │\n      │  iphone6splus │  iPhone 6s Plus        │    9.0,9.1     │\n      │  iphone7      │  iPhone 7              │      11.2      │\n      │  iphone7plus  │  iPhone 7 Plus         │      11.2      │\n      │  iphone8      │  iPhone 8              │      11.2      │\n      │  iphone8plus  │  iPhone 8 Plus         │      11.2      │\n      │  iphonese     │  iPhone SE             │      11.2      │\n      │  iphonex      │  iPhone X              │      11.2      │\n      └───────────────┴────────────────────────┴────────────────┴\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌───────────────┬────────────────────────┬────────────────┬\n      │   MODEL_ID    │       MODEL_NAME       │ OS_VERSION_IDS │\n      ├───────────────┼────────────────────────┼────────────────┼\n      │  ipad5        │  iPad (5th generation) │      11.2      │\n      │  ipadmini4    │  iPad mini 4           │      11.2      │\n      │  ipadpro_105  │  iPad Pro (10.5-inch)  │      11.2      │\n      │  iphone6s     │  iPhone 6s             │    10.3,11.2   │\n      │  iphone6splus │  iPhone 6s Plus        │    9.0,9.1     │\n      │  iphone7      │  iPhone 7              │      11.2      │\n      │  iphone7plus  │  iPhone 7 Plus         │      11.2      │\n      │  iphone8      │  iPhone 8              │      11.2      │\n      │  iphone8plus  │  iPhone 8 Plus         │      11.2      │\n      │  iphonese     │  iPhone SE             │      11.2      │\n      │  iphonex      │  iPhone X              │      11.2      │\n      └───────────────┴────────────────────────┴────────────────┴\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: \"If this input is set to `true` all files generated in the test run will\n      be downloaded. Otherwise, no any file will be downloaded. \\n\"\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.3/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2018-10-24T13:16:35.099462686Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: a4f0b3a9a9e0f7bfd7cb24f524151594fc615f87\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌──────────────┬───────────────────────┬─────────────────────┐\n      │   MODEL_ID   │          MODEL_NAME   │    OS_VERSION_IDS   │\n      ├──────────────┼───────────────────────┼─────────────────────┤\n      │ ipad5        │ iPad (5th generation) │ 11.2,12.0           │\n      │ ipadmini4    │ iPad mini 4           │ 11.2,12.0           │\n      │ ipadpro_105  │ iPad Pro (10.5-inch)  │ 11.2                │\n      │ iphone6      │ iPhone 6              │ 11.4                │\n      │ iphone6s     │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │\n      │ iphone6splus │ iPhone 6s Plus        │ 9.0,9.1             │\n      │ iphone7      │ iPhone 7              │ 11.2,11.4,12.0      │\n      │ iphone7plus  │ iPhone 7 Plus         │ 11.2,11.4,12.0      │\n      │ iphone8      │ iPhone 8              │ 11.2,11.4,12.0      │\n      │ iphone8plus  │ iPhone 8 Plus         │ 11.2,11.4,12.0      │\n      │ iphonese     │ iPhone SE             │ 11.2,11.4,12.0      │\n      │ iphonex      │ iPhone X              │ 11.2,11.4,12.0      │\n      └──────────────┴───────────────────────┴─────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌──────────────┬───────────────────────┬─────────────────────┐\n      │   MODEL_ID   │          MODEL_NAME   │    OS_VERSION_IDS   │\n      ├──────────────┼───────────────────────┼─────────────────────┤\n      │ ipad5        │ iPad (5th generation) │ 11.2,12.0           │\n      │ ipadmini4    │ iPad mini 4           │ 11.2,12.0           │\n      │ ipadpro_105  │ iPad Pro (10.5-inch)  │ 11.2                │\n      │ iphone6      │ iPhone 6              │ 11.4                │\n      │ iphone6s     │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │\n      │ iphone6splus │ iPhone 6s Plus        │ 9.0,9.1             │\n      │ iphone7      │ iPhone 7              │ 11.2,11.4,12.0      │\n      │ iphone7plus  │ iPhone 7 Plus         │ 11.2,11.4,12.0      │\n      │ iphone8      │ iPhone 8              │ 11.2,11.4,12.0      │\n      │ iphone8plus  │ iPhone 8 Plus         │ 11.2,11.4,12.0      │\n      │ iphonese     │ iPhone SE             │ 11.2,11.4,12.0      │\n      │ iphonex      │ iPhone X              │ 11.2,11.4,12.0      │\n      └──────────────┴───────────────────────┴─────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.5/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2018-12-14T14:52:15.623406333Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 0a54e4959f0b8dd37bcc60e2d24a5c56407f344e\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌──────────────┬───────────────────────┬─────────────────────┐\n      │   MODEL_ID   │          MODEL_NAME   │    OS_VERSION_IDS   │\n      ├──────────────┼───────────────────────┼─────────────────────┤\n      │ ipad5        │ iPad (5th generation) │ 11.2,12.0           │\n      │ ipadmini4    │ iPad mini 4           │ 11.2,12.0           │\n      │ ipadpro_105  │ iPad Pro (10.5-inch)  │ 11.2                │\n      │ iphone6      │ iPhone 6              │ 11.4                │\n      │ iphone6s     │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │\n      │ iphone6splus │ iPhone 6s Plus        │ 9.0,9.1             │\n      │ iphone7      │ iPhone 7              │ 11.2,11.4,12.0      │\n      │ iphone7plus  │ iPhone 7 Plus         │ 11.2,11.4,12.0      │\n      │ iphone8      │ iPhone 8              │ 11.2,11.4,12.0      │\n      │ iphone8plus  │ iPhone 8 Plus         │ 11.2,11.4,12.0      │\n      │ iphonese     │ iPhone SE             │ 11.2,11.4,12.0      │\n      │ iphonex      │ iPhone X              │ 11.2,11.4,12.0      │\n      └──────────────┴───────────────────────┴─────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌──────────────┬───────────────────────┬─────────────────────┐\n      │   MODEL_ID   │          MODEL_NAME   │    OS_VERSION_IDS   │\n      ├──────────────┼───────────────────────┼─────────────────────┤\n      │ ipad5        │ iPad (5th generation) │ 11.2,12.0           │\n      │ ipadmini4    │ iPad mini 4           │ 11.2,12.0           │\n      │ ipadpro_105  │ iPad Pro (10.5-inch)  │ 11.2                │\n      │ iphone6      │ iPhone 6              │ 11.4                │\n      │ iphone6s     │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │\n      │ iphone6splus │ iPhone 6s Plus        │ 9.0,9.1             │\n      │ iphone7      │ iPhone 7              │ 11.2,11.4,12.0      │\n      │ iphone7plus  │ iPhone 7 Plus         │ 11.2,11.4,12.0      │\n      │ iphone8      │ iPhone 8              │ 11.2,11.4,12.0      │\n      │ iphone8plus  │ iPhone 8 Plus         │ 11.2,11.4,12.0      │\n      │ iphonese     │ iPhone SE             │ 11.2,11.4,12.0      │\n      │ iphonex      │ iPhone X              │ 11.2,11.4,12.0      │\n      └──────────────┴───────────────────────┴─────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    summary: |\n      The max time this test execution can run before it is cancelled. It does not include any time necessary to prepare and clean up the target device. The maximum possible testing time is 3600 seconds.\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.6/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2019-08-07T14:49:47.211789761Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: ccc8b41c92ed8c0b2edecdff3be9318d1446c768\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io.addons.required:\n  - addon_id:\"addons-firebase-testlab\": null\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌──────────────┬───────────────────────┬─────────────────────┐\n      │   MODEL_ID   │          MODEL_NAME   │    OS_VERSION_IDS   │\n      ├──────────────┼───────────────────────┼─────────────────────┤\n      │ ipad5        │ iPad (5th generation) │ 11.2,12.0           │\n      │ ipadmini4    │ iPad mini 4           │ 11.2,12.0           │\n      │ ipadpro_105  │ iPad Pro (10.5-inch)  │ 11.2                │\n      │ iphone6      │ iPhone 6              │ 11.4                │\n      │ iphone6s     │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │\n      │ iphone6splus │ iPhone 6s Plus        │ 9.0,9.1             │\n      │ iphone7      │ iPhone 7              │ 11.2,11.4,12.0      │\n      │ iphone7plus  │ iPhone 7 Plus         │ 11.2,11.4,12.0      │\n      │ iphone8      │ iPhone 8              │ 11.2,11.4,12.0      │\n      │ iphone8plus  │ iPhone 8 Plus         │ 11.2,11.4,12.0      │\n      │ iphonese     │ iPhone SE             │ 11.2,11.4,12.0      │\n      │ iphonex      │ iPhone X              │ 11.2,11.4,12.0      │\n      └──────────────┴───────────────────────┴─────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌──────────────┬───────────────────────┬─────────────────────┐\n      │   MODEL_ID   │          MODEL_NAME   │    OS_VERSION_IDS   │\n      ├──────────────┼───────────────────────┼─────────────────────┤\n      │ ipad5        │ iPad (5th generation) │ 11.2,12.0           │\n      │ ipadmini4    │ iPad mini 4           │ 11.2,12.0           │\n      │ ipadpro_105  │ iPad Pro (10.5-inch)  │ 11.2                │\n      │ iphone6      │ iPhone 6              │ 11.4                │\n      │ iphone6s     │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │\n      │ iphone6splus │ iPhone 6s Plus        │ 9.0,9.1             │\n      │ iphone7      │ iPhone 7              │ 11.2,11.4,12.0      │\n      │ iphone7plus  │ iPhone 7 Plus         │ 11.2,11.4,12.0      │\n      │ iphone8      │ iPhone 8              │ 11.2,11.4,12.0      │\n      │ iphone8plus  │ iPhone 8 Plus         │ 11.2,11.4,12.0      │\n      │ iphonese     │ iPhone SE             │ 11.2,11.4,12.0      │\n      │ iphonex      │ iPhone X              │ 11.2,11.4,12.0      │\n      └──────────────┴───────────────────────┴─────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.7/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2019-08-15T08:36:51.426197429Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: b71d0cf4352d6d9ee6eae3d78075eee4a0ab2d6f\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io.addons.required:\n  - addon_id:\"addons-firebase-testlab\": null\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │           TAGS           │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2          │\n      │ iphone6     │ iPhone 6              │ 11.4                │ deprecated=11.4          │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3,11.2     │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ default, deprecated=11.2 │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1           │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1           │                          │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │           TAGS           │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2          │\n      │ iphone6     │ iPhone 6              │ 11.4                │ deprecated=11.4          │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3,11.2     │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ default, deprecated=11.2 │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1           │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1           │                          │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/0.9.9/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2019-09-05T13:35:05.179956895Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 51013e9211f897e8c80052095a659cbbd2e1b562\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │           TAGS           │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2          │\n      │ iphone6     │ iPhone 6              │ 11.4                │ deprecated=11.4          │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3,11.2     │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ default, deprecated=11.2 │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1           │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1           │                          │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone7,11.2,en,portrait`\n\n      `iphone7,11.2,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │           TAGS           │\n      ├─────────────┼───────────────────────┼─────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadmini4   │ iPad mini 4           │ 11.2,12.0           │ deprecated=11.2          │\n      │ ipadpro_105 │ iPad Pro (10.5-inch)  │ 11.2                │ deprecated=11.2          │\n      │ iphone6     │ iPhone 6              │ 11.4                │ deprecated=11.4          │\n      │ iphone6s    │ iPhone 6s             │ 10.3,11.2,11.4,12.0 │ deprecated=10.3,11.2     │\n      │ iphone7     │ iPhone 7              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone7plus │ iPhone 7 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphone8     │ iPhone 8              │ 11.2,11.4,12.0      │ default, deprecated=11.2 │\n      │ iphone8plus │ iPhone 8 Plus         │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonese    │ iPhone SE             │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonex     │ iPhone X              │ 11.2,11.4,12.0      │ deprecated=11.2          │\n      │ iphonexs    │ iPhone XS             │ 12.0,12.1           │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.0,12.1           │                          │\n      └─────────────┴───────────────────────┴─────────────────────┴──────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone7,11.2,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.0.0/step.yml",
    "content": "title: '[BETA] iOS Device Testing'\nsummary: Run iOS XCUItests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices.\n  The minimal setup of this step would be to select test type.\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2021-09-20T14:29:14.049372151Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 3e9d8f7f971c296280df38e2c6d0e26962b20bcf\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone8,14.7,en,portrait`\n\n      `iphone8,14.7,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬───────────────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │         OS_VERSION_IDS        │           TAGS           │\n      ├─────────────┼───────────────────────┼───────────────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 14.1                          │ deprecated=14.1          │\n      │ ipadmini4   │ iPad mini 4           │ 14.1                          │ deprecated=14.1          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6                     │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.1,14.7                │ deprecated=14.1          │\n      │ iphone7plus │ iPhone 7 Plus         │ 14.1                          │ deprecated=14.1          │\n      │ iphone8     │ iPhone 8              │ 11.4,12.0,12.4,13.6,14.1,14.7 │ deprecated=14.1, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0                          │                          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2                     │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1                          │                          │\n      └─────────────┴───────────────────────┴───────────────────────────────┴──────────────────────────┘\n\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n\n      For example:\n\n      `iphone8,14.7,en,portrait`\n\n      `iphone8,14.7,en,landscape`\n\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬───────────────────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │         OS_VERSION_IDS        │           TAGS           │\n      ├─────────────┼───────────────────────┼───────────────────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 14.1                          │ deprecated=14.1          │\n      │ ipadmini4   │ iPad mini 4           │ 14.1                          │ deprecated=14.1          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6                     │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.1,14.7                │ deprecated=14.1          │\n      │ iphone7plus │ iPhone 7 Plus         │ 14.1                          │ deprecated=14.1          │\n      │ iphone8     │ iPhone 8              │ 11.4,12.0,12.4,13.6,14.1,14.7 │ deprecated=14.1, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0                          │                          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2                     │                          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1                          │                          │\n      └─────────────┴───────────────────────┴───────────────────────────────┴──────────────────────────┘\n\n      ```\n    title: Test devices\n  test_devices: iphone8,14.7,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.0.2/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUItests on devices\ndescription: \"Run iOS XCUItests on physical devices with Google's Firebase Test Lab.\n  You do not have to set up and register your own devices and you don't need your\n  own Firebase account.\\n\\nWe'll go over the most important configuration information\n  for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\\n\\n###\n  Configuring the Step \\n\\nTo use the Step, you need to build an IPA file with Xcode's\n  `build-for-testing` action. You can use our dedicated Step:\\n\\n1. Add the **Xcode\n  Build for testing for iOS** Step to your Workflow. \\n\\n   The Step exports a .zip\n  file that contains your test directory (by default, it’s `Debug-iphoneos`) and the\n  xctestrun file.\\n1. Add the **iOS Device Testing** Step to the Workflow.\\n1. In\n  the **Test devices** input field, specify the devices on which you want to test\n  the app.\\n1. Optionally, you can set a test timeout and configure file download\n  in the **Debug** input group. The path to the downloaded files will be exported\n  as an Environment Variable and it can be used by subsequent Steps. \\n1. Make sure\n  you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1\n  or newer. With the older versions of the Step, you won’t be able to check your results\n  on the Test Reports page!\\n\\nPlease note you should not change the value of the\n  **API token** and the **Test API's base URL** input. \\n\\n### Troubleshooting \\n\\nIf\n  you get the **Build already exists** error, it is because you have more than one\n  instance of the Step in your Workflow. This doesn't work as Bitrise sends the build\n  slug to Firebase and having the Step more than once in the same Workflow results\n  in sending the same build slug multiple times. \\n\\n### Useful links \\n\\n[Device\n  testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\\n\\n###\n  Related Steps \\n\\n[Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2022-06-14T10:28:45.431193216Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 6d9778e478468d524b1c10e7aea9f74af1f6f143\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │ OS_VERSION_IDS │           TAGS           │\n      ├─────────────┼───────────────────────┼────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4           │                          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4           │                          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6      │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.7      │                          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2           │                          │\n      │ iphone8     │ iPhone 8              │ 12.4,13.6,14.7 │ deprecated=12.4, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0           │ deprecated=12.0          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2      │ deprecated=12.4          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1           │ deprecated=12.1          │\n      └─────────────┴───────────────────────┴────────────────┴──────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │ OS_VERSION_IDS │           TAGS           │\n      ├─────────────┼───────────────────────┼────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4           │                          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4           │                          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6      │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.7      │                          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2           │                          │\n      │ iphone8     │ iPhone 8              │ 12.4,13.6,14.7 │ deprecated=12.4, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0           │ deprecated=12.0          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2      │ deprecated=12.4          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1           │ deprecated=12.1          │\n      └─────────────┴───────────────────────┴────────────────┴──────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone8,14.7,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.1.0/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUItests on devices\ndescription: \"Run iOS XCUItests on physical devices with Google's Firebase Test Lab.\n  You do not have to set up and register your own devices and you don't need your\n  own Firebase account.\\n\\nWe'll go over the most important configuration information\n  for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\\n\\n###\n  Configuring the Step \\n\\nTo use the Step, you need to build an IPA file with Xcode's\n  `build-for-testing` action. You can use our dedicated Step:\\n\\n1. Add the **Xcode\n  Build for testing for iOS** Step to your Workflow. \\n\\n   The Step exports a .zip\n  file that contains your test directory (by default, it’s `Debug-iphoneos`) and the\n  xctestrun file.\\n1. Add the **iOS Device Testing** Step to the Workflow.\\n1. In\n  the **Test devices** input field, specify the devices on which you want to test\n  the app.\\n1. Optionally, you can set a test timeout and configure file download\n  in the **Debug** input group. The path to the downloaded files will be exported\n  as an Environment Variable and it can be used by subsequent Steps. \\n1. Make sure\n  you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1\n  or newer. With the older versions of the Step, you won’t be able to check your results\n  on the Test Reports page!\\n\\nPlease note you should not change the value of the\n  **API token** and the **Test API's base URL** input. \\n\\n### Troubleshooting \\n\\nIf\n  you get the **Build already exists** error, it is because you have more than one\n  instance of the Step in your Workflow. This doesn't work as Bitrise sends the build\n  slug to Firebase and having the Step more than once in the same Workflow results\n  in sending the same build slug multiple times. \\n\\n### Useful links \\n\\n[Device\n  testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\\n\\n###\n  Related Steps \\n\\n[Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2022-09-06T13:15:14.55247141Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: a30f92e220356609b5f0e5d51e426de904e3ba1c\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │ OS_VERSION_IDS │           TAGS           │\n      ├─────────────┼───────────────────────┼────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4           │                          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4           │                          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6      │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.7      │                          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2           │                          │\n      │ iphone8     │ iPhone 8              │ 12.4,13.6,14.7 │ deprecated=12.4, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0           │ deprecated=12.0          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2      │ deprecated=12.4          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1           │ deprecated=12.1          │\n      └─────────────┴───────────────────────┴────────────────┴──────────────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │ OS_VERSION_IDS │           TAGS           │\n      ├─────────────┼───────────────────────┼────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4           │                          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4           │                          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6      │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.7      │                          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2           │                          │\n      │ iphone8     │ iPhone 8              │ 12.4,13.6,14.7 │ deprecated=12.4, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0           │ deprecated=12.0          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2      │ deprecated=12.4          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1           │ deprecated=12.1          │\n      └─────────────┴───────────────────────┴────────────────┴──────────────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone8,14.7,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.1.1/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUItests on devices\ndescription: \"Run iOS XCUItests on physical devices with Google's Firebase Test Lab.\n  You do not have to set up and register your own devices and you don't need your\n  own Firebase account.\\n\\nWe'll go over the most important configuration information\n  for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\\n\\n###\n  Configuring the Step \\n\\nTo use the Step, you need to build an IPA file with Xcode's\n  `build-for-testing` action. You can use our dedicated Step:\\n\\n1. Add the **Xcode\n  Build for testing for iOS** Step to your Workflow. \\n\\n   The Step exports a .zip\n  file that contains your test directory (by default, it’s `Debug-iphoneos`) and the\n  xctestrun file.\\n1. Add the **iOS Device Testing** Step to the Workflow.\\n1. In\n  the **Test devices** input field, specify the devices on which you want to test\n  the app.\\n1. Optionally, you can set a test timeout and configure file download\n  in the **Debug** input group. The path to the downloaded files will be exported\n  as an Environment Variable and it can be used by subsequent Steps. \\n1. Make sure\n  you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1\n  or newer. With the older versions of the Step, you won’t be able to check your results\n  on the Test Reports page!\\n\\nPlease note you should not change the value of the\n  **API token** and the **Test API's base URL** input. \\n\\n### Troubleshooting \\n\\nIf\n  you get the **Build already exists** error, it is because you have more than one\n  instance of the Step in your Workflow. This doesn't work as Bitrise sends the build\n  slug to Firebase and having the Step more than once in the same Workflow results\n  in sending the same build slug multiple times. \\n\\n### Useful links \\n\\n[Device\n  testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\\n\\n###\n  Related Steps \\n\\n[Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2022-09-19T18:25:25.773015875Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 7807a82a8a16b0d1b148ae3fed450e46fb5ed44e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │ OS_VERSION_IDS │           TAGS           │\n      ├─────────────┼───────────────────────┼────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4           │                          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4           │                          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6      │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.7.     │                          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2           │                          │\n      │ iphone8     │ iPhone 8              │ 12.4,13.6,14.7 │ deprecated=12.4, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0           │ deprecated=12.0          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2      │ deprecated=12.4          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1           │ deprecated=12.1          │\n      └─────────────┴───────────────────────┴────────────────┴──────────────────────────┘\n      ```\n\n      Device and OS Capacity\n      ```\n      ┌─────────────┬───────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME      │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼───────────────────────┼───────────────┼─────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4          │ Low             │\n      │ ipadmini4   │ iPad mini 4           │ 15.4          │ Medium          │\n      │ iphone11    │ iPhone 11             │ 13.3          │ Medium          │\n      │ iphone11    │ iPhone 11             │ 13.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 12.4          │ High            │\n      │ iphone8     │ iPhone 8              │ 13.6          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 14.7          │ Medium          │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0          │ Medium          │\n      │ iphonexr    │ iPhone XR             │ 12.4          │ Medium          │\n      │ iphonexr    │ iPhone XR             │ 13.2          │ Medium          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1          │ Low             │\n      └─────────────┴───────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬────────────────┬──────────────────────────┐\n      │   MODEL_ID  │          NAME         │ OS_VERSION_IDS │           TAGS           │\n      ├─────────────┼───────────────────────┼────────────────┼──────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4           │                          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4           │                          │\n      │ iphone11    │ iPhone 11             │ 13.3,13.6      │                          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3,14.7.     │                          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2           │                          │\n      │ iphone8     │ iPhone 8              │ 12.4,13.6,14.7 │ deprecated=12.4, default │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0           │ deprecated=12.0          │\n      │ iphonexr    │ iPhone XR             │ 12.4,13.2      │ deprecated=12.4          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1           │ deprecated=12.1          │\n      └─────────────┴───────────────────────┴────────────────┴──────────────────────────┘\n      ```\n\n      Device and OS Capacity\n      ```\n      ┌─────────────┬───────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME      │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼───────────────────────┼───────────────┼─────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4          │ Low             │\n      │ ipadmini4   │ iPad mini 4           │ 15.4          │ Medium          │\n      │ iphone11    │ iPhone 11             │ 13.3          │ Medium          │\n      │ iphone11    │ iPhone 11             │ 13.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 13.3          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 12.4          │ High            │\n      │ iphone8     │ iPhone 8              │ 13.6          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 14.7          │ Medium          │\n      │ iphone8plus │ iPhone 8 Plus         │ 12.0          │ Medium          │\n      │ iphonexr    │ iPhone XR             │ 12.4          │ Medium          │\n      │ iphonexr    │ iPhone XR             │ 13.2          │ Medium          │\n      │ iphonexsmax │ iPhone XS Max         │ 12.1          │ Low             │\n      └─────────────┴───────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone8,14.7,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.1.2/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUItests on devices\ndescription: \"Run iOS XCUItests on physical devices with Google's Firebase Test Lab.\n  You do not have to set up and register your own devices and you don't need your\n  own Firebase account.\\n\\nWe'll go over the most important configuration information\n  for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\\n\\n###\n  Configuring the Step \\n\\nTo use the Step, you need to build an IPA file with Xcode's\n  `build-for-testing` action. You can use our dedicated Step:\\n\\n1. Add the **Xcode\n  Build for testing for iOS** Step to your Workflow. \\n\\n   The Step exports a .zip\n  file that contains your test directory (by default, it’s `Debug-iphoneos`) and the\n  xctestrun file.\\n1. Add the **iOS Device Testing** Step to the Workflow.\\n1. In\n  the **Test devices** input field, specify the devices on which you want to test\n  the app.\\n1. Optionally, you can set a test timeout and configure file download\n  in the **Debug** input group. The path to the downloaded files will be exported\n  as an Environment Variable and it can be used by subsequent Steps. \\n1. Make sure\n  you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1\n  or newer. With the older versions of the Step, you won’t be able to check your results\n  on the Test Reports page!\\n\\nPlease note you should not change the value of the\n  **API token** and the **Test API's base URL** input. \\n\\n### Troubleshooting \\n\\nIf\n  you get the **Build already exists** error, it is because you have more than one\n  instance of the Step in your Workflow. This doesn't work as Bitrise sends the build\n  slug to Firebase and having the Step more than once in the same Workflow results\n  in sending the same build slug multiple times. \\n\\n### Useful links \\n\\n[Device\n  testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\\n\\n###\n  Related Steps \\n\\n[Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2023-09-01T08:03:51.699253983Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 23afff488e39b24b225a02cbd3bb51c90542a1c6\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬─────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS              │\n      ├─────────────┼───────────────────────┼─────────────────────┼─────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4                │ reduced_stability=15.4          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4                │                                 │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7,16.5,16.6      │ deprecated=16.5                 │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8                │                                 │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2,15.7           │ reduced_stability=15.2, default │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5,16.6           │ deprecated=16.5                 │\n      │ iphone8     │ iPhone 8              │ 14.7,15.7,16.5,16.6 │ deprecated=16.5                 │\n      └─────────────┴───────────────────────┴─────────────────────┴─────────────────────────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬───────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME      │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼───────────────────────┼───────────────┼─────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4          │ Low             │\n      │ ipadmini4   │ iPad mini 4           │ 15.4          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.5          │ High            │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.6          │ Medium          │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2          │ Low             │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.7          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.6          │ Low             │\n      │ iphone8     │ iPhone 8              │ 14.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 16.5          │ High            │\n      │ iphone8     │ iPhone 8              │ 16.6          │ Medium          │\n      └─────────────┴───────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬─────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS              │\n      ├─────────────┼───────────────────────┼─────────────────────┼─────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4                │ reduced_stability=15.4          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4                │                                 │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7,16.5,16.6      │ deprecated=16.5                 │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8                │                                 │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2,15.7           │ reduced_stability=15.2, default │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5,16.6           │ deprecated=16.5                 │\n      │ iphone8     │ iPhone 8              │ 14.7,15.7,16.5,16.6 │ deprecated=16.5                 │\n      └─────────────┴───────────────────────┴─────────────────────┴─────────────────────────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬───────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME      │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼───────────────────────┼───────────────┼─────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4          │ Low             │\n      │ ipadmini4   │ iPad mini 4           │ 15.4          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.5          │ High            │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.6          │ Medium          │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2          │ Low             │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.7          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.6          │ Low             │\n      │ iphone8     │ iPhone 8              │ 14.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 16.5          │ High            │\n      │ iphone8     │ iPhone 8              │ 16.6          │ Medium          │\n      └─────────────┴───────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone8,14.7,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.1.3/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUItests on devices\ndescription: \"Run iOS XCUItests on physical devices with Google's Firebase Test Lab.\n  You do not have to set up and register your own devices and you don't need your\n  own Firebase account.\\n\\nWe'll go over the most important configuration information\n  for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\\n\\n###\n  Configuring the Step \\n\\nTo use the Step, you need to build an IPA file with Xcode's\n  `build-for-testing` action. You can use our dedicated Step:\\n\\n1. Add the **Xcode\n  Build for testing for iOS** Step to your Workflow. \\n\\n   The Step exports a .zip\n  file that contains your test directory (by default, it’s `Debug-iphoneos`) and the\n  xctestrun file.\\n1. Add the **iOS Device Testing** Step to the Workflow.\\n1. In\n  the **Test devices** input field, specify the devices on which you want to test\n  the app.\\n1. Optionally, you can set a test timeout and configure file download\n  in the **Debug** input group. The path to the downloaded files will be exported\n  as an Environment Variable and it can be used by subsequent Steps. \\n1. Make sure\n  you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1\n  or newer. With the older versions of the Step, you won’t be able to check your results\n  on the Test Reports page!\\n\\nPlease note you should not change the value of the\n  **API token** and the **Test API's base URL** input. \\n\\n### Troubleshooting \\n\\nIf\n  you get the **Build already exists** error, it is because you have more than one\n  instance of the Step in your Workflow. This doesn't work as Bitrise sends the build\n  slug to Firebase and having the Step more than once in the same Workflow results\n  in sending the same build slug multiple times. \\n\\n### Useful links \\n\\n[Device\n  testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\\n\\n###\n  Related Steps \\n\\n[Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n[Xcode\n  Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2024-05-31T07:35:31.719067856Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: e48b12c8bf422b6a5d2b1c02daa0d52e7e95c13a\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬─────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS              │\n      ├─────────────┼───────────────────────┼─────────────────────┼─────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4                │ reduced_stability=15.4          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4                │                                 │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7,16.5,16.6      │ deprecated=16.5                 │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8                │                                 │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2,15.7           │ reduced_stability=15.2, default │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5,16.6           │ deprecated=16.5                 │\n      │ iphone8     │ iPhone 8              │ 14.7,15.7,16.5,16.6 │ deprecated=16.5                 │\n      └─────────────┴───────────────────────┴─────────────────────┴─────────────────────────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬───────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME      │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼───────────────────────┼───────────────┼─────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4          │ Low             │\n      │ ipadmini4   │ iPad mini 4           │ 15.4          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.5          │ High            │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.6          │ Medium          │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2          │ Low             │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.7          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.6          │ Low             │\n      │ iphone8     │ iPhone 8              │ 14.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 16.5          │ High            │\n      │ iphone8     │ iPhone 8              │ 16.6          │ Medium          │\n      └─────────────┴───────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬───────────────────────┬─────────────────────┬─────────────────────────────────┐\n      │   MODEL_ID  │          NAME         │    OS_VERSION_IDS   │               TAGS              │\n      ├─────────────┼───────────────────────┼─────────────────────┼─────────────────────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4                │ reduced_stability=15.4          │\n      │ ipadmini4   │ iPad mini 4           │ 15.4                │                                 │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7,16.5,16.6      │ deprecated=16.5                 │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8                │                                 │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2,15.7           │ reduced_stability=15.2, default │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5,16.6           │ deprecated=16.5                 │\n      │ iphone8     │ iPhone 8              │ 14.7,15.7,16.5,16.6 │ deprecated=16.5                 │\n      └─────────────┴───────────────────────┴─────────────────────┴─────────────────────────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬───────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME      │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼───────────────────────┼───────────────┼─────────────────┤\n      │ ipad5       │ iPad (5th generation) │ 15.4          │ Low             │\n      │ ipadmini4   │ iPad mini 4           │ 15.4          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro         │ 14.7          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.5          │ High            │\n      │ iphone11pro │ iPhone 11 Pro         │ 16.6          │ Medium          │\n      │ iphone12pro │ iPhone 12 Pro         │ 14.8          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.2          │ Low             │\n      │ iphone13pro │ iPhone 13 Pro         │ 15.7          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.5          │ High            │\n      │ iphone14pro │ iPhone 14 Pro         │ 16.6          │ Low             │\n      │ iphone8     │ iPhone 8              │ 14.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8              │ 16.5          │ High            │\n      │ iphone8     │ iPhone 8              │ 16.6          │ Medium          │\n      └─────────────┴───────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone8,14.7,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.2.0/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUITests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices with Google's Firebase Test Lab. You do not have to set up and register your own devices and you don't need your own Firebase account.\n\n  We'll go over the most important configuration information for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\n\n  ### Configuring the Step\n\n  To use the Step, you need to build an IPA file with Xcode's `build-for-testing` action. You can use our dedicated Step:\n\n  1. Add the **Xcode Build for testing for iOS** Step to your Workflow.\n\n     The Step exports a .zip file that contains your test directory (by default, it’s `Debug-iphoneos`) and the xctestrun file.\n  1. Add the **iOS Device Testing** Step to the Workflow.\n  1. In the **Test devices** input field, specify the devices on which you want to test the app.\n  1. Optionally, you can set a test timeout and configure file download in the **Debug** input group. The path to the downloaded files will be exported as an Environment Variable and it can be used by subsequent Steps.\n  1. Make sure you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1 or newer. With the older versions of the Step, you won’t be able to check your results on the Test Reports page!\n\n  Please note you should not change the value of the **API token** and the **Test API's base URL** input.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  [Device testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\n\n  ### Related Steps\n\n  [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2025-06-16T11:52:32.557006707Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: abc2b0100fadd5828f946d8712703121eeeeadf7\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Low             │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ Medium          │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ Medium          │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Low             │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ Medium          │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone13pro,16.6,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.3.0/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUITests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices with Google's Firebase Test Lab. You do not have to set up and register your own devices and you don't need your own Firebase account.\n\n  We'll go over the most important configuration information for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\n\n  ### Configuring the Step\n\n  To use the Step, you need to build an IPA file with Xcode's `build-for-testing` action. You can use our dedicated Step:\n\n  1. Add the **Xcode Build for testing for iOS** Step to your Workflow.\n\n     The Step exports a .zip file that contains your test directory (by default, it’s `Debug-iphoneos`) and the xctestrun file.\n  1. Add the **iOS Device Testing** Step to the Workflow.\n  1. In the **Test devices** input field, specify the devices on which you want to test the app.\n  1. Optionally, you can set a test timeout and configure file download in the **Debug** input group. The path to the downloaded files will be exported as an Environment Variable and it can be used by subsequent Steps.\n  1. Make sure you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1 or newer. With the older versions of the Step, you won’t be able to check your results on the Test Reports page!\n\n  Please note you should not change the value of the **API token** and the **Test API's base URL** input.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  [Device testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\n\n  ### Related Steps\n\n  [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2025-08-11T07:40:40.804813206Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 393566b79d9f02dc37b336a7e4bff58a560f5e83\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ High            │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Low             │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ High            │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone13pro,16.6,en,portrait\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that\n      initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.3.1/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUITests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices with Google's Firebase Test Lab. You do not have to set up and register your own devices and you don't need your own Firebase account.\n\n  We'll go over the most important configuration information for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\n\n  ### Configuring the Step\n\n  To use the Step, you need to build an IPA file with Xcode's `build-for-testing` action. You can use our dedicated Step:\n\n  1. Add the **Xcode Build for testing for iOS** Step to your Workflow.\n\n     The Step exports a .zip file that contains your test directory (by default, it’s `Debug-iphoneos`) and the xctestrun file.\n  1. Add the **iOS Device Testing** Step to the Workflow.\n  1. In the **Test devices** input field, specify the devices on which you want to test the app.\n  1. Optionally, you can set a test timeout and configure file download in the **Debug** input group. The path to the downloaded files will be exported as an Environment Variable and it can be used by subsequent Steps.\n  1. Make sure you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1 or newer. With the older versions of the Step, you won’t be able to check your results on the Test Reports page!\n\n  Please note you should not change the value of the **API token** and the **Test API's base URL** input.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  [Device testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\n\n  ### Related Steps\n\n  [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2025-09-12T12:06:47.680689182Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 94898f33cf8614f347258fd0455feab57dc8d5ae\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ High            │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ High            │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone13pro,16.6,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.4.0/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUITests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices with Google's Firebase Test Lab. You do not have to set up and register your own devices and you don't need your own Firebase account.\n\n  We'll go over the most important configuration information for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\n\n  ### Configuring the Step\n\n  To use the Step, you need to build an IPA file with Xcode's `build-for-testing` action. You can use our dedicated Step:\n\n  1. Add the **Xcode Build for testing for iOS** Step to your Workflow.\n\n     The Step exports a .zip file that contains your test directory (by default, it’s `Debug-iphoneos`) and the xctestrun file.\n  1. Add the **iOS Device Testing** Step to the Workflow.\n  1. In the **Test devices** input field, specify the devices on which you want to test the app.\n  1. Optionally, you can set a test timeout and configure file download in the **Debug** input group. The path to the downloaded files will be exported as an Environment Variable and it can be used by subsequent Steps.\n  1. Make sure you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1 or newer. With the older versions of the Step, you won’t be able to check your results on the Test Reports page!\n\n  Please note you should not change the value of the **API token** and the **Test API's base URL** input.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  [Device testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\n\n  ### Related Steps\n\n  [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2025-10-01T09:35:53.976412952Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: f7ea94fb8feea5bb49a68e3bde8c08905a405c39\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ Medium          │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │     TAGS     │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │              │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │              │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ default      │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │              │\n      │ iphone15    │ iPhone 15              │ 18.0           │ preview=18.0 │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ preview=18.0 │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │              │\n      └─────────────┴────────────────────────┴────────────────┴──────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ Medium          │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone13pro,16.6,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/1.4.1/step.yml",
    "content": "title: iOS Device Testing\nsummary: Run iOS XCUITests on devices\ndescription: |-\n  Run iOS XCUItests on physical devices with Google's Firebase Test Lab. You do not have to set up and register your own devices and you don't need your own Firebase account.\n\n  We'll go over the most important configuration information for the Step. For more information, check out our [detailed guide](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html).\n\n  ### Configuring the Step\n\n  To use the Step, you need to build an IPA file with Xcode's `build-for-testing` action. You can use our dedicated Step:\n\n  1. Add the **Xcode Build for testing for iOS** Step to your Workflow.\n\n     The Step exports a .zip file that contains your test directory (by default, it’s `Debug-iphoneos`) and the xctestrun file.\n  1. Add the **iOS Device Testing** Step to the Workflow.\n  1. In the **Test devices** input field, specify the devices on which you want to test the app.\n  1. Optionally, you can set a test timeout and configure file download in the **Debug** input group. The path to the downloaded files will be exported as an Environment Variable and it can be used by subsequent Steps.\n  1. Make sure you have the **Deploy to Bitrise.io** Step in your Workflow, with version 1.4.1 or newer. With the older versions of the Step, you won’t be able to check your results on the Test Reports page!\n\n  Please note you should not change the value of the **API token** and the **Test API's base URL** input.\n\n  ### Troubleshooting\n\n  If you get the **Build already exists** error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.\n\n  ### Useful links\n\n  [Device testing for iOS](https://devcenter.bitrise.io/en/testing/device-testing-for-ios.html)\n\n  ### Related Steps\n\n  [Xcode Build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/issues\npublished_at: 2025-11-11T08:06:55.089821797Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios.git\n  commit: 3696376fc79744f11df3ef289fe86151a25aa546\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-virtual-device-testing-for-ios\nis_always_run: false\nis_skippable: false\nrun_if: .IsCI\nmeta:\n  bitrise.io:\n    addons_required:\n    - addons-testing\ninputs:\n- opts:\n    description: |\n      Open finder, and navigate to the directory you designated for Derived Data output.\n      Open the folder for your project, then the Build/Products folders inside it.\n      You should see a folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun. Select them both, then right-click on one of them and select Compress 2 items.\n    is_required: true\n    summary: |\n      The path to the zip file which contains the folder Debug-iphoneos and PROJECT_NAME_iphoneos_DEVELOPMENT_TARGET-arm64.xctestrun.\n    title: Zip path\n  zip_path: $BITRISE_TEST_BUNDLE_ZIP_PATH\n- opts:\n    description: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────────────────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │               TAGS               │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────────────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │                                  │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │                                  │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ deprecated=15.7, deprecated=16.6 │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │                                  │\n      │ iphone15    │ iPhone 15              │ 18.0           │ deprecated=18.0                  │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ deprecated=18.0                  │\n      │ iphone16pro │ iPhone 16 Pro          │ 18.3           │ default                          │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │ deprecated=15.7                  │\n      │ iphonese3   │ iPhone SE 3            │ 18.4           │                                  │\n      └─────────────┴────────────────────────┴────────────────┴──────────────────────────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone16pro │ iPhone 16 Pro          │ 18.3          │ High            │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ Medium          │\n      │ iphonese3   │ iPhone SE 3            │ 18.4          │ Medium          │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    is_required: true\n    summary: |\n      Format:\n      One device configuration per line and the parameters are separated with `,` in the order of: `deviceID,version,language,orientation`\n      For example:\n      `iphone8,14.7,en,portrait`\n      `iphone8,14.7,en,landscape`\n      Available devices and its versions:\n      ```\n      ┌─────────────┬────────────────────────┬────────────────┬──────────────────────────────────┐\n      │   MODEL_ID  │          NAME          │ OS_VERSION_IDS │               TAGS               │\n      ├─────────────┼────────────────────────┼────────────────┼──────────────────────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6           │                                  │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6           │                                  │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7,16.6      │ deprecated=15.7, deprecated=16.6 │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6           │                                  │\n      │ iphone15    │ iPhone 15              │ 18.0           │ deprecated=18.0                  │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0           │ deprecated=18.0                  │\n      │ iphone16pro │ iPhone 16 Pro          │ 18.3           │ default                          │\n      │ iphone8     │ iPhone 8               │ 15.7,16.6      │ deprecated=15.7                  │\n      │ iphonese3   │ iPhone SE 3            │ 18.4           │                                  │\n      └─────────────┴────────────────────────┴────────────────┴──────────────────────────────────┘\n      ```\n\n      Device and OS Capacity:\n      ```\n      ┌─────────────┬────────────────────────┬───────────────┬─────────────────┐\n      │   MODEL_ID  │       MODEL_NAME       │ OS_VERSION_ID │ DEVICE_CAPACITY │\n      ├─────────────┼────────────────────────┼───────────────┼─────────────────┤\n      │ ipad10      │ iPad (10th generation) │ 16.6          │ Medium          │\n      │ iphone11pro │ iPhone 11 Pro          │ 16.6          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 15.7          │ High            │\n      │ iphone13pro │ iPhone 13 Pro          │ 16.6          │ High            │\n      │ iphone14pro │ iPhone 14 Pro          │ 16.6          │ High            │\n      │ iphone15    │ iPhone 15              │ 18.0          │ Medium          │\n      │ iphone15pro │ iPhone 15 Pro          │ 18.0          │ Medium          │\n      │ iphone16pro │ iPhone 16 Pro          │ 18.3          │ High            │\n      │ iphone8     │ iPhone 8               │ 15.7          │ Medium          │\n      │ iphone8     │ iPhone 8               │ 16.6          │ Medium          │\n      │ iphonese3   │ iPhone SE 3            │ 18.4          │ Medium          │\n      └─────────────┴────────────────────────┴───────────────┴─────────────────┘\n      ```\n    title: Test devices\n  test_devices: iphone13pro,16.6,en,portrait\n- num_flaky_test_attempts: \"0\"\n  opts:\n    description: |-\n      Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason.\n\n      An execution that initially fails but succeeds on any reattempt is reported as FLAKY.\n      The maximum number of reruns allowed is 10. (Default: 0, which implies no reruns.)\n    is_required: true\n    summary: Specifies the number of times a test execution should be reattempted\n      if one or more of its test cases fail for any reason.\n    title: Number of times a test execution is reattempted\n- opts:\n    category: Debug\n    description: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    summary: |\n      Max time a test execution is allowed to run before it is automatically canceled. The default value is 900 (15 min).  Duration in seconds with up to nine fractional digits. Example: \"3.5\".\n    title: Test timeout\n  test_timeout: 900\n- download_test_results: \"false\"\n  opts:\n    category: Debug\n    description: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    is_required: true\n    summary: |\n      If this input is set to `true` all files generated in the test run will be downloaded. Otherwise, no any file will be downloaded.\n    title: Download files\n    value_options:\n    - \"false\"\n    - \"true\"\n- api_base_url: https://vdt.bitrise.io/test\n  opts:\n    category: Debug\n    description: |\n      The URL where test API is accessible.\n    is_dont_change_value: true\n    is_required: true\n    summary: The URL where test API is accessible.\n    title: Test API's base URL\n- api_token: $ADDON_VDTESTING_API_TOKEN\n  opts:\n    category: Debug\n    description: |\n      The token required to authenticate with the API.\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: The token required to authenticate with the API.\n    title: API Token\n- opts:\n    category: Debug\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- VDTESTING_DOWNLOADED_FILES_DIR: null\n  opts:\n    description: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    summary: The directory containing the downloaded files if you have set `download_test_results`\n      inputs above.\n    title: Downloaded files directory\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A list of flaky test cases. A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestSuit_1.TestClass_1.TestName_1\n      - TestSuit_1.TestClass_1.TestName_2\n      - TestSuit_1.TestClass_2.TestName_1\n      - TestSuit_2.TestClass_1.TestName_1\n      ...\n      ```\n\n      To export `BITRISE_FLAKY_TEST_CASES` Step Output `download_test_results` Step Input should be set to `true`.\n    summary: A list of flaky test cases. A test case is considered flaky if it has\n      failed at least once, but passed at least once as well.\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/virtual-device-testing-for-ios/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/vpnc-connect/1.0.0/step.yml",
    "content": "title: Cisco VPN connect\nsummary: Connects with Cisco VPN provided by VPN3000 Concentrator, Juniper/Netscreen,\n  IOS and PIX using vpnc\ndescription: |-\n  VPN client settings and credentials can be provided in several ways:\n  - existing config file `/etc/vpnc.conf`\n  - commandline options input in this step\n  - config file content input in this step\n  More info about available configuration options and settings resolution order can be found on\n  [vpnc homepage](https://www.unix-ag.uni-kl.de/~massar/vpnc/) and [manual](https://linux.die.net/man/8/vpnc).\nwebsite: https://github.com/DroidsOnRoids/bitrise-step-vpnc-connect\nsource_code_url: https://github.com/DroidsOnRoids/bitrise-step-vpnc-connect\nsupport_url: https://github.com/DroidsOnRoids/bitrise-step-vpnc-connect/issues\npublished_at: 2017-06-28T09:23:25.879160231Z\nsource:\n  git: https://github.com/DroidsOnRoids/bitrise-step-vpnc-connect.git\n  commit: 96e95a537e0621ca3a0cc7dbb974d40b71c78b45\ntype_tags:\n- utility\ndeps:\n  apt_get:\n  - name: vpnc\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- commandline_options: null\n  opts:\n    description: |\n      Options specified here will take precedence over config files.\n    summary: vpnc commandline options\n    title: Commandline options\n- config_file_content: null\n  opts:\n    description: |\n      If not empty, value will be saved to `/etc/vpnc/default.conf` overwriting existing file.\n    is_expand: false\n    summary: Default config file content\n    title: Config file content\n"
  },
  {
    "path": "steps/vpnc-connect/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/wait-for-android-emulator/0.9.0/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains `start-android-emulator` step,\n  and you've set `wait_for_boot` param to false, use this step to check\n  if android emulator is booted or wait for finishing boot.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2017-02-14T15:30:57.907238373+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 9d5fdffa349aea2fa04dc5845c3e1de57cc1b7d0\nhost_os_tags:\n- ubuntu\nproject_type_tags:\n- android\ntype_tags:\n- emulator\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"180\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.0/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains `start-android-emulator` step,\n  and you've set `wait_for_boot` param to false, use this step to check\n  if android emulator is booted or wait for finishing boot.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2017-03-22T15:26:02.122894843+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: db746a6681bb14ef2e9aca5d7a97eb45c160a8cd\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"180\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.1/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains `start-android-emulator` step,\n  and you've set `wait_for_boot` param to false, use this step to check\n  if android emulator is booted or wait for finishing boot.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2017-03-28T17:08:38.348501225+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 100d8e5882f2ecf0f593b6dfd41c3f7043e17b1e\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"180\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.2/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains `start-android-emulator` step,\n  and you've set `wait_for_boot` param to false, use this step to check\n  if android emulator is booted or wait for finishing boot.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2017-05-08T17:33:33.147675559+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 2d5dbea8cce7c7dee3b8323f229d90090cec4627\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"300\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.3/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains `start-android-emulator` step,\n  and you've set `wait_for_boot` param to false, use this step to check\n  if android emulator is booted or wait for finishing boot.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2017-12-22T10:14:27.364170534+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 9eef4d5dcfcd9cab56861ae478639cb826dfffed\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"300\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.4/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains `start-android-emulator` step,\n  and you've set `wait_for_boot` param to false, use this step to check\n  if android emulator is booted or wait for finishing boot.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2018-02-01T15:19:09.301912729+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: aa012fca46f8fee56a0fd162a17baa2505ad472e\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"300\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.5/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains the `start-android-emulator` step,\n  and you've set the `wait_for_boot` parameter to `false`, use this step to check\n  if the android emulator is booted or wait for it to finish booting.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2021-06-24T11:53:10.086732008Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 0f5ab61ccfa07a08c46ac5d8685e2b36b4e5af92\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"300\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.6/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your workflow contains the `start-android-emulator` step,\n  and you've set the `wait_for_boot` parameter to `false`, use this step to check\n  if the android emulator is booted or wait for it to finish booting.\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2021-08-10T11:45:17.328641887Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 0e8a878c111c4dd9a2da9f18473e41d524ea7056\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: \"300\"\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android sdk path\n    is_required: true\n    title: Android sdk path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.7/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your Workflow contains the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step,\n  you can use this Step to check if the Android emulator is booted or wait for it to finish booting.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Make sure to add this Step after the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step.\n  1. Add the emulator's serial to the **Emulator serial** input. By default, this is set to the `$BITRISE_EMULATOR_SERIAL` Env Var, which is generated by the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step.\n  1. Specify the number of seconds the Step should wait for the emulator to boot in the **Waiting timeout (secs)** input.\n  1. Specify the location of the Android SDK in the **Android SDK path** input.\n\n  ### Useful links\n\n  * [Run tests using the Android emulator](https://devcenter.bitrise.io/en/steps-and-workflows/workflow-recipes-for-android-apps/-android--run-tests-using-the-emulator.html)\n  * [Workflow recipe: Run tests using the Android emulator](https://devcenter.bitrise.io/en/steps-and-workflows/workflow-recipes-for-android-apps/-android--run-tests-using-the-emulator.html)\n\n  ### Related Steps\n\n  * [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager)\n  * [Gradel Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2022-07-07T09:55:04.60115123Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 1eeccee0d07ed95a63ef10674fbe65115364c51e\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: 300\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android SDK path\n    is_required: true\n    title: Android SDK path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.8/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your Workflow contains the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step,\n  you can use this Step to check if the Android emulator is booted or wait for it to finish booting.\n\n  **Warning:** This Step is not yet supported on Apple Silicon (M1) machines. If you cannot find a solution to this error, try running this Workflow on an Intel-based machine type.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Make sure to add this Step after the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step.\n  1. Add the emulator's serial to the **Emulator serial** input. By default, this is set to the `$BITRISE_EMULATOR_SERIAL` Env Var, which is generated by the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step.\n  1. Specify the number of seconds the Step should wait for the emulator to boot in the **Waiting timeout (secs)** input.\n  1. Specify the location of the Android SDK in the **Android SDK path** input.\n\n  ### Useful links\n\n  * [Run tests using the Android emulator](https://devcenter.bitrise.io/en/steps-and-workflows/workflow-recipes-for-android-apps/-android--run-tests-using-the-emulator.html)\n  * [Workflow recipe: Run tests using the Android emulator](https://devcenter.bitrise.io/en/steps-and-workflows/workflow-recipes-for-android-apps/-android--run-tests-using-the-emulator.html)\n\n  ### Related Steps\n\n  * [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager)\n  * [Gradel Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2022-07-18T09:55:41.572738-05:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: 5cd6329df83a84cbf9e43b61827e1033422fd0b8\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: 300\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android SDK path\n    is_required: true\n    title: Android SDK path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/1.0.9/step.yml",
    "content": "title: Wait for Android emulator\nsummary: Wait for the emulator to finish boot\ndescription: |-\n  If your Workflow contains the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step,\n  you can use this Step to check if the Android emulator is booted or wait for it to finish booting.\n\n  **Warning:** This Step is not yet supported on Apple Silicon (M1) machines. If you cannot find a solution to this error, try running this Workflow on an Intel-based machine type.\n\n  ### Configuring the Step\n\n  To configure the Step:\n\n  1. Make sure to add this Step after the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step.\n  1. Add the emulator's serial to the **Emulator serial** input. By default, this is set to the `$BITRISE_EMULATOR_SERIAL` Env Var, which is generated by the [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager) Step.\n  1. Specify the number of seconds the Step should wait for the emulator to boot in the **Waiting timeout (secs)** input.\n  1. Specify the location of the Android SDK in the **Android SDK path** input.\n\n  ### Useful links\n\n  * [Run tests using the Android emulator](https://devcenter.bitrise.io/en/steps-and-workflows/workflow-recipes-for-android-apps/-android--run-tests-using-the-emulator.html)\n  * [Workflow recipe: Run tests using the Android emulator](https://devcenter.bitrise.io/en/steps-and-workflows/workflow-recipes-for-android-apps/-android--run-tests-using-the-emulator.html)\n\n  ### Related Steps\n\n  * [AVD Manager](https://www.bitrise.io/integrations/steps/avd-manager)\n  * [Gradel Runner](https://www.bitrise.io/integrations/steps/gradle-runner)\nwebsite: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsource_code_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator\nsupport_url: https://github.com/bitrise-steplib/steps-wait-for-android-emulator/issues\npublished_at: 2023-05-08T10:23:49.588206807Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-wait-for-android-emulator.git\n  commit: b6be9e6051cbe4c0bc64d8762f3fb2ff3e9b2a81\nhost_os_tags:\n- ubuntu\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-wait-for-android-emulator\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator with the given serial will be checked if booted, or wait for it to boot.\n    is_required: true\n    summary: Emulator serial to check\n    title: Emulator serial\n- boot_timeout: 300\n  opts:\n    description: |\n      Maximum time to wait for emulator to boot.\n    is_required: true\n    summary: Maximum time to wait for emulator to boot\n    title: Waiting timeout (secs)\n- android_home: $ANDROID_HOME\n  opts:\n    description: Android SDK path\n    is_required: true\n    title: Android SDK path\n"
  },
  {
    "path": "steps/wait-for-android-emulator/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/waldo-upload/0.3.0/step.yml",
    "content": "title: Waldo Upload\nsummary: |\n  Uploads a build to Waldo.\ndescription: |\n  Uploads a build to Waldo.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2020-09-21T17:02:12.251977-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 5b9d9f35c3e6a9c32d24dddda6a2906e62b143c5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    title: Waldo upload token\n  upload_token: null\n- find_symbols: \"no\"\n  opts:\n    category: Symbols\n    description: |\n      **iOS only.** Attempts to find the symbols associated with the\n      specified `.app` build path.\n\n      This input is _ignored_ if a symbols path is specified.\n    is_required: false\n    title: Find symbols associated with the build upload\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Symbols\n    description: |\n      **iOS only.** A `.dSYM` or `.xcarchive` path.\n\n      The symbols path can also be a ZIP archive: `.dSYM.zip` or\n      `.xcarchive.zip`.\n    is_required: false\n    summary: A `.dSYM` or `.xcarchive` path.\n    title: Symbols path\n  symbols_path: null\n- opts:\n    description: |\n      An arbitrary string that can be associated with a build.\n    is_required: false\n    title: Waldo variant name\n  variant_name: null\n"
  },
  {
    "path": "steps/waldo-upload/1.0.0/step.yml",
    "content": "title: Waldo Upload\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2020-10-09T18:26:01.779552-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: f4aef3aa7356aaafac70133271f2074d09e637e4\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    title: Waldo upload token\n  upload_token: null\n- find_symbols: \"no\"\n  opts:\n    category: Symbols\n    description: |\n      **iOS only.** Attempts to find the symbols associated with the\n      specified `.app` build path.\n\n      This input is _ignored_ if a symbols path is specified.\n    is_required: false\n    title: Find symbols associated with the build upload\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Symbols\n    description: |\n      **iOS only.** A `.dSYM` or `.xcarchive` path.\n\n      The symbols path can also be a ZIP archive: `.dSYM.zip` or\n      `.xcarchive.zip`.\n    is_required: false\n    summary: A `.dSYM` or `.xcarchive` path.\n    title: Symbols path\n  symbols_path: null\n- opts:\n    description: |\n      An arbitrary string that can be associated with a build.\n    is_required: false\n    title: Waldo variant name\n  variant_name: null\n"
  },
  {
    "path": "steps/waldo-upload/1.0.1/step.yml",
    "content": "title: Waldo Upload\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2020-10-13T10:13:24.55512-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 6964923b1548ee5ee978b43b91b35703a49bd84b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    title: Waldo upload token\n  upload_token: null\n- find_symbols: \"no\"\n  opts:\n    category: Symbols\n    description: |\n      **iOS only.** Attempts to find the symbols associated with the\n      specified `.app` build path.\n\n      This input is _ignored_ if a symbols path is specified.\n    is_required: false\n    title: Find symbols associated with the build upload\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Symbols\n    description: |\n      **iOS only.** A `.dSYM` or `.xcarchive` path.\n\n      The symbols path can also be a ZIP archive: `.dSYM.zip` or\n      `.xcarchive.zip`.\n    is_required: false\n    summary: A `.dSYM` or `.xcarchive` path.\n    title: Symbols path\n  symbols_path: null\n- opts:\n    description: |\n      An arbitrary string that can be associated with a build.\n    is_required: false\n    title: Waldo variant name\n  variant_name: null\n"
  },
  {
    "path": "steps/waldo-upload/1.1.0/step.yml",
    "content": "title: Waldo Upload\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2021-06-10T15:31:03.001188-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 7f0e470257af85ab5b2fdeb1541881ec27b502a7\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    title: Waldo upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string that can be associated with a build.\n    is_required: false\n    title: Waldo variant name\n  variant_name: null\n- find_symbols: \"no\"\n  opts:\n    category: Symbols\n    description: |\n      **iOS only.** Attempts to find the symbols associated with the\n      specified `.app` build path.\n\n      This input is _ignored_ if a symbols path is specified.\n    is_required: false\n    title: Find symbols associated with the build upload\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Symbols\n    description: |\n      **iOS only.** A `.dSYM` or `.xcarchive` path.\n\n      The symbols path can also be a ZIP archive: `.dSYM.zip` or\n      `.xcarchive.zip`.\n    is_required: false\n    summary: A `.dSYM` or `.xcarchive` path.\n    title: Symbols path\n  symbols_path: null\n"
  },
  {
    "path": "steps/waldo-upload/1.1.1/step.yml",
    "content": "title: Waldo Upload\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2021-06-14T10:17:29.733993-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 0cdb19011639bd75951336793f0e54c01bc4dac0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: curl\n  apt_get:\n  - name: curl\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    title: Waldo upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string that can be associated with a build.\n    is_required: false\n    title: Waldo variant name\n  variant_name: null\n- find_symbols: \"no\"\n  opts:\n    category: Symbols\n    description: |\n      **iOS only.** Attempts to find the symbols associated with the\n      specified `.app` build path.\n\n      This input is _ignored_ if a symbols path is specified.\n    is_required: false\n    title: Find symbols associated with the build upload\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Symbols\n    description: |\n      **iOS only.** A `.dSYM` or `.xcarchive` path.\n\n      The symbols path can also be a ZIP archive: `.dSYM.zip` or\n      `.xcarchive.zip`.\n    is_required: false\n    summary: A `.dSYM` or `.xcarchive` path.\n    title: Symbols path\n  symbols_path: null\n"
  },
  {
    "path": "steps/waldo-upload/2.0.0/step.yml",
    "content": "title: Waldo Upload\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2021-11-08T10:18:30.95531-05:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 7aca3fe5c5ff75f75aed4d0f81772f1c9a57e33b\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      A `.app`, `.ipa`, or `.apk` path.\n\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: A `.app`, `.ipa`, or `.apk` path.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string that can be associated with a build.\n    is_required: false\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      Hash of originating git commit.\n    is_required: false\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      Branch name for originating git commit.\n    is_required: false\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      Prints additional debug information if enabled.\n    is_required: false\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/waldo-upload/2.1.0/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2022-03-25T17:18:20.246555-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 741156f8fba0a24d08606d690729c7b4ed449c07\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app`, `.ipa`, or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/waldo-upload/2.1.1/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2022-04-13T10:15:02.20555-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: f8a15eb8b94dd3bc774ce135525376eaa926ce34\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app`, `.ipa`, or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/waldo-upload/2.2.0/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app`, `.ipa`, or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2022-04-26T17:24:23.409267-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: f20d9076956d1e471072bfad9083c92a01c3933b\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode build for simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Xcode Archive & Export for iOS** Step generates a `.ipa` at `$BITRISE_IPA_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app`, `.ipa`, or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/waldo-upload/2.3.0/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app` or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2022-11-10T13:25:13.863865-05:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: d5f400bab6cb4673db89e96fac9846bf78c28ba1\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app` or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/waldo-upload/2.3.1/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app` or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2023-02-10T11:10:56.664366-05:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 080edc1bccc7244d3f9c7b8dce762164c7f31884\nproject_type_tags:\n- ios\n- android\n- xamarin\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app` or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      An arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/waldo-upload/2.4.0/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app` or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2024-05-07T13:23:24.045865-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 4c5884a92a0c987c334455671d5acfb2e0a52144\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app` or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      This is an arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- WALDO_BUILD_ID: null\n  opts:\n    description: |\n      This is a unique identifier for the build that you just uploaded. Empty if\n      the upload failed.\n    summary: The ID of the uploaded build.\n    title: Build ID\n"
  },
  {
    "path": "steps/waldo-upload/2.4.1/step.yml",
    "content": "title: Upload to Waldo\nsummary: |\n  Uploads your build to Waldo.\ndescription: |\n  Uploads your build (`.app` or `.apk`) to Waldo.\n\n  You must specify at least a build path and a Waldo upload token.\n\n  Typically the build path is generated by a previous build Step in your\n  Workflow. For example:\n\n  - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n  - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n\n  Each application registered in Waldo is associated with a unique upload\n  token. You can find the upload token for your app by going to the\n  Documentation screen for your app in [Waldo](https://app.waldo.io/). This\n  token _should_ be specified as a _secret_ environment variable.\nwebsite: https://github.com/waldoapp/bitrise-step-waldo-upload\nsource_code_url: https://github.com/waldoapp/bitrise-step-waldo-upload\nsupport_url: https://github.com/waldoapp/bitrise-step-waldo-upload/issues\npublished_at: 2024-05-22T10:45:26.18487-04:00\nsource:\n  git: https://github.com/waldoapp/bitrise-step-waldo-upload.git\n  commit: 88615e9d3d47c051fa127da80f261b72da254d60\nproject_type_tags:\n- ios\n- android\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/waldoapp/bitrise-step-waldo-upload\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- build_path: null\n  opts:\n    description: |\n      Typically this path is generated by a previous build Step in your\n      Workflow. For example:\n\n      - the **Xcode Build for Simulator** Step generates a `.app` at `$BITRISE_APP_DIR_PATH`\n      - the **Android Build** Step generates a `.apk` at `$BITRISE_APK_PATH`\n    is_required: true\n    summary: The path to your `.app` or `.apk` build.\n    title: Build path\n- opts:\n    description: |\n      Each application registered in Waldo is associated with a unique upload\n      token.\n    is_required: true\n    is_sensitive: true\n    summary: The upload token associated with your app.\n    title: Upload token\n  upload_token: null\n- opts:\n    description: |\n      This is an arbitrary string to associate with this build.\n    is_required: false\n    summary: An optional variant name.\n    title: Variant name\n  variant_name: null\n- git_commit: null\n  opts:\n    category: git configuration\n    description: |\n      This is the hash of the originating git commit (also known as the “git\n      SHA”) for this build. If omitted, Waldo attempts to infer the git\n      commit from the CI provider (if any) or from the current git repository\n      (if accessible).\n    is_required: false\n    summary: The originating git commit hash.\n    title: Git commit\n- git_branch: null\n  opts:\n    category: git configuration\n    description: |\n      This is the branch name (if any) of the originating git commit for this\n      build. If omitted, Waldo attempts to infer the git branch name from the\n      CI provider (if any) or from the current git repository (if\n      accessible).\n    is_required: false\n    summary: The originating git commit branch name.\n    title: Git branch\n- is_debug_mode: \"no\"\n  opts:\n    category: Debug\n    description: |\n      If this mode is enabled, additional debug information is printed.\n    is_required: false\n    summary: Print additional debug information?\n    title: Debug mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- WALDO_BUILD_ID: null\n  opts:\n    description: |\n      This is a unique identifier for the build that you just uploaded. Empty if\n      the upload failed.\n    summary: The ID of the uploaded build.\n    title: Build ID\n"
  },
  {
    "path": "steps/waldo-upload/step-info.yml",
    "content": "maintainer: verified\n"
  },
  {
    "path": "steps/web-translate-it/1.0.1/step.yml",
    "content": "title: Web Translate It\nsummary: Install web translate it and perform a pull operation.\ndescription: This step runs a `wti pull` after installing the web translate it gem.\n  You need an account on https://webtranslateit.com to be able to run this step.\nwebsite: https://github.com/mAu888/steps-wti\nsource_code_url: https://github.com/mAu888/steps-wti\nsupport_url: https://github.com/mAu888/steps-wti/issues\npublished_at: 2016-05-04T16:15:43.644180786+02:00\nsource:\n  git: https://github.com/mAu888/steps-wti.git\n  commit: f020a7295a9b8462a9511cf220311ce0a975618b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- translation\n- localization\n- xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: If no `.wti` file can be located in the $wti_working_directory (defaults\n      to current working directory), the step creates a `.wti` file based on the $wti_api_key\n      you provide. If neither a `.wti` file nor an $wti_api_key are given, the step\n      fails.\n    is_required: false\n    summary: Find the API key on webtranslateit.com in your project settings.\n    title: Web Translate It API Key\n  wti_api_key: null\n- opts:\n    is_required: false\n    summary: The directory containing the `.wti` file.\n    title: Working directory\n  wti_working_directory: null\n"
  },
  {
    "path": "steps/web-translate-it/1.0.2/step.yml",
    "content": "title: Web Translate It\nsummary: Install web translate it and perform a pull operation.\ndescription: This step runs a `wti pull` after installing the web translate it gem.\n  You need an account on https://webtranslateit.com to be able to run this step.\nwebsite: https://github.com/mAu888/steps-wti\nsource_code_url: https://github.com/mAu888/steps-wti\nsupport_url: https://github.com/mAu888/steps-wti/issues\npublished_at: 2016-05-12T17:56:32.545261148+02:00\nsource:\n  git: https://github.com/mAu888/steps-wti.git\n  commit: c212a5cd7f27f9ce12220a78cdda569a6879df48\nhost_os_tags:\n- osx-10.10\ntype_tags:\n- utility\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: If no `.wti` file can be located in the $wti_working_directory (defaults\n      to current working directory), the step creates a `.wti` file based on the $wti_api_key\n      you provide. If neither a `.wti` file nor an $wti_api_key are given, the step\n      fails.\n    is_required: false\n    summary: Find the API key on webtranslateit.com in your project settings.\n    title: Web Translate It API Key\n  wti_api_key: null\n- opts:\n    is_required: false\n    summary: The directory containing the `.wti` file.\n    title: Working directory\n  wti_working_directory: null\n"
  },
  {
    "path": "steps/web-translate-it/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/wetransfer/0.0.5/step.yml",
    "content": "title: wetransfer\nsummary: |\n  Upload files to wetransfer and share a short url to download\ndescription: |\n  This step send files to wetransfer. Wetransfer give you a short url to download files. Limit 2GO.\nwebsite: https://github.com/kawaiseb/bitrise-step-wetransfer\nsource_code_url: https://github.com/kawaiseb/bitrise-step-wetransfer\nsupport_url: https://github.com/kawaiseb/bitrise-step-wetransfer/issues\npublished_at: 2018-02-22T16:29:48.082619+01:00\nsource:\n  git: https://github.com/kawaiseb/bitrise-step-wetransfer.git\n  commit: 29f5f867ebd4622efb1682904fb656f313263e39\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    is_required: true\n    title: Email of the sender\n  wtu_mailsender: null\n- opts:\n    is_required: true\n    title: One or more email separated by coma for receiver\n  wtu_mailreceiver: null\n- opts:\n    is_required: true\n    title: The path where are stored one or more files to upload\n  wtu_filepath: null\n- opts:\n    is_required: true\n    title: A little body for the mail\n  wtu_message: null\n- opts:\n    is_required: true\n    title: The language of the wetransfer receiver\n    value_options:\n    - fr\n    - en\n  wtu_language: fr\n- opts:\n    description: |\n      Step prints additional debug information if this option\n      is enabled\n    is_required: true\n    title: Debug mode ?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wtu_debug_mode: \"no\"\n"
  },
  {
    "path": "steps/wetransfer/step-info.yml",
    "content": "deprecate_notes: This step is deprecated. The wetransfer API does not work anymore.\nmaintainer: community\nremoval_date: \"2018-03-26\"\n"
  },
  {
    "path": "steps/xamarin-android-test/0.9.0/step.yml",
    "content": "title: Xamarin android Test\nsummary: Xamarin android Test\ndescription: Xamarin android Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-android-test/issues\npublished_at: 2015-12-18T12:11:11.148259524+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-android-test.git\n  commit: c64c416f7f688521540d7f871d56551bff65a8ab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- is_clean_build: true\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - true\n    - false\n- emulator_serial: null\n  opts:\n    description: |\n      Emulator to boot\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Emulator serial to boot\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-android-test/0.9.1/step.yml",
    "content": "title: Xamarin android Test\nsummary: Xamarin android Test\ndescription: Xamarin android Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-android-test/issues\npublished_at: 2015-12-18T17:30:41.800932389+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-android-test.git\n  commit: e1470e362073957fcc10bbbc0fae66b0d16ee50a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: AnyCPU\n- is_clean_build: true\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - true\n    - false\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator to boot\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Emulator serial to boot\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-android-test/1.0.0/step.yml",
    "content": "title: Xamarin android Test\nsummary: Xamarin android Test\ndescription: |-\n  Xamarin android Test\n\n  Use solution configuration-platform combination for automatig tests, which maps to an android project configuration-platform combination, which:\n\n  * DO NOT 'Use Shared Mono runtime' see: PROJECT_TO_TEST/Options/Build/Android Build/General/Packaging and Deployment\n  * Use 'Enable developer instarumentation (debugging and profiling)' see: PROJECT_TO_TEST/Options/Build/Android Build/General/Debugging Options\n\n  Initialize you android app in your UITest project as follows:\n\n  ```\n  AndroidAppConfigurator androidConfigurator = ConfigureApp.Android;\n\n  string apkPath = Environment.GetEnvironmentVariable(\"ANDROID_APK_PATH\");\n  if (!string.IsNullOrEmpty(apkPath))\n  {\n    androidConfigurator.ApkFile(apkPath);\n  }\n\n  string emulatorSerial = Environment.GetEnvironmentVariable(\"BITRISE_EMULATOR_SERIAL\");\n  if (!string.IsNullOrEmpty(emulatorSerial))\n  {\n    androidConfigurator.DeviceSerial(emulatorSerial);\n  }\n\n  return androidConfigurator.StartApp();\n  ```\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-android-test/issues\npublished_at: 2017-02-20T13:08:42.336526801+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-android-test.git\n  commit: 948c4a3671d0e64ac39ed648de8249d8f1dadcd6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-android-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin solution configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin solution platform\n    is_expand: true\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    is_expand: true\n    is_required: false\n    title: Test name to run\n  test_to_run: null\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    description: |\n      Emulator to boot\n    is_expand: true\n    is_required: true\n    title: Emulator serial to boot\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-android-test/1.1.0/step.yml",
    "content": "title: Xamarin android Test\nsummary: Xamarin android Test\ndescription: |-\n  Xamarin android Test\n\n  Use solution configuration-platform combination for automatig tests, which maps to an android project configuration-platform combination, which:\n\n  * DO NOT 'Use Shared Mono runtime' see: PROJECT_TO_TEST/Options/Build/Android Build/General/Packaging and Deployment\n  * Use 'Enable developer instarumentation (debugging and profiling)' see: PROJECT_TO_TEST/Options/Build/Android Build/General/Debugging Options\n\n  Initialize you android app in your UITest project as follows:\n\n  ```\n  AndroidAppConfigurator androidConfigurator = ConfigureApp.Android;\n\n  string apkPath = Environment.GetEnvironmentVariable(\"ANDROID_APK_PATH\");\n  if (!string.IsNullOrEmpty(apkPath))\n  {\n    androidConfigurator.ApkFile(apkPath);\n  }\n\n  string emulatorSerial = Environment.GetEnvironmentVariable(\"BITRISE_EMULATOR_SERIAL\");\n  if (!string.IsNullOrEmpty(emulatorSerial))\n  {\n    androidConfigurator.DeviceSerial(emulatorSerial);\n  }\n\n  return androidConfigurator.StartApp();\n  ```\n\n  Add Internet permission to you Android app.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-android-test/issues\npublished_at: 2017-06-27T14:59:26.949544895+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-android-test.git\n  commit: 54f583899f3e06a4111e6bac36e5fad299bfa190\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-android-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    category: Testing\n    description: |\n      Emulator to boot\n    is_required: true\n    title: Emulator serial to boot\n- opts:\n    category: Testing\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n\n      Format example: `Multiplatform.UItest.Tests(Android)`\n    title: Test name to run\n  test_to_run: null\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin solution configuration\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Release\n- opts:\n    category: Config\n    description: |\n      Xamarin solution platform\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: Any CPU\n- build_tool: xbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-android-test/1.2.0/step.yml",
    "content": "title: Xamarin android Test\nsummary: Xamarin android Test\ndescription: |-\n  Xamarin android Test\n\n  Use solution configuration-platform combination for automatig tests, which maps to an android project configuration-platform combination, which:\n\n  * DO NOT 'Use Shared Mono runtime' see: PROJECT_TO_TEST/Options/Build/Android Build/General/Packaging and Deployment\n  * Use 'Enable developer instarumentation (debugging and profiling)' see: PROJECT_TO_TEST/Options/Build/Android Build/General/Debugging Options\n\n  Initialize you android app in your UITest project as follows:\n\n  ```\n  AndroidAppConfigurator androidConfigurator = ConfigureApp.Android;\n\n  string apkPath = Environment.GetEnvironmentVariable(\"ANDROID_APK_PATH\");\n  if (!string.IsNullOrEmpty(apkPath))\n  {\n    androidConfigurator.ApkFile(apkPath);\n  }\n\n  string emulatorSerial = Environment.GetEnvironmentVariable(\"BITRISE_EMULATOR_SERIAL\");\n  if (!string.IsNullOrEmpty(emulatorSerial))\n  {\n    androidConfigurator.DeviceSerial(emulatorSerial);\n  }\n\n  return androidConfigurator.StartApp();\n  ```\n\n  Add Internet permission to you Android app.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-android-test/issues\npublished_at: 2017-08-09T14:08:35.329327703+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-android-test.git\n  commit: 62118658bfa011f7991f477ab8ffe518b1d6d6c3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-android-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    category: Testing\n    description: |\n      Emulator to boot\n    is_required: true\n    title: Emulator serial to boot\n- opts:\n    category: Testing\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n\n      Format example: `Multiplatform.UItest.Tests(Android)`\n    title: Test name to run\n  test_to_run: null\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin solution configuration\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Release\n- opts:\n    category: Config\n    description: |\n      Xamarin solution platform\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: Any CPU\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-android-test/1.2.2/step.yml",
    "content": "title: Xamarin android Test\nsummary: Xamarin android Test\ndescription: |-\n  Xamarin Android Test\n\n  Use a solution configuration-platform combination for automating tests, that maps to an Android project configuration-platform combination that:\n\n  * DOES NOT 'Use Shared Mono runtime' See: PROJECT_TO_TEST/Options/Build/Android Build/General/Packaging and Deployment\n  * Uses 'Enable developer instrumentation (debugging and profiling)'. See: PROJECT_TO_TEST/Options/Build/Android Build/General/Debugging Options\n\n  Initialize you android app in your UITest project as follows:\n\n  ```\n  AndroidAppConfigurator androidConfigurator = ConfigureApp.Android;\n\n  string apkPath = Environment.GetEnvironmentVariable(\"ANDROID_APK_PATH\");\n  if (!string.IsNullOrEmpty(apkPath))\n  {\n    androidConfigurator.ApkFile(apkPath);\n  }\n\n  string emulatorSerial = Environment.GetEnvironmentVariable(\"BITRISE_EMULATOR_SERIAL\");\n  if (!string.IsNullOrEmpty(emulatorSerial))\n  {\n    androidConfigurator.DeviceSerial(emulatorSerial);\n  }\n\n  return androidConfigurator.StartApp();\n  ```\n\n  Add Internet permission to you Android app.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-android-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-android-test/issues\npublished_at: 2019-11-08T14:02:07.957480418Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-android-test.git\n  commit: 00a658c2dfed8d457439b7dd7bc8bb5f3aacf487\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-android-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- emulator_serial: $BITRISE_EMULATOR_SERIAL\n  opts:\n    category: Testing\n    description: |\n      Emulator to boot\n    is_required: true\n    title: Emulator serial to boot\n- opts:\n    category: Testing\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n\n      Format example: `Multiplatform.UItest.Tests(Android)`\n    title: Test name to run\n  test_to_run: null\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin solution configuration\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Release\n- opts:\n    category: Config\n    description: |\n      Xamarin solution platform\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: Any CPU\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-android-test/step-info.yml",
    "content": "deprecate_notes: |\n  The Xamarin development platform is not officially supported.\n  [More info](https://blog.bitrise.io/post/xamarin-support-ends-in-2022-on-bitrise)\nmaintainer: bitrise\nremoval_date: \"2022-01-31\"\n"
  },
  {
    "path": "steps/xamarin-archive/0.9.0/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2016-10-18T13:23:24.088239754+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: b2b815aa5ed4aeee1066bbdd8280c5ba5c075c3b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- build\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project tyes to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: \"Force use mdtool for building iOS, tvOS and macOS projects?\\n\\nBy\n      default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild`\n      build tool. \\nIf you want to switch to use `mdtool`, set this input to `yes`.\\n\\n_Android\n      projects will build with `xbuild`._\"\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.0.0/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2016-10-26T12:12:49.465842111+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 7c0a13e500b68848d8d21e8b1fa85263f094abb7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- build\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project tyes to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: \"Force use mdtool for building iOS, tvOS and macOS projects?\\n\\nBy\n      default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild`\n      build tool. \\nIf you want to switch to use `mdtool`, set this input to `yes`.\\n\\n_Android\n      projects will build with `xbuild`._\"\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.1.0/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2016-11-02T14:00:38.822317192+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 626811b247751a528a41f14dc4b234c34245f188\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- build\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project tyes to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: \"Force use mdtool for building iOS, tvOS and macOS projects?\\n\\nBy\n      default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild`\n      build tool. \\nIf you want to switch to use `mdtool`, set this input to `yes`.\\n\\n_Android\n      projects will build with `xbuild`._\"\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.1.1/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2016-11-08T17:26:12.805571984+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 13fe411ec8389546640d77e87a24c873fd8351fa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- build\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project tyes to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: \"Force use mdtool for building iOS, tvOS and macOS projects?\\n\\nBy\n      default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild`\n      build tool. \\nIf you want to switch to use `mdtool`, set this input to `yes`.\\n\\n_Android\n      projects will build with `xbuild`._\"\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.1.2/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-01-01T12:32:02.092660289+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: ef3a01b1ccb1f9dc04679a013cd8f7d75f31787c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- build\n- xamarin\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: \"Force use mdtool for building iOS, tvOS and macOS projects?\\n\\nBy\n      default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild`\n      build tool. \\nIf you want to switch to use `mdtool`, set this input to `yes`.\\n\\n_Android\n      projects will build with `xbuild`._\"\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.2.0/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-01-05T16:56:30.779857512+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: d4cc7128c3d2c6bfd68097f766c23da76dae1687\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: |-\n      Force use mdtool for building iOS, tvOS and macOS projects?\n\n      By default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild` build tool.\n      If you want to switch to use `mdtool`, set this input to `yes`.\n\n      _Android projects will build with `xbuild`._\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.3.1/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-01-19T16:17:48.902639587+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 4376f144543f120c4d1b66d7fcb405cee5ff8886\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: |-\n      Force use mdtool for building iOS, tvOS and macOS projects?\n\n      By default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild` build tool.\n      If you want to switch to use `mdtool`, set this input to `yes`.\n\n      _Android projects will build with `xbuild`._\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.3.2/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-02-08T12:09:54.563833601+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: c02ca446d3627216372426b3cee37093cce4f985\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: |-\n      Force use mdtool for building iOS, tvOS and macOS projects?\n\n      By default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild` build tool.\n      If you want to switch to use `mdtool`, set this input to `yes`.\n\n      _Android projects will build with `xbuild`._\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.3.3/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-04-18T11:58:11.977024803+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: c052837c9a272e8afe83db7ef87933d42bc7405e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- force_mdtool: \"no\"\n  opts:\n    description: |-\n      Force use mdtool for building iOS, tvOS and macOS projects?\n\n      By default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild` build tool.\n      If you want to switch to use `mdtool`, set this input to `yes`.\n\n      _Android projects will build with `xbuild`._\n    is_required: true\n    title: (Experimental) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.4.1/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-06-01T18:16:11.975169541+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: b7e8d3025133792fb9932523647a0aa2279e6559\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- ios_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\n- build_tool: xbuild\n  opts:\n    description: Which tool to use for building?\n    title: (Experimental) Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\n- force_mdtool: \"no\"\n  opts:\n    description: |-\n      DEPRECATED - Use `build_tool` to specify the build tool to use.\n\n      Force use mdtool for building iOS, tvOS and macOS projects?\n\n      By default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild` build tool.\n      If you want to switch to use `mdtool`, set this input to `yes`.\n\n      _Android projects will build with `xbuild`._\n    is_required: true\n    title: (DEPRECATED) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.4.2/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-06-12T15:14:58.130045252+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: a62cb35e85e612435cc09beda1e4058d6a5ee6da\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    category: Config\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- build_tool: xbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    title: (Experimental) Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\n- force_mdtool: \"no\"\n  opts:\n    category: Debug\n    description: |-\n      DEPRECATED - Use `build_tool` to specify the build tool to use.\n\n      Force use mdtool for building iOS, tvOS and macOS projects?\n\n      By default step will build __iOS__, __tvOS__ and __macOS__ projects with `xbuild` build tool.\n      If you want to switch to use `mdtool`, set this input to `yes`.\n\n      _Android projects will build with `xbuild`._\n    is_required: true\n    title: (DEPRECATED) Force use mdtool for builds?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- ios_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be append to the end of the iOS build command.\n    title: (Experimental) Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be append to the end of the Android build command.\n    title: (Experimental) Options to append to the Android build command\n- opts:\n    category: Debug\n    description: These options will be append to the end of the tvOS build command.\n    title: (Experimental) Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be append to the end of the macOS build command.\n    title: (Experimental) Options to append to the macOS build command\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.5.0/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2017-08-09T14:04:06.905673202+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: fdafddf694a1544bf741d69c9760a77dd9e56cd1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    category: Config\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\n- ios_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be append to the end of the iOS build command.\n    title: Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be append to the end of the Android build command.\n    title: Options to append to the Android build command\n- opts:\n    category: Debug\n    description: These options will be append to the end of the tvOS build command.\n    title: Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be append to the end of the macOS build command.\n    title: Options to append to the macOS build command\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.5.1/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2019-10-24T10:44:26.427374879Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 2831bd06cb7b63aa825dfd12d8e0eb3a68e79190\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    category: Config\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\n- ios_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the iOS build command.\n    title: Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the Android build command.\n    title: Options to append to the Android build command\n- opts:\n    category: Debug\n    description: These options will be appended to the end of the tvOS build command.\n    title: Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the macOS build command.\n    title: Options to append to the macOS build command\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.5.2/step.yml",
    "content": "title: Xamarin Archive\nsummary: Xamarin Archive\ndescription: Create an archive for your Xamarin application.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2019-12-10T13:51:17.099214569Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: ac9feccde23c0ea19b0f05c078026aca37f8bfa6\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    category: Config\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\n- ios_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the iOS build command.\n    title: Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the Android build command.\n    title: Options to append to the Android build command\n- opts:\n    category: Debug\n    description: These options will be appended to the end of the tvOS build command.\n    title: Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the macOS build command.\n    title: Options to append to the macOS build command\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.5.3/step.yml",
    "content": "title: Xamarin Archive\nsummary: Generates deployable artifact, for example, an .ipa or an APK file for your\n  Xamarin application.\ndescription: |-\n  This Step archives your Xamarin application and moves the generated files to the deployment folder. From there, the **Deploy to Bitrise.io** Step picks up the files and moves them to **APPS & ARTIFACTS**. Feel free to check them out. You can deliver the archived files to the respective marketplace by adding a delivery Step to your Workflow.\n\n  ###Configuring the Step\n  1. Set the the location of your Xamarin solution file in the **Path to the Xamarin Solution file** input.\n  1. Set the **Xamarin solution configuration** input to the Xamarin project Configuration you wish to use (for example, `Release`).\n  2. Set the target platform of your solution configuration in the **Xamarin solution platform** input (for example, `iPhone`).\n\n  ###Troubleshooting\n  Make sure you insert the **Xamarin Archive** Step after the relevant code signing Step and before any delivery Step. For example, if you're archiving an .ipa file, make sure you have uploaded the code signing files to Bitrise and have the **Certificate and profile installer** Step in your Workflow. For APK file generation, you will need to upload your keystore file and have the **Android Sign** Step in your Workflow.\n\n  ###Useful links\n  - [Creating a signed .ipa for Xamarin apps](https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xamarin/)\n  - [Xamarin Android code signing](https://devcenter.bitrise.io/code-signing/xamarin-android-code-signing/xamarin-android-code-signing/)\n  - [Deploying your Xamarin app](https://devcenter.bitrise.io/tutorials/xamarin/deploy-your-xamarin-app/#what-if-you-are-already-using-or-want-to-use-another-deployment-service)\n\n  ###Related Steps\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [NuGet Restore](https://www.bitrise.io/integrations/steps/nuget-restore)\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2021-04-20T16:06:21.93464408Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 7c48d570dd19f6a0e2d524ea434ad8d4a531d7b7\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    category: Config\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\n- ios_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the iOS build command.\n    title: Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the Android build command.\n    title: Options to append to the Android build command\n- opts:\n    category: Debug\n    description: These options will be appended to the end of the tvOS build command.\n    title: Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the macOS build command.\n    title: Options to append to the macOS build command\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created android .apk file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/1.6.0/step.yml",
    "content": "title: Xamarin Archive\nsummary: Generates deployable artifact, for example, an .ipa or an APK file for your\n  Xamarin application.\ndescription: |-\n  This Step archives your Xamarin application and moves the generated files to the deployment folder. From there, the **Deploy to Bitrise.io** Step picks up the files and moves them to **APPS & ARTIFACTS**. Feel free to check them out. You can deliver the archived files to the respective marketplace by adding a delivery Step to your Workflow.\n\n  ###Configuring the Step\n  1. Set the the location of your Xamarin solution file in the **Path to the Xamarin Solution file** input.\n  1. Set the **Xamarin solution configuration** input to the Xamarin project Configuration you wish to use (for example, `Release`).\n  2. Set the target platform of your solution configuration in the **Xamarin solution platform** input (for example, `iPhone`).\n\n  ###Troubleshooting\n  Make sure you insert the **Xamarin Archive** Step after the relevant code signing Step and before any delivery Step. For example, if you're archiving an .ipa file, make sure you have uploaded the code signing files to Bitrise and have the **Certificate and profile installer** Step in your Workflow. For APK file generation, you will need to upload your keystore file and have the **Android Sign** Step in your Workflow.\n\n  ###Useful links\n  - [Creating a signed .ipa for Xamarin apps](https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xamarin/)\n  - [Xamarin Android code signing](https://devcenter.bitrise.io/code-signing/xamarin-android-code-signing/xamarin-android-code-signing/)\n  - [Deploying your Xamarin app](https://devcenter.bitrise.io/tutorials/xamarin/deploy-your-xamarin-app/#what-if-you-are-already-using-or-want-to-use-another-deployment-service)\n\n  ###Related Steps\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [Android Sign](https://www.bitrise.io/integrations/steps/sign-apk)\n  - [NuGet Restore](https://www.bitrise.io/integrations/steps/nuget-restore)\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-archive/issues\npublished_at: 2021-08-06T11:22:53.426781808Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-archive.git\n  commit: 7052699e42dcbe5e9a093b9af158fc90a0237e3a\nproject_type_tags:\n- xamarin\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-archive\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Config\n    description: The Xamarin Solution file `.sln` path.\n    is_required: true\n    title: Path to the Xamarin Solution file\n  xamarin_solution: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: Xamarin solution configuration.\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: $BITRISE_XAMARIN_CONFIGURATION\n- opts:\n    category: Config\n    description: Xamarin solution platform.\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: $BITRISE_XAMARIN_PLATFORM\n- opts:\n    category: Config\n    description: |-\n      Comma separated list of project types to build.\n\n      __Empty list means: build all project types.__\n\n      Available platforms:\n\n      - android\n      - ios\n      - macos\n      - tvos\n    title: Specify project types to build\n  project_type_whitelist: android,ios,macos,tvos\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\n- ios_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the iOS build command.\n    title: Options to append to the iOS build command\n- android_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the Android build command.\n    title: Options to append to the Android build command\n- opts:\n    category: Debug\n    description: These options will be appended to the end of the tvOS build command.\n    title: Options to append to the tvOS build command\n  tvos_build_command_custom_options: null\n- macos_build_command_custom_options: null\n  opts:\n    category: Debug\n    description: These options will be appended to the end of the macOS build command.\n    title: Options to append to the macOS build command\noutputs:\n- BITRISE_APK_PATH: \"\"\n  opts:\n    title: The created Android .apk file's path\n- BITRISE_AAB_PATH: \"\"\n  opts:\n    title: The created Android .aab file's path\n- BITRISE_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created iOS .xcarchive file's path\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created iOS .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created iOS .dSYM.zip file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The create iOS .app file's path\n- BITRISE_TVOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created tvOS .xcarchive file's path\n- BITRISE_TVOS_IPA_PATH: null\n  opts:\n    title: The created tvOS .ipa file's path\n- BITRISE_TVOS_DSYM_PATH: null\n  opts:\n    title: The created tvOS .dSYM file's path\n- BITRISE_TVOS_APP_PATH: null\n  opts:\n    title: The create tvOS .app file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: \"\"\n  opts:\n    title: The created macOS .xcarchive file's path\n- BITRISE_MACOS_APP_PATH: null\n  opts:\n    title: The created macOS .app file's path\n- BITRISE_MACOS_PKG_PATH: null\n  opts:\n    title: The created macOS .pkg file's path\n"
  },
  {
    "path": "steps/xamarin-archive/step-info.yml",
    "content": "deprecate_notes: |\n  The Xamarin development platform is not officially supported.\n  [More info](https://blog.bitrise.io/post/xamarin-support-ends-in-2022-on-bitrise)\nmaintainer: bitrise\nremoval_date: \"2022-01-31\"\n"
  },
  {
    "path": "steps/xamarin-components-restore/0.9.0/step.yml",
    "content": "title: Step Xamarin Components Restore\nsummary: Step Xamarin Components Restore\ndescription: Step Xamarin Components Restore\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-components-restore\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-components-restore.git\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-components-restore/issues\npublished_at: 2015-12-17T13:21:31.411856314+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-components-restore.git\n  commit: b9bad61dcab4dfd9c0d9242ae724a37900c9269c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- dependency\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin solution\n  xamarin_solution: $BITRISE_PROJECT_PATH\n"
  },
  {
    "path": "steps/xamarin-components-restore/step-info.yml",
    "content": "deprecate_notes: |\n  The Xamarin development platform is not officially supported.\n  [More info](https://blog.bitrise.io/post/xamarin-support-ends-in-2022-on-bitrise)\nmaintainer: bitrise\nremoval_date: \"2022-01-31\"\n"
  },
  {
    "path": "steps/xamarin-insights/0.9.0/step.yml",
    "content": "title: Xamarin.Insights\nsummary: Upload your dSym to Xamarin.Insights\ndescription: Upload your dSym to Xamarin.Insights\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-insights\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-insights\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-insights/issues\npublished_at: 2016-02-08T12:55:06.75242244+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-insights.git\n  commit: eced0a55ac0cb86def5b5bfb63efc05a2bf97655\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      API Key for Xamarin.Insights\n    is_expand: true\n    is_required: true\n    title: API Key for Xamarin.Insights\n  xamarin_insights_api_key: null\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      Path to your zipped dSYM file\n    is_expand: true\n    is_required: true\n    title: Path to your zipped dSYM file\n"
  },
  {
    "path": "steps/xamarin-insights/1.0.0/step.yml",
    "content": "title: Xamarin.Insights\nsummary: Upload your dSym to Xamarin.Insights\ndescription: Upload your dSYM to Xamarin.Insights\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-insights\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-insights\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-insights/issues\npublished_at: 2016-02-16T11:20:46.38038923+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-insights.git\n  commit: 998405eaac7bf366f69af388fdca547d9c2d4f08\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- deploy\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      API Key for Xamarin.Insights\n    is_expand: true\n    is_required: true\n    title: API Key for Xamarin.Insights\n  xamarin_insights_api_key: null\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: |\n      Path to your dSYM file\n    is_expand: true\n    is_required: true\n    title: Path to your dSYM file\n"
  },
  {
    "path": "steps/xamarin-insights/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, the Xamarin Insights service will be shutted down on March 31, 2018.\nmaintainer: bitrise\nremoval_date: \"2018-08-01\"\n"
  },
  {
    "path": "steps/xamarin-ios-test/0.9.0/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2015-12-18T12:01:10.459343588+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 6e12990113d5b430e4280ec15b3afce7295d2955\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- is_clean_build: true\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - true\n    - false\n- opts:\n    is_expand: true\n    is_required: true\n    title: Build tool\n    value_options:\n    - xbuild\n    - mdtool\n  xamarin_builder: xbuild\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.1\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/0.9.1/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2015-12-18T15:53:51.823366027+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 43d29087f433d87db93ecdd0d48734d0ad2f6521\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: null\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- is_clean_build: true\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - true\n    - false\n- opts:\n    is_expand: true\n    is_required: true\n    title: Build tool\n    value_options:\n    - xbuild\n    - mdtool\n  xamarin_builder: xbuild\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.1\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/0.9.2/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2015-12-21T11:04:48.490559482+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 1750d3d932dee3d1954c43b86dbc1283214ef1f1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: null\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- is_clean_build: true\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - true\n    - false\n- opts:\n    is_expand: true\n    is_required: true\n    title: Build tool\n    value_options:\n    - xbuild\n    - mdtool\n  xamarin_builder: xbuild\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.1\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/0.9.3/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2015-12-21T16:11:05.296232386+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 6e9689892160719adfbdcd3abfcc23a860a51f0e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: null\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- is_clean_build: true\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - true\n    - false\n- opts:\n    is_expand: true\n    is_required: true\n    title: Build tool\n    value_options:\n    - xbuild\n    - mdtool\n  xamarin_builder: xbuild\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.1\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/1.0.1/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2016-06-08T17:25:21.283424024+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 2299c0f6d362707ad28e99edbc7c6c256a2908fb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n    title: OS version\n  simulator_os_version: iOS 9.3\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/1.0.2/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2016-06-09T13:10:27.304202378+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 0468fc445aaa9da0583be36cd910957183a989df\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/1.0.3/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2016-07-15T16:44:33.779442048+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: ef607770b4572d8808f6e2bdc9d57d312556db14\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/1.0.4/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2016-09-07T13:04:16.021809785+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 5c3164b12087bafceb2f9ffea067d1ef45229329\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/2.0.0/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2016-10-19T17:47:55.466686965+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 8ccd088f630838d736c86c064f021219aba8d566\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-ios-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/2.1.0/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2016-10-26T12:28:56.662124789+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 3fbdbf42f659d8a9ad626e655053c82e3f85eb4a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-ios-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/2.1.1/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: Xamarin iOS Test\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2017-02-06T14:25:54.035998106+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 50ae38f79727c41388ef7afcc1baa98464195873\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-ios-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/2.2.0/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: |-\n  Xamarin iOS Test\n\n  Use solution configuration-platform combination for automatig tests, which maps to an ios project configuration-platform combination, which:\n\n  * Starts the Xamarin Test Cloud Agent in your AppDelegate\n  * Builds for Simulator platform\n\n  Initialize you ios app in your UITest project as follows:\n\n  ```\n  iOSAppConfigurator iosConfigurator = ConfigureApp.iOS;\n\n  string appBundlePath = Environment.GetEnvironmentVariable(\"APP_BUNDLE_PATH\");\n  if (!string.IsNullOrEmpty(appBundlePath))\n  {\n    iosConfigurator.AppBundle(appBundlePath);\n  }\n\n  string simulatorUDID = Environment.GetEnvironmentVariable(\"IOS_SIMULATOR_UDID\");\n  if (!string.IsNullOrEmpty(simulatorUDID))\n  {\n    iosConfigurator.DeviceIdentifier(simulatorUDID);\n  }\n\n  return iosConfigurator.StartApp();\n  ```\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2017-03-02T14:22:12.017326241+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 7b6397c961a84c725d0172fc67357317f9d6f598\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-ios-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin solution configuration\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin solution platform\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: iPhoneSimulator\n- opts:\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n    title: Test name to run\n  test_to_run: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    title: OS version\n  simulator_os_version: latest\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/2.3.1/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: |-\n  Xamarin iOS Test\n\n  Use solution configuration-platform combination for automatig tests, which maps to an ios project configuration-platform combination, which:\n\n  * Starts the Xamarin Test Cloud Agent in your AppDelegate\n  * Builds for Simulator platform\n\n  Initialize you ios app in your UITest project as follows:\n\n  ```\n  iOSAppConfigurator iosConfigurator = ConfigureApp.iOS;\n\n  string appBundlePath = Environment.GetEnvironmentVariable(\"APP_BUNDLE_PATH\");\n  if (!string.IsNullOrEmpty(appBundlePath))\n  {\n    iosConfigurator.AppBundle(appBundlePath);\n  }\n\n  string simulatorUDID = Environment.GetEnvironmentVariable(\"IOS_SIMULATOR_UDID\");\n  if (!string.IsNullOrEmpty(simulatorUDID))\n  {\n    iosConfigurator.DeviceIdentifier(simulatorUDID);\n  }\n\n  return iosConfigurator.StartApp();\n  ```\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2017-06-27T14:49:13.474628796+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 70e1f4925659175a480b341922eef332c1d5352a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-ios-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n\n      Format example: `Multiplatform.UItest.Tests(iOS)`\n    title: Test name to run\n  test_to_run: null\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin solution configuration\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Debug\n- opts:\n    category: Config\n    description: |\n      Xamarin solution platform\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: iPhoneSimulator\n- build_tool: xbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/2.4.0/step.yml",
    "content": "title: Xamarin iOS Test\nsummary: Xamarin iOS Test\ndescription: |-\n  Xamarin iOS Test\n\n  Use solution configuration-platform combination for automatig tests, which maps to an ios project configuration-platform combination, which:\n\n  * Starts the Xamarin Test Cloud Agent in your AppDelegate\n  * Builds for Simulator platform\n\n  Initialize you ios app in your UITest project as follows:\n\n  ```\n  iOSAppConfigurator iosConfigurator = ConfigureApp.iOS;\n\n  string appBundlePath = Environment.GetEnvironmentVariable(\"APP_BUNDLE_PATH\");\n  if (!string.IsNullOrEmpty(appBundlePath))\n  {\n    iosConfigurator.AppBundle(appBundlePath);\n  }\n\n  string simulatorUDID = Environment.GetEnvironmentVariable(\"IOS_SIMULATOR_UDID\");\n  if (!string.IsNullOrEmpty(simulatorUDID))\n  {\n    iosConfigurator.DeviceIdentifier(simulatorUDID);\n  }\n\n  return iosConfigurator.StartApp();\n  ```\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-ios-test/issues\npublished_at: 2017-08-09T14:25:05.085320758+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-ios-test.git\n  commit: 7439a7b08129e6b0751a08797c4ed1ef6ddd1bab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-ios-test\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n      * iPhone 6\n      * iPhone 6s Plus\n      * iPad\n      * iPad Air\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |\n      A couple of format examples:\n      * iOS 8.4\n      * iOS 9.3\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |\n      Comma-separated list of names of tests to run.\n      If not specified all tests will run.\n\n      Format example: `Multiplatform.UItest.Tests(iOS)`\n    title: Test name to run\n  test_to_run: null\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin solution configuration\n    is_required: true\n    title: Xamarin solution configuration\n  xamarin_configuration: Debug\n- opts:\n    category: Config\n    description: |\n      Xamarin solution platform\n    is_required: true\n    title: Xamarin solution platform\n  xamarin_platform: iPhoneSimulator\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-ios-test/step-info.yml",
    "content": "deprecate_notes: |\n  The Xamarin development platform is not officially supported.\n  [More info](https://blog.bitrise.io/post/xamarin-support-ends-in-2022-on-bitrise)\nmaintainer: bitrise\nremoval_date: \"2022-01-31\"\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/0.9.0/step.yml",
    "content": "title: Submit apk to Xamarin Test Cloud\nsummary: Submit apk to Xamarin Test Cloud\ndescription: Submit apk to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2015-12-18T13:33:05.479305891+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 146fc2c7348c49d56ac260716352a533d85d70c1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: AnyCPU\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - true\n    - false\n  test_cloud_is_async: true\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/0.9.1/step.yml",
    "content": "title: Submit apk to Xamarin Test Cloud\nsummary: Submit apk to Xamarin Test Cloud\ndescription: Submit apk to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-01-25T17:23:07.562757093+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 4d0276d6b95ea9f8303f6a7d671f7f1791eeb8cc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: AnyCPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - true\n    - false\n  test_cloud_is_async: true\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.0.0/step.yml",
    "content": "title: Submit apk to Xamarin Test Cloud\nsummary: Submit apk to Xamarin Test Cloud\ndescription: Submit apk to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-02-01T19:46:08.336575167+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: c3780e0650dad04e52e8977ffac9aa17ca0bbfa1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - true\n    - false\n  test_cloud_is_async: true\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.0.1/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-02-12T02:23:49.505982147+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: b4c42c21d5912172b0be5d502d6055e8905e1a1c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - true\n    - false\n  test_cloud_is_async: true\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.1.0/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-05-18T18:05:15.547151916+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 535810887647e17a3e418feb33d8ce23f5c2a989\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - true\n    - false\n  test_cloud_is_async: true\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.1.1/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-05-25T15:51:48.889904995+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 6de0373b417b6666deaed0359949ceb4a88bc4ae\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - true\n    - false\n  test_cloud_is_async: true\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.2.0/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-06-08T11:38:43.302894694+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: ea77dfd571e729dd46b444fb722f70a826413c53\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.2.1/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-07-07T11:23:22.751685111+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 34cae7d352e547f1b1d0c934fbddc6ef6dd62acd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n      'keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>'\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.2.2/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-09-01T14:33:31.029585243+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: a0b4c91d8ed14ccdc8d1138a70cb1e9f28ed68c9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/1.2.3/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-09-07T13:07:32.01294611+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: b534d2f33c8696c5c2f6fe8020f23d69a1c53d5c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/2.0.0/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-10-19T11:34:37.733304308+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: e2238f5e2b85e2b1378195962daa5e3e6de97ea3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/2.1.0/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2016-10-26T12:06:10.172749954+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 1ed42956cb4692d1c75197cadd01e70af5ce9503\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/2.1.1/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2017-03-02T14:32:41.448313498+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 99d503e25a4890088af427f2a5d2e42b5be5ba70\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/2.2.0/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2017-06-28T10:46:31.13554223+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: 34b0b2b1e57ccdf8812c921a8fe01e602b9520df\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    category: Testing\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    category: Testing\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    category: Testing\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    category: Debug\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    category: Debug\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    category: Debug\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    category: Debug\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\n- build_tool: xbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: (Experimental) Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/2.3.0/step.yml",
    "content": "title: Xamarin Test Cloud for Android\nsummary: Xamarin Test Cloud for Android\ndescription: Upload your Android test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android/issues\npublished_at: 2017-08-09T14:39:43.321359971+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android.git\n  commit: f5e253978cd67e8fb7fc8c528217b7ce44e5563c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    category: Testing\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    category: Testing\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    category: Testing\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Release\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: Any CPU\n- opts:\n    category: Debug\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds `--async-json` flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    category: Debug\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    category: Debug\n    description: |\n      Signing parameters to pass Xamarin Test Cloud.\n\n      Required parameters:\n\n      - PATH-TO-KEYSTORE\n      - KEYSTORE-PASSWORD\n      - KEYALIAS\n      - KEYALIAS-PASSWORD\n\n      Example:\n\n      `keystore <PATH-TO-KEYSTORE> <KEYSTORE-PASSWORD> <KEYALIAS> <KEYALIAS-PASSWORD>`\n    summary: Signing parameters\n    title: Signing parameters\n  sign_parameters: null\n- opts:\n    category: Debug\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n\n      - `--app-name APP-NAME`\n      - `--category NUNIT-CATEGORY`\n      - `--fixture NUNIT-FIXTURE`\n      - `--sign-info SIGN-INFO-SI-PATH`\n\n      Example:\n\n      ```\n      --app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      --app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n      ```\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: (Experimental) Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID. This output is available only if `test_cloud_is_async` is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-android/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, please use [App Center upload and schedule tests](https://github.com/bitrise-steplib/steps-appcenter-test) Step instead.\nmaintainer: bitrise\nremoval_date: \"2018-10-26\"\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-android/0.9.0/step.yml",
    "content": "title: Submit calabash android test to Xamarin Test Cloud\nsummary: Submit calabash android test to Xamarin Test Cloud\ndescription: Submit calabash android test to Xamarin Test Cloud\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android/issues\npublished_at: 2015-12-18T13:01:23.254085924+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android.git\n  commit: c3740a7b59805d34f19d640d0d8ffd39550c8168\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: APK path\n    is_expand: true\n    is_required: true\n    title: APK path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-android/0.9.1/step.yml",
    "content": "title: Submit calabash android test to Xamarin Test Cloud\nsummary: Submit calabash android test to Xamarin Test Cloud\ndescription: Submit calabash android test to Xamarin Test Cloud\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android/issues\npublished_at: 2015-12-21T13:58:44.950692981+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android.git\n  commit: ec797e072d34898c61775b14e3fe459f6fbc46a1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: APK path\n    is_expand: true\n    is_required: true\n    title: APK path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-android/0.9.2/step.yml",
    "content": "title: Submit Calabash Android test to Xamarin Test Cloud\nsummary: Submit Calabash Android test to Xamarin Test Cloud step\ndescription: Submit Calabash Android test to Xamarin Test Cloud step\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android/issues\npublished_at: 2016-03-09T08:00:44.770564525+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android.git\n  commit: de761fb261ce6116382e857ad9c1ddc08f79d868\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: APK path\n    is_expand: true\n    is_required: true\n    title: APK path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-android/1.0.0/step.yml",
    "content": "title: Submit Calabash Android test to Xamarin Test Cloud\nsummary: Submit Calabash Android test to Xamarin Test Cloud step\ndescription: Submit Calabash Android test to Xamarin Test Cloud step\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android/issues\npublished_at: 2017-01-23T15:24:10.362522627+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android.git\n  commit: 553d7813dfff09f43a13184f333a8b08ed51ddc4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- android\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-android\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.Droid/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.Droid`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains xamarin-test-cloud and or calabash-android gem.\n    title: Gemfile path\n- apk_path: $BITRISE_APK_PATH\n  opts:\n    description: |-\n      Path to the APK to test.\n\n      __The APK should have Internet permission.__\n\n      In case of Xamarin:\n\n      Use an APK, which not built using Shared mono runtime (_Shared mono runtime is enabled by default in DEBUG builds_).\n    is_required: true\n    title: APK path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\n- android_home: $ANDROID_HOME\n  opts:\n    description: |\n      Path to the Android Home Directory.\n    is_expand: true\n    is_required: true\n    title: Android Home Directory\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-android/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, please use [App Center upload and schedule tests](https://github.com/bitrise-steplib/steps-appcenter-test) Step instead.\nmaintainer: bitrise\nremoval_date: \"2018-10-26\"\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/0.9.0/step.yml",
    "content": "title: Submit calabash ios test to Xamarin Test Cloud\nsummary: Submit calabash ios test to Xamarin Test Cloud\ndescription: Submit calabash ios test to Xamarin Test Cloud\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios/issues\npublished_at: 2015-12-18T12:53:21.773388487+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios.git\n  commit: 98d9a0802c36b48f32a5892d5f6db8b4a5c24d37\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- calabash_features: null\n  opts:\n    description: |\n      Path to Calabash features folder\n    is_expand: true\n    is_required: true\n    title: Path to Calabash features folder\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: IPA path\n    is_expand: true\n    is_required: true\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: dSYM path\n    is_expand: true\n    is_required: true\n    title: dSYM path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - -params, [--test-parameters=key:value] # Test parameters (e.g., -params username:nat@xamarin.com password:xamarin)\n      - -w, [--workspace=WORKSPACE] # Path to your Calabash workspace (containing your features folder)\n      - -c, [--config=CONFIG] # Cucumber configuration file (cucumber.yml)\n      - [--skip-config-check], [--no-skip-config-check] # Force running without Cucumber profile (cucumber.yml)\n      - -p, [--profile=PROFILE] # Profile to run (profile from cucumber.yml)\n      - [--priority], [--no-priority] # Run as priority test execution. Please note: This is only available for some tiers, and priority test executions cost double.\n      - [--locale=LOCALE] # System language\n\n      Example:\n      '--locale=en_US --skip-config-check'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/0.9.1/step.yml",
    "content": "title: Submit calabash ios test to Xamarin Test Cloud\nsummary: Submit calabash ios test to Xamarin Test Cloud\ndescription: Submit calabash ios test to Xamarin Test Cloud\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios/issues\npublished_at: 2015-12-21T10:50:21.066695751+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios.git\n  commit: b7f351f5a817a887a10e35b938b681dc025c7110\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: IPA path\n    is_expand: true\n    is_required: true\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: dSYM path\n    is_expand: true\n    is_required: true\n    title: dSYM path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - -params, [--test-parameters=key:value] # Test parameters (e.g., -params username:nat@xamarin.com password:xamarin)\n      - -w, [--workspace=WORKSPACE] # Path to your Calabash workspace (containing your features folder)\n      - -c, [--config=CONFIG] # Cucumber configuration file (cucumber.yml)\n      - [--skip-config-check], [--no-skip-config-check] # Force running without Cucumber profile (cucumber.yml)\n      - -p, [--profile=PROFILE] # Profile to run (profile from cucumber.yml)\n      - [--priority], [--no-priority] # Run as priority test execution. Please note: This is only available for some tiers, and priority test executions cost double.\n      - [--locale=LOCALE] # System language\n\n      Example:\n      '--locale=en_US --skip-config-check'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/0.9.2/step.yml",
    "content": "title: Submit Calabash iOS test to Xamarin Test Cloud\nsummary: Submit Calabash iOS test to Xamarin Test Cloud step\ndescription: Submit Calabash iOS test to Xamarin Test Cloud step\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios/issues\npublished_at: 2016-03-09T07:59:32.546358495+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios.git\n  commit: c9ccd5609565d02dcdc4bd7deefdb45a49f5fe59\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: IPA path\n    is_expand: true\n    is_required: true\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: dSYM path\n    is_expand: true\n    is_required: true\n    title: dSYM path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - -params, [--test-parameters=key:value] # Test parameters (e.g., -params username:nat@xamarin.com password:xamarin)\n      - -w, [--workspace=WORKSPACE] # Path to your Calabash workspace (containing your features folder)\n      - -c, [--config=CONFIG] # Cucumber configuration file (cucumber.yml)\n      - [--skip-config-check], [--no-skip-config-check] # Force running without Cucumber profile (cucumber.yml)\n      - -p, [--profile=PROFILE] # Profile to run (profile from cucumber.yml)\n      - [--priority], [--no-priority] # Run as priority test execution. Please note: This is only available for some tiers, and priority test executions cost double.\n      - [--locale=LOCALE] # System language\n\n      Example:\n      '--locale=en_US --skip-config-check'\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/0.9.3/step.yml",
    "content": "title: Submit Calabash iOS test to Xamarin Test Cloud\nsummary: Submit Calabash iOS test to Xamarin Test Cloud step\ndescription: Submit Calabash iOS test to Xamarin Test Cloud step\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios/issues\npublished_at: 2016-06-27T14:09:38.395789973+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios.git\n  commit: c2fb0514126f55ed80e00012fae92c77357c5c04\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- ios\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: IPA path\n    is_required: true\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: dSYM path\n    is_required: true\n    title: dSYM path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_required: true\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - -params, [--test-parameters=key:value] # Test parameters (e.g., -params username:nat@xamarin.com password:xamarin)\n      - -w, [--workspace=WORKSPACE] # Path to your Calabash workspace (containing your features folder)\n      - -c, [--config=CONFIG] # Cucumber configuration file (cucumber.yml)\n      - [--skip-config-check], [--no-skip-config-check] # Force running without Cucumber profile (cucumber.yml)\n      - -p, [--profile=PROFILE] # Profile to run (profile from cucumber.yml)\n      - [--priority], [--no-priority] # Run as priority test execution. Please note: This is only available for some tiers, and priority test executions cost double.\n      - [--locale=LOCALE] # System language\n\n      Example:\n      '--locale=en_US --skip-config-check'\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/0.9.4/step.yml",
    "content": "title: Submit Calabash iOS test to Xamarin Test Cloud\nsummary: Submit Calabash iOS test to Xamarin Test Cloud step\ndescription: Submit Calabash iOS test to Xamarin Test Cloud step\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios/issues\npublished_at: 2016-08-12T17:29:30.02783918+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios.git\n  commit: 21ecc9cdbab0c981b10fae762dcef536c7a08039\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\n- ios\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: IPA path\n    is_required: true\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: dSYM path\n    is_required: true\n    title: dSYM path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_required: true\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - -params, [--test-parameters=key:value] # Test parameters (e.g., -params username:nat@xamarin.com password:xamarin)\n      - -w, [--workspace=WORKSPACE] # Path to your Calabash workspace (containing your features folder)\n      - -c, [--config=CONFIG] # Cucumber configuration file (cucumber.yml)\n      - [--skip-config-check], [--no-skip-config-check] # Force running without Cucumber profile (cucumber.yml)\n      - -p, [--profile=PROFILE] # Profile to run (profile from cucumber.yml)\n      - [--priority], [--no-priority] # Run as priority test execution. Please note: This is only available for some tiers, and priority test executions cost double.\n      - [--locale=LOCALE] # System language\n\n      Example:\n      '--locale=en_US --skip-config-check'\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/1.0.0/step.yml",
    "content": "title: Submit Calabash iOS test to Xamarin Test Cloud\nsummary: Submit Calabash iOS test to Xamarin Test Cloud step\ndescription: Submit Calabash iOS test to Xamarin Test Cloud step\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios/issues\npublished_at: 2017-03-16T14:04:11.564778312+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios.git\n  commit: 4dc8e9a5835b08bf1c663ec2115aab5bc277906a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-calabash-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: \"Path to the directory, which contains your calabash features directory.\\n\\nFor\n      emxaple:\\nIf calabash features directory path is: `CreditCardValidator.iOS/features`,\n      \\ \\nthen work_dir should be: `CreditCardValidator.iOS`\"\n    is_required: true\n    title: Directory of your calabash features\n  work_dir: null\n- gem_file_path: $work_dir/Gemfile\n  opts:\n    description: |\n      Path to the Gemfile which contains calabash-cucumber gem.\n\n      If Gemfile not exist or does not contain calabash-cucumber gem: latest version will be used\n    title: Gemfile path\n- ipa_path: $BITRISE_IPA_PATH\n  opts:\n    description: IPA path\n    is_required: true\n    title: IPA path\n- dsym_path: $BITRISE_DSYM_PATH\n  opts:\n    description: dSYM path\n    is_required: true\n    title: dSYM path\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_required: true\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - -params, [--test-parameters=key:value] # Test parameters (e.g., -params username:nat@xamarin.com password:xamarin)\n      - -w, [--workspace=WORKSPACE] # Path to your Calabash workspace (containing your features folder)\n      - -c, [--config=CONFIG] # Cucumber configuration file (cucumber.yml)\n      - [--skip-config-check], [--no-skip-config-check] # Force running without Cucumber profile (cucumber.yml)\n      - -p, [--profile=PROFILE] # Profile to run (profile from cucumber.yml)\n      - [--priority], [--no-priority] # Run as priority test execution. Please note: This is only available for some tiers, and priority test executions cost double.\n      - [--locale=LOCALE] # System language\n\n      Example:\n      '--locale=en_US --skip-config-check'\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-calabash-ios/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, please use [App Center upload and schedule tests](https://github.com/bitrise-steplib/steps-appcenter-test) Step instead.\nmaintainer: bitrise\nremoval_date: \"2018-10-26\"\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/0.9.0/step.yml",
    "content": "title: Submit ipa to Xamarin Test Cloud\nsummary: Submit ipa to Xamarin Test Cloud\ndescription: Submit ipa to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2015-12-18T13:25:34.859110242+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 219f519b58a7acde741e9f801b9acc458d97eb54\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_expand: true\n    is_required: true\n    title: Build tool\n    value_options:\n    - xbuild\n    - mdtool\n  xamarin_builder: xbuild\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/0.9.1/step.yml",
    "content": "title: Submit ipa to Xamarin Test Cloud\nsummary: Submit ipa to Xamarin Test Cloud\ndescription: Submit ipa to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2015-12-21T16:18:31.609454628+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: bdc48f86c1d8698fbff66eeaa8c3aa5ae9f0433b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Project\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Path to Xamarin UITest Project\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin UITest Project\n  xamarin_test_project: null\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    is_expand: true\n    is_required: true\n    title: Build tool\n    value_options:\n    - xbuild\n    - mdtool\n  xamarin_builder: xbuild\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/0.9.2/step.yml",
    "content": "title: Submit ipa to Xamarin Test Cloud\nsummary: Submit ipa to Xamarin Test Cloud\ndescription: Submit ipa to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-01-25T17:25:26.141174837+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 51583bbf0a55d3954999e811ae7b5430850f4a52\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/0.9.3/step.yml",
    "content": "title: Submit ipa to Xamarin Test Cloud\nsummary: Submit ipa to Xamarin Test Cloud\ndescription: Submit ipa to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-01-28T13:28:01.596629238+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 2a90bff5759bea397f92a457cb21ff83b592824a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.0.0/step.yml",
    "content": "title: Submit ipa to Xamarin Test Cloud\nsummary: Submit ipa to Xamarin Test Cloud\ndescription: Submit ipa to Xamarin Test Cloud.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-02-01T19:48:18.588947172+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: ffac906d3f1f601b336d73f1737482a990245cd7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.0.1/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-02-12T13:01:31.733062632+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: bf4086d67f1047a9b1be3d15175e7fa9432095bc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_expand: true\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_expand: true\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_expand: true\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.1.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-05-18T17:58:45.898117896+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 11c418894ebc7abf1c5a17bd214d1b7470ac6dab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.1.1/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-05-25T15:55:14.232814972+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 3c2b49a0a1ce17f11921f5d4f6988307593a5ddc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.2.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-06-08T11:26:25.355196951+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 87cf08bc7861ccc9f6c4ac81d45cde1a1e3a5b79\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.2.1/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-07-21T15:51:29.404681756+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: b877a45afc3f689dd62e56ca05e73765cc65d989\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/1.2.2/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-09-07T13:11:00.023630062+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 983a029e4fc733096026a690a012e5f025d83b28\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/2.0.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-10-19T11:37:59.766816664+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: c74b8d52d9e9c3c36e0764b12d4c7d1b04ac9edc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/2.1.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2016-10-26T12:09:03.659879418+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 0fafd158545c53ea21898838dfc681d35f9d3d9e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/2.1.1/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2017-01-03T15:16:01.89627127+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 200697a4c94d253719ad9c9efd4e893b4ffdd6c3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/2.2.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2017-03-02T14:27:51.595620071+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 91dd553b6b84cd9cb9e40562ce1a47be0fc5c40e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/2.3.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2017-06-28T10:43:04.475822534+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 162e06319a5658a76474309e94ba3506dcdad5f3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    category: Testing\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    category: Testing\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    category: Testing\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    category: Debug\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    category: Debug\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    category: Debug\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\n- build_tool: xbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: (Experimental) Which tool to use for building?\n    value_options:\n    - xbuild\n    - msbuild\n    - mdtool\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/2.4.0/step.yml",
    "content": "title: Xamarin Test Cloud for iOS\nsummary: Xamarin Test Cloud for iOS\ndescription: Upload your iOS test suite to Xamarin Test Cloud and run it on thousands\n  of real devices.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios/issues\npublished_at: 2017-08-09T14:43:43.25968159+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios.git\n  commit: 53694f87e675161e27d0d9bb6d0204083ef4adeb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xamarin-test-cloud-for-ios\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |\n      The e-mail address of the team member submitting the tests.\n    is_required: true\n    summary: User email\n    title: User email\n  xamarin_user: null\n- opts:\n    category: Testing\n    description: |\n      Api key.\n    is_required: true\n    summary: Api key\n    title: Api key\n  test_cloud_api_key: null\n- opts:\n    category: Testing\n    description: |\n      Device selection id from the Test Cloud upload dialog.\n    is_required: true\n    summary: Device selection id\n    title: Device selection id\n  test_cloud_devices: null\n- opts:\n    category: Testing\n    description: |\n      Test series.\n    summary: Test series\n    title: Test series\n  test_cloud_series: master\n- opts:\n    category: Config\n    description: |\n      Path to Xamarin Solution\n    is_required: true\n    title: Path to Xamarin Solution\n  xamarin_project: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |\n      Xamarin project configuration\n    is_required: true\n    title: Xamarin project configuration\n  xamarin_configuration: Debug\n- opts:\n    category: Config\n    description: |\n      Xamarin platform\n    is_required: true\n    title: Xamarin platform\n  xamarin_platform: iPhone\n- opts:\n    category: Debug\n    description: |\n      Don't wait for cloud test run to complete.\n\n      Adds '--async-json' flag to Xamarin Test Cloud upload command.\n    summary: Don't wait for cloud test run to complete\n    title: Don't wait for cloud test run to complete\n    value_options:\n    - \"yes\"\n    - \"no\"\n  test_cloud_is_async: \"yes\"\n- opts:\n    category: Debug\n    description: |\n      Run tests in parallel by method/fixture.\n    summary: Run tests in parallel by method/fixture\n    title: Run tests in parallel by method/fixture\n    value_options:\n    - none\n    - by_test_fixture\n    - by_test_chunk\n  test_cloud_parallelization: none\n- opts:\n    category: Debug\n    description: |\n      Other parameters to pass Xamarin Test Cloud.\n\n      Available parameters:\n      - --app-name APP-NAME\n      - --category NUNIT-CATEGORY\n      - --fixture NUNIT-FIXTURE\n      - --sign-info SIGN-INFO-SI-PATH\n\n      Example:\n      '--app-name <APP-NAME> --category <NUNIT-CATEGORY> --sign-info <SIGN-INFO-SI-PATH>\n      '--app-name <APP-NAME> --fixture <NUNIT-FIXTURE> --sign-info <SIGN-INFO-SI-PATH>\n    summary: Other parameters\n    title: Other parameters\n  other_parameters: null\n- build_tool: msbuild\n  opts:\n    category: Debug\n    description: Which tool to use for building?\n    is_required: true\n    title: (Experimental) Which tool to use for building?\n    value_options:\n    - msbuild\n    - xbuild\noutputs:\n- BITRISE_XAMARIN_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XAMARIN_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: \"\"\n    title: Result of the tests.\n- BITRISE_XAMARIN_TEST_TO_RUN_ID: null\n  opts:\n    description: |\n      Test to run ID.\n\n      This output is available only if 'test_cloud_is_async' is set to 'yes'.\n    title: Test to run ID.\n"
  },
  {
    "path": "steps/xamarin-test-cloud-for-ios/step-info.yml",
    "content": "deprecate_notes: |\n  This step is deprecated, please use [App Center upload and schedule tests](https://github.com/bitrise-steplib/steps-appcenter-test) Step instead.\nmaintainer: bitrise\nremoval_date: \"2018-10-26\"\n"
  },
  {
    "path": "steps/xamarin-user-management/0.9.0/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin.\ndescription: |-\n  This step helps you authenticate your user with Xamarin and to download your Xamarin license file.\n  You can also use this to logout the user from the machine.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2015-12-17T13:23:09.824564421+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: d5384d52a9ad2ee53a5534f78a7f35b7f357c13b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Xamarin action to run\n    value_options:\n    - login\n    - logout\n  xamarin_action: login\n- bitrise_repository: $BITRISE_APP_SLUG\n  opts:\n    description: |\n      Bitrise repository slug\n    is_expand: true\n    is_required: true\n    title: Bitrise repository slug\n- opts:\n    description: |\n      Set true if you want to download the Xamarin.iOS license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.iOS License\n    value_options:\n    - true\n    - false\n  xamarin_ios_license: true\n- opts:\n    description: |\n      Set true if you want to download the Xamarin.Android license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Android License\n    value_options:\n    - true\n    - false\n  xamarin_android_license: true\n"
  },
  {
    "path": "steps/xamarin-user-management/0.9.1/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin.\ndescription: |-\n  This step helps you authenticate your user with Xamarin and to download your Xamarin license file.\n  You can also use this to logout the user from the machine.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2015-12-18T12:43:16.124635724+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: 00c0d087b5e1cc4cb724dd92f04523b9f6fcce1e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- opts:\n    is_expand: true\n    is_required: true\n    title: Xamarin action to run\n    value_options:\n    - login\n    - logout\n  xamarin_action: login\n- bitrise_repository: $BITRISE_APP_SLUG\n  opts:\n    description: |\n      Bitrise repository slug\n    is_expand: true\n    is_required: true\n    title: Bitrise repository slug\n- opts:\n    description: |\n      Set true if you want to download the Xamarin.iOS license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.iOS License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_ios_license: \"yes\"\n- opts:\n    description: |\n      Set true if you want to download the Xamarin.Android license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Android License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_android_license: \"yes\"\n"
  },
  {
    "path": "steps/xamarin-user-management/1.0.0/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin and to download your\n  Xamarin liceses.\ndescription: This step helps you authenticate your user with Xamarin and to download\n  your Xamarin licenses.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2016-02-03T18:11:32.518941147+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: b9e1455157b462d7644c4c59939e8508781dc9b2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: |\n      Bitrise build slug\n    is_expand: true\n    is_required: true\n    title: Bitrise build slug\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.iOS license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.iOS License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_ios_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Android license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Android License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_android_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Mac license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Mac License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_mac_license: \"no\"\n"
  },
  {
    "path": "steps/xamarin-user-management/1.0.1/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin and to download your\n  Xamarin liceses.\ndescription: This step helps you authenticate your user with Xamarin and to download\n  your Xamarin licenses.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2016-03-05T17:06:16.142402471+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: 70be744e9f72e74df4f63a4cc8ce150efa3cefb6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: |\n      Bitrise build slug\n    is_expand: true\n    is_required: true\n    title: Bitrise build slug\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.iOS license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.iOS License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_ios_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Android license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Android License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_android_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Mac license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Mac License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_mac_license: \"no\"\n"
  },
  {
    "path": "steps/xamarin-user-management/1.0.2/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin and to download your\n  Xamarin liceses.\ndescription: This step helps you authenticate your user with Xamarin and to download\n  your Xamarin licenses.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2016-05-09T17:49:30.774937872+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: 865f29a50637147dfefc1b497c526d28e17d0469\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\ninputs:\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: |\n      Bitrise build slug\n    is_expand: true\n    is_required: true\n    title: Bitrise build slug\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.iOS license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.iOS License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_ios_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Android license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Android License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_android_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Mac license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Mac License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_mac_license: \"no\"\n"
  },
  {
    "path": "steps/xamarin-user-management/1.0.3/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin and to download your\n  Xamarin liceses.\ndescription: This step helps you authenticate your user with Xamarin and to download\n  your Xamarin licenses.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2016-09-15T16:28:33.656881872+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: f913b52b0d03e3e18be17feb4d086f7aac4741b9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- \"access control\"\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: false\nrun_if: .IsCI\ninputs:\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: |\n      Bitrise build slug\n    is_expand: true\n    is_required: true\n    title: Bitrise build slug\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.iOS license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.iOS License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_ios_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Android license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Android License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_android_license: \"yes\"\n- opts:\n    description: |\n      Set to yes if you want to download the Xamarin.Mac license file\n    is_expand: true\n    is_required: true\n    title: Xamarin.Mac License\n    value_options:\n    - \"yes\"\n    - \"no\"\n  xamarin_mac_license: \"no\"\n"
  },
  {
    "path": "steps/xamarin-user-management/1.1.0/step.yml",
    "content": "title: Xamarin User Management\nsummary: This step helps you authenticate your user with Xamarin.\ndescription: This step helps you authenticate your user with Xamarin.\nwebsite: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsource_code_url: https://github.com/bitrise-steplib/steps-xamarin-user-management\nsupport_url: https://github.com/bitrise-steplib/steps-xamarin-user-management/issues\npublished_at: 2017-06-08T16:17:09.718726573+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xamarin-user-management.git\n  commit: a5f64623053614f4ddb92ba825b8cfdffe3813b1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- xamarin\ntype_tags:\n- access-control\nis_requires_admin_user: false\nis_always_run: true\nis_skippable: true\nrun_if: .IsCI\ninputs:\n- build_slug: $BITRISE_BUILD_SLUG\n  opts:\n    description: |\n      Bitrise build slug\n    is_expand: true\n    is_required: true\n    title: Bitrise build slug\n"
  },
  {
    "path": "steps/xamarin-user-management/step-info.yml",
    "content": "deprecate_notes: This step is deprecated, [The Component Store](https://docs.microsoft.com/en-us/xamarin/cross-platform/troubleshooting/component-nuget?tabs=vswin) has been discontinued\n  as of May 15, 2018.\nmaintainer: bitrise\nremoval_date: \"2019-01-06\"\n"
  },
  {
    "path": "steps/xcode-analyze/1.0.0/step.yml",
    "content": "title: Xcode Analyze\ndescription: Runs Xcode's `analyze` action.\nsummary: |-\n  Find flaws — potential bugs — in the source code of a project with the\n  static analyzer built into Xcode.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2015-09-04T10:08:29.382895403+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 639886e4716988116518d7fce3dc462b59278c8e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: null\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: null\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: null\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-analyze/1.1.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws — potential bugs — in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2015-09-09T17:25:10.010823096+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 734efdf96e70db3a43bdfbe1722b4addc6567e37\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-analyze/1.2.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws — potential bugs — in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2015-09-14T15:42:41.644092451+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 40ae5f0b76207c8ceba275a142a4eeb0f6839b11\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-analyze/1.3.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2015-11-06T13:22:53.545989235+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: aefea31aab10bc0dd3d60dd95d328f2d0be45a56\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: xctool\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_tool: xctool\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Build tool\n    value_options:\n    - xctool\n    - xcodebuild\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-analyze/1.4.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2015-12-04T14:18:01.177210708+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 19e5e6b66afc84f72a7693105dc8c2fc73cefc0b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/1.4.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2015-12-04T14:36:53.587581067+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 4e701507c2aabc3e5982c991cf12805060ea12ea\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/1.5.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2016-01-25T15:59:45.546860497+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 9b26cfe3c3e1209baea7f76872a0324edbfd20fa\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/1.5.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2016-03-16T14:15:04.818899173+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 569e479927d2ef08ffb0c5ccd4e48f955a800d55\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/1.6.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2016-06-06T16:01:25.307842463+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: be8ea19aa7eb9310a95f5686b65d225ae0763668\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/1.6.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2016-12-19T16:02:02.808883725+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 88e02bd6146e55d5d9f97585b8fcde44e094a076\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/1.7.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2017-11-22T15:14:19.382722705+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: ab74c69599eadb1c639fb1abced011d6ed160225\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip the code signing set this option to `yes`.\n    title: Disable Code Signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n"
  },
  {
    "path": "steps/xcode-analyze/2.0.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-io/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-io/steps-xcode-analyze/issues\npublished_at: 2018-07-18T14:34:57.221448686+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-analyze.git\n  commit: 211b8d0d5241506042337aba3409ddac21eb143c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip the code signing set this option to `yes`.\n    title: Disable Code Signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated raw-xcodebuild-output.log.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.1.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2019-04-24T14:29:55.379581179Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 4d9874525238e3d706d6c3ea6a9ed45f31fd8288\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip the code signing set this option to `yes`.\n    title: Disable Code Signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated raw-xcodebuild-output.log.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.1.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2019-10-15T08:57:37.265361326Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 8b565bfc9d2cfc8b72151f15a3ddd1fa05ef50b9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip the code signing set this option to `yes`.\n    title: Disable Code Signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated raw-xcodebuild-output.log.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.2.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2019-10-30T12:15:49.215150604Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 87a8b3626ad9dd95d7b2214076e67236b3748180\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip the code signing set this option to `yes`.\n    title: Disable Code Signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated raw-xcodebuild-output.log.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.2.2/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\ndescription: |-\n  Find flaws (potential bugs) in the source code of a project with the\n  static analyzer built into Xcode.\n\n  Runs Xcode's `analyze` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2020-10-02T07:58:53.880925294Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 9bc8737369b2205d5b0f228cf5197fae7406b0a1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: '`.xcodeproj` or `.xcworkspace` path'\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity.\n\n      Specify code signing identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is NOT accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip the code signing set this option to `yes`.\n    title: Disable Code Signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated raw-xcodebuild-output.log.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.2.3/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: \"The Step uses the static analyzer built directly into Xcode to analyze\n  your app's source code: the static analyzer tries out thousands of possible code\n  paths in a few seconds, reporting potential bugs that might have remained hidden\n  or bugs that might be nearly impossible to replicate. \\n\\nThis process also identifies\n  areas in your code that don’t follow recommended API usage, such as Foundation,\n  UIKit, and AppKit idioms. \\n\\n### Configuring the Step \\n\\nIn most cases, you don't\n  need to change the Step's configuration. The default input values work well if you\n  added your iOS app on the website, using automatic configuration. \\n\\nTo make sure\n  the Step works well for you:\\n\\n1. Make sure the **Project (or Workspace) path**\n  points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative\n  to the app's root directory.\\n1. Make sure the **Scheme name** input points to a\n  valid shared Xcode scheme. Note that it must be a shared scheme! \\n1. Optionally,\n  you can force the Step to use specific code signing identities. To do so, use the\n  **Force code signing with Identity** and **Force code signing with Provisioning\n  Profile** inputs. \\n\\n   For detailed instructions on their use, see the inputs\n  themselves.\\n\\n### Useful links \\n\\n* [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n*\n  [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\\n\\n###\n  Related Steps \\n\\n* [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\\n*\n  [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2020-11-19T17:33:32.378195885Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: c881256bef1f2c29415b980716ec22dbc5ad0749\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.3.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: \"The Step uses the static analyzer built directly into Xcode to analyze\n  your app's source code: the static analyzer tries out thousands of possible code\n  paths in a few seconds, reporting potential bugs that might have remained hidden\n  or bugs that might be nearly impossible to replicate. \\n\\nThis process also identifies\n  areas in your code that don’t follow recommended API usage, such as Foundation,\n  UIKit, and AppKit idioms. \\n\\n### Configuring the Step \\n\\nIn most cases, you don't\n  need to change the Step's configuration. The default input values work well if you\n  added your iOS app on the website, using automatic configuration. \\n\\nTo make sure\n  the Step works well for you:\\n\\n1. Make sure the **Project (or Workspace) path**\n  points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative\n  to the app's root directory.\\n1. Make sure the **Scheme name** input points to a\n  valid shared Xcode scheme. Note that it must be a shared scheme! \\n1. Optionally,\n  you can force the Step to use specific code signing identities. To do so, use the\n  **Force code signing with Identity** and **Force code signing with Provisioning\n  Profile** inputs. \\n\\n   For detailed instructions on their use, see the inputs\n  themselves.\\n\\n### Useful links \\n\\n* [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n*\n  [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\\n\\n###\n  Related Steps \\n\\n* [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\\n*\n  [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2021-02-17T15:10:57.538161918Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 94bf60b85fcd4142f1af5a320cc08b5e0ff3ce90\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/xcode-analyze/2.4.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: \"The Step uses the static analyzer built directly into Xcode to analyze\n  your app's source code: the static analyzer tries out thousands of possible code\n  paths in a few seconds, reporting potential bugs that might have remained hidden\n  or bugs that might be nearly impossible to replicate. \\n\\nThis process also identifies\n  areas in your code that don’t follow recommended API usage, such as Foundation,\n  UIKit, and AppKit idioms. \\n\\n### Configuring the Step \\n\\nIn most cases, you don't\n  need to change the Step's configuration. The default input values work well if you\n  added your iOS app on the website, using automatic configuration. \\n\\nTo make sure\n  the Step works well for you:\\n\\n1. Make sure the **Project (or Workspace) path**\n  points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative\n  to the app's root directory.\\n1. Make sure the **Scheme name** input points to a\n  valid shared Xcode scheme. Note that it must be a shared scheme! \\n1. Optionally,\n  you can force the Step to use specific code signing identities. To do so, use the\n  **Force code signing with Identity** and **Force code signing with Provisioning\n  Profile** inputs. \\n\\n   For detailed instructions on their use, see the inputs\n  themselves.\\n\\n### Useful links \\n\\n* [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n*\n  [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\\n\\n###\n  Related Steps \\n\\n* [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\\n*\n  [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2021-07-15T14:16:06.410674972Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 9c1e91f1be3af196f04445f0f7db1f8b28862c09\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/2.4.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: |-\n  The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.\n\n  This process also identifies areas in your code that don’t follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.\n\n  ### Configuring the Step\n\n  In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.\n\n  To make sure the Step works well for you:\n\n  1. Make sure the **Project (or Workspace) path** points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative to the app's root directory.\n  1. Make sure the **Scheme name** input points to a valid shared Xcode scheme. Note that it must be a shared scheme!\n  1. Optionally, you can force the Step to use specific code signing identities. To do so, use the **Force code signing with Identity** and **Force code signing with Provisioning Profile** inputs.\n\n     For detailed instructions on their use, see the inputs themselves.\n\n  ### Useful links\n\n  * [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  * [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\n\n  ### Related Steps\n\n  * [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2022-01-28T12:59:52.418534214Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 4045311d1a9331eda1604a386fc17fd3a469cf1f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/2.5.0/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: |-\n  The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.\n\n  This process also identifies areas in your code that don’t follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.\n\n  ### Configuring the Step\n\n  In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.\n\n  To make sure the Step works well for you:\n\n  1. Make sure the **Project (or Workspace) path** points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative to the app's root directory.\n  1. Make sure the **Scheme name** input points to a valid shared Xcode scheme. Note that it must be a shared scheme!\n  1. Optionally, you can force the Step to use specific code signing identities. To do so, use the **Force code signing with Identity** and **Force code signing with Provisioning Profile** inputs.\n\n     For detailed instructions on their use, see the inputs themselves.\n\n  ### Useful links\n\n  * [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  * [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\n\n  ### Related Steps\n\n  * [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2023-08-30T06:15:12.537608957Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 2c30096dc14ce066d110320c02c3dbb0098c1427\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/2.5.1/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: |-\n  The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.\n\n  This process also identifies areas in your code that don’t follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.\n\n  ### Configuring the Step\n\n  In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.\n\n  To make sure the Step works well for you:\n\n  1. Make sure the **Project (or Workspace) path** points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative to the app's root directory.\n  1. Make sure the **Scheme name** input points to a valid shared Xcode scheme. Note that it must be a shared scheme!\n  1. Optionally, you can force the Step to use specific code signing identities. To do so, use the **Force code signing with Identity** and **Force code signing with Provisioning Profile** inputs.\n\n     For detailed instructions on their use, see the inputs themselves.\n\n  ### Useful links\n\n  * [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  * [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\n\n  ### Related Steps\n\n  * [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2025-09-11T14:55:26.861304431Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: b0ecbeb34a7c286b5a6cf47528dc5d3b4747d66f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/2.5.2/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: |-\n  The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.\n\n  This process also identifies areas in your code that don’t follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.\n\n  ### Configuring the Step\n\n  In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.\n\n  To make sure the Step works well for you:\n\n  1. Make sure the **Project (or Workspace) path** points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative to the app's root directory.\n  1. Make sure the **Scheme name** input points to a valid shared Xcode scheme. Note that it must be a shared scheme!\n  1. Optionally, you can force the Step to use specific code signing identities. To do so, use the **Force code signing with Identity** and **Force code signing with Provisioning Profile** inputs.\n\n     For detailed instructions on their use, see the inputs themselves.\n\n  ### Useful links\n\n  * [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  * [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\n\n  ### Related Steps\n\n  * [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2025-09-18T09:50:21.066216519Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: 605e0c442ddf5cb52035fb765bfdfa25f8593279\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/2.5.3/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: |-\n  The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.\n\n  This process also identifies areas in your code that don't follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.\n\n  ### Configuring the Step\n\n  In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.\n\n  To make sure the Step works well for you:\n\n  1. Make sure the **Project (or Workspace) path** points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative to the app's root directory.\n  1. Make sure the **Scheme name** input points to a valid shared Xcode scheme. Note that it must be a shared scheme!\n  1. Optionally, you can force the Step to use specific code signing identities. To do so, use the **Force code signing with Identity** and **Force code signing with Provisioning Profile** inputs.\n\n     For detailed instructions on their use, see the inputs themselves.\n\n  ### Useful links\n\n  * [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  * [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\n\n  ### Related Steps\n\n  * [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2025-10-14T09:05:02.038043509Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: ee3272cd609fae791075e255c52d3423ea73b42b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    description: Do a clean Xcode build before testing?\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/2.5.4/step.yml",
    "content": "title: Xcode Analyze\nsummary: |-\n  Find flaws and potential bugs in the source code of an app with the\n  static analyzer built into Xcode.\ndescription: |-\n  The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.\n\n  This process also identifies areas in your code that don't follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.\n\n  ### Configuring the Step\n\n  In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.\n\n  To make sure the Step works well for you:\n\n  1. Make sure the **Project (or Workspace) path** points to the path of the `.xcodeproj` or `.xcworkspace` file of your app, relative to the app's root directory.\n  1. Make sure the **Scheme name** input points to a valid shared Xcode scheme. Note that it must be a shared scheme!\n  1. Optionally, you can force the Step to use specific code signing identities. To do so, use the **Force code signing with Identity** and **Force code signing with Provisioning Profile** inputs.\n\n     For detailed instructions on their use, see the inputs themselves.\n\n  ### Useful links\n\n  * [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  * [Device testing for iOS](https://devcenter.bitrise.io/testing/device-testing-for-ios/)\n\n  ### Related Steps\n\n  * [Xcode build for simulator](https://app.bitrise.io/integrations/steps/xcode-build-for-simulator)\n  * [Xcode Test for iOS](https://app.bitrise.io/integrations/steps/xcode-test)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-analyze\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-analyze\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-analyze/issues\npublished_at: 2025-11-10T13:48:25.994268346Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-analyze.git\n  commit: fc587af7b2dc07a8f7e6292c33e6ac2b46f63270\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-analyze\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the Step.\n      If you leave it empty, the default working directory will be used.\n    is_expand: true\n    is_required: false\n    summary: Working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      The path to your app's `.xcodeproj` or `.xcworkspace` file, relative to\n      the Step's working directory (if one is specified).\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The path of the `.xcodeproj` or `.xcworkspace` file\n    title: Xcode project or workspace path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Xcode scheme to use for the analysis.\n      **IMPORTANT**: The scheme must be marked as shared in Xcode!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: The Xcode scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"no\"\n  opts:\n    description: Do a clean Xcode build before testing?\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use specified code signing identity.\n      Specify a code signing identity as a full ID (for example, `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify a code signing group (for example, `iPhone Developer` or `iPhone Distribution`).\n    title: Force code signing with identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force the `xcodebuild` command to use a specified provisioning profile.\n      You must use the provisioning profile's UUID. The profile's name is NOT accepted by xcodebuild.\n      To get your UUID:\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n      Format example:\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with provisioning profile\n- disable_codesign: \"yes\"\n  opts:\n    description: In order to skip code signing, set this option to `yes`.\n    title: Disable code signing\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Add `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n      Indexing is needed for\n\n      * Autocomplete.\n      * Ability to quickly jump to definition.\n      * Get class and method help by alt clicking.\n      None of the above ar needed in a CI environment.\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In a CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Disable indexing during the build run to potentially make the build faster.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching.\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project.\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      If the input is set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n      If the input is set to `xcodebuild`, the raw xcodebuild output will be printed.\n    is_expand: true\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: This directory will contain the generated `raw-xcodebuild-output.log`.\n    is_required: true\n    summary: Output directory path\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n"
  },
  {
    "path": "steps/xcode-analyze/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-archive/0.9.2/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-08-21T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 775a2c5c50db099e302fe92f265719b20f980059\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: null\n- opts:\n    description: |\n      The Scheme to use.\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: null\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: null\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_expand: true\n    is_required: false\n    title: Output directory path\n  output_dir: ./build\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n"
  },
  {
    "path": "steps/xcode-archive/0.9.3/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-09-03T23:08:06.193350613+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: f890ab95b76f0e8a89cce08f798a1124c735119b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: null\n- opts:\n    description: |\n      The Scheme to use.\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: null\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: null\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_expand: true\n    is_required: false\n    title: Output directory path\n  output_dir: ./build\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.0.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-09-09T16:37:22.741310808+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: f2ce4791c1bb9c73504a367ec1edfa4ec7bfd0d4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: ./build\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.1.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-09-10T12:03:56.169087852+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 97bc3ed85237118d9dd8bcedc03ae2300316cacd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.1.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-09-11T16:51:07.347180116+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 15c1f1cc7d04350a1dd0a2e13582cedc670fc298\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.10.0/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-09-23T17:08:52.348263001+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 52f1c86cb9693e0de1fa53c54294222cefde731b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Export options path\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.10.1/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-10-11T11:19:17.972209523+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 4ac4bf0a2d4af500936fa33bd3c0600146dce8bb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n"
  },
  {
    "path": "steps/xcode-archive/1.2.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-09-14T16:31:55.863068672+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 96ab8bfa2e81cc7d23d07d6c644dc0c84d43e42e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-10-28T14:01:21.031971233+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 81a9892588d1f44bfff5e4d589719cd3f77d918c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used if Xcode version > 6 .\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-10-28T19:32:59.077132079+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 326d7ffdcec47ee71f4910ecd169882d8c3fab0e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used if Xcode version > 6 .\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.2/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-10-28T22:45:12.84503658+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 7bde2ea91aba900d5f550f4816997a3182abd92d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used if Xcode version > 6 .\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.3/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-10-28T23:07:35.312600942+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 57bee7cb5211bf06f1a86d59fc90d112815b3627\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used if Xcode version > 6 .\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.4/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-10-29T13:39:20.408122728+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 758096ef549c4acd446cc722ae08c729b2f019c5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.5/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-11-03T13:40:57.513110331+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 4f870c6b08bd761ae78f4b2af295099f6b763a01\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.3.6/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-11-03T16:04:31.654419716+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: fc2f40c32387d1a825460ca5af1fc2a4aa302e47\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.4.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-11-05T17:59:37.281657504+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 31d201d86eead53bb578f20962420b4245667738\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: xctool\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_tool: xctool\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Build tool\n    value_options:\n    - xctool\n    - xcodebuild\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.4.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-11-06T18:19:17.546987702+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 4dff30e96307525f4b1af5740777cc636885a8ec\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: xctool\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- build_tool: xctool\n  opts:\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Build tool\n    value_options:\n    - xctool\n    - xcodebuild\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.5.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-12-03T15:11:10.673873012+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: aeb58b9b87897a47db96dbc1d6a39b54a122313e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.5.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-12-04T13:23:37.247889225+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 4fbfe44db97e67713812a6cc44c61f9b1bcd90ad\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.5.2/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2015-12-04T14:39:58.914696865+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 781835ec0c49825c986f489e700a9e3f81e2bf63\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.6.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-01-25T15:43:50.376576649+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: a587a6dd6f0da1c0fa11dba512170515fdc2d57b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.6.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-02-23T13:50:04.095195255+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 73c2c37ac66d4d4baa8729a95764b4c1bbf54bf9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .ipa file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.7.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-03-17T15:03:28.837175547+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 66eb4b978c33587dd575df013ff8a103d145f0a4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.7.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-03-31T12:56:20.839596893+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: e8cdd40710cf159a36c522539c86814742926263\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.7.2/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-05-05T14:03:50.091717509+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: a7d2251921caf6b57aae22d78dfefadf61631df1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.7.3/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-05-20T18:01:38.106491279+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 403f8b0f0a8ccee5a32fff175a072c0a5daed3bd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.8.0/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-06-06T12:35:49.088635109+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: e5ee1d87f5dd50436b53aaaf7accf2512150eb26\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n    title: Force code signing with Identity\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.8.1/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-06-23T17:01:43.168844687+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 572fdc98a810f8e1c66416860806098dab3aa5df\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.8.2/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-07-01T12:15:00.894191725+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 24c8da06a91dcf1e42ba45740664a4c432ec30f3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.8.3/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-07-05T15:46:15.446996154+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: aa8290a3bf1ebdac1623f982f0831b6a51ae6b13\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.8.4/step.yml",
    "content": "title: Xcode Archive\nsummary: |-\n  Create an archive so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-07-26T14:23:26.70576013+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: bfb33de84bc6b61cc1b7581aa9ad2678a77af9f2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.8.5/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-07-26T15:00:05.077552808+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 817c14450724a449a9dfa21827aeaea3dc51e6d9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.9.0/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-08-11T15:38:51.084206943+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 5d79bb56c064b605f1538c97c34fbdde4ffdb96d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.9.1/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-09-06T17:48:34.903686746+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: c82b41c05453d8aeaf53e18caafe8a004b152423\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Export options path\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/1.9.2/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-09-19T14:01:24.246899256+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 33fb80d0fc63594190dbe64d3a98e682785fd412\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      If this input is set to `yes`, step will use deprecated ipa export method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Export options path\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive/2.0.0/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-11-18T14:41:31.583990872+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 54f971c469ad1382c01e9577bead5897a3db1812\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.0.1/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-archive/issues\npublished_at: 2016-11-18T16:28:59.10521288+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 7f55b19345bef4557d5c7552ed014525636bdd94\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.0.2/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2016-11-23T15:19:56.611135172+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 6f56664b54e31ca69dfb6c95095f3557e1f31c8a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.0.3/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2016-11-29T14:27:13.09898647+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 617db0c36d408d26c35014a629315f84b9f78e4d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.0.4/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2016-12-06T15:17:52.019776447+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 93873a15b0c7101ad64387de9cabbe335e39dd26\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.0.5/step.yml",
    "content": "title: Xcode Archive for iOS\nsummary: Run Xcode Archive command and export an iOS IPA\ndescription: |-\n  Run Xcode Archive command and export an iOS IPA.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-02-09T10:03:21.667174002+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 5e0014fbabd3d29047bb26556bfd74f6cf164453\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: golang\n    bin_name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: \"__Export option:__\\n\\nDescribes how Xcode should export the archive.\n      \\  \\n\\nIf you select `auto-detect` step will figure out proper export method\n      \\ \\nbased on provisioning profile embedded into generated xcodearchive.\"\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: \"__Export option:__  \\n\\nFor __App Store__ exports, should the package\n      include bitcode?\"\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: \"__Export option:__  \\n\\nFor __non-App Store__ exports, should Xcode\n      re-compile the app from bitcode?\"\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: \"__Export option:__  \\n\\nThe Developer Portal team to use for this\n      export.\\n\\nFormat example:\\n\\n- `1MZX23ABCD4`\"\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.0.6/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-06-08T11:17:47.388208659+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 4b3c9260876eb2c79f4bc82c9e0ee454242c7971\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.1.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-07-24T16:41:10.631553291+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: f08f4aa94d4ad4173229afdd726a145302b9b76d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.1.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-08-15T13:43:03.922558662+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 6dbc53d834942da667c44689779b44fae38592f5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.2.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-08-30T13:45:04.156545156+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 3b616f4e1990cc15537f6e267b5aae75f994303d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.2.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-09-04T16:56:21.869206246+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 7bd426ffbd5c50b81a0f80017d3c1e4fbf89e8b6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Code Signing Options (deprecated)\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-09-15T17:53:58.555378158+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 6209d31ca8a3c90fbba1dce9f3f901b52733b55d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-09-21T14:56:53.766366118+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: eff55ed16d1e40aa56218c033345438ba51bdaa3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-09-29T20:58:52.09245421+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 2ce0ae9ebbde0e0af44e99f6e0bd6f7d4965f844\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-10-06T18:17:37.327331982+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 9f3cf809b288c527585209f77d87d03f13501261\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-10-11T17:47:14.475099401+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 9db40a99772946fcb51dc85521d385e1d6414fe6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.6/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-10-20T18:28:09.220827576+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 8fb22df445734eeec60214a57e4d329a1339ac6f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.3.7/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-10-26T13:53:54.254328099+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: d21bcd58bb944aa949319fafc0bbb3b9232e4fcc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-11-22T11:43:43.037252375+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 11035ae0419c6eb6543bf7cc8e6cace3c335633b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-11-22T12:28:48.779185663+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 2c5e1983567046f89a62cb620d618393e51e00ce\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.10/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-07-18T12:35:31.65406591Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 1c924863e2b001abcd15af5f676b70a56b88d01d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.11/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-08-01T13:07:46.354399105Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: bb50939224fdfa29acc39735fc469c52a2ddca32\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.12/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-08-01T16:39:41.424514477Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 4931b5ff1786695db76eca2de1d90fb328322279\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.13/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-08-17T14:09:35.810999826Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: d38d5c9c12cf80d7ea58c7ab968312db973d40dc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.14/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-08-22T09:09:00.802895347Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 0f34f35cad4035f066f2d9b48ee9d8fdfa71b810\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.15/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-08-27T15:37:21.402836779Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: de1e767589f3c6144b5cbcf1c21c9ff56cf28ff1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.16/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-10-26T12:56:31.889830717Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 878247f0cb54cf66a384355f0ca5ee78c4e0435e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.17/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-12-07T15:06:59.351991091Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: afcaa92c17125692aeec605cc907cec1a8212f0f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.18/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-12-19T15:17:27.381765712Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 5b1471ce47a29e2ea0cd3ce511d4ecdf6b5b9f9d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.19/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-12-20T16:01:29.210733956Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 7d8a0f19411edcf0fd5e4f794977af43769b539d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-11-22T18:19:48.368056463+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: a055115162b99b51ab90088e020b421f3c103b73\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.20/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2019-02-14T12:49:29.011918147Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 3c56a851cfd2e29ed125d3893df70a3aa3f3196c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.21/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2019-03-01T10:54:20.593549577Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: c3ea1dc97351e1a5f83528ce4dd2aafda2b06720\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2017-12-08T14:48:00.394589159+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: d5a0fd236a0eb504402ddb711901d3d6fdbba750\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    category: Export Options\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    category: Export Options\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    category: Export Options\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    category: Export Options\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-01-02T12:30:44.456014662+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: a4707f5c045c0e04e8a021da9a9b044246071054\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-01-17T15:39:29.946748+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 012719d13d9500b390437a23677534aeb6884b23\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.6/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-02-07T15:15:16.344665147+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 664b0d63e49ca2c2a46325588bb6471ddea1444a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    category: Export Options (debug)\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: Config\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: Config\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- force_team_id: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Signing Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Deprecated\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.7/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: !!timestamp 2018-05-07T15:31:18.606155338+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 84c46465fc2926a0338c33007dca8e948dfe35de\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n  upload_bitcode: \"yes\"\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.8/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: !!timestamp 2018-05-08T13:25:56.235402796+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 1a79984af4a758f93a793f928612ed4e42602727\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.4.9/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-io/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-io/steps-xcode-archive\nsupport_url: https://github.com/bitrise-io/steps-xcode-archive/issues\npublished_at: 2018-06-12T16:13:10.334856143+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-archive.git\n  commit: 3c94dfa939317abb001184d4fd98b6f5fa3544e7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect` step will figure out proper export method\n      based on provisioning profile embedded into generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **Capitalization also matters**, `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.5.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2019-04-18T15:17:38.80346851Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 95e00f357cea01ff520b5103bc9a5a3da2055e32\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: Debug\n    description: If this input is set to `yes`, the generated .xcarchive will be zipped\n      and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: |-\n      The created .xcarchive.zip file's path.\n\n      This environment will be exported only if, is_export_xcarchive_zip=\"yes\"\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.6.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2019-07-10T09:41:27.933022616Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 54295929c7fe6f0beb231ef19c680389839cd1f2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.6.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2019-09-27T16:54:33.933022616Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: a8fcd80d3ab6f121df12b626f043344726e113b1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.6.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2019-10-10T12:38:30.685274912Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: edffa8b1c092685618857d586859bfa3c5e96e90\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.7.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2019-10-22T07:50:40.36478587Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: d25b478ae7b83f6b6d2353014381dd17e801147c\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.7.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2019-12-10T15:40:42.910264667Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 8b2aa80d6c8dea5055a9ffe213a6733ca1c99b95\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.7.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run Xcode Archive command and then Export an IPA from the archive.\ndescription: |-\n  Run Xcode Archive command and then Export an IPA from the archive\n  for iOS, tvOS or watchOS.\n\n  You can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-03-04T10:42:14.574738287Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: b0eab0b0416e042a16f690d3b85ab240ad72bec1\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-04-21T07:38:52.623836772Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 7e851f103d4d5983dee7f1aa24e6438f70e3d239\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-05-12T12:01:35.762315487Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 76ab8e77ab00525ea143720ea5c9ade7c0601d56\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-06-04T13:08:00.319430455Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: db638fe6026f19536b0c14aaf0c52b030871939a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-06-12T09:15:20.758532709Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: db942a15f84b1febe0a991f0f607f93d6c0b42c2\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-06-16T19:56:23.381947267Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 3ca834400637d08bc65c9f9650a1f977f134163e\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-06-22T11:53:05.936369038Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f9b8f6015ab17b8abf4bd9d829504dce349830ca\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.6/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-07-22T15:49:20.316488658Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f6f55f7ec9957739c8413f86197e87cfb0576eb5\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/2.8.7/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-10-01T12:38:54.094694513Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: ba19fe16cdb0d8ee3a7ea8be5e8c5b65037acf2a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\n- opts:\n    category: Debug\n    description: If this input is set to `yes`, step will use deprecated ipa export\n      method.\n    is_required: true\n    title: Use deprecated ipa export method?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  use_deprecated_export: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.0.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-12-09T16:02:49.60519886Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 1ecab8b5c0673cd32e31ea29843a579fbb7d2131\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory and export the directory path.\n      Otherwise this environment points to the .app.DSYM directory path.\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      If `export_all_dsyms` is set to `\"yes\"`, step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise this environment points to the zipped .app.DSYM directory path.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.1.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2020-12-15T11:17:48.640300135Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 29cba9b687aaa7565eea34a552ed6def1a86acf7\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.1.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-01-12T08:53:03.698067705Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 733acc53652578a0dc2be89ae3b0ac521a024da7\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"yes\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.2.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-02-17T15:12:20.681325026Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 4f81fbde946655ebf7e08b70558cbe53c0a3de0e\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (DEVELOPMENT_TEAM).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (CODE_SIGN_IDENTITY).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (PROVISIONING_PROFILE).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.2.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-05-12T09:45:04.409596189Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: cd840fa3ba5bf1489b6a9661e68092be053834a3\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.2.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-05-21T07:13:07.196817348Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: e0b6477b23d0dcb6b7f714bf7ee0d17bd466c7e1\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.2.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-05-31T07:44:57.081890954Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f21ac663a842810120c5a9ecc438001cf62ae3c1\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.2.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-06-01T13:50:11.686539941Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 8beb1ecfa23429cd34d02b6306931f542a302560\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.2.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-06-04T12:23:40.354255787Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: eb781af69a9651d272a2fc6b62faefe15376ad3a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODE_ARCHIVE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw archive results log file.\n\n      If `output_tool=xcpretty` and the archive fails this log will contain the archive output.\n    title: The full, raw archive output file path\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.3.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-06-25T13:11:56.397523Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 08d24cea5ea72a5c3d1301e3512021e8aed7f0fc\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.3.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-07-23T07:59:07.692661101Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: a9e07e9b6419f0bbd8a0023b9761aac41f0649a8\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/3.3.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: \"\\nThe Step archives your Xcode project by running the `xcodebuild archive`\n  command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive`\n  command. This .ipa file can be shared, installed on test devices, or uploaded to\n  the App Store Connect.\\n\\n### Configuring the Step\\n\\nBefore you can use the Step,\n  you need code signing files. Certificates must be uploaded to Bitrise while provisioning\n  profiles should be either uploaded or, if using the iOS Auto Provisioning Step,\n  downloaded from the Apple Developer Portal or generated automatically.\\n\\nTo configure\n  the Step:\\n\\n1. Make sure the **Project (or Workspace) path** input points to the\n  correct location.\\n\\n   By default, you do not have to change this.\\n1. Set the\n  correct value to the **Select method for export** input. If you use the **iOS Auto\n  Provision** Step, the value of this input should be the same as the **Distribution\n  type** input of that Step.\\n1. Make sure the target scheme is a valid, existing\n  Xcode scheme.\\n1. Optionally, you can define a configuration type to be used (such\n  as Debug or Release) in the **Configuration name** input.\\n\\n   By default, the\n  selected Xcode scheme determines which configuration will be used. This option overwrites\n  the configuration set in the scheme.\\n1. If you wish to use a different Developer\n  portal team than the one set in your Xcode project, enter the ID in the **he Developer\n  Portal team to use for this export** input.\\n\\n### Troubleshooting\\n\\nIf the Step\n  fails, check your code signing files first. Make sure they are the right type for\n  your export method. For example, an `app-store` export method requires an App Store\n  type provisioning profile and a Distribution certificate.\\n\\nCheck **Debug** for\n  additional options to run the Step. The **Additional options for xcodebuild call**\n  input allows you add any flags that the `xcodebuild` command supports.  \\n\\nMake\n  sure the **Scheme name** and **Configuration name** inputs contain values that actually\n  exist in your Xcode project.\\n\\n### Useful links\\n\\n- https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\\n-\n  https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\\n-\n  https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\\n\\n### Related\n  Steps\\n\\n- [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\\n-\n  [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\\n-\n  [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-07-26T15:53:06.749571931Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: fb1434ff424669d4769b81e389d249fb281d19f0\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- export_method: auto-detect\n  opts:\n    description: |-\n      `auto-detect` option is **DEPRECATED** - use direct export methods!\n\n      Describes how Xcode should export the archive.\n\n      If you select `auto-detect`, the step will figure out proper export method\n      based on the provisioning profile embedded into the generated xcodearchive.\n    is_required: true\n    summary: \"\"\n    title: Select method for export\n    value_options:\n    - auto-detect\n    - app-store\n    - ad-hoc\n    - enterprise\n    - development\n- opts:\n    description: |-\n      The Developer Portal team to use for this export.\n\n      Optional, only required if you want to use a different team for\n      distribution, not the one you have set in your Xcode project.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    summary: \"\"\n    title: The Developer Portal team to use for this export\n  team_id: null\n- compile_bitcode: \"yes\"\n  opts:\n    description: |\n      For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    is_required: true\n    summary: \"\"\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: For __App Store__ exports, should the package include bitcode?\n    is_required: true\n    summary: \"\"\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    description: \"If the app is using CloudKit, this configures the \\\"com.apple.developer.icloud-container-environment\\\"\n      entitlement.  \\nAvailable options vary depending on the type of provisioning\n      profile used, but may include: Development and Production.\"\n    summary: \"\"\n    title: iCloud container environment\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- force_team_id: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Development Team (`DEVELOPMENT_TEAM`).\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force code signing with Development Team\n- force_code_sign_identity: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Code Signing Identity (`CODE_SIGN_IDENTITY`).\n\n      Specify Code Signing Identity as full ID (e.g. `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `iPhone Developer` or `iPhone Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      This means that instead of `iOS` (`iOS Distribution/Development`) you have to use\n      `iPhone` (`iPhone Distribution` or `iPhone Development`).\n      **The input is case sensitive**: `iPhone Distribution` works but `iphone distribution` does not!\n    title: Force code signing with Code Signing Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE_SPECIFIER`).\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: Force Build Settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile (`PROVISIONING_PROFILE`).\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - `c5be4123-1234-4f9d-9843-0d9be985a068`\n    title: Force code signing with Provisioning Profile\n- custom_export_options_plist_content: null\n  opts:\n    category: Debug\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, the step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile, the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- artifact_name: ${scheme}\n  opts:\n    category: Debug\n    description: This name will be used as basename for the generated .xcarchive,\n      .ipa and .dSYM.zip files.\n    title: Generated Artifact Name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.0.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-10-13T13:21:10.928225846Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 62bf370fbb9d86da8fc4f16e8e91a0cce99a3d70\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.0.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-10-14T09:42:56.764149706Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 52eff572d767efbc929b8979b1c2050f303440ac\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.0.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-10-14T14:57:42.993669341Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f199dede35616193bb3c802c7b5b370042c854ce\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.0.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-10-18T12:05:33.453258775Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: aa4fda9a413cacb12bfdb445e412b53f5d5497bf\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.0.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-10-25T13:40:19.730034652Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 791ba442245600cfa1567107e4a6361558502abf\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated .app directory\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive file's path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path.\n    title: The created .xcarchive.zip file's path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.1.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-11-29T10:32:00.286662683Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: efbaec0eb292865c116e25ee28735073aec1fcae\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Run the Xcode archive command and then export an .ipa from the archive.\ndescription: |2-\n\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command. This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n\n  ### Configuring the Step\n\n  Before you can use the Step, you need code signing files. Certificates must be uploaded to Bitrise while provisioning profiles should be either uploaded or, if using the iOS Auto Provisioning Step, downloaded from the Apple Developer Portal or generated automatically.\n\n  To configure the Step:\n\n  1. Make sure the **Project path** input points to the correct location.\n\n     By default, you do not have to change this.\n  2. Set the correct value to the **Distribution method** input. If you use the **iOS Auto Provision** Step, the value of this input should be the same as the **Distribution type** input of that Step.\n  3. Make sure the target scheme is a valid, existing Xcode scheme.\n  4. Optionally, you can define a configuration type to be used (such as Debug or Release) in the **Build configuration** input.\n\n     By default, the selected Xcode scheme determines which configuration will be used. This option overwrites the configuration set in the scheme.\n  5. If you wish to use a different Developer portal team than the one set in your Xcode project, enter the ID in the **Developer Portal team** input.\n\n  ### Troubleshooting\n\n  If the Step fails, check your code signing files first. Make sure they are the right type for your export method. For example, an `app-store` distribution method requires an App Store type provisioning profile and a Distribution certificate.\n\n  Check **Debugging** for additional options to run the Step. The **Additional options for xcodebuild command** input allows you add any flags that the `xcodebuild` command supports.\n\n  Make sure the **Scheme** and **Build configuration** inputs contain values that actually exist in your Xcode project.\n\n  ### Useful links\n\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/create-signed-ipa-for-xcode/\n  - https://devcenter.bitrise.io/code-signing/ios-code-signing/resigning-an-ipa/\n  - https://devcenter.bitrise.io/deploy/ios-deploy/ios-deploy-index/\n\n  ### Related Steps\n\n  - [Certificate and profile installer](https://www.bitrise.io/integrations/steps/certificate-and-profile-installer)\n  - [iOS Auto Provision](https://www.bitrise.io/integrations/steps/ios-auto-provision)\n  - [Deploy to iTunesConnect](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-deliver)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-12-02T08:09:49.354078372Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: c4825fa38e9bc0b1fc333d34957f24fafd03f568\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-12-07T11:50:25.102536651Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: eb2baab896e6549cad464c27ebc43a4aaa666ed1\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-12-13T13:42:41.774363382Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 43b4b09f1377167049791b3167b71418b91ba45f\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2021-12-17T16:08:48.683614704Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 47ecb5906a50b4bb1f9eabeb1826634b3de04027\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-01-06T17:32:05.349149646Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 47f2c49853f0c40a6bfe18b21bf005ec37e5b969\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-01-11T08:49:08.744020291Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 5c9699bcfa5fdab70fd8d47b1786025a793ee4d6\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.6/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-01-20T13:50:33.417111996Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 2511d2c9c5a830e4bc53e3ec61906da98cc7ec05\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.7/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-01-28T08:42:35.890842318Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 51608700dae31cab655971d7fcbb098ac4d5dc7d\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.2.8/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-02-23T21:17:37.051631167Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f92bd475f30fed98bbdbd335b1f19689216fb545\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.3.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-03-07T08:07:41.212164639Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 99aa48e129ad425e91075948df6ffa6ff6b6870c\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.3.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-03-21T10:21:08.959499707Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: d2b29bb4f30e4f3d4b29bbad0bbc051d561d201d\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.3.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-04-14T15:23:54.668013454Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 2b88aa60e8a52cb4cb9dcc5aa4382e045d38a326\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.3.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-05-04T13:59:23.700087612Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: ffdfc83e7c9561db75fe1e8044767b1082c11fe1\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.4.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\\n`).\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-05-11T15:48:41.910846524Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 16729ba49389a2368689f6e6e6b8503cc6d394ed\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.5.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-05-25T09:05:36.515183018Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: d6100891055e13cac9e7a2f1da17d993585aafc3\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      If empty, no setting is changed. This is required when the `-xcconfig` additional option is used.\n\n      When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings. Can be the contents,\n      file path or empty.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      When setting the `-xcconfig` option, makes sure to clear the \"Build settings (xcconfig)\" input, as can not specify both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.5.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-05-31T08:33:20.521891623Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: c55aa3e0e8ca07dda3bcd0765d798e3e48070766\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      If empty, no setting is changed. This is required when the `-xcconfig` additional option is used.\n\n      When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings. Can be the contents,\n      file path or empty.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      When setting the `-xcconfig` option, makes sure to clear the \"Build settings (xcconfig)\" input, as can not specify both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.5.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-06-01T13:42:32.199386116Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 87d58cd4e1d223724c687a0e96168acc44801674\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\ndeps:\n  check_only:\n  - name: xcode\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.6.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-08-10T13:27:54.269867331Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 013d8733c1f9674d0dee08cabe694d2231cec66b\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.7.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-09-21T07:07:01.959267189Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 9f4ef188d017b110374ea71ba9445bae1acfa6ef\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.7.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2022-12-19T15:49:27.289670244Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 2b0843ef8b74a7742a4c39504b968b852859faaa\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.7.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-03-01T10:11:40.446262617Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 0d41c4805683ea1858001d0c40d6a8237463fd98\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.8.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-06-16T12:25:54.430232399Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 1b144352bb901ca2c7998e28c24e9ea62c437a4f\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/4.8.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-08-15T12:38:03.540198279Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 6767810079746f2324958e939bcc3dcf793ae9c6\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-08-30T06:11:09.349118587Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: bcec4063db2c0319dc799d4fe9c047cfbd84d34a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-10-11T13:20:36.776292981Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 95cdf6e80cca94419892112353f2b0c0917e1766\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-10-13T10:08:23.736255155Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: a04a86dbbd2ff357ceb196110895ef609b334a1b\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2023-12-12T11:19:46.050387965Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: d1f823a481da3cfb92d5821f2028e7b20a7c0ffa\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-01-30T12:45:04.196870085Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 9fe301071df5c2c70e052184c14d060853a44190\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-01-31T14:15:44.229895743Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 4ae06af4f41286f613971462496fe622647a091a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.0.6/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-02-07T10:01:17.400603426Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 1ce5c37fa788d77960e049a6311ee0c9ad2f6b8f\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.1.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-02-23T09:30:50.847496585Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 979d481546c89f37fccd529cfb27add42e4c245a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.1.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-02-27T13:42:22.968743737Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f7d8619ec543651ff9bd65eafcc69452f4158ea2\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.1.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-04-16T14:29:14.73874971Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 3e1f85aca9fb0d8dba270a6563c20c545d8c9b74\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.1.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-08-05T07:26:53.198180333Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f0f967c324700b5be227131d075d3b77410757c8\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.2.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-09-16T12:43:57.27654111Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 6ad5c535db9e1efd7b28741a6dbb5ef95dd9320b\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.2.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-10-15T07:27:40.195518798Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 8bb1aa325def00e71c5f1c2caec82bb72f0d3f2f\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.2.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-10-21T19:39:58.493898208Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 1274c93c6e81458bf9190eefcca83f5f0b847307\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.3.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2024-11-08T14:57:59.003071189Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: bb085da2d47162557ed07798d3ca0a8172fcb01f\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.3.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-01-08T09:58:03.398857605Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 2ff58427479d6b7be9a14f3986e949f771c52ff1\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.4.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-01-16T08:11:35.057040869Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: d6317e5df8a95c93e6661aeb8fc01cf6448a42a9\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.4.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-03-21T15:53:19.634229902Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 360f0ce9e002bb61fc017ceb18c09bfb7099e299\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.5.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-03-27T14:05:43.2475955Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 2fdb09356b9512759ab88b4b1ddca7cf48504c4c\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.5.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-04-08T13:20:19.827681718Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 3871405d85c9b0512f91666d69b1109ded369d66\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.6.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-04-10T13:16:35.867157262Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: cc31aeb2ac84e4b1862f521a664bc9e7d436b375\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.7.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-05-15T15:01:49.3214975Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 427a05a248b7a860271eee058ed129351d8d0fb2\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.8.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-07-01T14:34:37.955634145Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 928b8a38984ee7e22de1c660936f12d9c93dd039\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.8.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-08-18T08:52:08.85387402Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: a0506f5232dd6493e84c6c28ee047236ec0d120c\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.8.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-09-04T14:22:59.029932404Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: f02c4b2edb8802e6c05a06468aaa88bcf117a1d4\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.8.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-09-11T14:54:08.724355829Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 4acd46406a2bf87bb01a666d15c9f87ff60fd5ec\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.8.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-09-18T09:50:52.184460738Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 9b936e35093af51e8a29640c41d021d60360dc8f\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.8.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-10-14T09:06:05.531707317Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 1bc853eca31f5e110f0892ce064ae3c8a8b89d72\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.9.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-11-10T14:08:05.24001503Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 878fee4c309f38fbaa9521f48e6312d45cbfbf4a\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.9.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-11-10T14:59:28.963709229Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: b3d1b5c26427e6029943b1b1b53722e670496c09\nproject_type_tags:\n- ios\n- react-native\n- flutter\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.9.2/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-11-10T15:36:04.472093477Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 75fc4eeb7578681c173d79f2abf91b26d775b85e\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.9.3/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2025-11-11T14:58:05.097330626Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 5add2103feca1400c426572a06909165a1da1a6c\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.9.4/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2026-01-13T15:30:28.78710959Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 3f995438296d59dafc15cc1d9e295b6cc7678b0a\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/5.9.5/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are `none`: Disable collecting cache content and `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2026-01-30T15:48:26.942297378Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 50b1c761f7273e3833e4bbec0e5596214bcaa9e1\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/6.0.0/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  Caching:\n  - [Build Cache](https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/configuring-the-build-cache-for-xcode-in-the-bitrise-ci-environment.html)\n  - [Managing dependencies with SPM](https://docs.bitrise.io/en/bitrise-ci/dependencies-and-caching/ios-dependencies/managing-dependencies-with-spm.html)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2026-03-12T16:11:45.605163704Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 478fe9896f006207fc74b978e75edd92e524176d\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/xcode-archive/6.0.0/bin/xcode-archive-darwin-amd64\n    hash: sha256-c43c4bfe0b4655b6a08650de8b5eebe8e498c2236d0dd539a13090bccb7ec73e\n  darwin-arm64:\n    storage_uri: steps/xcode-archive/6.0.0/bin/xcode-archive-darwin-arm64\n    hash: sha256-b6208cf5b947473ac4250ad864ebf071806fd649e8f0b0a3747b7126a6ca3834\n  linux-amd64:\n    storage_uri: steps/xcode-archive/6.0.0/bin/xcode-archive-linux-amd64\n    hash: sha256-5e0b69bea0ed0c4cf167b17dc07c791fd6782de25515e68e6dce5de64c15635c\n  linux-arm64:\n    storage_uri: steps/xcode-archive/6.0.0/bin/xcode-archive-linux-arm64\n    hash: sha256-43e86bae7ca763f14cc65556b47068a61dcc9fb30044ed33755d2f5b5cb4c604\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/6.0.1/step.yml",
    "content": "title: Xcode Archive & Export for iOS\nsummary: Automatically manages your code signing assets, archives and exports an .ipa\n  in one Step.\ndescription: |-\n  The Step archives your Xcode project by running the `xcodebuild archive` command and then exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.\n  With this Step, you can use automatic code signing in a [CI environment without having to use Xcode](https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes).\n  In short, the Step:\n  - Logs you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  - Downloads any provisioning profiles needed for your project based on the **Distribution method**.\n  - Runs your build. It archives your Xcode project by running the `xcodebuild archive` command and exports the archive into an .ipa file with the `xcodebuild -exportArchive` command.\n  This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project path**: Add the path where the Xcode Project or Workspace is located.\n  2. **Scheme**: Add the scheme name you wish to archive your project later.\n  3. **Distribution method**: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.\n\n  Under **xcodebuild configuration**:\n  1. **Build configuration**: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.\n  2. **Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.\n  3. **Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options are `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n  The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **IPA export configuration**:\n  1. **Developer Portal team**: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.\n  2. **Rebuild from bitcode**: For non-App Store exports, should Xcode re-compile the app from bitcode?\n  3. **Include bitcode**: For App Store exports, should the package include bitcode?\n  4. **iCloud container environment**: If the app is using CloudKit, this input configures the `com.apple.developer.icloud-container-environment` entitlement. Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n  5. **Export options plist content**: Specifies a `plist` file content that configures archive exporting. If not specified, the Step will auto-generate it.\n\n  Under **Step Output Export configuration**:\n  1. **Output directory path**: This directory will contain the generated artifacts.\n  2. **Export all dSYMs**: Export additional dSYM files besides the app dSYM file for Frameworks.\n  3. **Override generated artifact names**:  This name is used as basename for the generated Xcode archive, app, `.ipa` and dSYM files. If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used. If Product Name is not specified, the Scheme will be used.\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\n\n  Caching:\n  - [Build Cache](https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/configuring-the-build-cache-for-xcode-in-the-bitrise-ci-environment.html)\n  - [Managing dependencies with SPM](https://docs.bitrise.io/en/bitrise-ci/dependencies-and-caching/ios-dependencies/managing-dependencies-with-spm.html)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive/issues\npublished_at: 2026-03-27T08:50:43.090275122Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive.git\n  commit: 9c99522130ed9e4c7f60fe8b04121364356d1518\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/xcode-archive/6.0.1/bin/xcode-archive-darwin-amd64\n    hash: sha256-c419fcbf4cf012232b97cfc2fa8b58fabbade3638f9e5036cc1fde57d757ef04\n  darwin-arm64:\n    storage_uri: steps/xcode-archive/6.0.1/bin/xcode-archive-darwin-arm64\n    hash: sha256-069d3a6e488531c7f460f324147d720eecd75d3a2df834f8a9f5982e57141318\n  linux-amd64:\n    storage_uri: steps/xcode-archive/6.0.1/bin/xcode-archive-linux-amd64\n    hash: sha256-a6a49805dc103533bc13b940e132ee11d32af554637351b096da00f6d66f892d\n  linux-arm64:\n    storage_uri: steps/xcode-archive/6.0.1/bin/xcode-archive-linux-arm64\n    hash: sha256-06849314ef7e19821fa5918b80f590a48c1546dab3aa63d92eb2f20941fab5fc\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Platform to archive the product for.\n      If set to `detect`, the step will try to detect the platform from the Xcode project settings.\n\n      Its value sets xcodebuild's `-destination` option.\n      Example: `-destination generic/platform=iOS Simulator`.\n    is_required: true\n    summary: Platform to archive the product for.\n    title: Platform\n    value_options:\n    - detect\n    - iOS\n    - watchOS\n    - tvOS\n    - visionOS\n  platform: detect\n- distribution_method: development\n  opts:\n    description: |-\n      Describes how Xcode should export the archive.\n\n      The input value sets the method in the export options plist content.\n\n      Note: In Xcode 15.3, distribution methods have been renamed. The values of this input reflect the old names. When running with Xcode 15.3 and later, the new names are passed to `xcodebuild`:\n      - `debugging`, when `development` is selected\n      - `app-store-connect`, when `app-store` is selected\n      - `release-testing`, when `ad-hoc` is selected\n      - `enterprise` is unchanged\n    is_required: true\n    summary: Describes how Xcode should export the archive.\n    title: Distribution method\n    value_options:\n    - development\n    - app-store\n    - ad-hoc\n    - enterprise\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `archive` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n\n      `-destination` is set automatically, unless specified explicitely.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how `xcodebuild` command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how `xcodebuild` command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- export_development_team: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      The Developer Portal team to use for this export\n\n      Defaults to the team used to build the archive.\n\n      Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Developer Portal team to use for this export.\n    title: Developer Portal team\n- compile_bitcode: \"yes\"\n  opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?\n    title: Rebuild from bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: For __App Store__ exports, should the package include bitcode?\n    title: Include bitcode\n    value_options:\n    - \"yes\"\n    - \"no\"\n  upload_bitcode: \"yes\"\n- icloud_container_environment: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment` entitlement.\n\n      Available options vary depending on the type of provisioning profile used, but may include: `Development` and `Production`.\n    summary: If the app is using CloudKit, this configures the `com.apple.developer.icloud-container-environment`\n      entitlement.\n    title: iCloud container environment\n- opts:\n    category: IPA export configuration\n    is_required: true\n    summary: Set this flag if the archive is for internal testflight distribution.\n      Distribution method has to be set to app-store\n    title: Testflight Internal Testing Only\n    value_options:\n    - \"yes\"\n    - \"no\"\n  testflight_internal_testing_only: \"no\"\n- export_options_plist_content: null\n  opts:\n    category: IPA export configuration\n    description: |-\n      Specifies a plist file content that configures archive exporting.\n\n      If not specified, the Step will auto-generate it.\n    summary: Specifies a plist file content that configures archive exporting.\n    title: Export options plist content\n- opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- export_all_dsyms: \"yes\"\n  opts:\n    category: Step Output Export configuration\n    is_required: true\n    summary: Export additional dSYM files besides the app dSYM file for Frameworks.\n    title: Export all dSYMs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- artifact_name: null\n  opts:\n    category: Step Output Export configuration\n    description: |-\n      This name will be used as basename for the generated Xcode Archive, App, IPA and dSYM files.\n\n      If not specified, the Product Name (`PRODUCT_NAME`) Build settings value will be used.\n      If Product Name is not specified, the Scheme will be used.\n    summary: This name will be used as basename for the generated Xcode Archive, App,\n      IPA and dSYM files.\n    title: Override generated artifact names\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_IPA_PATH: null\n  opts:\n    summary: Local path of the created .ipa file\n    title: .ipa file path\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: Local path of the generated `.app` directory\n    title: .app directory path\n- BITRISE_DSYM_DIR_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the directory which contains the dSYMs files.\n      If `export_all_dsyms` is set to `yes`, the Step will collect every dSYM (app dSYMs and framwork dSYMs).\n    title: The created .dSYM dir's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: |-\n      This Environment Variable points to the path of the zip file which contains the dSYM files.\n      If `export_all_dsyms` is set to `yes`, the Step will also collect framework dSYMs in addition to app dSYMs.\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    summary: The created .xcarchive file's path\n    title: .xcarchive file path\n- BITRISE_XCARCHIVE_ZIP_PATH: null\n  opts:\n    summary: The created .xcarchive.zip file's path.\n    title: .xcarchive.zip path\n- BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild archive` command log. The log\n      is placed into the `Output directory path`.\n    title: '`xcodebuild archive` command log file path'\n- BITRISE_XCODEBUILD_EXPORT_ARCHIVE_LOG_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild -exportArchive` command log.\n      The log is placed into the `Output directory path`.\n    title: '`xcodebuild -exportArchive` command log file path'\n- BITRISE_IDEDISTRIBUTION_LOGS_PATH: null\n  opts:\n    description: Exported when `xcodebuild -exportArchive` command fails.\n    title: Path to the xcdistributionlogs\n"
  },
  {
    "path": "steps/xcode-archive/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-archive-mac/0.1.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac/issues\npublished_at: 2015-12-24T18:08:47.991330459+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 6498e7c978e0b1528b87e88d55935a694cdb5436\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_dont_change_value: false\n    is_expand: true\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"yes\"\n  opts:\n    is_dont_change_value: false\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.0.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac/issues\npublished_at: 2015-12-26T11:04:24.152667471+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 2bc746cf85e65817ccc5347b1b4a2134b404a7e5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n      Specifies a path to a plist file that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      in case of the methods development, or App Store.\n      Auto generated export options available for export methods:\n      - app-store\n      - development\n      If step doesn't find export method based on provisioning profile, development will be use.\n      If you would like to export a Developer ID signed application, please create a plist with the corresponding method.\n      Call xcodebuild -help for available export options.\n    is_expand: true\n    is_required: false\n    title: Export options path\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.1.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac/issues\npublished_at: 2016-01-04T20:51:25.199715496+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: f1b74d027b7c1ede50a57a0975e695ae02ca73b8\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n      Specifies a path to a plist file that configures archive exporting.\n      Call xcodebuild -help for available export options.\n    is_expand: true\n    is_required: false\n    title: Export options path\n- export_format: APP\n  opts:\n    description: '\"In case of an Xcode 6 build, the format of the export has to be\n      specified as APP or PKG.\"'\n    is_required: true\n    title: Export format\n    value_options:\n    - APP\n    - PKG\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist, relevant for builds with Xcode version 7 and above.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.1.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac/issues\npublished_at: 2016-01-04T22:53:59.823395992+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 2d07f242929af670229e6020a688be21de5ea0da\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    is_expand: true\n    is_required: false\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.1.2/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac/issues\npublished_at: 2016-01-09T14:42:24.468906529+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: d94232975c4648c9cff3ee3741a20d30c85e5a54\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    is_expand: true\n    is_required: false\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.1.3/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-new-xcode-archive-mac/issues\npublished_at: 2016-03-11T07:27:46.441287558+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: be61a398cb937e7df488c002029b9994eae9657c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    is_expand: true\n    is_required: false\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.1.4/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-03-11T12:20:29.389294091+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 3204d5d61a935bbd4343f25d9d4f08b8f25cace7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: false\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    is_required: false\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: |-\n      If set to \"yes\" then it'll use the `PROVISIONING_PROFILE` (set\n      to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\n      and `CODE_SIGN_IDENTITY` (set to the value\n      of the `$BITRISE_CODE_SIGN_IDENTITY` environment)\n      Xcode Command Line parameters,\n      for force the use of specified Certificate and Provisioning Profile,\n      to the ones\n    is_expand: false\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    is_expand: true\n    is_required: false\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.1.6/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-07-12T13:32:31.060254734+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 6164952045d952a333697d6a8111383d224399d9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.10.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2020-10-29T09:29:24.756455054Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 279a9cc1af2fb6ecd83c3f7cf08415400ed97940\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.10.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2022-02-04T19:26:23.421668903Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 7b0a04b45bba0c5702244c59b95898959a8cbb41\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.10.2/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your macOS project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2022-03-03T09:51:24.238569547Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 8e3e9332626b8fa3516f9ca9ca88a152a9b14a4a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    is_required: true\n    summary: Scheme to use in archiving\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    summary: Do a clean Xcode build before the archive?\n    title: Clean build before archive\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    description: The created .app.zip or .pkg file's path\n    title: Exported file path\n- BITRISE_APP_PATH: null\n  opts:\n    description: The created .app path\n    title: '`.app` path'\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: The created .dSYM.zip file's path\n    title: '`.dSYM` ZIP path'\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path\n    title: '`.xcarchive` ZIP path'\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    description: The created .xcarchive dir's path\n    title: '`.xcarchive` path'\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.10.3/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: Create an archive for your macOS project\ndescription: |\n  The Step creates an archive using the `xcodebuild archive` command for your macOS project so you can share it, upload it, or deploy it.\n\n  ### Configuring the Step\n\n  Before you start:\n\n  Make sure your certificates are uploaded to Bitrise's **Code Signing** tab.\n\n  To configure the Step:\n\n  Under **app/pkg export configs**:\n\n  1. Select the signing method for your project Xcode should use in the **Export method** input.\n  1. (Optional) Specify a custom export option in the **Custom export options plist content** input. If you leave this input blank or the Step doesn't find an export method based on the provisioning profile(s), the Step will use the development method.\n\n  Under **xcodebuild configs**:\n\n  1. Add the path where your Xcode Project or Workspace is located in the **Project (or Workspace) path** input.\n  1. Add the scheme name you want to use to archive your project in the **Scheme name** input.\n  1. (Optional) By default, your Scheme defines which configuration is used, but you can override this option in the **Configuration name** input.\n  1. In the **Clean build before archive** input, select `yes`, if you want to run a `clean xcodebuild` before the `archive` action. Select `no` to skip this.\n  1. (Optional) If you wish to make your build times faster, and you don't need indexing, consider turning it off by setting **Disable indexing during the build** input to `yes`.\n\n  Under **force archive codesign settings**:\n\n  1. (Optional) If you want to force `xcodebuild` to use specified code sign identities or provisioning profiles, you can do so in the inputs under the **force archive codesign settings** tab.\n\n  Under **step output configs**:\n\n  1. Select an `xcodebuild` command log format in the **Output tool** input. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty, and `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n  1. Specify which directory will contain the generated `.app` or `.pkg` files and the `.dSYM.zip` files in the **Output directory** input.\n  1. Provide a name to use as a basename for the generated files in the **Generated Artifact Name** input.\n  1. If you want to export the archive, set the **Export the generated archive?** input to `yes`. This will compress the generated files into a zip file and move them to a folder `output_dir`.\n  1. If you want to export the dsyms, set the **Export all dsyms?** input to `yes`.\n  1. Set **Enable verbose logging** input to `yes` to produce more informative logs.\n\n  ### Troubleshooting\n\n  If you receive an error about missing signing certificates during this Step, make sure that your certificates are uploaded to Bitrise's **Code Signing** tab.\n\n  ### Useful links\n\n  * [iOS code signing](https://devcenter.bitrise.io/en/code-signing/ios-code-signing.html)\n\n  ### Related Steps\n\n  * [Export macOS Xcode archive](https://www.bitrise.io/integrations/steps/export-xcarchive-mac)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2022-10-03T10:39:11.402061836Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: c20f33db778197f7ddf1acefd2fbf0eef35baa8c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, Step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the Step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    is_required: true\n    summary: Scheme to use in archiving\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    summary: Do a clean Xcode build before the archive?\n    title: Clean build before archive\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the Step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` Step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    description: The created .app.zip or .pkg file's path\n    title: Exported file path\n- BITRISE_APP_PATH: null\n  opts:\n    description: The created .app path\n    title: '`.app` path'\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: The created .dSYM.zip file's path\n    title: '`.dSYM` ZIP path'\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path\n    title: '`.xcarchive` ZIP path'\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    description: The created .xcarchive dir's path\n    title: '`.xcarchive` path'\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.11.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: Create an archive for your macOS project\ndescription: |\n  The Step creates an archive using the `xcodebuild archive` command for your macOS project so you can share it, upload it, or deploy it.\n\n  ### Configuring the Step\n\n  Before you start:\n\n  Make sure your certificates are uploaded to Bitrise's **Code Signing** tab.\n\n  To configure the Step:\n\n  Under **app/pkg export configs**:\n\n  1. Select the signing method for your project Xcode should use in the **Export method** input.\n  1. (Optional) Specify a custom export option in the **Custom export options plist content** input. If you leave this input blank or the Step doesn't find an export method based on the provisioning profile(s), the Step will use the development method.\n\n  Under **xcodebuild configs**:\n\n  1. Add the path where your Xcode Project or Workspace is located in the **Project (or Workspace) path** input.\n  1. Add the scheme name you want to use to archive your project in the **Scheme name** input.\n  1. (Optional) By default, your Scheme defines which configuration is used, but you can override this option in the **Configuration name** input.\n  1. In the **Clean build before archive** input, select `yes`, if you want to run a `clean xcodebuild` before the `archive` action. Select `no` to skip this.\n  1. (Optional) If you wish to make your build times faster, and you don't need indexing, consider turning it off by setting **Disable indexing during the build** input to `yes`.\n\n  Under **force archive codesign settings**:\n\n  1. (Optional) If you want to force `xcodebuild` to use specified code sign identities or provisioning profiles, you can do so in the inputs under the **force archive codesign settings** tab.\n\n  Under **step output configs**:\n\n  1. Select an `xcodebuild` command log format in the **Output tool** input. Available options are `xcpretty`: The xcodebuild command's output will be prettified by xcpretty, and `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n  1. Specify which directory will contain the generated `.app` or `.pkg` files and the `.dSYM.zip` files in the **Output directory** input.\n  1. Provide a name to use as a basename for the generated files in the **Generated Artifact Name** input.\n  1. If you want to export the archive, set the **Export the generated archive?** input to `yes`. This will compress the generated files into a zip file and move them to a folder `output_dir`.\n  1. If you want to export the dsyms, set the **Export all dsyms?** input to `yes`.\n  1. Set **Enable verbose logging** input to `yes` to produce more informative logs.\n\n  ### Troubleshooting\n\n  If you receive an error about missing signing certificates during this Step, make sure that your certificates are uploaded to Bitrise's **Code Signing** tab.\n\n  ### Useful links\n\n  * [iOS code signing](https://devcenter.bitrise.io/en/code-signing/ios-code-signing.html)\n\n  ### Related Steps\n\n  * [Export macOS Xcode archive](https://www.bitrise.io/integrations/steps/export-xcarchive-mac)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2023-08-30T07:09:16.764574835Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 35b35de84c3d49e868800182e76e4733df5eabd9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, Step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the Step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    is_required: true\n    summary: Scheme to use in archiving\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    summary: Do a clean Xcode build before the archive?\n    title: Clean build before archive\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the Step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` Step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    description: The created .app.zip or .pkg file's path\n    title: Exported file path\n- BITRISE_APP_PATH: null\n  opts:\n    description: The created .app path\n    title: '`.app` path'\n- BITRISE_DSYM_PATH: null\n  opts:\n    description: The created .dSYM.zip file's path\n    title: '`.dSYM` ZIP path'\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    description: The created .xcarchive.zip file's path\n    title: '`.xcarchive` ZIP path'\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    description: The created .xcarchive dir's path\n    title: '`.xcarchive` path'\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.2.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-07-14T16:49:30.422059814+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 4b6cf8ca95a913c5e9fd54a1aaaa913eb4806fbf\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated Xcode archive (.xcarchive)\n      and the .app file.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.3.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-08-12T17:05:37.079620227+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: d243e4e2cfc0efaa9d52cba36fc92eb997ad20c3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.3.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-10-04T14:47:50.626197413+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: ee931b724c8787d00592aa9080d0dd7d50b51ce2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.3.2/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-10-28T10:50:20.167043408+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 00ff89ce19ff1f5fa1166e6d133ee87dc31c0223\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.3.3/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2016-12-20T12:17:16.402327711+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: c5e7e51e3fecf3c09ba3356ffb92d8c6b441d699\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\n- xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: Use force code signing attributes?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- export_options_path: null\n  opts:\n    description: |-\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: Export options path\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting used in `exportOptions` plist.\n      `none` means no resigning during export.\n      Upload and install proper certificates when exporting with different identity than the one used for archive.\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - development\n    - developer-id\n    - none\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app or .pkg file's path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.4.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2017-03-06T14:26:02.473751497+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 5c6444d1688f86449addbcc24352bb783492c9c7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    description: |-\n      The method for exporting the application.\n\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - developer-id\n    - development\n    - none\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- force_team_id: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- custom_export_options_plist_content: null\n  opts:\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- export_options_path: null\n  opts:\n    description: |-\n      __DEPRECATED!__\n\n      Use `custom_export_options_plist_content` instead.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: '[DEPRECATED] Export options path'\n- is_force_code_sign: \"no\"\n  opts:\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile_specifier/force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: '[DEPRECATED] Use force code signing attributes?'\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.4.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2017-05-17T16:22:43.170947631+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 70baf19a2c027688cfa2980e2683320d9cfd3290\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - developer-id\n    - development\n    - none\n- force_team_id: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_provisioning_profile_specifier: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- force_code_sign_identity: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    category: DEPRECATED configs\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile_specifier/force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: '[DEPRECATED] Use force code signing attributes?'\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    category: DEPRECATED configs\n    description: |-\n      __DEPRECATED!__\n\n      Use `custom_export_options_plist_content` instead.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: '[DEPRECATED] Export options path'\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.5.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2017-08-15T13:39:06.703940613+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 06469924fd8c4306fc9e36635940bf11ba5372e1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - developer-id\n    - development\n    - none\n- force_team_id: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_provisioning_profile_specifier: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- force_code_sign_identity: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    category: DEPRECATED configs\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile_specifier/force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: '[DEPRECATED] Use force code signing attributes?'\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    category: DEPRECATED configs\n    description: |-\n      __DEPRECATED!__\n\n      Use `custom_export_options_plist_content` instead.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: '[DEPRECATED] Export options path'\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.5.2/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2017-09-27T16:24:13.737903156+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: a97c606457e6c490d55fe670aaffd90dd575c1c0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - app-store\n    - developer-id\n    - development\n    - none\n- force_team_id: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_provisioning_profile_specifier: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- force_code_sign_identity: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_force_code_sign: \"no\"\n  opts:\n    category: DEPRECATED configs\n    description: \"__DEPRECATED!__ \\n\\nUse `force_code_sign_identity` and `force_provisioning_profile_specifier/force_provisioning_profile`\n      instead.\\n\\nIf set to \\\"yes\\\" then it'll use the `PROVISIONING_PROFILE` (set\\nto\n      the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)\\nand `CODE_SIGN_IDENTITY`\n      (set to the value\\nof the `$BITRISE_CODE_SIGN_IDENTITY` environment)\\nXcode\n      Command Line parameters,\\nfor force the use of specified Certificate and Provisioning\n      Profile,\\nto the ones\"\n    is_required: true\n    title: '[DEPRECATED] Use force code signing attributes?'\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_options_path: null\n  opts:\n    category: DEPRECATED configs\n    description: |-\n      __DEPRECATED!__\n\n      Use `custom_export_options_plist_content` instead.\n\n      Specifies a path to a plist file that configures archive exporting.\n      If not specified, it will generate an export options plist with the method specified in `export_method`.\n      Call xcodebuild -help for available export options.\n    title: '[DEPRECATED] Export options path'\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.6.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2017-11-23T10:50:51.647271451+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 1df88a1c883b52a9f1b909d0ac9c6848e49348bb\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.6.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2017-12-08T14:49:32.996499432+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 5a5759df75f8f65aa13e41dfc005aa2ca33d471f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.6.2/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2018-01-17T15:43:38.459231+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: a9f048805a64827952fe74b765e9360df24aee5f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.7.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2019-04-29T12:20:06.3802264Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 2a3b01f673288715a563d44bf77c10cc57950930\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If step doesn't find export method based on provisioning profile, development will be use.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code sign identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code sign group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **Capitalization also matters**, `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID, profile's name is not acceptable by xcodebuild.\n\n      How to get your UUID:\n\n      - In xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.8.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2019-10-15T09:30:19.792157486Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: 8af91aad080d85f324950a0e36ec131fab18273f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.9.0/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2020-09-01T14:03:29.177309403Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: f60650e6acba193d1a3d59061fd07c0d6287a3db\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/1.9.1/step.yml",
    "content": "title: Xcode Archive for Mac\nsummary: |-\n  Create an archive for your OS X project so you can share it, upload it, deploy it and catch them\n  all! Well, maybe not the last one.\ndescription: \"\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-archive-mac/issues\npublished_at: 2020-09-02T07:23:15.185616741Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-archive-mac.git\n  commit: aff65cf03f7919c04810a5c8a6384fc633dc8ce6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-archive-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- export_method: development\n  opts:\n    category: app/pkg export configs\n    description: |-\n      The method for exporting the application.\n\n      - `development`: Save a copy of the application signed with your Development identity.\n      - `app-store`: Sign and package application for distribution in the Mac App Store.\n      - `developer-id`: Save a copy of the application signed with your Developer ID.\n      - `none`: Export a copy of the application without re-signing.\n\n      See `xcodebuild -help` for more information.\n    is_required: true\n    title: Export method\n    value_options:\n    - development\n    - app-store\n    - developer-id\n    - none\n- custom_export_options_plist_content: null\n  opts:\n    category: app/pkg export configs\n    description: |-\n      Used for Xcode version 7 and above.\n\n      Specifies a custom export options plist content that configures archive exporting.\n      If empty, step generates these options based on provisioning profile,\n      with default values.\n\n      Auto generated export options available for export methods:\n\n      - app-store\n      - ad-hoc\n      - enterprise\n      - development\n\n      If the step doesn't find an export method based on the provisioning profile(s), the development method will be used.\n\n      Call `xcodebuild -help` for available export options.\n    title: Custom export options plist content\n- opts:\n    category: xcodebuild configs\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: xcodebuild configs\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    category: xcodebuild configs\n    description: |\n      (optional) The configuration to use. By default, your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not (for example, if you have a typo\n      in the value of this input), Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- is_clean_build: \"yes\"\n  opts:\n    category: xcodebuild configs\n    is_required: true\n    title: Do a clean Xcode build before the archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: xcodebuild configs\n    description: |\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: xcodebuild configs\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: null\n- disable_index_while_building: \"yes\"\n  opts:\n    category: xcodebuild configs\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- force_team_id: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use the specified Developer Portal team during archive.\n\n      Format example:\n\n      - `1MZX23ABCD4`\n    title: Force Developer Portal team to use during archive\n- force_code_sign_identity: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use specified Code Sign Identity.\n\n      Specify code signing identity as full ID (e.g. `Mac Developer: Bitrise Bot (VV2J4SV8V4)`)\n      or specify code signing group ( `Mac Developer` or `Mac Distribution` ).\n\n      You also have to **specify the Identity in the format it's stored in Xcode project settings**,\n      and **not how it's presented in the Xcode.app GUI**!\n      **The input is case sensitive**: `Mac Distribution` works but `mac distribution` does not!\n    title: Force code signing with Identity\n- force_provisioning_profile_specifier: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Used for Xcode version 8 and above.\n\n      Force xcodebuild to use specified Provisioning Profile.\n\n      How to get your Provisioning Profile Specifier:\n\n      - In Xcode make sure you disabled `Automatically manage signing` on your project's `General` tab\n      - Now you can select your Provisioning Profile Specifier's name as `Provisioning Profile` input value on your project's `General` tab\n      - `force_provisioning_profile_specifier` input value build up by the Team ID and the Provisioning Profile Specifier name, separated with slash character ('/'): `TEAM_ID/PROFILE_SPECIFIER_NAME`\n\n      Format example:\n\n      - `1MZX23ABCD4/My Provisioning Profile`\n    title: Force code signing with Provisioning Profile Specifier\n- force_provisioning_profile: null\n  opts:\n    category: force archive codesign settings\n    description: |-\n      Force xcodebuild to use the specified Provisioning Profile.\n\n      Use Provisioning Profile's UUID. The profile's name is not accepted by xcodebuild.\n\n      How to get your UUID:\n\n      - In Xcode select your project -> Build Settings -> Code Signing\n      - Select the desired Provisioning Profile, then scroll down in profile list and click on Other...\n      - The popup will show your profile's UUID.\n\n      Format example:\n\n      - c5be4123-1234-4f9d-9843-0d9be985a068\n    title: Force code signing with Provisioning Profile\n- opts:\n    category: step output configs\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: step output configs\n    description: |\n      This directory will contain the generated .app or .pkg file's and .dSYM.zip files.\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- artifact_name: ${scheme}\n  opts:\n    category: step output configs\n    description: This name will be used as basename for the generated .xcarchive,\n      .app or .pkg and .dSYM.zip files.\n    is_required: true\n    title: Generated Artifact Name\n- is_export_xcarchive_zip: \"no\"\n  opts:\n    category: step output configs\n    description: |\n      If this input is set to `yes`, the generated .xcarchive will be zipped and moved to `output_dir`.\n    is_required: true\n    title: Export the generated archive?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_export_all_dsyms: \"no\"\n  opts:\n    category: step output configs\n    description: |-\n      If this input is set to `yes` step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path.\n      Otherwise only .app dsym will be zipped and the zip path exported.\n    is_required: true\n    title: Export all dsyms?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: step output configs\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_EXPORTED_FILE_PATH: null\n  opts:\n    title: The created .app.zip or .pkg file's path\n- BITRISE_APP_PATH: null\n  opts:\n    title: The created .app path\n- BITRISE_DSYM_PATH: null\n  opts:\n    title: The created .dSYM.zip file's path\n- BITRISE_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive.zip file's path\n- BITRISE_MACOS_XCARCHIVE_PATH: null\n  opts:\n    title: The created .xcarchive dir's path\n"
  },
  {
    "path": "steps/xcode-archive-mac/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.10.0/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2019-04-18T15:12:09.326086603Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 32d7c3f99ae4571a2f5a5f0b39095190c5178c0a\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    summary: Simulator name\n    title: Simulator\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.0/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2019-10-30T12:15:32.793500081Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: d4cfaea41b0f9d21255e89ef983fe21c67aca6bd\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.1/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2019-11-06T17:10:23.123826226Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: bd9f118ca4949df48bbf4043950a01d9ee58cdde\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.2/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2019-12-17T13:02:49.026052066Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 74fb252cfd3640e6903c903f10ba15ac686f1b3d\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.3/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2020-09-10T10:54:58.879704681Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 24dca8a168776951eb55f845ae68e4338aa16963\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme's archive action\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.4/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2020-09-10T14:39:10.442809465Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 92907f5096554347d916c092d51f3ba74a6d2c91\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme's archive action\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.5/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2022-02-09T13:54:53.461262913Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 6d5c9586bcd0b74472d967ee0251b84a82cf37ac\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme's archive action\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.11.6/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: \"This Step runs the `xcodebuild` command to build and deploy your iOS,\n  tvOS, or watchOS app for a simulator. You can use this to perform quick tests for\n  your app or to show it off in a browser to your clients. \\nThe Step generates the\n  following outputs:\\n* `BITRISE_APP_DIR_PATH`: the path to the generated `.app` file.\\n*\n  `BITRISE_APP_DIR_PATH_LIST`: the path to the generated `.app` file and the paths\n  to every dependent target app. The paths are separated with the `|` character.\\n*\n  `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: the path to the log file of the raw\n  build results.\\n\\nThe Step also creates an `.xctestrun` file which you can use to\n  run tests.\\n\\nMake sure to include this Step after the Steps that install the necessary\n  dependencies, such as **Run Cocoapods Install** in your Workflow. \\n\\n### Configuring\n  the Step\\n\\nTo configure the Step:\\n\\n1. **Project (or Workspace) path**: The path\n  to your project's `.xcodeproj` or `.xworkspace` file. By default, this is stored\n  in an Environment Variable when you add your app to Bitrise.\\n1. **Scheme name**:\n  The Xcode Scheme of your project. This is stored in an Environment Variable by default\n  when you add your app to Bitrise.\\n1. **Device model**: The type of device you want\n  to run the app on. Set it exactly as it appears in the device selection menu in\n  Xcode.\\n1. **OS version**: The version of device operating system you want to run\n  the app on. Set it exactly as it appears in the device selection menu in Xcode.\n  The default value is latest.\\n1. **Platform**: The platform you want to run the\n  app on. The default value is `iOS`. Make sure that the values of the **Device model**\n  input and the **Platform** input are compatible: for example, if you set **Device\n  model** to `Apple TV 1080p`, set **Platform** to `tvOS`.\\n1. **Configuration name**:\n  By default, your Scheme's archive action defines which configuration is used, but\n  you can overwrite it with this option. Ensure that the Configuration you specify\n  exists in your Xcode Project; otherwise, this input will be ignored. \\n1. **Disable\n  indexing during the build**: By setting this input to `no`, you can disable indexing\n  during the build, which can speed up your build time.\\n1. **Enable caching of Swift\n  Package Manager packages**: To disable swift package caching, set this input to\n  `none`.\\n\\nUnder **Debug**:\\n\\n1. **Additional options for xcodebuild call**: You\n  can add additional options to the end of the xcodebuild call. For example, `-xcconfig\n  PATH -verbose`.\\n1. **Working directory**: If you would like to change the working\n  directory of the Step, you can do so with this input.\\n1. **Output directory path**:\n  You can change the output directory, which will contain the generated `.app` artifacts\n  with this input.\\n1. **Do a clean Xcode build before the build?**: Set this input\n  to `yes` to do a clean Xcode build before the build. \\n1. **Output tool**: You can\n  set this input to `xcpretty` to prettify your output. If you set it to `xcodebuild`,\n  the raw xcodebuild output will be printed. \\n1. **Enable verbose logging?**: Set\n  this input to `yes` if you want to enable verbose logs.\\n\\n### Useful links\\n\\n*\n  [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\\n\\n###\n  Related Steps\\n\\n* [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n*\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2022-03-11T15:51:14.759020505Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: f550cbf0e3f852f7c7611faeb46dc194198e4330\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it exactly as it appears in the device selection menu in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it exactly as it appears in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it exactly as it appears in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (Optional) The configuration to use. By default your Scheme's archive action\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the Step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.12.0/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: \"This Step runs the `xcodebuild` command to build and deploy your iOS,\n  tvOS, or watchOS app for a simulator. You can use this to perform quick tests for\n  your app or to show it off in a browser to your clients. \\nThe Step generates the\n  following outputs:\\n* `BITRISE_APP_DIR_PATH`: the path to the generated `.app` file.\\n*\n  `BITRISE_APP_DIR_PATH_LIST`: the path to the generated `.app` file and the paths\n  to every dependent target app. The paths are separated with the `|` character.\\n*\n  `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: the path to the log file of the raw\n  build results.\\n\\nThe Step also creates an `.xctestrun` file which you can use to\n  run tests.\\n\\nMake sure to include this Step after the Steps that install the necessary\n  dependencies, such as **Run Cocoapods Install** in your Workflow. \\n\\n### Configuring\n  the Step\\n\\nTo configure the Step:\\n\\n1. **Project (or Workspace) path**: The path\n  to your project's `.xcodeproj` or `.xworkspace` file. By default, this is stored\n  in an Environment Variable when you add your app to Bitrise.\\n1. **Scheme name**:\n  The Xcode Scheme of your project. This is stored in an Environment Variable by default\n  when you add your app to Bitrise.\\n1. **Device model**: The type of device you want\n  to run the app on. Set it exactly as it appears in the device selection menu in\n  Xcode.\\n1. **OS version**: The version of device operating system you want to run\n  the app on. Set it exactly as it appears in the device selection menu in Xcode.\n  The default value is latest.\\n1. **Platform**: The platform you want to run the\n  app on. The default value is `iOS`. Make sure that the values of the **Device model**\n  input and the **Platform** input are compatible: for example, if you set **Device\n  model** to `Apple TV 1080p`, set **Platform** to `tvOS`.\\n1. **Configuration name**:\n  By default, your Scheme's archive action defines which configuration is used, but\n  you can overwrite it with this option. Ensure that the Configuration you specify\n  exists in your Xcode Project; otherwise, this input will be ignored. \\n1. **Disable\n  indexing during the build**: By setting this input to `no`, you can disable indexing\n  during the build, which can speed up your build time.\\n1. **Allow Codesigning**:\n  When building an app for the simulator, code signing is not required and is set\n  to `no` by default. On rare occasions though, you may need to set the flag to `yes`,\n  usually when working with certain test cases or third-party dependencies. \\n1. **Enable\n  caching of Swift Package Manager packages**: To disable swift package caching, set\n  this input to `none`.\\n\\nUnder **Debug**:\\n\\n1. **Additional options for xcodebuild\n  call**: You can add additional options to the end of the xcodebuild call. For example,\n  `-xcconfig PATH -verbose`.\\n1. **Working directory**: If you would like to change\n  the working directory of the Step, you can do so with this input.\\n1. **Output directory\n  path**: You can change the output directory, which will contain the generated `.app`\n  artifacts with this input.\\n1. **Do a clean Xcode build before the build?**: Set\n  this input to `yes` to do a clean Xcode build before the build. \\n1. **Output tool**:\n  You can set this input to `xcpretty` to prettify your output. If you set it to `xcodebuild`,\n  the raw xcodebuild output will be printed. \\n1. **Enable verbose logging?**: Set\n  this input to `yes` if you want to enable verbose logs.\\n\\n### Useful links\\n\\n*\n  [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\\n\\n###\n  Related Steps\\n\\n* [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\\n*\n  [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\\n\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2022-05-13T13:12:23.722409765Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: a8b46afca7f18b25dd4b43a695ad603aaf7bad53\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it exactly as it appears in the device selection menu in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    title: Device model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it exactly as it appears in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it exactly as it appears in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (Optional) The configuration to use. By default your Scheme's archive action\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- code_signing_allowed: \"no\"\n  opts:\n    description: |-\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      Only on rare occasions do you need to set the flag to \"yes\", usually when working with certain test cases or third-party dependencies.\n    title: Code Signing Allowed\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the Step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.12.1/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2022-11-04T11:15:10.753919999Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 35c2a4f2a68a16c68db54e9e78f42ec1ec3532e7\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      _xcodebuild steps:_\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      _xcodebuild steps:_\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set this exactly as it appears in the device selection menu in Xcode's device selection UI.\n\n      A couple of examples (the actual available options depend on which versions are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K\n\n      Don't forget to set the platform to `tvOS Simulator` in order to use an Apple TV simulator.\n    is_required: true\n    summary: The simulated device to use when building\n    title: Device Model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set this exactly as it appears in Xcode's device selection UI.\n\n      A couple of format examples (the actual available options depend on which versions are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: true\n    summary: The OS version to build for\n    title: OS Version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set this exactly as it appears in Xcode's device selection UI.\n\n      A couple of examples (the actual available options depend on which versions are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    summary: The platform to build for (iOS or tvOS)\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (Optional) The name of the Xcode Configuration to use (Debug, Release, etc.). By default your Scheme's archive action defines which Configuration should be used, but this can be overridden it with this option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: The name of the Xcode Configuration to use when building\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      When this input is enabled, `COMPILER_INDEX_STORE_ENABLE=NO` is added to the `xcodebuild` command, which disables indexing while building. Disabling this could speed up your builds by eliminating a (normally) unnecessary step.\n\n      Indexing is useful for certain editor features — like autocompletion, jump to definition, and code information lookup — but these features are generally not necessary in a CI environment.\n    summary: This may speed up builds by skipping indexing while building.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- code_signing_allowed: \"no\"\n  opts:\n    description: |-\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n    summary: Whether or not to allow code signing for this build\n    title: Code signing allowed\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: The working directory of the Step\n    summary: The working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    summary: Whether or not to do a clean build before building\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_expand: false\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path to the raw build results log file.\n\n      If `output_tool` is set to `xcpretty` and the build fails, this log will contain the build output.\n    summary: The path to the full build output log\n    title: Full raw build output filepath\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.12.2/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2023-02-08T18:09:43.972734124Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: c86330cd1d64d6d6db6cf312c80d4b7d33507fcc\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      _xcodebuild steps:_\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      _xcodebuild steps:_\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set this exactly as it appears in the device selection menu in Xcode's device selection UI.\n\n      A couple of examples (the actual available options depend on which versions are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K\n\n      Don't forget to set the platform to `tvOS Simulator` in order to use an Apple TV simulator.\n    is_required: true\n    summary: The simulated device to use when building\n    title: Device Model\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set this exactly as it appears in Xcode's device selection UI.\n\n      A couple of format examples (the actual available options depend on which versions are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: true\n    summary: The OS version to build for\n    title: OS Version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set this exactly as it appears in Xcode's device selection UI.\n\n      A couple of examples (the actual available options depend on which versions are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    summary: The platform to build for (iOS or tvOS)\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: null\n  opts:\n    description: |-\n      (Optional) The name of the Xcode Configuration to use (Debug, Release, etc.). By default your Scheme's archive action defines which Configuration should be used, but this can be overridden it with this option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: The name of the Xcode Configuration to use when building\n    title: Configuration name\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      When this input is enabled, `COMPILER_INDEX_STORE_ENABLE=NO` is added to the `xcodebuild` command, which disables indexing while building. Disabling this could speed up your builds by eliminating a (normally) unnecessary step.\n\n      Indexing is useful for certain editor features — like autocompletion, jump to definition, and code information lookup — but these features are generally not necessary in a CI environment.\n    summary: This may speed up builds by skipping indexing while building.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- code_signing_allowed: \"no\"\n  opts:\n    description: |-\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n    summary: Whether or not to allow code signing for this build\n    title: Code signing allowed\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: The working directory of the Step\n    summary: The working directory of the Step\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    summary: Whether or not to do a clean build before building\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_expand: false\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path to the raw build results log file.\n\n      If `output_tool` is set to `xcpretty` and the build fails, this log will contain the build output.\n    summary: The path to the full build output log\n    title: Full raw build output filepath\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.9.0/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2018-08-10T16:37:05.687217292+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 4476ea04cd3b4086b75710e64c4bd09c998f68de\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    summary: Simulator name\n    title: Simulator\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.9.1/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2018-09-06T15:49:35.154596447Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 606d26dca2a48a79cebc15624ea49865ec454fc1\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    summary: Simulator name\n    title: Simulator\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.9.2/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2018-09-26T11:11:10.622961321Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 0b9278989088be35fe3dc3bb67075545d6c68ac2\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    summary: Simulator name\n    title: Simulator\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.9.3/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2018-12-17T16:31:45.467783537Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 34c5f8c3ef05c78a80a3847c279633319ced9036\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    summary: Simulator name\n    title: Simulator\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/0.9.4/step.yml",
    "content": "title: Xcode build for simulator\nsummary: Runs Xcode Build command for simulators.\ndescription: |\n  Runs Xcode Build command for simulators\n  for iOS, tvOS or watchOS.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2018-12-21T13:52:46.13127786Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 414d08f760b1ff51773fe3eda8728667e630288b\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ndeps:\n  brew:\n  - name: go\n  apt_get:\n  - name: go\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: \"true\"\n    summary: Simulator name\n    title: Simulator\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * \"8.4\"\n      * latest\n    is_required: \"true\"\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: \"true\"\n    title: Platform\n    value_options:\n    - iOS\n    - tvOS\n  simulator_platform: iOS\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    is_required: \"true\"\n    title: Configuration name\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: \"true\"\n    title: Do a clean Xcode build before the build?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    title: The generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path + every dependent target's app path.\n\n\n      The paths are separated with `|` character, eg: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/1.0.0/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2023-06-30T11:34:09.806218364Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 3f19ebc35e77eed1e2d4a57354ca073253aaab1b\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: generic/platform=iOS Simulator\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n    value_options:\n    - generic/platform=iOS Simulator\n    - generic/platform=watchOS Simulator\n    - generic/platform=tvOS Simulator\n- opts:\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      *Code signing allowed: Whether or not to allow code signing for this build*\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig), allow code signing\n  xcconfig_content: |-\n    CODE_SIGNING_ALLOWED=NO\n    COMPILER_INDEX_STORE_ENABLE = NO\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used. (Defined in the Scheme's archive action )\n\n      The input value sets xcodebuild's `-configuration` option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `build` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step Output Export configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODEBUILD_BUILD_FOR_SIMULATOR_LOG_PATH: null\n  opts:\n    description: |-\n      The file path of the raw `xcodebuild build` command log. The log is placed into the `Output directory path`.\n\n      Only set if `log_formatter` is set to `xcpretty`.\n    summary: The path to the full build output log\n    title: '`xcodebuild build` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/2.0.0/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2023-08-30T06:17:43.360329659Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: cf15fb75408c26af8338b1b9131ed3dfc6d3a2d1\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: generic/platform=iOS Simulator\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n    value_options:\n    - generic/platform=iOS Simulator\n    - generic/platform=watchOS Simulator\n    - generic/platform=tvOS Simulator\n- opts:\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      *Code signing allowed: Whether or not to allow code signing for this build*\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig), allow code signing\n  xcconfig_content: |-\n    CODE_SIGNING_ALLOWED=NO\n    COMPILER_INDEX_STORE_ENABLE = NO\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used. (Defined in the Scheme's archive action )\n\n      The input value sets xcodebuild's `-configuration` option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `build` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step Output Export configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n\n      - `none`: Disable collecting cache content\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODEBUILD_BUILD_FOR_SIMULATOR_LOG_PATH: null\n  opts:\n    description: |-\n      The file path of the raw `xcodebuild build` command log. The log is placed into the `Output directory path`.\n\n      Only set if `log_formatter` is set to `xcpretty`.\n    summary: The path to the full build output log\n    title: '`xcodebuild build` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/3.0.0/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2024-08-27T06:28:41.879849249Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 0c3b871ba9e540592179bdc00d45a0eefe4bbfe6\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: generic/platform=iOS Simulator\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n    value_options:\n    - generic/platform=iOS Simulator\n    - generic/platform=watchOS Simulator\n    - generic/platform=tvOS Simulator\n- opts:\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      *Code signing allowed: Whether or not to allow code signing for this build*\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig), allow code signing\n  xcconfig_content: |-\n    CODE_SIGNING_ALLOWED=NO\n    COMPILER_INDEX_STORE_ENABLE = NO\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used. (Defined in the Scheme's archive action )\n\n      The input value sets xcodebuild's `-configuration` option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `build` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step Output Export configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODEBUILD_BUILD_FOR_SIMULATOR_LOG_PATH: null\n  opts:\n    description: |-\n      The file path of the raw `xcodebuild build` command log. The log is placed into the `Output directory path`.\n\n      Only set if `log_formatter` is set to `xcpretty`.\n    summary: The path to the full build output log\n    title: '`xcodebuild build` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/3.0.1/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2025-09-04T14:23:30.47116686Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 5e0d628bd46d7fc90f442ac0e2a63baa9a76cb46\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: generic/platform=iOS Simulator\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n    value_options:\n    - generic/platform=iOS Simulator\n    - generic/platform=watchOS Simulator\n    - generic/platform=tvOS Simulator\n- opts:\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      *Code signing allowed: Whether or not to allow code signing for this build*\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig), allow code signing\n  xcconfig_content: |-\n    CODE_SIGNING_ALLOWED=NO\n    COMPILER_INDEX_STORE_ENABLE = NO\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used. (Defined in the Scheme's archive action )\n\n      The input value sets xcodebuild's `-configuration` option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `build` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step Output Export configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODEBUILD_BUILD_FOR_SIMULATOR_LOG_PATH: null\n  opts:\n    description: |-\n      The file path of the raw `xcodebuild build` command log. The log is placed into the `Output directory path`.\n\n      Only set if `log_formatter` is set to `xcpretty`.\n    summary: The path to the full build output log\n    title: '`xcodebuild build` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/3.0.2/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2025-09-11T14:13:47.939947734Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 1f939c3ad9e397ef2c29561ecf4b882b5f9273ac\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: generic/platform=iOS Simulator\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n    value_options:\n    - generic/platform=iOS Simulator\n    - generic/platform=watchOS Simulator\n    - generic/platform=tvOS Simulator\n- opts:\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      *Code signing allowed: Whether or not to allow code signing for this build*\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig), allow code signing\n  xcconfig_content: |-\n    CODE_SIGNING_ALLOWED=NO\n    COMPILER_INDEX_STORE_ENABLE = NO\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used. (Defined in the Scheme's archive action )\n\n      The input value sets xcodebuild's `-configuration` option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `build` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step Output Export configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODEBUILD_BUILD_FOR_SIMULATOR_LOG_PATH: null\n  opts:\n    description: |-\n      The file path of the raw `xcodebuild build` command log. The log is placed into the `Output directory path`.\n\n      Only set if `log_formatter` is set to `xcpretty`.\n    summary: The path to the full build output log\n    title: '`xcodebuild build` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/3.0.3/step.yml",
    "content": "title: Xcode Build for Simulator\nsummary: Runs `xcodebuild` commands for simulators\ndescription: |\n  This Step runs the `xcodebuild` command to build and deploy an app to an iOS, tvOS, or watchOS simulator. You can use this to perform quick tests of your app, or to show it off in a browser to your clients.\n\n  The Step generates the following outputs:\n\n  - `BITRISE_APP_DIR_PATH`: The path to the generated `.app` file.\n  - `BITRISE_APP_DIR_PATH_LIST`: The path to the generated `.app` file, and the paths to every dependent target app.\n    (Paths are separated by the `|` (pipe) character.)\n  - `BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH`: The path to the raw log file for the build.\n\n  The Step also creates an `.xctestrun` file which you can use to run tests.\n\n  Make sure to include this Step after the Steps that install the necessary dependencies — such as _Run Cocoapods Install_ — in your Workflow.\n\n  ### Configuring the Step\n\n  Minimum configuration:\n\n  1. In the **Project path** input, enter the path to your Xcode Project or Workspace.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_PROJECT_PATH` Environment Variable.)\n  1. In the **Scheme** input, enter the name of the Scheme you'd like to use for building your project.\n    (Only necessary if you plan to use a different scheme than the one set in the `BITRISE_SCHEME` Environment Variable.)\n\n  For more configuration options, see the descriptions of other inputs in the `step.yml` or in the Workflow Editor.\n\n  ### Useful links\n\n  - [Deploying an iOS app for simulators](https://devcenter.bitrise.io/en/deploying/ios-deployment/deploying-an-ios-app-for-simulators.html)\n\n  ### Related Steps\n\n  - [Xcode build for testing for iOS](https://www.bitrise.io/integrations/steps/xcode-build-for-test)\n  - [Appetize.io deploy](https://www.bitrise.io/integrations/steps/appetize-deploy)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator/issues\npublished_at: 2025-11-13T12:48:17.976077529Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-simulator.git\n  commit: 833e31ab560aa43de8a7b9bec98db162d6cc69f5\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-simulator\ninputs:\n- opts:\n    description: |-\n      Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: generic/platform=iOS Simulator\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n    value_options:\n    - generic/platform=iOS Simulator\n    - generic/platform=watchOS Simulator\n    - generic/platform=tvOS Simulator\n- opts:\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      *Code signing allowed: Whether or not to allow code signing for this build*\n      When building an app for the simulator, code signing is not required and is set to \"no\" by default.\n      On rare occasions, you may need to set the flag to \"yes\" — usually when working with certain test cases or third-party dependencies.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig), allow code signing\n  xcconfig_content: |-\n    CODE_SIGNING_ALLOWED=NO\n    COMPILER_INDEX_STORE_ENABLE = NO\n- configuration: null\n  opts:\n    category: xcodebuild configuration\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used. (Defined in the Scheme's archive action )\n\n      The input value sets xcodebuild's `-configuration` option.\n\n      **If the Configuration specified in this input does not exist in your project, the Step will silently ignore the value, and fall back to using the Configuration specified in the Scheme.**\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `build` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step Output Export configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_APP_DIR_PATH: null\n  opts:\n    summary: The path to the generated (and copied) app directory\n    title: Generated (and copied) app directory\n- BITRISE_APP_DIR_PATH_LIST: null\n  opts:\n    description: |-\n      This output will include the main target app's path, plus every dependent target's app path.\n\n      The paths are separated by a `|` (pipe) character. (Example: `/deploy109787178/sample-apps-ios-workspace-swift.app|/deploy109787178/bitfall.sample-apps-ios-workspace-swift-watch.app`)\n    summary: List of the generated (and copied) app paths\n    title: List of the generated app paths\n- BITRISE_XCODEBUILD_BUILD_FOR_SIMULATOR_LOG_PATH: null\n  opts:\n    description: |-\n      The file path of the raw `xcodebuild build` command log. The log is placed into the `Output directory path`.\n\n      Only set if `log_formatter` is set to `xcpretty`.\n    summary: The path to the full build output log\n    title: '`xcodebuild build` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-simulator/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.1.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2018-10-05T14:48:58.818026962Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 7403fd0f0527b117e044af6a1f4365f7cc0dc697\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The generated *.xctestrun and app bundle zip ready for testing\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.1.1/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2018-10-08T13:07:49.695656641Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 33dd162911722b976ed92ded5292ca297b9b645d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The generated *.xctestrun and app bundle zip ready for testing\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.2.0/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2018-10-09T10:57:38.091782749Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: c8d0d909bdc91e612dbf2627daa6ec797d899dfa\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.2.1/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2018-11-16T16:58:27.804935902Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 327acd54ff8c70c66437c4f028082a7ac545c2de\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.2.2/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2018-12-21T13:31:48.147515593Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 13e675b6dbf4a22dc80328df43f0ad85a2b906d5\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.2.3/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2019-02-21T12:37:35.71046987Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: f7cb45fe021a9e857174e380879b7d2e9b488ed0\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.3.0/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2019-04-18T10:23:08.808674042Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: a05b3250aa446d0987faffe87fc414f12186fc49\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: \"true\"\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: \"true\"\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: \"true\"\n    title: Device destination\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: \"true\"\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: \"false\"\n    is_required: \"true\"\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: \"true\"\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.4.0/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: Performs xcodebuild's build-for-testing action, to build tests without\n  running them.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2019-10-30T12:17:28.8773762Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 9cb8316edaa24f76513c68dfc5892addb36d7f33\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check _Destinations_ section.\n    is_required: true\n    title: Device destination\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/0.4.1/step.yml",
    "content": "title: '[BETA] Xcode Build for testing for iOS'\nsummary: Performs xcodebuild's build-for-testing action\ndescription: \"The Step runs Xcode's `xcodebuild` command with the `build-for-testing`\n  option. This builds your app for testing and also creates an `.xctestrun` file.\n  \\n\\n### Configuring the Step \\n\\nAt a minimum, the Step needs valid values for three\n  inputs:\\n\\n- **Project (or Workspace) path**: This is the path to the `.xcodeproj`\n  or `.xcworkspace` file. In most cases, leave it on the default value.\\n- **Scheme\n  name**: The name of your Xcode scheme. By default, the Step will use the scheme\n  that was set when you added the app on Bitrise.\\n- **Device destination**: The device\n  and platform type to build the tests for. For available values call, `man xcodebuild`\n  and check the Destinations section. \\nWe also recommend checking out our [System\n  reports page](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  on GitHub: you can check out the available, pre-installed simulators and other tools.\n  \\n\\nOptionally, you can define the configuration to use in the **Configuration name**\n  input. Normally, the scheme defines the configuration type, such as **debug** or\n  **release**.\\n\\nThe Step can also cache your Swift PM dependencies. To enable caching,\n  make sure the **Enable caching of Swift Package Manager packages** input is set\n  to `swift_packages`.\\n\\n### Troubleshooting\\n\\nIn the **Debug** option group, you\n  can:\\n\\n- Add additional flags to the `xcodebuild` command. \\n- Enable verbose logging.\\n-\n  Change the output directory path and the output tool.\\n\\n### Useful links\\n\\n- [Running\n  Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n- [Building\n  from the Command Line with Xcode](https://developer.apple.com/library/archive/technotes/tn2339/_index.html)\\n\\n###\n  Related Steps \\n\\n- [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\\n-\n  [Xcode Analyze](https://www.bitrise.io/integrations/steps/xcode-analyze)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-07-22T09:42:26.22813327Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 1cdbc506262b55b3a448557b0f0f2e1d2f907c0c\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: A `.xcodeproj` or `.xcworkspace` path.\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    summary: The Scheme to use.\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    title: Configuration name\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Specify destination to build the testes for.\n      For available values call: `man xcodebuild` and check the _Destinations_ section.\n    is_required: true\n    title: Device destination\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- cache_level: swift_packages\n  opts:\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    is_required: true\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the xcodebuild call.\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    category: Debug\n    description: This directory will contain the generated .app artifacts.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: Enable verbose logging?\n    is_required: true\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_BUILD_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw build results log file.\n      If `output_tool=xcpretty` and the build fails this log will contain the build output.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.0.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: \"The Step runs Xcode's `xcodebuild` command with the `build-for-testing`\n  option. This builds your app for testing and also creates an `.xctestrun` file.\n  \\n\\n### Configuring the Step \\n\\nAt a minimum, the Step needs valid values for three\n  inputs:\\n\\n- **Project (or Workspace) path**: This is the path to the `.xcodeproj`\n  or `.xcworkspace` file. In most cases, leave it on the default value.\\n- **Scheme\n  name**: The name of your Xcode scheme. By default, the Step will use the scheme\n  that was set when you added the app on Bitrise.\\n- **Device destination**: The device\n  and platform type to build the tests for. For available values call, `man xcodebuild`\n  and check the Destinations section. \\nWe also recommend checking out our [System\n  reports page](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  on GitHub: you can check out the available, pre-installed simulators and other tools.\n  \\n\\nOptionally, you can define the configuration to use in the **Configuration name**\n  input. Normally, the scheme defines the configuration type, such as **debug** or\n  **release**.\\n\\nThe Step can also cache your Swift PM dependencies. To enable caching,\n  make sure the **Enable caching of Swift Package Manager packages** input is set\n  to `swift_packages`.\\n\\n### Troubleshooting\\n\\nIn the **Debug** option group, you\n  can:\\n\\n- Add additional flags to the xcodebuild command.\\n- Enable verbose logging.\\n-\n  Change the output directory path and the output tool.\\n\\n### Useful links\\n\\n- [Running\n  Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n- [Building\n  from the Command Line with Xcode](https://developer.apple.com/library/archive/technotes/tn2339/_index.html)\\n\\n###\n  Related Steps \\n\\n- [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\\n-\n  [Xcode Analyze](https://www.bitrise.io/integrations/steps/xcode-analyze)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-10-04T11:52:20.390022264Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 2a1187c93b40cb979fa866641ed37b8697526dfd\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: This is the path of the raw build results log file.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.0.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: \"The Step runs Xcode's `xcodebuild` command with the `build-for-testing`\n  option. This builds your app for testing and also creates an `.xctestrun` file.\n  \\n\\n### Configuring the Step \\n\\nAt a minimum, the Step needs valid values for three\n  inputs:\\n\\n- **Project (or Workspace) path**: This is the path to the `.xcodeproj`\n  or `.xcworkspace` file. In most cases, leave it on the default value.\\n- **Scheme\n  name**: The name of your Xcode scheme. By default, the Step will use the scheme\n  that was set when you added the app on Bitrise.\\n- **Device destination**: The device\n  and platform type to build the tests for. For available values call, `man xcodebuild`\n  and check the Destinations section. \\nWe also recommend checking out our [System\n  reports page](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  on GitHub: you can check out the available, pre-installed simulators and other tools.\n  \\n\\nOptionally, you can define the configuration to use in the **Configuration name**\n  input. Normally, the scheme defines the configuration type, such as **debug** or\n  **release**.\\n\\nThe Step can also cache your Swift PM dependencies. To enable caching,\n  make sure the **Enable caching of Swift Package Manager packages** input is set\n  to `swift_packages`.\\n\\n### Troubleshooting\\n\\nIn the **Debug** option group, you\n  can:\\n\\n- Add additional flags to the xcodebuild command.\\n- Enable verbose logging.\\n-\n  Change the output directory path and the output tool.\\n\\n### Useful links\\n\\n- [Running\n  Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n- [Building\n  from the Command Line with Xcode](https://developer.apple.com/library/archive/technotes/tn2339/_index.html)\\n\\n###\n  Related Steps \\n\\n- [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\\n-\n  [Xcode Analyze](https://www.bitrise.io/integrations/steps/xcode-analyze)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-10-08T11:04:37.62330397Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 874e944cd157c0127599d3a379e3b89134702515\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    title: 'Path to the built test directory (example: PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    title: 'Path to the built xctestrun file (example: PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: This is the path of the raw build results log file.\n    title: The full, raw build output file path\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.1.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app for testing and also creates an `.xctestrun` file.\n\n  ### Configuring the Step\n\n  At a minimum, the Step needs valid values for three inputs:\n\n  - **Project (or Workspace) path**: This is the path to the `.xcodeproj` or `.xcworkspace` file. In most cases, leave it on the default value.\n  - **Scheme name**: The name of your Xcode scheme. By default, the Step will use the scheme that was set when you added the app on Bitrise.\n  - **Device destination**: The device and platform type to build the tests for. For available values call, `man xcodebuild` and check the Destinations section.\n  We also recommend checking out our [System reports page](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) on GitHub: you can check out the available, pre-installed simulators and other tools.\n\n  Optionally, you can define the configuration to use in the **Configuration name** input. Normally, the scheme defines the configuration type, such as **debug** or **release**.\n\n  The Step can also cache your Swift PM dependencies. To enable caching, make sure the **Enable caching of Swift Package Manager packages** input is set to `swift_packages`.\n\n  ### Troubleshooting\n\n  In the **Debug** option group, you can:\n\n  - Add additional flags to the xcodebuild command.\n  - Enable verbose logging.\n  - Change the output directory path and the output tool.\n\n  ### Useful links\n\n  - [Running Xcode tests](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n  - [Building from the Command Line with Xcode](https://developer.apple.com/library/archive/technotes/tn2339/_index.html)\n\n  ### Related Steps\n\n  - [Xcode Test for iOS](https://www.bitrise.io/integrations/steps/xcode-test)\n  - [Xcode Analyze](https://www.bitrise.io/integrations/steps/xcode-analyze)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-12-07T10:52:32.140923017Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: b252209892dd3654d0c71fb7e881e6033c555b00\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.1.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-12-08T13:44:04.027350773Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 533912688c3c22017f239f8224e8bfdf7bf98f72\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.2.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-12-13T13:40:42.849254303Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: bc3be45ce91237855be3694f4ef36eb5791b2950\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.2.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2021-12-17T16:10:41.135890896Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: ac8ccf4b818860bad0d4908929b5d2236cdd6955\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.2.2/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-01-06T17:37:31.260891427Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 51ef2c9ae3659095d57abc46dde739c584866e27\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.2.3/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-01-20T13:51:47.215442473Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 60499ded0ea9f12f567ab27efc892de471b06a12\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.2.4/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-01-28T09:10:45.141968705Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 284613cad824ec1e09f2d08e89d09287ebbc9ca5\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.2.5/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-02-23T21:18:29.496584345Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: a9b11d3886a39e06f9b93ff97d9aeeab3a64be93\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.3.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-02-25T08:54:44.017258515Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 9b31a562861717e9f368a37573d5e2ec48b7b958\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n    is_required: true\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.3.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-03-21T10:23:10.322554907Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: b0e5ce4114afb97e3100a0b3f33737afc48ab0eb\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.3.2/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. The build settings must be separated by newline character (`\\n`). For example:\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n  The input value sets xcodebuild's `-xcconfig` option.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-04-14T15:07:42.038667926Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 4820d57e5eb982c6701b73be7ff3e0c6256bc574\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: Additional options to be added to the executed xcodebuild command.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    description: This directory will contain the generated artifacts.\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    description: If this input is set, the Step will print additional logs for debugging.\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    description: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/1.4.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-06-01T13:18:04.369563189Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 1906fb798bf2f5b6d160a37f876776dccdd0af1a\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_DIR_PATH: null\n  opts:\n    summary: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n    title: 'Path to the built test directory (example: `PROJECT_DERIVED_DATA/Build/Products/Debug-iphoneos`)'\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    summary: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n    title: 'Path to the built xctestrun file (example: `PROJECT_DERIVED_DATA/Build/Products/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`)'\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: The built test directory and the built xctestrun file compressed as a\n      single zip\n    title: The built test directory and the built xctestrun file compressed as a single\n      zip\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: The file path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/2.0.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-06-17T08:29:02.802143181Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: e8cfa57427a8a67716aaa6dc59a50ee387fb4cab\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/2.1.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-08-10T13:55:06.11031847Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 2860f87ffc4a2bedd36afb25cd29ccf105524828\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/2.1.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-10-06T12:00:17.11028711Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 81bf66fcfb9c9cebae78d302103753f417eb9a26\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/2.1.2/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2022-11-03T11:26:42.224350297Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 963bfcbe05ce5e1abaa3030860be176d827399ff\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/2.1.3/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2023-03-01T10:13:27.763787767Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 0aded2dab3ada2d4134b7d7dd9052301578fc064\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/2.2.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2023-06-16T12:24:34.123358025Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 920e4b0b08354c6dba44d1952da2ff60f40c9850\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.0.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2023-08-30T06:16:53.02686271Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: d788a0113cb9eb82d66d619e009026127dfcce33\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.0.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2024-10-21T20:11:09.597076054Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: d6dc79d334b42643570106b431407013aa41c856\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    is_required: false\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    is_required: false\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    is_required: false\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.1.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2024-11-21T12:55:59.28669387Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: dbed6ffcac25d9dd340b5dfe70d00437fd15f9f9\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.1.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-01-15T08:34:53.774707013Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: e2790c7c4717a4e2213c0d3b7f9b66c29708575a\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.2.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-04-01T11:43:42.949420984Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: b3cfae8a4f31022c1b05b79acaee2f37ab7871ad\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.0/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-04-25T11:42:25.92898402Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 5b4085cc28e2d7db9a072571f070ff225e16bbf6\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.1/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-05-16T09:57:49.143035901Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 5d1c6f333cb97ea5174df8cb4e62a6331d302cb1\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.10/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-11-13T08:23:26.248720422Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 80496e273ed80fb779cfdecca17f5245cb672095\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.2/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-06-18T14:14:12.53962918Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 90bc6cc598e4e12968122d9cf5692022c20155cb\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.3/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-08-27T08:52:34.732549747Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: b11eab7ec63dcdb583de2590f1444c0eff3f9e9a\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.4/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-09-02T12:18:15.714365343Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 76907f741007862a98d1b4cc937aad22527c31eb\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.5/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-09-04T14:23:27.413829388Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 2ad6b088e2d762764efcf247ed0ae6eff15d4010\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.6/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-09-11T14:55:00.444793138Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 8a65ac3c15592e1237fad65a00e6b190ea48a0c1\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.7/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-09-18T09:49:34.365651062Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: cab13f2dca887cd208ac3317aafe575ab17f53e5\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.8/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-09-25T12:46:41.536079348Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 53e849d42e90557c080b4ede7eb4a3bfadfaefc8\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/3.3.9/step.yml",
    "content": "title: Xcode Build for testing for iOS\nsummary: Performs xcodebuild's build-for-testing action\ndescription: |-\n  The Step runs Xcode's `xcodebuild` command with the `build-for-testing` option. This builds your app and associated tests so that you can, for example, upload it to a third-party testing service to run your tests on a real device.\n  The Step also creates an `.xctestrun` file.\n  To be able to run your tests on a real device it needs code signing. The **Automatic code signing method** Step input allows you to log you into your Apple Developer account based on the [Apple service connection you provide on Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html) and download any provisioning profiles needed for your project based on the **Distribution method**.\n  Please note that the **Automatic code signing method** input is by default set to `off`, so if you need code signing, select either the `api-key` or the `apple-id`option of the input.\n\n  ### Configuring the Step\n  Before you start:\n  - Make sure you have connected your [Apple Service account to Bitrise](https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html).\n  Alternatively, you can upload certificates and profiles to Bitrise manually, then use the **Certificate and Profile Installer** Step before this Step.\n  - Make sure certificates are uploaded to Bitrise's **Code Signing** tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.\n\n  To configure the Step:\n  1. **Project (or Workspace) path**: This is the path where the `.xcodeproj` or `.xcworkspace` files are localed.\n  2. **Scheme**: Add the scheme name you wish to build for testing.\n  3. **Build Configuration**: If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option.\n  4. **Device destination specifier**: Destination specifier describes the device to use as a destination. The input value sets xcodebuild's `-destination` option.\n\n  Under **xcodebuild configuration**\n  5. **Build settings (xcconfig)**:  Build settings to override the project's build settings. Can be the contents, file path or empty.\n  6. **Additional options for the xcodebuild command**:  Additional options to be added to the executed xcodebuild command.\n\n  Under **Xcode build log formatting**:\n  1. **Log formatter**: Defines how `xcodebuild` command's log is formatted. Available options: `xcpretty`: The xcodebuild command's output will be prettified by xcpretty. `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases.\n\n  Under **Automatic code signing**:\n  1. **Automatic code signing method**: Select the Apple service connection you want to use for code signing. Available options: `off` if you don't do automatic code signing, `api-key` [if you use API key authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-api-key.html), and `apple-id` [if you use Apple ID authorization](https://devcenter.bitrise.io/en/accounts/connecting-to-services/connecting-to-an-apple-service-with-apple-id.html).\n  2. **Register test devices on the Apple Developer Portal**: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this to `yes` may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n  3. **The minimum days the Provisioning Profile should be valid**: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.\n  4. The **Code signing certificate URL**, the **Code signing certificate passphrase**, the **Keychain path**, and the **Keychain password** inputs are automatically populated if certificates are uploaded to Bitrise's **Code Signing** tab. If you store your files in a private repo, you can manually edit these fields.\n\n  If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in the **App Store Connect connection override** category. Note that this only works if **Automatic code signing method** is set to `api-key`.\n\n  Under **Step Output configuration**:\n  1. **Output directory path**: This directory contains the generated artifacts.\n\n  Under **Caching**:\n  1. **Enable collecting cache content**: Defines what cache content should be automatically collected. Available options are:\n    - `none`: Disable collecting cache content\n    - `swift_packages`: Collect Swift PM packages added to the Xcode project\n\n  Under Debugging:\n  1. **Verbose logging***: You can set this input to `yes` to produce more informative logs.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-build-for-test/issues\npublished_at: 2025-10-14T09:04:55.379880152Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-build-for-test.git\n  commit: 8b8f28e4fe4998d06840932dd594e3b1755497e5\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- build\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-build-for-test\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- configuration: Debug\n  opts:\n    description: |-\n      Xcode Build Configuration.\n\n      If not specified, the default Build Configuration will be used.\n\n      The input value sets xcodebuild's `-configuration` option.\n    is_required: true\n    summary: Xcode Build Configuration.\n    title: Build Configuration\n- destination: generic/platform=iOS\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      Recommended values:\n      - `generic/platform=iOS` to build tests for physical devices\n      - `generic/platform=iOS Simulator` to build tests for Simulators\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Build tests for a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to build all the Test Plans or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Build tests for a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: null\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command’s output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- automatic_code_signing: \"off\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      This input determines which Bitrise Apple service connection should be used for automatic code signing.\n\n      Available values:\n      - `off`: Do not do any auto code signing.\n      - `api-key`: [Bitrise Apple Service connection with API Key](https://devcenter.bitrise.io/getting-started/connecting-to-services/setting-up-connection-to-an-apple-service-with-api-key/).\n      - `apple-id`: [Bitrise Apple Service connection with Apple ID](https://devcenter.bitrise.io/getting-started/connecting-to-services/connecting-to-an-apple-service-with-apple-id/).\n    is_required: true\n    summary: This input determines which Bitrise Apple service connection should be\n      used for automatic code signing.\n    title: Automatic code signing method\n    value_options:\n    - \"off\"\n    - api-key\n    - apple-id\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal.\n\n      Note that setting this to yes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.\n    is_required: true\n    summary: If this input is set, the Step will register the known test devices on\n      Bitrise from team members with the Apple Developer Portal.\n    title: Register test devices on the Apple Developer Portal\n    value_options:\n    - \"yes\"\n    - \"no\"\n  register_test_devices: \"no\"\n- opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set, the Step will register the listed devices from this file with the Apple Developer Portal.\n\n      The format of the file is a comma separated list of the identifiers. For example:\n      `00000000–0000000000000001,00000000–0000000000000002,00000000–0000000000000003`\n\n      And in the above example the registered devices appear with the name of `Device 1`, `Device 2` and `Device 3` in the Apple Developer Portal.\n\n      Note that setting this will have a higher priority than the Bitrise provided devices list.\n    summary: If this input is set, the Step will register the listed devices from\n      this file with the Apple Developer Portal.\n    title: Path of file containing the devices to be registered\n  test_device_list_path: null\n- min_profile_validity: \"0\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days.\n\n      Otherwise the Step renews the managed Provisioning Profile if it is expired.\n    is_required: true\n    summary: If this input is set to >0, the managed Provisioning Profile will be\n      renewed if it expires within the configured number of days.\n    title: The minimum days the Provisioning Profile should be valid\n- apple_team_id: \"\"\n  opts:\n    category: Automatic code signing\n    description: |-\n      The Apple Developer Portal team to use for downloading code signing assets.\n\n      Defining this is only required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams.\n    summary: The Apple Developer Portal team to use for downloading code signing assets.\n    title: Developer Portal team ID\n- certificate_url_list: $BITRISE_CERTIFICATE_URL\n  opts:\n    category: Automatic code signing\n    description: |-\n      URL of the code signing certificate to download.\n\n      Multiple URLs can be specified, separated by a pipe (`|`) character.\n\n      Local file path can be specified, using the `file://` URL scheme.\n    is_required: true\n    is_sensitive: true\n    summary: URL of the code signing certificate to download.\n    title: Code signing certificate URL\n- opts:\n    category: Automatic code signing\n    description: |-\n      Passphrases for the provided code signing certificates.\n\n      Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`|`) character.\n\n      Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass|`, `|pass|`, `|`)\n    is_required: false\n    is_sensitive: true\n    summary: Passphrases for the provided code signing certificates.\n    title: Code signing certificate passphrase\n  passphrase_list: $BITRISE_CERTIFICATE_PASSPHRASE\n- keychain_path: $HOME/Library/Keychains/login.keychain\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    summary: Path to the Keychain where the code signing certificates will be installed.\n    title: Keychain path\n- keychain_password: $BITRISE_KEYCHAIN_PASSWORD\n  opts:\n    category: Automatic code signing\n    is_dont_change_value: true\n    is_required: true\n    is_sensitive: true\n    summary: Password for the provided Keychain.\n    title: Keychain password\n- fallback_provisioning_profile_url_list: null\n  opts:\n    category: Automatic code signing\n    description: |\n      If set, provided provisioning profiles will be used on Automatic code signing error.\n\n      URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`|`) character.\n\n      You can specify a local path as well, using the `file://` scheme.\n      For example: `file://./BuildAnything.mobileprovision`.\n\n      Can also provide a local directory that contains files with `.mobileprovision` extension.\n      For example: `./profilesDirectory/`\n    is_sensitive: true\n    title: Fallback provisioning profile URLs\n- opts:\n    category: Step output configuration\n    is_required: true\n    summary: This directory will contain the generated artifacts.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    is_required: true\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- api_key_path: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Local path or remote URL to the private key (p8 file) for App Store Connect API.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      The input value can be a file path (eg. `$TMPDIR/private_key.p8`) or an HTTPS URL.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_id`, `api_key_issuer_id`).\n    summary: Local path or remote URL to the private key (p8 file). This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API private key\n- api_key_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_issuer_id`).\n    summary: Private key ID used for App Store Connect authentication. This overrides\n      the Bitrise-managed API connection.\n    title: App Store Connect API key ID\n- api_key_issuer_id: null\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Private key issuer ID used for App Store Connect authentication.\n      This overrides the Bitrise-managed API connection, only set this input if you want to control the API connection\n      on a step-level. Most of the time it's easier to set up the connection on the App Settings page on Bitrise.\n      This input only takes effect if the other two connection override inputs are set too (`api_key_path`, `api_key_id`).\n    summary: Private key issuer ID used for App Store Connect authentication. This\n      overrides the Bitrise-managed API connection.\n    title: App Store Connect API issuer ID\n- api_key_enterprise_account: \"no\"\n  opts:\n    category: App Store Connect connection override\n    description: |-\n      Indicates if the account is an enterprise type.\n      This overrides the Bitrise-managed API connection, only set this input if you know you have an enterprise account.\n    is_required: true\n    summary: Indicates if the account is an enterprise type. This overrides the Bitrise-managed\n      API connection.\n    title: App Store Connect API enterprise account\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- compression_level: 6\n  opts:\n    description: |-\n      ZIP compression level to control speed / archive size.\n\n      Valid values are between 0 and 9. Defaults to 6.\n      - 0: no compression\n      - 1: fastest compression\n      - 9: best compression\n    is_required: false\n    summary: ZIP compression level to control speed / archive size.\n    title: Compression level\noutputs:\n- BITRISE_TEST_BUNDLE_PATH: null\n  opts:\n    summary: Directory of the built targets' binaries and built associated tests.\n    title: Test Bundle directory\n- BITRISE_TEST_BUNDLE_ZIP_PATH: null\n  opts:\n    summary: Zipped directory of the built targets' binaries and built associated\n      tests.\n    title: Zipped Test Bundle directory\n- BITRISE_XCTESTRUN_FILE_PATH: null\n  opts:\n    description: |-\n      File path of the built xctestrun file (example: `$SYMROOT/ios-simple-objc_iphoneos12.0-arm64e.xctestrun`).\n\n      If `Test Plan` Step Input is set BITRISE_XCTESTRUN_FILE_PATH points to the provided Test Plan's xctestrun file.\n      Otherwise points to the scheme's default Test Plan's xctestrun file (or to the first xctestrun without default Test Plan).\n    summary: File path of the built xctestrun file.\n    title: xctestrun file path\n- BITRISE_XCODE_RAW_RESULT_TEXT_PATH: null\n  opts:\n    summary: File path of the raw `xcodebuild build-for-testing` command log.\n    title: '`xcodebuild build-for-testing` command log file path'\n"
  },
  {
    "path": "steps/xcode-build-for-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-build-version/0.0.4/step.yml",
    "content": "title: Get Xcode project version\nsummary: |\n  Gets version and build number of the project\ndescription: |\n  Gets project's version and build number\nwebsite: https://github.com/nodes-ios/bitrise-step-xcode-build-version\nsource_code_url: https://github.com/nodes-ios/bitrise-step-xcode-build-version\nsupport_url: https://github.com/nodes-ios/bitrise-step-xcode-build-version/issues\npublished_at: 2020-05-26T12:27:36.983107+01:00\nsource:\n  git: https://github.com/nodes-ios/bitrise-step-xcode-build-version.git\n  commit: f9b5c936bc586769dce3daa5762e5e4f597b1955\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Use it with Xcode 11 and higher.\n\n      If not set it tries to find it.\n    is_required: false\n    summary: Path to the 'xcodeproj'.\n    title: Path to the 'xcodeproj'\n  project_path: \"\"\n- info_plist_path: \"\"\n  opts:\n    description: |\n      File of your release 'Info.plist' file.\n\n      If not set it tries to find it.\n    is_required: false\n    summary: Path to the 'Info.plist' file.\n    title: Path to the 'Info.plist'\noutputs:\n- XBV_PROJECT_VERSION: null\n  opts:\n    description: |\n      Project Version, eg, 1.3.9\n    summary: Project version.\n    title: CFBundleShortVersionString\n- XBV_PROJECT_BUILD: null\n  opts:\n    description: |\n      Project build number, e.g., 85\n    summary: Project build number.\n    title: CFBundleVersion\n"
  },
  {
    "path": "steps/xcode-build-version/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xcode-create-device-pair/1.0.0/step.yml",
    "content": "title: Create Simulator Device Pair\nsummary: Creates an iPhone and Apple Watch simulator device pair\ndescription: |\n  Creates or finds an existing active simulator device pair between an iPhone and an Apple Watch.\n\n  The step looks up simulator devices by name and OS version, checks if an active pair already\n  exists between them, and creates one if needed.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-create-device-pair\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-create-device-pair\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-create-device-pair/issues\npublished_at: 2026-04-10T09:31:47.384725-05:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-create-device-pair.git\n  commit: 9f3b97bcaa1a949d77a69c4bdcfefb731ebbefc9\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-create-device-pair\nrun_if: .IsCI\ninputs:\n- iphone_device: Bitrise iOS default\n  opts:\n    description: |\n      The simulator device name as shown in `xcrun simctl list devices` and listed on bitrise.io/stacks.\n    is_required: true\n    summary: The name of the iPhone simulator device (e.g. \"iPhone 17 Pro\")\n    title: iPhone device name\n- ios_version: null\n  opts:\n    description: |\n      The iOS runtime version. Use dot notation (e.g. \"18.4\", \"17.5\").\n    is_required: true\n    summary: The iOS version for the iPhone simulator (e.g. \"18.4\")\n    title: iOS version\n- opts:\n    description: |\n      The simulator device name as shown in `xcrun simctl list devices` and listed on bitrise.io/stacks.\n    is_required: true\n    summary: The name of the Apple Watch simulator device (e.g. \"Apple Watch Series\n      11 (46mm)\")\n    title: Watch device name\n  watch_device: Apple Watch Series 11 (46mm)\n- opts:\n    description: |\n      The watchOS runtime version. Use dot notation (e.g. \"11.5\", \"26.0\").\n    is_required: true\n    summary: The watchOS version for the Watch simulator (e.g. \"11.5\")\n    title: watchOS version\n  watchos_version: null\n- delete_blocking_pairs: \"true\"\n  opts:\n    description: |\n      When true and pairing fails because a device has reached its maximum number of\n      allowed pairs, the step deletes the conflicting pair(s) and retries.\n      When false, the step fails immediately on a capacity error.\n    is_required: true\n    summary: Delete existing pairs blocking creation of the new pair\n    title: Delete blocking pairs on capacity error\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_DEVICE_PAIR_UDID: null\n  opts:\n    description: |\n      The UUID identifier of the active device pair between the specified iPhone and Apple Watch simulators.\n    summary: The UUID of the created or existing device pair\n    title: Device Pair UDID\n- BITRISE_IPHONE_UDID: null\n  opts:\n    description: |\n      The UDID of the iPhone simulator device that was matched by the given device name and iOS version.\n    summary: The UDID of the resolved iPhone simulator device\n    title: iPhone Simulator UDID\n- BITRISE_WATCH_UDID: null\n  opts:\n    description: |\n      The UDID of the Apple Watch simulator device that was matched by the given device name and watchOS version.\n    summary: The UDID of the resolved Apple Watch simulator device\n    title: Watch Simulator UDID\n"
  },
  {
    "path": "steps/xcode-create-device-pair/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-project-info/1.0.1/step.yml",
    "content": "title: Xcode Project Info\nsummary: Extracts version and build number to environment variables.\ndescription: |-\n  This step will simply read version and build number from given `Info.plist` path,\n  then export those to **APP_VERSION** and **APP_BUILD** environment variables.\n\n  After this you can use these variables in other steps (ex. sending message on Slack).\nwebsite: https://github.com/tadija/bitrise-step-xcode-project-info\nsource_code_url: https://github.com/tadija/bitrise-step-xcode-project-info\nsupport_url: https://github.com/tadija/bitrise-step-xcode-project-info/issues\npublished_at: 2016-04-21T17:49:32.149684094+02:00\nsource:\n  git: https://github.com/tadija/bitrise-step-xcode-project-info.git\n  commit: cc682e9a0b4ec39b3868cbe059f0486efe681690\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- versioning\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- info_plist_path: Info.plist\n  opts:\n    is_required: true\n    summary: Path to project's Info.plist file.\n    title: Info.plist file path\noutputs:\n- APP_VERSION: null\n  opts:\n    title: Version (CFBundleShortVersionString from Info.plist)\n- APP_BUILD: null\n  opts:\n    title: Build (CFBundleVersion from Info.plist)\n"
  },
  {
    "path": "steps/xcode-project-info/1.0.2/step.yml",
    "content": "title: Xcode Project Info\nsummary: Extracts version and build number to environment variables.\ndescription: |-\n  This step will simply read version and build number from given `Info.plist` path,\n  then export those to **APP_VERSION** and **APP_BUILD** environment variables.\n\n  After this you can use these variables in other steps (ex. sending message on Slack).\nwebsite: https://github.com/tadija/bitrise-step-xcode-project-info\nsource_code_url: https://github.com/tadija/bitrise-step-xcode-project-info\nsupport_url: https://github.com/tadija/bitrise-step-xcode-project-info/issues\npublished_at: 2016-04-25T13:15:37.659925407+02:00\nsource:\n  git: https://github.com/tadija/bitrise-step-xcode-project-info.git\n  commit: 4793020329dccfc179be4cdd9384f4e974d5d0b4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- xcode\n- versioning\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- info_plist_path: Info.plist\n  opts:\n    is_required: true\n    summary: Path to project's Info.plist file.\n    title: Info.plist file path\noutputs:\n- APP_VERSION: null\n  opts:\n    title: Version (CFBundleShortVersionString from Info.plist)\n- APP_BUILD: null\n  opts:\n    title: Build (CFBundleVersion from Info.plist)\n"
  },
  {
    "path": "steps/xcode-project-info/2.0.0/step.yml",
    "content": "title: Xcode Project Info\nsummary: Extracts Xcode project info data to environment variables.\ndescription: |-\n  This step will simply read Xcode Project Info data from `Info.plist` file,\n  then export that data to environment variables prefixed with **XPI_**.\n\n  After this you can use these environment variables in other steps (ex. sending message on Slack).\nwebsite: https://github.com/tadija/bitrise-step-xcode-project-info\nsource_code_url: https://github.com/tadija/bitrise-step-xcode-project-info\nsupport_url: https://github.com/tadija/bitrise-step-xcode-project-info/issues\npublished_at: 2016-05-05T13:18:52.770586331+02:00\nsource:\n  git: https://github.com/tadija/bitrise-step-xcode-project-info.git\n  commit: 18e5437229039efa79266cee505147b667d98a93\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- xamarin\n- cordova\n- ionic\n- react-native\ntype_tags:\n- utility\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- info_plist_path: Info.plist\n  opts:\n    description: \"Source directory is considered to be root directory created by the\n      Git Clone step.\\nIf your `Info.plist` file is in **RootDir/ProjectName** directory\n      (for example), \\nthen you should set this input to `ProjectName/Info.plist`.\"\n    is_required: true\n    summary: \"\"\n    title: Relative path from Source directory to Info.plist file\noutputs:\n- XPI_VERSION: null\n  opts:\n    title: Version (CFBundleShortVersionString from Info.plist)\n- XPI_BUILD: null\n  opts:\n    title: Build (CFBundleVersion from Info.plist)\n"
  },
  {
    "path": "steps/xcode-project-info/2.1.0/step.yml",
    "content": "title: Xcode Project Info\nsummary: Extracts Xcode project info data to environment variables.\ndescription: |-\n  This step will simply extract Xcode project information (Version and Build),\n  and export them into environment variables prefixed with **XPI_**.\n\n  Afterwards, you can use these environment variables in other steps (ie. sending message on Slack).\nwebsite: https://github.com/tadija/bitrise-step-xcode-project-info\nsource_code_url: https://github.com/tadija/bitrise-step-xcode-project-info\nsupport_url: https://github.com/tadija/bitrise-step-xcode-project-info/issues\npublished_at: 2020-04-22T19:28:47.441149+02:00\nsource:\n  git: https://github.com/tadija/bitrise-step-xcode-project-info.git\n  commit: 24855768b9d73f84942e293c4550e49b09440dd5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- artifact-info\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\ninputs:\n- info_plist_path: Info.plist\n  opts:\n    description: \"Source directory is considered to be root directory created by the\n      Git Clone step.\\nIf your `Info.plist` file is in **RootDir/ProjectName** directory\n      (for example), \\nthen you should set this input to `ProjectName/Info.plist`.\"\n    is_required: true\n    summary: \"\"\n    title: Relative path from Source directory to Info.plist file\n- opts:\n    description: |-\n      Required for Xcode 11+, since version & build numbers are no longer stored in Info.plist, but replaced by the variables $(MARKETING_VERSION) and $(CURRENT_PROJECT_VERSION).\n      The actual numbers should be extracted from the pbxproj file.\n    is_required: false\n    summary: \"\"\n    title: Relative path from Source directory to Xcode project file\n  xcodeproj_path: null\n- opts:\n    description: The version & build number can differ depending on the target. If\n      not specified, the default target will be used.\n    is_required: false\n    summary: \"\"\n    title: For Xcode 11+ projects, get the version & build for this target\n  target: null\noutputs:\n- XPI_VERSION: null\n  opts:\n    title: Version ($CFBundleShortVersionString or $MARKETING_VERSION)\n- XPI_BUILD: null\n  opts:\n    title: Build ($CFBundleVersion or $CURRENT_PROJECT_VERSION)\n"
  },
  {
    "path": "steps/xcode-project-info/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xcode-result-bundle-to-checks/1.0.0/step.yml",
    "content": "title: Xcode Result Bundle to GitHub Checks\nsummary: |\n  Generates a human-readable test report from the Xcode result bundle and shows it on GitHub Checks.\ndescription: |\n  Generates a human-readable test report from the Xcode result bundle and shows it on GitHub Checks.\nwebsite: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks\nsource_code_url: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks\nsupport_url: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks/issues\npublished_at: 2021-10-25T19:38:24.734504+09:00\nsource:\n  git: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks.git\n  commit: c74a7a55e73aa00a6468a351deed5648e271bc50\nproject_type_tags:\n  - ios\n  - macos\ntype_tags:\n  - test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n    - name: node\nis_always_run: true\nis_skippable: true\nrun_if: .IsCI\ninputs:\n  - xcresult_path: $BITRISE_XCRESULT_PATH\n    opts:\n      description: |\n        Path to the xcresult bundle.\n      is_expand: true\n      is_required: true\n      summary: Path to the xcresult bundle.\n      title: Result bundle path\n\n  - title: Xcode test results\n    opts:\n      description: |\n        Title for the check results.\n      is_expand: true\n      is_required: false\n      summary: Title for the check results.\n      title: Title\n\n  - github_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n    opts:\n      description: |\n        The name of the owner of the GitHub repository.\n      is_expand: true\n      is_required: false\n      summary: The name of the GitHub repository.\n      title: GitHub repository owner\n\n  - github_repo: $BITRISEIO_GIT_REPOSITORY_SLUG\n    opts:\n      description: |\n        The name of the GitHub repository.\n      is_expand: true\n      is_required: false\n      summary: The name of the GitHub repository.\n      title: GitHub repository\n\n  - head_sha: $GIT_CLONE_COMMIT_HASH\n    opts:\n      description: |\n        The SHA of the commit to check.\n      is_expand: true\n      is_required: false\n      is_dont_change_value: true\n      summary: The SHA of the commit to check.\n      title: Commit SHA-1 Hash\n"
  },
  {
    "path": "steps/xcode-result-bundle-to-checks/1.1.0/step.yml",
    "content": "title: Xcode Result Bundle to GitHub Checks\nsummary: |\n  Generates a human-readable test report from the Xcode result bundle and shows it on GitHub Checks.\ndescription: |\n  Generates a human-readable test report from the Xcode result bundle and shows it on GitHub Checks.\nwebsite: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks\nsource_code_url: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks\nsupport_url: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks/issues\npublished_at: 2021-10-25T19:38:24.734504+09:00\nsource:\n  git: https://github.com/kishikawakatsumi/bitrise-step-xcode-result-bundle-to-checks.git\n  commit: 69941364c7292e18db3f71c2a6acb4ad2f9fb723\nproject_type_tags:\n  - ios\n  - macos\ntype_tags:\n  - test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n    - name: node\nis_always_run: true\nis_skippable: true\nrun_if: .IsCI\ninputs:\n  - xcresult_path: $BITRISE_XCRESULT_PATH\n    opts:\n      description: |\n        Path to the xcresult bundle.\n      is_expand: true\n      is_required: true\n      summary: Path to the xcresult bundle.\n      title: Result bundle path\n\n  - title: Xcode test results\n    opts:\n      description: |\n        Title for the check results.\n      is_expand: true\n      is_required: false\n      summary: Title for the check results.\n      title: Title\n\n  - show_passed_tests: true\n    opts:\n      description: |\n        Whether to show passed tests.\n      is_expand: true\n      is_required: false\n      summary: Whether to show passed tests.\n      title: Show passed tests\n      value_options:\n        - \"false\"\n        - \"true\"\n\n  - show_code_coverage: true\n    opts:\n      description: |\n        Whether to show code coverage.\n      is_expand: true\n      is_required: false\n      summary: Whether to show code coverage.\n      title: Show code coverage\n      value_options:\n        - \"false\"\n        - \"true\"\n\n  - github_owner: $BITRISEIO_GIT_REPOSITORY_OWNER\n    opts:\n      description: |\n        The name of the owner of the GitHub repository.\n      is_expand: true\n      is_required: false\n      summary: The name of the GitHub repository.\n      title: GitHub repository owner\n\n  - github_repo: $BITRISEIO_GIT_REPOSITORY_SLUG\n    opts:\n      description: |\n        The name of the GitHub repository.\n      is_expand: true\n      is_required: false\n      summary: The name of the GitHub repository.\n      title: GitHub repository\n\n  - head_sha: $GIT_CLONE_COMMIT_HASH\n    opts:\n      description: |\n        The SHA of the commit to check.\n      is_expand: true\n      is_required: false\n      is_dont_change_value: true\n      summary: The SHA of the commit to check.\n      title: Commit SHA-1 Hash\n"
  },
  {
    "path": "steps/xcode-result-bundle-to-checks/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xcode-start-simulator/0.1.0/step.yml",
    "content": "title: Start Xcode simulator\nsummary: Starts an Xcode simulator.\ndescription: |-\n  Starts an Xcode simulator.\n\n  It uses the `xcrun simctl` command to launch a simulator, and optionally wait for it to finish booting.\n  The simulator will be running in the background after the Step exits, and can be used by later Steps in the workflow.\n\n  It allows two use cases:\n  * Boot simulator in the background and use it in the xcode-test Step:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n    - xcode-test:\n        inputs:\n        - project_path: ./ios-sample/ios-sample.xcodeproj\n        - scheme: ios-sample\n        # Simulator\n        - destination: $BITRISE_XCODE_DESTINATION # Use the same destination as the xcode-start-simulator Step\n    ```\n\n  * Detect if simulator timed out and restart the build:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n        - wait_for_boot_timeout: 90\n    - trigger-bitrise-workflow:\n        is_always_run: true\n        run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n        inputs:\n        - api_token: $INSERT_RESTART_TRIGGER_TOKEN\n        - workflow_id: insert_workflow\n    ```\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator/issues\npublished_at: 2022-06-22T22:08:28.396183+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator.git\n  commit: 320ffbfbb0ec740d08990bfcbb38b20ef20d71a5\nproject_type_tags:\n- ios\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\ndeps:\n  check_only:\n  - name: xcode\nis_always_run: false\nis_skippable: false\ninputs:\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the simulator device to be started.\n\n      The input value uses the same format as xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the simulator device to be started.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    description: |-\n      When larger than 0, will wait for the simulator boot to complete.\n\n      Setting this value to an int larger than 0 makes it possible to detect hangs or timeouts when booting simulator by waiting for the simulator to boot before this step completes.\n      If a timeout occurs, the `BITRISE_SIMULATOR_STATUS` output will be set to `hanged`.\n      The reccomended value is 90.\n\n      Using `0` (the default) enables the Simulator boot to occur in parallel to other Steps.\n    is_required: true\n    summary: When larger than 0, will wait for the simulator boot to complete.\n    title: Simulator boot timeout (in seconds)\n  wait_for_boot_timeout: 0\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: |-\n      If enabled, will shutdown and erase a simulator's contents and settings.\n\n      This option is not needed when starting from a clean state on a CI build.\n      It may be used when running testing multiple apps on the same simulator or for making sure that the simulator is indeed in a clean state when an app fails to install due to an unexpected issue.\n\n      When enabled erasing contents takes about a second.\n    is_required: true\n    summary: If enabled, will shutdown and erase a simulator's contents and settings.\n    title: Shutdown and erase simulator before use\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reset: \"no\"\noutputs:\n- BITRISE_SIMULATOR_STATUS: null\n  opts:\n    description: |\n      The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n\n      It can be used to trigger a new build conditionally:\n\n      ```\n      is_always_run: true\n      run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n      ```\n    title: The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n    value_options:\n    - booted\n    - failed\n    - hanged\n- BITRISE_XCODE_DESTINATION: null\n  opts:\n    description: |-\n      Device destination specifier\n\n      The destination specifer provided in the `destination` Input. It can be used as Input of other Steps, to avoid duplication.\n    title: Device destination specifier\n"
  },
  {
    "path": "steps/xcode-start-simulator/0.2.0/step.yml",
    "content": "title: Start Xcode simulator\nsummary: Starts an Xcode simulator.\ndescription: |-\n  Starts an Xcode simulator.\n\n  It uses the `xcrun simctl` command to launch a simulator, and optionally wait for it to finish booting.\n  The simulator will be running in the background after the Step exits, and can be used by later Steps in the workflow.\n\n  It allows two use cases:\n  * Boot simulator in the background and use it in the xcode-test Step:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n    - xcode-test:\n        inputs:\n        - project_path: ./ios-sample/ios-sample.xcodeproj\n        - scheme: ios-sample\n        # Simulator\n        - destination: $BITRISE_XCODE_DESTINATION # Use the same destination as the xcode-start-simulator Step\n    ```\n\n  * Detect if simulator timed out and restart the build:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n        - wait_for_boot_timeout: 90\n    - trigger-bitrise-workflow:\n        is_always_run: true\n        run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n        inputs:\n        - api_token: $INSERT_RESTART_TRIGGER_TOKEN\n        - workflow_id: insert_workflow\n    ```\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator/issues\npublished_at: 2022-09-12T14:42:28.249146423Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator.git\n  commit: 9fb2fbc69577d4246bb2038e628d6be1ef8244bd\nproject_type_tags:\n- ios\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\ndeps: {}\nis_always_run: false\nis_skippable: false\ninputs:\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the simulator device to be started.\n\n      The input value uses the same format as xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the simulator device to be started.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    description: |-\n      When larger than 0, will wait for the simulator boot to complete.\n\n      Setting this value to an int larger than 0 makes it possible to detect hangs or timeouts when booting simulator by waiting for the simulator to boot before this step completes.\n      If a timeout occurs, the `BITRISE_SIMULATOR_STATUS` output will be set to `hanged`.\n      The recommended value is 90.\n\n      Using `0` (the default) enables the Simulator boot to occur in parallel to other Steps.\n    is_required: true\n    summary: When larger than 0, will wait for the simulator boot to complete.\n    title: Simulator boot timeout (in seconds)\n  wait_for_boot_timeout: 0\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: |-\n      If enabled, will shutdown and erase a simulator's contents and settings.\n\n      This option is not needed when starting from a clean state on a CI build.\n      It may be used when running testing multiple apps on the same simulator or for making sure that the simulator is indeed in a clean state when an app fails to install due to an unexpected issue.\n\n      When enabled erasing contents takes about a second.\n    is_required: true\n    summary: If enabled, will shutdown and erase a simulator's contents and settings.\n    title: Shutdown and erase simulator before use\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reset: \"no\"\noutputs:\n- BITRISE_SIMULATOR_STATUS: null\n  opts:\n    description: |\n      The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n\n      It can be used to trigger a new build conditionally:\n\n      ```\n      is_always_run: true\n      run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n      ```\n    title: The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n    value_options:\n    - booted\n    - failed\n    - hanged\n- BITRISE_XCODE_DESTINATION: null\n  opts:\n    description: |-\n      Device destination specifier\n\n      The destination specifer provided in the `destination` Input. It can be used as Input of other Steps, to avoid duplication.\n    title: Device destination specifier\n"
  },
  {
    "path": "steps/xcode-start-simulator/0.2.1/step.yml",
    "content": "title: Start Xcode simulator\nsummary: Starts an Xcode simulator.\ndescription: |-\n  Starts an Xcode simulator.\n\n  It uses the `xcrun simctl` command to launch a simulator, and optionally wait for it to finish booting.\n  The simulator will be running in the background after the Step exits, and can be used by later Steps in the workflow.\n\n  It allows two use cases:\n  * Boot simulator in the background and use it in the xcode-test Step:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n    - xcode-test:\n        inputs:\n        - project_path: ./ios-sample/ios-sample.xcodeproj\n        - scheme: ios-sample\n        # Simulator\n        - destination: $BITRISE_XCODE_DESTINATION # Use the same destination as the xcode-start-simulator Step\n    ```\n\n  * Detect if simulator timed out and restart the build:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n        - wait_for_boot_timeout: 90\n    - trigger-bitrise-workflow:\n        is_always_run: true\n        run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n        inputs:\n        - api_token: $INSERT_RESTART_TRIGGER_TOKEN\n        - workflow_id: insert_workflow\n    ```\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator/issues\npublished_at: 2023-08-01T08:10:18.844186171Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator.git\n  commit: b63652023d4cbfb38831dfd223ec5bb10d79ef91\nproject_type_tags:\n- ios\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\ndeps: {}\nis_always_run: false\nis_skippable: false\ninputs:\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the simulator device to be started.\n\n      The input value uses the same format as xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the simulator device to be started.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    description: |-\n      When larger than 0, will wait for the simulator boot to complete.\n\n      Setting this value to an int larger than 0 makes it possible to detect hangs or timeouts when booting simulator by waiting for the simulator to boot before this step completes.\n      If a timeout occurs, the `BITRISE_SIMULATOR_STATUS` output will be set to `hanged`.\n      The recommended value is 90.\n\n      Using `0` (the default) enables the Simulator boot to occur in parallel to other Steps.\n    is_required: true\n    summary: When larger than 0, will wait for the simulator boot to complete.\n    title: Simulator boot timeout (in seconds)\n  wait_for_boot_timeout: 0\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: |-\n      If enabled, will shutdown and erase a simulator's contents and settings.\n\n      This option is not needed when starting from a clean state on a CI build.\n      It may be used when running testing multiple apps on the same simulator or for making sure that the simulator is indeed in a clean state when an app fails to install due to an unexpected issue.\n\n      When enabled erasing contents takes about a second.\n    is_required: true\n    summary: If enabled, will shutdown and erase a simulator's contents and settings.\n    title: Shutdown and erase simulator before use\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reset: \"no\"\noutputs:\n- BITRISE_SIMULATOR_STATUS: null\n  opts:\n    description: |\n      The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n\n      It can be used to trigger a new build conditionally:\n\n      ```\n      is_always_run: true\n      run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n      ```\n    title: The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n    value_options:\n    - booted\n    - failed\n    - hanged\n- BITRISE_XCODE_DESTINATION: null\n  opts:\n    description: |-\n      Device destination specifier\n\n      The destination specifer provided in the `destination` Input. It can be used as Input of other Steps, to avoid duplication.\n    title: Device destination specifier\n"
  },
  {
    "path": "steps/xcode-start-simulator/0.3.0/step.yml",
    "content": "title: Start Xcode simulator\nsummary: Starts an Xcode simulator.\ndescription: |-\n  Starts an Xcode simulator.\n\n  It uses the `xcrun simctl` command to launch a simulator, and optionally wait for it to finish booting.\n  The simulator will be running in the background after the Step exits, and can be used by later Steps in the workflow.\n\n  It allows two use cases:\n  * Boot simulator in the background and use it in the xcode-test Step:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n    - xcode-test:\n        inputs:\n        - project_path: ./ios-sample/ios-sample.xcodeproj\n        - scheme: ios-sample\n        # Simulator\n        - destination: $BITRISE_XCODE_DESTINATION # Use the same destination as the xcode-start-simulator Step\n    ```\n\n  * Detect if simulator timed out and restart the build:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n        - wait_for_boot_timeout: 90\n    - trigger-bitrise-workflow:\n        is_always_run: true\n        run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n        inputs:\n        - api_token: $INSERT_RESTART_TRIGGER_TOKEN\n        - workflow_id: insert_workflow\n    ```\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator/issues\npublished_at: 2023-11-27T11:55:26.376796975Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator.git\n  commit: 4847ec2824ffd804e854770de0e3cc0fc2702612\nproject_type_tags:\n- ios\n- react-native\n- flutter\n- cordova\n- ionic\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\ndeps: {}\nis_always_run: false\nis_skippable: false\ninputs:\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the simulator device to be started.\n\n      The input value uses the same format as xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the simulator device to be started.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    description: |-\n      When larger than 0, will wait for the simulator boot to complete.\n\n      Setting this value to an int larger than 0 makes it possible to detect hangs or timeouts when booting simulator by waiting for the simulator to boot before this step completes.\n      If a timeout occurs, the `BITRISE_SIMULATOR_STATUS` output will be set to `hanged`.\n      The recommended value is 90.\n\n      Using `0` (the default) enables the Simulator boot to occur in parallel to other Steps.\n    is_required: true\n    summary: When larger than 0, will wait for the simulator boot to complete.\n    title: Simulator boot timeout (in seconds)\n  wait_for_boot_timeout: 0\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: |-\n      If enabled, will shutdown and erase a simulator's contents and settings.\n\n      This option is not needed when starting from a clean state on a CI build.\n      It may be used when running testing multiple apps on the same simulator or for making sure that the simulator is indeed in a clean state when an app fails to install due to an unexpected issue.\n\n      When enabled erasing contents takes about a second.\n    is_required: true\n    summary: If enabled, will shutdown and erase a simulator's contents and settings.\n    title: Shutdown and erase simulator before use\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reset: \"no\"\noutputs:\n- BITRISE_SIMULATOR_STATUS: null\n  opts:\n    description: |\n      The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n\n      It can be used to trigger a new build conditionally:\n\n      ```\n      is_always_run: true\n      run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n      ```\n    title: The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n    value_options:\n    - booted\n    - failed\n    - hanged\n- BITRISE_XCODE_DESTINATION: null\n  opts:\n    description: |-\n      Device destination specifier\n\n      The destination specifer provided in the `destination` Input. It can be used as Input of other Steps, to avoid duplication.\n    title: Device destination specifier\n"
  },
  {
    "path": "steps/xcode-start-simulator/0.3.1/step.yml",
    "content": "title: Start Xcode simulator\nsummary: Starts an Xcode simulator.\ndescription: |-\n  Starts an Xcode simulator.\n\n  It uses the `xcrun simctl` command to launch a simulator, and optionally wait for it to finish booting.\n  The simulator will be running in the background after the Step exits, and can be used by later Steps in the workflow.\n\n  It allows two use cases:\n  * Boot simulator in the background and use it in the xcode-test Step:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n    - xcode-test:\n        inputs:\n        - project_path: ./ios-sample/ios-sample.xcodeproj\n        - scheme: ios-sample\n        # Simulator\n        - destination: $BITRISE_XCODE_DESTINATION # Use the same destination as the xcode-start-simulator Step\n    ```\n\n  * Detect if simulator timed out and restart the build:\n    ```yaml\n    - xcode-start-simulator:\n        inputs:\n        - destination: platform=iOS Simulator,name=iPhone 8,OS=latest\n        - wait_for_boot_timeout: 90\n    - trigger-bitrise-workflow:\n        is_always_run: true\n        run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n        inputs:\n        - api_token: $INSERT_RESTART_TRIGGER_TOKEN\n        - workflow_id: insert_workflow\n    ```\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator/issues\npublished_at: 2025-11-12T15:20:13.066083903Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-start-simulator.git\n  commit: 623bd8cec2edb68915772199d3a7e248ad8c725a\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-start-simulator\ndeps: {}\nis_always_run: false\nis_skippable: false\ninputs:\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the simulator device to be started.\n\n      The input value uses the same format as xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the simulator device to be started.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    description: |-\n      When larger than 0, will wait for the simulator boot to complete.\n\n      Setting this value to an int larger than 0 makes it possible to detect hangs or timeouts when booting simulator by waiting for the simulator to boot before this step completes.\n      If a timeout occurs, the `BITRISE_SIMULATOR_STATUS` output will be set to `hanged`.\n      The recommended value is 90.\n\n      Using `0` (the default) enables the Simulator boot to occur in parallel to other Steps.\n    is_required: true\n    summary: When larger than 0, will wait for the simulator boot to complete.\n    title: Simulator boot timeout (in seconds)\n  wait_for_boot_timeout: 0\n- opts:\n    category: Debugging\n    is_required: true\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- opts:\n    category: Debugging\n    description: |-\n      If enabled, will shutdown and erase a simulator's contents and settings.\n\n      This option is not needed when starting from a clean state on a CI build.\n      It may be used when running testing multiple apps on the same simulator or for making sure that the simulator is indeed in a clean state when an app fails to install due to an unexpected issue.\n\n      When enabled erasing contents takes about a second.\n    is_required: true\n    summary: If enabled, will shutdown and erase a simulator's contents and settings.\n    title: Shutdown and erase simulator before use\n    value_options:\n    - \"yes\"\n    - \"no\"\n  reset: \"no\"\noutputs:\n- BITRISE_SIMULATOR_STATUS: null\n  opts:\n    description: |\n      The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n\n      It can be used to trigger a new build conditionally:\n\n      ```\n      is_always_run: true\n      run_if: '{{enveq \"BITRISE_SIMULATOR_STATUS\" \"hanged\"}}'\n      ```\n    title: The status of the simulator, will be set to `booted`, `failed` or `hanged`.\n    value_options:\n    - booted\n    - failed\n    - hanged\n- BITRISE_XCODE_DESTINATION: null\n  opts:\n    description: |-\n      Device destination specifier\n\n      The destination specifer provided in the `destination` Input. It can be used as Input of other Steps, to avoid duplication.\n    title: Device destination specifier\n"
  },
  {
    "path": "steps/xcode-start-simulator/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-test/0.9.2/step.yml",
    "content": "title: Xcode Test\ndescription: Runs Xcode's `test` action.\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-new-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-new-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-new-xcode-test/issues\npublished_at: 2015-08-22T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 0d9ddce7d8d606aa3f3f655fd1c3e12be47c7b70\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: null\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: null\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n"
  },
  {
    "path": "steps/xcode-test/0.9.3/step.yml",
    "content": "title: Xcode Test\ndescription: Runs Xcode's `test` action.\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-08-23T14:35:38.611929345+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: ad299e72fefaeaf7ba0a9c13750dfbb7a7d950c6\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: null\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: null\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: null\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-test/1.0.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-09T17:04:07.519766656+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 49ca8fcd5bb5b544fb34dfee4305b76d80ad896f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-test/1.1.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-15T17:34:40.897782136+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: d4dc10267398c1cf9bcf76f4bf437f8885dded54\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-test/1.1.1/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-15T20:20:44.890793719+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: f477acc54abe952cf80d35776cbda41b9b552a83\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-test/1.1.2/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-16T10:46:32.454173816+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: aa054d79d061e607dec6d529281a04e5af9b3f0f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-test/1.10.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-01-09T12:40:03.348873942+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 1bbccbe5ad36c4db431ab610676660653e413504\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n"
  },
  {
    "path": "steps/xcode-test/1.11.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-01-25T15:16:10.012899268+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: ca4c8d981a43a643756829ea52af5d13e72e4aa5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n"
  },
  {
    "path": "steps/xcode-test/1.12.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-02-12T17:06:39.586698476+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: c3e6b5ebba153b633f56849b8c5aa801a63dd6db\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.12.1/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-03-02T17:41:26.020946931+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: e9126545bc787ffca2410ab8ab8517a6030c2079\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-03-16T14:09:56.706511695+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 066e0290ea39d8b5d5106964eb3c6317bf138f8c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` becomes two additional flags:\n\n        * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n        * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.1/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-03-17T15:10:46.930128289+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 960a6a3b7a55cc1408e78caf265fa52aff5934a2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` becomes two additional flags:\n\n        * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n        * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.2/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-03-18T17:04:45.488612097+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: d24cf4aaa6598357c3b81d94c38a9191edc8f99a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` becomes two additional flags:\n\n        * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n        * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.3/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-03-21T16:44:34.954566589+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 75dedb99540742308e375c3c81b4e235568030b4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` becomes two additional flags:\n\n        * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n        * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.4/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-03-31T13:02:37.689235934+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 69d9d23dd93dd35f12790f9ccd19ee083bbc425a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` becomes two additional flags:\n\n        * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n        * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.5/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-04-04T16:31:21.322361614+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 2764f79b853aa883a235806237e6d23787ca2c93\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` becomes two additional flags:\n\n        * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n        * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.6/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-04-08T14:32:59.494423425+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 2dd5539bde4edbf5e409393d6b408559b2112fa8\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` befor the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.7/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-04-12T17:22:24.934092837+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 4e1bb587f0994459f48f5740ecbf9ca915ebd13e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` befor the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.13.8/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-07-12T13:17:34.968192904+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 30c14ed44e8de47f8973b9c5cfe8affe26217d0d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.14.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-07-26T18:00:41.374703228+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: fcb76ff1ade0d2939073e4a7565c1a22044f27cc\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.14.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-09-16T10:56:13.654812904+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 17ab571aaa811ee7a051a079bce909dafbea1b16\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.15.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-09-19T13:49:14.923323632+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: d210994418a293f509ddfeb2e8a479024872130c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: |-\n      If `should_retry_test_on_fail: yes` step will retry the test if first attempt\n        failed.\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.16.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-09-23T17:21:56.198531658+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 91540cc29bf59f9f22f6def57af16994d0d0a317\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: |-\n      If `should_retry_test_on_fail: yes` step will retry the test if first attempt\n        failed.\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.16.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-09-28T10:40:20.888057144+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 603e12f29a6d99d716dddd1c301f775d00417bac\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: |-\n      If `should_retry_test_on_fail: yes` step will retry the test if first attempt\n        failed.\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.17.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-09-29T12:44:15.403456066+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: beab1e80fe56beb1790546f83584a41da19671d5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: |-\n      If `should_retry_test_on_fail: yes` step will retry the test if first attempt\n        failed.\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.17.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-10-11T11:24:59.65315843+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: d8529305de308165addf8fec43841717a7b97d77\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.17.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-11-15T21:41:43.746457407+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 6f5b44e84ee932b1f3d48aa41eb776dc995cfc7a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-11-18T16:24:04.035686462+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 613461d9d0df6a7ac43310de98538bd5f724309a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2016-11-29T13:28:45.730356265+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: a7815a6a9609c8ba3cc5ad03cb004d567ef35348\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.10/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-01-25T10:51:42.112931786+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 77a97194823f287cb45ef88838007ff4701b129d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.11/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-02-05T11:12:56.197405934+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: fc3e3afff10919d1618dcd9b0684d99cf0d89c52\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.12/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-02-21T18:38:59.407307187+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: b4210b36fb00a92df04a6a84158874eaf5e2fd07\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.13/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-03-02T15:50:26.818918874+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: fb97eb9afd07e668e179c3556fe03e528d7c3847\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.14/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: !!timestamp 2018-05-07T11:10:03.674635192+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 20ae50bf9514b252f914d80ceb3289270ec16ed3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.15/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-07-03T14:51:55.483429087+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 9d4e2e84fdeb5c8bcf8ddb0c9dca9a1b10dde829\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.16/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-07-18T14:21:32.579839437+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 53277f5dd3df08763af2671dbb35dab166436d3a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.17/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-10-01T13:10:56.618846565Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: b1487db6a46467a38b1181e95dadd288096ce8ee\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-04-04T12:38:45.429529196+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: cb397612a30273d600c4487b15f77e512733cf00\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.3/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-04-13T16:12:16.629141588+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: d8274ceecc366f86306baf46421b5fc046451766\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.4/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-06-08T13:02:31.275964413+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: ead4984ab84ab697948116cb58d3cae6890283ab\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"no\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.5/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-06-09T17:11:15.729388822+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 77fe3b155091c3f2de0db91198653106b318ecee\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.6/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-07-27T16:16:30.647345363+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: bac4bf860f5d1c112a5b955051e5e291ecf53313\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.7/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-08-07T14:46:41.192411803+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: e821734864cb7b515240f392fc7195f490855a1a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION\n        -derivedDataPath DERIVED_DATA_PATH`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.8/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-10-09T14:14:08.881229807+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: f5a713b65f4c43709e260e5ac6968166f1c086a4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the setp's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.18.9/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action, on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action, on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2017-12-08T15:03:09.981255043+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 509c5fb4c4f0796c4e93a33c4395409928d47018\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    category: Testing\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    category: Testing\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    category: Testing\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Config\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    category: Config\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build: false` step runs `xcodebuild OPTIONS build OPTIONS` before the test,\n      to generate the project derived datas. After that comes `xcodebuild OPTIONS build test OPTIONS`,\n      which command's log is presented in the step's log.\n\n      If `single_build: true`, then step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- opts:\n    category: Debug\n    description: Wait to simulator boot or start test immediately?\n    title: (Experimental) Wait to simulator boot?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  wait_for_simulator_boot: \"yes\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/1.2.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-18T21:11:06.433547909+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 1b94c32fb0a2ff6dce89546e801e3462807e54ed\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n"
  },
  {
    "path": "steps/xcode-test/1.3.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-21T13:23:03.3458695+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 2d2a59bc7adecc82858df2b31bd01142271f6fad\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPad\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    title: Full results / summary of the text, as printed by Xcode.\n"
  },
  {
    "path": "steps/xcode-test/1.4.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-28T15:30:05.380881978+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: fa8565247b02fa1ce51dafc0839cdb617810fc93\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    title: Full results / summary of the text, as printed by Xcode.\n"
  },
  {
    "path": "steps/xcode-test/1.4.1/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-29T11:17:28.040626699+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: fa9a94940e1cd8be5ef0bad0151874ef3f3d9cc0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    title: Full results / summary of the text, as printed by Xcode.\n"
  },
  {
    "path": "steps/xcode-test/1.4.2/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-29T15:14:23.445077167+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 73f2e16f3b01eda230676ee44037bccf4f605be7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    title: Full results / summary of the text, as printed by Xcode.\n"
  },
  {
    "path": "steps/xcode-test/1.5.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-09-30T16:59:06.710156659+02:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 62f5aabf1e2ca1b0e07fd708f283024f747e4445\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    title: Full results / summary of the text, as printed by Xcode.\n"
  },
  {
    "path": "steps/xcode-test/1.6.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-10-28T16:31:44.932623792+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: d1d5f53c43b12113d58bb7b9179272ef9bd3b6b4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_TEST_FULL_RESULTS_TEXT: null\n  opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    title: Full results / summary of the text, as printed by Xcode.\n"
  },
  {
    "path": "steps/xcode-test/1.7.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-11-09T13:01:07.403459882+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 5853f3d7ffe7c329ee63aac61dd367540aa985f7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_full_output: \"no\"\n  opts:\n    description: |-\n      If this option is set to \"no\" then only the test results / test summary\n      will be printed. If set to \"yes\" then every output generated\n      by `xcodebuild` (compile & test) will be presented.\n    is_expand: true\n    is_required: true\n    title: Present the full compile & test output?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      When available this output will contain the full test results\n      printed by Xcode.\n\n      Something like:\n\n          Failing tests:\n            -[BitriseSampleWithYMLTests testFailExample()]\n          ** TEST FAILED **\n\n          Test Suite 'All tests' started at 2015-09-20 10:18:46.342\n          Test Suite 'BitriseSampleWithYMLTests.xctest' started at 2015-09-20 10:18:46.343\n          Test Suite 'BitriseSampleWithYMLTests' started at 2015-09-20 10:18:46.343\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' started.\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testExample]' passed (0.000 seconds).\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' started.\n          /Users/viktorbenei/develop/sample-apps-ios-with-bitrise-yml/BitriseSampleWithYMLTests/BitriseSampleWithYMLTests.swift:33: error: -[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample] : XCTAssertTrue failed -\n          Test Case '-[BitriseSampleWithYMLTests.BitriseSampleWithYMLTests testFailExample]' failed (0.001 seconds).\n    is_expand: true\n    is_required: true\n    title: Full results / summary of the test, as printed by Xcode, will be saved\n      into this file\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-summary-${BITRISE_SCHEME}.log\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test/1.8.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-12-05T18:07:45.757847673+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 02a457a5a5cf6f44b1d4b0048c680a6f80691539\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Workfing directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n    is_expand: true\n    is_required: false\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_expand: true\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_expand: true\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_dont_change_value: false\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test/1.9.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2015-12-30T09:27:49.760814627+01:00\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 0d088baff5edaddc79d9acff5bb91f77835f767d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\n- manager: brew\n  name: go\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6\n- opts:\n    description: |\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: false\n    title: OS version\n  simulator_os_version: latest\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      **This option is only available if you set `xcpretty` as the `output_tool`.**\n\n      Test results in HTML format, generated by `xcpretty`,\n      will be saved to this file.\n    is_required: true\n    title: Test results file path\n  test_results_file_path: ${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test/2.0.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2018-11-15T09:37:39.909392013Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: fe8afa01fb192b69d4717df3550f418ec6a33c0d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.1.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2019-01-10T12:47:53.485931868Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 3f69dd1f610bd6ec8accbebb520362b47571ea07\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.1.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2019-01-23T10:22:05.429793564Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 064086e1603483293786825b626f2ddcd44a468e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.1.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2019-03-08T15:24:31.960566729Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: 7729bcb9966510d128306b679175f7e3e2517537\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.2.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-io/steps-xcode-test\nsource_code_url: https://github.com/bitrise-io/steps-xcode-test\nsupport_url: https://github.com/bitrise-io/steps-xcode-test/issues\npublished_at: 2019-03-18T11:39:48.931126821Z\nsource:\n  git: https://github.com/bitrise-io/steps-xcode-test.git\n  commit: f008558ffc47dbc9bd41a08f5e6a6fc18388a692\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-io/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.3.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-04-15T11:14:15.514629025Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 97d7bf32baa7d43c27b97dfb050732e0ec90aba4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.3.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-05-10T14:07:00.505401961Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 4f55fd573bc53b2c355baaeabc116cd5bf294d5a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.3.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-06-18T07:24:15.887149508Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: c05bd3a50ee36040bd047cf4618615083a9d0b2c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 6\n      * iPhone 6 Plus\n      * iPad\n      * iPad Air\n      * Apple TV 1080p (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 6s Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-10-10T11:39:00.952067785Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: e4252f96a2f3f09fd5a36967f88df2eb8d0e84ca\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-10-15T08:56:59.010234508Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 315a6c99be6ad0d803d589d3267c792678676a0e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-11-08T08:23:46.477560006Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 44e855b997eff833c20d9e7563bc2a0c447b745e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.3/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs Xcode's `test` action on an iOS project.\ndescription: |-\n  Runs Xcode's `test` action on an iOS project.\n\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2019-11-26T13:10:42.411438245Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: b103484d0955ecd24008835b907e6f30ee602cf9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.4/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2020-02-13T16:12:56.812892134Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 679ccae558c63940da1992326ae4c323e86a9fb2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: (Experimental) Explicitly perform a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: (Experimental) Rerun test, when it fails?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.5/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2020-03-10T13:53:41.864816202Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 2f36e5fc43f2d1f1133e69c8fa095a3c7dfaa544\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.4.6/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2020-06-03T13:23:51.876568807Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: c5bca453fef5ea652139eb3ea0e41f594fc2a51d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.5.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-01-07T10:27:10.348817439Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 489cd0633ac4b95e546a2fdaebddb8d77754cb27\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.6.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-04-28T07:20:30.901070381Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 53e3c1cdbef2a8e4c04befcccfdeafb8c1b4cee9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the BITRISE_DEPLOY_DIR, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.6.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-05-07T07:14:40.614278098Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: cc93177733096e7d40d61c4725a8cc512f942e57\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.6.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-05-11T08:02:15.956012301Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 1a66f76c7f7379c354f0223faee5b1dd8b214962\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      The Scheme to use.\n\n      **IMPORTANT**: The Scheme has to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Working directory of the step.\n      You can leave it empty to leave the working directory unchanged.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: 'If `should_retry_test_on_fail: yes` step will retry the test if\n      first attempt failed.'\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH: null\n  opts:\n    description: |-\n      This is the path of the raw test results log file.\n\n      If the compilation fails this log will contain the compilation output,\n      if the tests can be started it'll only include the test output.\n    title: The full, raw test output file path\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n"
  },
  {
    "path": "steps/xcode-test/2.7.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-07-07T09:51:15.134116955Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 13e1022a599a97962899ec687bfb0e66d432e6d8\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: \"Run tests in a specific Test Plan associated with the Scheme.  \\nLeave\n      this input empty to run the default Test Plan or Test Targets associated with\n      the Scheme.\"\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: \"If you set this input to `yes`, the Step will rerun your tests.\n      With Xcode 13 and above, only your failed test cases will be rerun. With older\n      Xcode versions, all test cases will be rerun. \\n Please note that this feature\n      is only available from Xcode 13 and above, earlier versions support rerunning\n      ALL test cases instead of a specific failed one.  \"\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/2.7.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-07-07T13:21:26.177820845Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 9291499fe187a17ada373518552bbc4575ea175f\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: \"Run tests in a specific Test Plan associated with the Scheme.  \\nLeave\n      this input empty to run the default Test Plan or Test Targets associated with\n      the Scheme.\"\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: \"If `single_build` is set to false, the step runs `xcodebuild OPTIONS\n      build OPTIONS` before the test \\nto generate the project derived data. After\n      that comes `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented\n      in the step's log.\\n\\nIf `single_build` is set to true, then the step calls\n      only `xcodebuild OPTIONS build test OPTIONS`.\"\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: \"If you set this input to `yes`, the Step will rerun your tests.\n      With Xcode 13 and above, only your failed test cases will be rerun. With older\n      Xcode versions, all test cases will be rerun. \\n Please note that this feature\n      is only available from Xcode 13 and above, earlier versions support rerunning\n      ALL test cases instead of a specific failed one.  \"\n    is_required: true\n    title: Should retry test on failure?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/3.0.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-07-26T12:03:18.651632121Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 9f99f5385f2cec422105c8970b0a300ae9820f2e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test will repeat based on Test Repetition Mode.\n\n      Should be more than 1 if the Test Repetition Mode (`test_repetition_mode`) is other than `none`.\n    is_required: true\n    summary: The maximum number of times a test will repeat based on Test Repetition\n      Mode.\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If enabled, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n    summary: If enabled, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build` is set to false, the Step runs `xcodebuild OPTIONS build OPTIONS` before the test\n      to generate the project derived data. This is followed by `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented in the Step's log.\n\n      If `single_build` is set to true, then the Step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      If you set this input to `yes`, the Step will rerun ALL your tests once in the case of failed test/s. Note that ALL your tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (test_repetition_mode).\n    is_required: true\n    summary: If you set this input to `yes`, the Step will rerun your failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/3.0.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-07-26T13:30:13.789390375Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 9f99f5385f2cec422105c8970b0a300ae9820f2e\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test will repeat based on Test Repetition Mode.\n\n      Should be more than 1 if the Test Repetition Mode (`test_repetition_mode`) is other than `none`.\n    is_required: true\n    summary: The maximum number of times a test will repeat based on Test Repetition\n      Mode.\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If enabled, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n    summary: If enabled, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build` is set to false, the Step runs `xcodebuild OPTIONS build OPTIONS` before the test\n      to generate the project derived data. This is followed by `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented in the Step's log.\n\n      If `single_build` is set to true, then the Step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      If you set this input to `yes`, the Step will rerun ALL your tests once in the case of failed test/s. Note that ALL your tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (test_repetition_mode).\n    is_required: true\n    summary: If you set this input to `yes`, the Step will rerun your failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/3.0.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-08-04T13:02:00.779891438Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 5853101084bac5812b0f68957b9d1b7da7dd974c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test will repeat based on Test Repetition Mode.\n\n      Should be more than 1 if the Test Repetition Mode (`test_repetition_mode`) is other than `none`.\n    is_required: true\n    summary: The maximum number of times a test will repeat based on Test Repetition\n      Mode.\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If enabled, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n    summary: If enabled, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build` is set to false, the Step runs `xcodebuild OPTIONS build OPTIONS` before the test\n      to generate the project derived data. This is followed by `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented in the Step's log.\n\n      If `single_build` is set to true, then the Step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      If you set this input to `yes`, the Step will rerun ALL your tests once in the case of failed test/s. Note that ALL your tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (test_repetition_mode).\n    is_required: true\n    summary: If you set this input to `yes`, the Step will rerun your failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/3.1.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme name** input field must be marked as Shared in Xcode. \\nThe\n  **Device**, **OS version**, **Platform** input fields must be set to the value that's\n  shown in Xcode’s device selection dropdown menu.\\nIf you wish to export code coverage\n  files as well, set the \\\"Generate code coverage files?\\\" to `yes`.\\n\\n### Troubleshooting\\nIf\n  the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode\n  Test for iOS** Step will not be able to export the test results on the Test Reports\n  page and you won't be able to view them either.\\nThe xcpretty output tool does not\n  support parallel tests. \\nIf parallel tests are enabled in your project, go to the\n  Step’s Debug section and set the **Output tool** input’s value to xcodebuild.\\nIf\n  the Xcode test fails with the error `Unable to find a destination matching the provided\n  destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-09-07T09:15:00.066583356Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 825db06fd667bcdbcee25b6839d0ebff93ee59ae\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: The Scheme to use.\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iPhone 8 Plus\n      * iPhone Xs Max\n      * iPad Air (3rd generation)\n      * iPad Pro (12.9-inch) (3rd generation)\n      * Apple TV 4K (don't forget to set the platform to `tvOS Simulator` to use this option!)\n    is_required: true\n    title: Device\n  simulator_device: iPhone 8 Plus\n- opts:\n    description: |-\n      Set it as it is shown in\n      Xcode's device selection dropdown UI.\n\n      A couple of format examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * 8.4\n      * latest\n    is_required: true\n    title: OS version\n  simulator_os_version: latest\n- opts:\n    description: |-\n      Set it as it is shown in Xcode's device selection dropdown UI.\n\n      A couple of examples (the\n      actual available options depend on which versions\n      are installed):\n\n      * iOS Simulator\n      * tvOS Simulator\n    is_required: true\n    title: Platform\n    value_options:\n    - iOS Simulator\n    - tvOS Simulator\n  simulator_platform: iOS Simulator\n- export_uitest_artifacts: \"false\"\n  opts:\n    description: |-\n      If enabled, the attachments of the UITest will be exported into the `BITRISE_DEPLOY_DIR`, as a compressed ZIP file.\n      Attachments include screenshots taken during the UI test, and other artifacts.\n\n      __NOTE:__ works only with Xcode version < 11.\n    title: Export UITest Artifacts\n    value_options:\n    - \"true\"\n    - \"false\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    description: |-\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    is_required: true\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test will repeat based on Test Repetition Mode.\n\n      Should be more than 1 if the Test Repetition Mode (`test_repetition_mode`) is other than `none`.\n    is_required: true\n    summary: The maximum number of times a test will repeat based on Test Repetition\n      Mode.\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If enabled, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n    summary: If enabled, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Debug\n    description: You can enable the verbose log for easier debugging.\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\n- headless_mode: \"yes\"\n  opts:\n    category: Debug\n    description: |-\n      If you run your tests in headless mode the xcodebuild will start a simulator in a background.\n      In headless mode the simulator will not be visible but your tests (even the screenshots) will run just like if you run a simulator in foreground.\n\n      **NOTE:** Headless mode is available with Xcode 9.x or newer.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the test in headless mode?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- is_clean_build: \"no\"\n  opts:\n    category: Debug\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debug\n    description: |-\n      If set to `xcpretty`, the xcodebuild output will be prettified by xcpretty.\n\n\n      If set to `xcodebuild`, only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      The build log will always be added as an artifact.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcodebuild build test` call.\n\n      If you leave empty this input, xcodebuild will be called as:\n\n      `xcodebuild\n        -project\\-workspace PROJECT.xcodeproj\\WORKSPACE.xcworkspace\n        -scheme SCHEME\n        build test\n        -destination platform=PLATFORM Simulator,name=NAME,OS=VERSION`\n\n      In case of `generate_code_coverage_files: \"yes\"`\n      `xcodebuild` gets two additional flags:\n\n      * GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES\n      * GCC_GENERATE_TEST_COVERAGE_FILES=YES\n\n      If you want to add more options, list that separated by space character.\n      Example: `-xcconfig PATH -verbose`\n    title: Additional options for `xcodebuild build test` call\n  xcodebuild_test_options: \"\"\n- opts:\n    category: Debug\n    description: |-\n      If `single_build` is set to false, the Step runs `xcodebuild OPTIONS build OPTIONS` before the test\n      to generate the project derived data. This is followed by `xcodebuild OPTIONS build test OPTIONS`. This command's log is presented in the Step's log.\n\n      If `single_build` is set to true, then the Step calls only `xcodebuild OPTIONS build test OPTIONS`.\n    title: Run xcodebuild test only\n    value_options:\n    - \"true\"\n    - \"false\"\n  single_build: \"true\"\n- opts:\n    category: Debug\n    description: |-\n      Previous Xcode versions and configurations may throw the error `iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.`\n      when the compilation before performing the tests takes too long.\n\n      This is fixed by running `xcodebuild OPTIONS build test OPTIONS` instead of `xcodebuild OPTIONS test OPTIONS`.\n      Calling an explicit build before the test results in the code being compiled twice, thus creating an overhead.\n\n      Unless you are sure that your configuration is not prone to this error, it is recommended to leave this option turned on.\n    is_required: true\n    title: Should run a build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_build_before_test: \"yes\"\n- opts:\n    category: Debug\n    description: |-\n      If you set this input to `yes`, the Step will rerun ALL your tests once in the case of failed test/s. Note that ALL your tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (test_repetition_mode).\n    is_required: true\n    summary: If you set this input to `yes`, the Step will rerun your failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: Debug\n    description: |-\n      Options added to the end of the `xcpretty` test call.\n\n      If you leave empty this input, xcpretty will be called as:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty`\n\n      In case of leaving this input on default value:\n\n      `set -o pipefail && XCODEBUILD_TEST_COMMAND | xcpretty --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n\n      If you want to add more options, list that separated by space character.\n    title: Additional options for `xcpretty` test call\n  xcpretty_test_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Debug\n    description: |-\n      Available options:\n      - `none` : Disable caching\n      - `swift_packages` : Cache Swift PM packages added to the Xcode project\n    title: Enable caching of Swift Package Manager packages\n    value_options:\n    - none\n    - swift_packages\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debug\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.0.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme** input field must be marked as Shared in Xcode.\\n\\n###\n  Troubleshooting\\nIf the **Deploy to Bitrise.io** Step is missing from your Workflow,\n  then the **Xcode Test for iOS** Step will not be able to export the test results\n  on the Test Reports page and you won't be able to view them either.\\nThe xcpretty\n  output tool does not support parallel tests. \\nIf parallel tests are enabled in\n  your project, go to the Step's Debug section and set the **Log formatter** input's\n  value to xcodebuild.\\nIf the Xcode test fails with the error `Unable to find a destination\n  matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-10-07T07:27:57.362106842Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 14b5cf60e3366f51bc983d1d13d033a3400b1312\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.0.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: \"This Steps runs all those Xcode tests that are included in your project.\n  \\nThe Step will work out of the box if your project has test targets and your Workflow\n  has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage\n  files if needed) to the Test Reports page. \\nThis Step does not need any code signing\n  files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\\n\\n###\n  Configuring the Step\\nIf you click into the Step, there are some required input\n  fields whose input must be set in accordance with the Xcode configuration of the\n  project.  \\nThe **Scheme** input field must be marked as Shared in Xcode.\\n\\n###\n  Troubleshooting\\nIf the **Deploy to Bitrise.io** Step is missing from your Workflow,\n  then the **Xcode Test for iOS** Step will not be able to export the test results\n  on the Test Reports page and you won't be able to view them either.\\nThe xcpretty\n  output tool does not support parallel tests. \\nIf parallel tests are enabled in\n  your project, go to the Step's Debug section and set the **Log formatter** input's\n  value to xcodebuild.\\nIf the Xcode test fails with the error `Unable to find a destination\n  matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports)\n  to see if the requested simulator is on the stack or not. \\nIf it is not, then pick\n  a simulator that is on the stack.\\n\\n### Useful links\\n- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\\n-\n  [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\\n\\n###\n  Related Steps\\n- [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\\n-\n  [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2021-10-08T11:04:31.568890553Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: c26acd3cc4e169acd7cc6bfc818f26b72180545d\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: \"If `single_build` is set to false, the step runs `xcodebuild build`\n      before the test,  \\nand exports the raw xcodebuild log.\"\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.0.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-01-28T08:41:29.138814761Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 8cad0bf047deb73a278c1760e156e3806af7ca02\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.0.3/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-02-21T09:14:40.744072334Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: ff0eab7400129d0791b0e455333f169d06c88667\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.0.4/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-02-24T08:41:37.534535941Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 3185a957c63e3960ee55ba5a208a76e7d77eb01b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n    is_required: true\n    summary: Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.1.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-04-28T11:42:25.028580845Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 513dc4d3b08f53a15cbe0bad6e86acb402c9f1f3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings.\n\n      Build settings must be separated by newline character (`\\n`).\n\n      Example:\n\n      ```\n      COMPILER_INDEX_STORE_ENABLE = NO\n      ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n      ```\n\n      The input value sets xcodebuild's `-xcconfig` option.\n    summary: Build settings to override the project's build settings.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.2.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-06-01T12:15:02.75361065Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: d084e66c1726162ca4f06ae6ccbabccf8db2e701\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.3.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-07-07T15:32:02.695716389Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: eb9eddb4770c2d1f597b549997ce917ae515be59\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.4.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-08-15T12:28:28.604974918Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: c22c347242953bb374ab6b0434673333dba52318\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n\n      The raw xcodebuild log will be exported in both cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcpretty\n    - xcodebuild\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.5.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's Debug section and set the **Log formatter** input's value to xcodebuild.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-08-26T12:18:08.423211119Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 0588b1f176a342f580d2af2c4b68ae978f4c64bf\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.6.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-09-12T14:40:06.157525137Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: deb39d7e9e055a22f33550ed3110fb3c71beeb79\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.7.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2022-12-12T11:16:43.286916356Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 81ce5e86753e870e7baaae9d254e67ccb9466c52\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.7.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-05-10T22:39:14.108716607Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: ce0dae9a3381cd581bb9de5ee4965aea8f2154e4\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.7.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-07-18T11:07:36.826551842Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 6165d7c74d94955c58260f6be0ec933731b2da3e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.7.3/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-07-24T11:14:00.293317933Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 96bccac339b34ec6a294f4f152aff530bfdb0a77\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.7.4/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-08-01T11:37:47.172893723Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: ab4b14a227a9230a8164fafef22f31d8a8d7b08e\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/4.7.5/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-08-09T09:44:48.834979464Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: df755f32010959efb7378b673e046cd87a5bdd50\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcpretty\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: swift_packages\n  opts:\n    category: Caching\n    description: |-\n      Defines what cache content should be automatically collected.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n    summary: Defines what cache content should be automatically collected.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/5.0.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-08-10T11:20:05.405813187Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 92d41f39d5b4e6a58f56b77977103c8af0da281d\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/5.0.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-09-05T08:51:39.413427266Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 74f1d53ba7ff4d31db5569257aee95569f7909e8\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/5.1.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2023-11-27T11:55:57.889398647Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 4e14f19dd7ad5a9bcb1318bcbdab3b8d9ef63ce3\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/5.1.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2024-04-08T11:03:54.789032239Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 497f1110471c51c363331fd306a205e8a56bff64\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, the Step will rerun the tests in the case of failed tests.\n\n      Note that all the tests will be rerun, not just the ones that failed.\n\n      This input is not available if you are using Xcode 13+. In that case, we recommend using the `retry_on_failure` Test Repetition Mode (`test_repetition_mode`).\n    is_required: true\n    summary: If set, the Step will rerun the tests in the case of failed tests.\n    title: Should retry tests on failure? (Not available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  should_retry_test_on_fail: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/6.0.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2024-11-15T08:28:59.37548459Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 2d52e4b24129b1f4d36d85eab21266fd4da2e8db\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/6.0.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-03-10T13:13:07.048323758Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: d0bfcffbf915da8217c3286629ece67c49bcd084\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n"
  },
  {
    "path": "steps/xcode-test/6.1.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-07-29T12:28:28.055006576Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 093250a4b2c49e5bd4ffc6e040eb0f06d0ca9bb2\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.1.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-09-04T14:22:51.085632382Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: f8ab8ae061a71f2a4566b225a47701570f1d84a1\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.1.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-09-11T14:54:39.951033086Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 5a4f1388ae71ccbae67ecf1ef462df6214ff823b\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.1.3/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-09-18T09:50:44.417314136Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: b1be0c6287a3fb1336b67a15b8a026ba7859fa18\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.2.0/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-09-30T13:43:19.926582456Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: cdcaebdb7814bd6525d60d12cbc124ba416e45c9\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.2.1/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-10-14T09:04:37.658543803Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: a58bbeb2461ce80ad3ba131ec069c7ae8609e3c3\nproject_type_tags:\n- ios\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.2.2/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2025-11-10T13:50:57.323658096Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: b6ed5f30a97166ba7f29cb56fe586f2624058ce3\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.2.3/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2026-02-04T09:45:26.12402143Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: f62f5b4b9291c4b0739aa62af5e7ac4290beafe2\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/6.2.4/step.yml",
    "content": "title: Xcode Test for iOS\nsummary: Runs your project's pre-defined Xcode tests on every build.\ndescription: |-\n  This Steps runs all those Xcode tests that are included in your project.\n  The Step will work out of the box if your project has test targets and your Workflow has the **Deploy to Bitrise.io** Step which exports the test results and (code coverage files if needed) to the Test Reports page.\n  This Step does not need any code signing files since the Step deploys only the test results to [bitrise.io](https://www.bitrise.io).\n\n  ### Configuring the Step\n  If you click into the Step, there are some required input fields whose input must be set in accordance with the Xcode configuration of the project.\n  The **Scheme** input field must be marked as Shared in Xcode.\n\n  ### Troubleshooting\n  If the **Deploy to Bitrise.io** Step is missing from your Workflow, then the **Xcode Test for iOS** Step will not be able to export the test results on the Test Reports page and you won't be able to view them either.\n  The xcpretty output tool does not support parallel tests.\n  If parallel tests are enabled in your project, go to the Step's **xcodebuild log formatting** section and set the **Log formatter** input's value to `xcodebuild` or `xcbeautify`.\n  If the Xcode test fails with the error `Unable to find a destination matching the provided destination specifier`, then check our [system reports](https://stacks.bitrise.io) to see if the requested simulator is on the stack or not.\n  If it is not, then pick a simulator that is on the stack.\n\n  ### Useful links\n  - [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)\n  - [Running Xcode Tests for iOS](https://devcenter.bitrise.io/testing/running-xcode-tests/)\n\n  ### Related Steps\n  - [Deploy to Bitrise.io](https://www.bitrise.io/integrations/steps/deploy-to-bitrise-io)\n  - [iOS Device Testing](https://www.bitrise.io/integrations/steps/virtual-device-testing-for-ios)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test/issues\npublished_at: 2026-03-27T11:57:55.333648491Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test.git\n  commit: 95158684abd5180e2fd5626302ec8ea9e6f42984\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/xcode-test/6.2.4/bin/xcode-test-darwin-amd64\n    hash: sha256-91ac1cfb6283c6d96362a08c6397926b09032b806384f2d20a9ecbe6b33c7ffa\n  darwin-arm64:\n    storage_uri: steps/xcode-test/6.2.4/bin/xcode-test-darwin-arm64\n    hash: sha256-7d978ffee198e17795ab60c3f4d1c2fdc4a913f092b6df184339356cd6b766f8\n  linux-amd64:\n    storage_uri: steps/xcode-test/6.2.4/bin/xcode-test-linux-amd64\n    hash: sha256-6fe858e9081016f95bbdac121ddc05230de31aec5101ef7593eb969123b20d81\n  linux-arm64:\n    storage_uri: steps/xcode-test/6.2.4/bin/xcode-test-linux-arm64\n    hash: sha256-db458878811b0d9b5d10571fe3068146117326a3be26f5599f87710420f50c2f\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |-\n      Xcode Project (`.xcodeproj`) or Workspace (`.xcworkspace`) path.\n      The input value sets xcodebuild's `-project` or `-workspace` option.\n\n      If this is a Swift package, this should be the path to the `Package.swift` file.\n    is_required: true\n    summary: Path of the Xcode Project (`.xcodeproj`), Workspace (`.xcworkspace`)\n      or Swift package (`Package.swift`)\n    title: Project path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |-\n      Xcode Scheme name.\n\n      The input value sets xcodebuild's `-scheme` option.\n    is_required: true\n    summary: Xcode Scheme name.\n    title: Scheme\n  scheme: $BITRISE_SCHEME\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    description: |-\n      Run tests in a specific Test Plan associated with the Scheme.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Run tests in a specific Test Plan associated with the Scheme.\n    title: Test Plan\n  test_plan: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: retry_on_failure\n- maximum_test_repetitions: 3\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option.\n\n      You can't define `-xcconfig` option in `Additional options for the xcodebuild command` if this input is set.\n\n      If empty, no setting is changed. When set it can be either:\n      1.  Existing `.xcconfig` file path.\n\n          Example:\n\n          `./ios-sample/ios-sample/Configurations/Dev.xcconfig`\n\n      2.  The contents of a newly created temporary `.xcconfig` file. (This is the default.)\n\n          Build settings must be separated by newline character (`\\n`).\n\n          Example:\n          ```\n          COMPILER_INDEX_STORE_ENABLE = NO\n          ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES\n          ```\n    summary: Build settings to override the project's build settings, using xcodebuild's\n      `-xcconfig` option.\n    title: Build settings (xcconfig)\n  xcconfig_content: COMPILER_INDEX_STORE_ENABLE = NO\n- opts:\n    category: xcodebuild configuration\n    is_required: true\n    summary: If this input is set, `clean` xcodebuild action will be performed besides\n      the `test` action.\n    title: Perform clean action\n    value_options:\n    - \"yes\"\n    - \"no\"\n  perform_clean_action: \"no\"\n- opts:\n    category: xcodebuild configuration\n    description: |-\n      Additional options to be added to the executed xcodebuild command.\n\n      Prefer using `Build settings (xcconfig)` input for specifying `-xcconfig` option. You can't use both.\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- log_formatter: xcbeautify\n  opts:\n    category: xcodebuild log formatting\n    description: |-\n      Defines how xcodebuild command's log is formatted.\n\n      Available options:\n      - `xcbeautify`: The xcodebuild command's output will be beautified by xcbeautify.\n      - `xcodebuild`: Only the last 20 lines of raw xcodebuild output will be visible in the build log.\n      - `xcpretty`: The xcodebuild command's output will be prettified by xcpretty.\n\n      The raw xcodebuild log will be exported in all cases.\n    is_required: true\n    summary: Defines how xcodebuild command's log is formatted.\n    title: Log formatter\n    value_options:\n    - xcbeautify\n    - xcodebuild\n    - xcpretty\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcbeautify command.\n    title: Additional options for the xcbeautify command\n  xcbeautify_options: null\n- opts:\n    category: xcodebuild log formatting\n    summary: Additional options to be added to the executed xcpretty command.\n    title: Additional options for the xcpretty command\n  xcpretty_options: --color --report html --output \"${BITRISE_DEPLOY_DIR}/xcode-test-results-${BITRISE_SCHEME}.html\"\n- cache_level: none\n  opts:\n    category: Branch-based (legacy) caching\n    description: |-\n      Defines what cache content should be automatically collected. Use key-based caching instead for better performance.\n\n      Available options:\n      - `none`: Disable collecting cache content.\n      - `swift_packages`: Collect Swift PM packages added to the Xcode project.\n\n      With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages.\n      [See devcenter for more information.](https://devcenter.bitrise.io/en/dependencies-and-caching/managing-dependencies-for-ios-apps/managing-dependencies-with-spm.html#caching-swift-packages)\n    summary: Defines what cache content should be automatically collected. Use key-based\n      caching instead for better performance.\n    title: Enable collecting cache content\n    value_options:\n    - none\n    - swift_packages\n- opts:\n    category: Debugging\n    summary: If this input is set, the Step will print additional logs for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n- collect_simulator_diagnostics: never\n  opts:\n    category: Debugging\n    summary: If this input is set, the simulator verbose logging will be enabled and\n      the simulator diagnostics log will be exported.\n    title: Collect Simulator diagnostics\n    value_options:\n    - always\n    - on_failure\n    - never\n- headless_mode: \"yes\"\n  opts:\n    category: Debugging\n    description: |-\n      In headless mode the simulator is not launched in the foreground.\n\n      If this input is set, the simulator will not be visible but tests (even the screenshots) will run just like if you run a simulator in foreground.\n    summary: In headless mode the simulator is not launched in the foreground.\n    title: Run the simulator in headless mode\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    description: Result of the tests. 'succeeded' or 'failed'.\n    title: Test result\n    value_options:\n    - succeeded\n    - failed\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    description: The path of the generated `.xcresult`.\n    title: The path of the generated `.xcresult`\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    description: The path of the zipped `.xcresult`.\n    title: The path of the zipped `.xcresult`\n- BITRISE_XCODE_TEST_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full, test attachments zip path\n- BITRISE_XCODEBUILD_BUILD_LOG_PATH: null\n  opts:\n    description: |-\n      If `single_build` is set to false, the step runs `xcodebuild build` before the test,\n      and exports the raw xcodebuild log.\n    title: xcodebuild build command log file path\n- BITRISE_XCODEBUILD_TEST_LOG_PATH: null\n  opts:\n    description: The step exports the `xcodebuild test` command output log.\n    title: xcodebuild test command log file path\n- BITRISE_FLAKY_TEST_CASES: null\n  opts:\n    description: |-\n      A test case is considered flaky if it has failed at least once, but passed at least once as well.\n\n      The list contains the test cases in the following format:\n      ```\n      - TestTarget_1.TestClass_1.TestMethod_1\n      - TestTarget_1.TestClass_1.TestMethod_2\n      - TestTarget_1.TestClass_2.TestMethod_1\n      - TestTarget_2.TestClass_1.TestMethod_1\n      ...\n      ```\n    title: List of flaky test cases\n"
  },
  {
    "path": "steps/xcode-test/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-test-bundle-builder/0.0.4/step.yml",
    "content": "title: Build xcode test runner for remote testing service\nsummary: Build your XCTest or XCUITest runner to upload to remote testing service\ndescription: Build your XCTest or XCUITest bundle to upload to remote testing service\n  such as AWS Device Farm\nwebsite: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise\nsource_code_url: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise\nsupport_url: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise/issues\npublished_at: 2016-10-20T12:52:37.497284495+02:00\nsource:\n  git: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise.git\n  commit: 414362b33adea6aa6c020b28bda7ccfee4839df3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\noutputs:\n- TEST_BUNDLE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n"
  },
  {
    "path": "steps/xcode-test-bundle-builder/0.0.7/step.yml",
    "content": "title: Build xcode test runner for remote testing service\nsummary: Build your XCTest or XCUITest runner to upload to remote testing service\ndescription: Build your XCTest or XCUITest bundle to upload to remote testing service\n  such as AWS Device Farm\nwebsite: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise\nsource_code_url: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise\nsupport_url: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise/issues\npublished_at: 2019-02-22T16:26:54.419905+01:00\nsource:\n  git: https://github.com/otusweb/xCode-test-bundle-builder-for-bitrise.git\n  commit: 6cc7be8648c96cc329513fa02967832acb58f279\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\ntype_tags:\n- build\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    summary: \"\"\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path.\n    is_required: true\n    summary: \"\"\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n    is_required: true\n    summary: \"\"\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- configuration: null\n  opts:\n    description: |\n      (optional) The configuration to use. By default your Scheme\n      defines which configuration (Debug, Release, ...) should be used,\n      but you can overwrite it with this option.\n      **Make sure that the Configuration you specify actually exists\n      in your Xcode Project**. If it does not, if you have a typo\n      in the value of this input Xcode will simply use the Configuration\n      specified by the Scheme and will silently ignore this parameter!\n    summary: \"\"\n    title: Configuration name\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_expand: false\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |\n      This directory will contain the generated .ipa and .dSYM.zip files.\n    is_required: true\n    summary: \"\"\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\noutputs:\n- TEST_BUNDLE_IPA_PATH: null\n  opts:\n    title: The created .ipa file's path\n"
  },
  {
    "path": "steps/xcode-test-bundle-builder/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.0/step.yml",
    "content": "title: Xcode Test\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2015-12-03T18:43:28.122618407+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 40108f26163f51d3b08a03b604f43fe367226a0a\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.1/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2015-12-05T10:44:09.161077246+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: ac68e0523b5413bf4eb9599b17b6e9378a9d1169\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.2/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: |-\n  Write the tests and run them on every build just to make sure those tiny\n  code goblins didn't put something in the code that shouldn't be there while\n  you were at the daily Scrum meeting.\ndescription: Runs Xcode's `test` action.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2015-12-06T10:56:19.639868507+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: d85c0afe7bf14459967b76135c2e3f72ec463cd9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.3/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Run Xcode Test on your Mac OS X app project.\ndescription: Runs Xcode's `test` action, configured for Mac OS X app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2015-12-17T14:14:12.104469283+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 80eb5cee1bf1b153537495374c29ec32fed8b2e0\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.4/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Run Xcode Test on your Mac OS X app project.\ndescription: Runs Xcode's `test` action, configured for Mac OS X app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2016-03-09T18:20:56.685421805+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 7fca7ad8604a345c756d292ecc8c56a7e4e183c3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    is_expand: true\n    is_required: false\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_expand: true\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_expand: true\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_expand: true\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.5/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Run Xcode Test on your Mac OS X app project.\ndescription: Runs Xcode's `test` action, configured for Mac OS X app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2016-07-12T12:58:29.473998412+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 0ea522e732e43172e4162cf3f24dae1927572497\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- mac\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.0.6/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Run Xcode Test on your Mac OS X app project.\ndescription: Runs Xcode's `test` action, configured for Mac OS X app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2016-12-19T16:06:58.051969582+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: ea4947753abd2b02d92ae9b87121c3fdaa00db38\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- build\n- xcode\ndependencies:\n- manager: _\n  name: xcode\ndeps:\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.1.0/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Run Xcode Test on your Mac OS X app project.\ndescription: Runs Xcode's `test` action, configured for Mac OS X app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2017-02-24T11:49:19.908070809+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: bd824aaad04a5a885eefd7d18d7a9642e90389ca\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ndependencies:\n- manager: _\n  name: xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.1.2/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Run Xcode Test on your Mac OS X app project.\ndescription: Runs Xcode's `test` action, configured for Mac OS X app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2017-12-11T11:42:56.813502436+01:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 7db724cc60f52a279c81e0482a41159f95f2b48c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ndependencies:\n- manager: _\n  name: xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Do a clean Xcode build before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.2.1/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode Test on your macOS app project.\ndescription: Runs Xcode's `test` action, configured for macOS app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2018-04-10T11:25:10.333955027+02:00\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: d368cf481ce86b5a8b5711c8ad981c13a41fdcd9\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ndependencies:\n- manager: _\n  name: xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.3.0/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode Test on your macOS app project.\ndescription: Runs Xcode's `test` action, configured for macOS app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2019-03-22T15:39:36.231554019Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: dc018e33163d8980aea2b4dcc3936d3c7855f39c\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ndependencies:\n- manager: _\n  name: xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.4.0/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode Test on your macOS app project.\ndescription: Runs Xcode's `test` action, configured for macOS app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2019-05-06T08:47:02.35417956Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 1a711844798adce59ec7e4b1e1cf5e74a69218b1\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ndependencies:\n- manager: _\n  name: xcode\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.4.1/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode Test on your macOS app project.\ndescription: Runs Xcode's `test` action, configured for macOS app projects.\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2020-03-17T11:44:50.267628145Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: a7e6716c080e665014011ee79043030f247d8949\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.4.2/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode's `test` action for macOS app projects.\ndescription: \"This Step runs your pre-defined tests, and the **Deploy to Bitrise.io**\n  Step deploys your test results to Bitrise.\\nYou don't have to upload code signing\n  files for this.\\nHowever, if you set a team for your project locally, in Xcode,\n  then Xcode will ask for that team’s Developer certificate before running the test.\\n\\n\\n###\n  Configuring the Step\\nThis Step has a default configuration that does not need to\n  be modified, which means that if pre-defined tests are written correctly, they will\n  work. \\nHere is a rundown of the inputs should you wish to modify them.\\n1. Add\n  the path of your project in the **Project (or Workspace) path** input.\\n2. Add the\n  scheme name in the **Scheme name** input. Please note the scheme has to be marked\n  as shared in Xcode.\\n3. Add the device or simulator on which the app will run in\n  the **Destination** input, for example, `platform=OS X,arch=x86_64`.\\n4. Set the\n  **Should a clean Xcode build run before testing?** input to `yes` to run a clean\n  build without cache.\\n5. Select `yes` in **Generate code coverage files?** input\n  if you wish to get code coverage analysis of your tests.\\n6. If you wish to use\n  xcpretty formatter for your xcodebuild as an output tool, select `xcpretty` in the\n  **Output tool** input. \\nIf this input is set to `xcodebuild`, the raw xcodebuild\n  output gets printed.\\n7. Add extra options to the end of the `xcodebuild` call in\n  the **Additional options for xcodebuild call** input. \\nUse multiple options separated\n  by a space character, for example, `-xcconfig PATH -verboseAdditional`.\\n9. Set\n  the **Disable indexing during the build** input to `yes` to speed up your build.\\n\\n###\n  Troubleshooting\\n\\nIf your app does not have test targets defined, the primary workflow\n  will be the only automatically created workflow and it will NOT include the **Xcode\n  Test for Mac** Step.\\n\\n\\n### Useful links\\n- [Getting started with MacOS apps](https://devcenter.bitrise.io/getting-started/getting-started-with-macos-apps/)\\n-\n  [About code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Xcode Archive for Mac](https://www.bitrise.io/integrations/steps/xcode-archive-mac)\\n-\n  [Deploy to iTunes Connect - Application Loader ](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2022-02-03T10:09:15.775284712Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 47bb705e2a700ed77f48fd42cabce9a22a9ddb98\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: \"\"\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.5.0/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode's `test` action for macOS app projects.\ndescription: \"This Step runs your pre-defined tests, and the **Deploy to Bitrise.io**\n  Step deploys your test results to Bitrise.\\nYou don't have to upload code signing\n  files for this.\\nHowever, if you set a team for your project locally, in Xcode,\n  then Xcode will ask for that team’s Developer certificate before running the test.\\n\\n\\n###\n  Configuring the Step\\nThis Step has a default configuration that does not need to\n  be modified, which means that if pre-defined tests are written correctly, they will\n  work. \\nHere is a rundown of the inputs should you wish to modify them.\\n1. Add\n  the path of your project in the **Project (or Workspace) path** input.\\n2. Add the\n  scheme name in the **Scheme name** input. Please note the scheme has to be marked\n  as shared in Xcode.\\n3. Add the device or simulator on which the app will run in\n  the **Destination** input, for example, `platform=OS X,arch=x86_64`.\\n4. Set the\n  **Should a clean Xcode build run before testing?** input to `yes` to run a clean\n  build without cache.\\n5. Select `yes` in **Generate code coverage files?** input\n  if you wish to get code coverage analysis of your tests.\\n6. If you wish to use\n  xcpretty formatter for your xcodebuild as an output tool, select `xcpretty` in the\n  **Output tool** input. \\nIf this input is set to `xcodebuild`, the raw xcodebuild\n  output gets printed.\\n7. Add extra options to the end of the `xcodebuild` call in\n  the **Additional options for xcodebuild call** input. \\nUse multiple options separated\n  by a space character, for example, `-xcconfig PATH -verboseAdditional`.\\n9. Set\n  the **Disable indexing during the build** input to `yes` to speed up your build.\\n\\n###\n  Troubleshooting\\n\\nIf your app does not have test targets defined, the primary workflow\n  will be the only automatically created workflow and it will NOT include the **Xcode\n  Test for Mac** Step.\\n\\n\\n### Useful links\\n- [Getting started with MacOS apps](https://devcenter.bitrise.io/getting-started/getting-started-with-macos-apps/)\\n-\n  [About code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\\n\\n###\n  Related Steps\\n- [Xcode Archive for Mac](https://www.bitrise.io/integrations/steps/xcode-archive-mac)\\n-\n  [Deploy to iTunes Connect - Application Loader ](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\"\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2022-05-23T15:16:38.820340333Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: d1ddddc433810c8b482d4099855eb791fd8fcfb3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: CODE_SIGNING_ALLOWED='NO'\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.5.1/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode's `test` action for macOS app projects.\ndescription: |-\n  This Step runs your pre-defined tests, and the **Deploy to Bitrise.io** Step deploys your test results to Bitrise.\n  You don't have to upload code signing files for this.\n  However, if you set a team for your project locally, in Xcode, then Xcode will ask for that team’s Developer certificate before running the test.\n\n  ### Configuring the Step\n  This Step has a default configuration that does not need to be modified, which means that if pre-defined tests are written correctly, they will work.\n  Here is a rundown of the inputs should you wish to modify them.\n  1. Add the path of your project in the **Project (or Workspace) path** input.\n  2. Add the scheme name in the **Scheme name** input. Please note the scheme has to be marked as shared in Xcode.\n  3. Add the device or simulator on which the app will run in the **Destination** input, for example, `platform=OS X,arch=x86_64`.\n  4. Set the **Should a clean Xcode build run before testing?** input to `yes` to run a clean build without cache.\n  5. Select `yes` in **Generate code coverage files?** input if you wish to get code coverage analysis of your tests.\n  6. If you wish to use xcpretty formatter for your xcodebuild as an output tool, select `xcpretty` in the **Output tool** input.\n  If this input is set to `xcodebuild`, the raw xcodebuild output gets printed.\n  7. Add extra options to the end of the `xcodebuild` call in the **Additional options for xcodebuild call** input.\n  Use multiple options separated by a space character, for example, `-xcconfig PATH -verboseAdditional`.\n  9. Set the **Disable indexing during the build** input to `yes` to speed up your build.\n\n  ### Troubleshooting\n\n  If your app does not have test targets defined, the primary workflow will be the only automatically created workflow and it will NOT include the **Xcode Test for Mac** Step.\n\n  ### Useful links\n  - [Getting started with MacOS apps](https://devcenter.bitrise.io/getting-started/getting-started-with-macos-apps/)\n  - [About code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Xcode Archive for Mac](https://www.bitrise.io/integrations/steps/xcode-archive-mac)\n  - [Deploy to iTunes Connect - Application Loader ](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2022-07-20T09:24:09.351730579Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 912b82e991886695b3ec3c4dd129b0b5de1eb068\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\ndeps:\n  brew:\n  - name: go\n  check_only:\n  - name: xcode\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: CODE_SIGNING_ALLOWED='NO'\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.5.2/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode's `test` action for macOS app projects.\ndescription: |-\n  This Step runs your pre-defined tests, and the **Deploy to Bitrise.io** Step deploys your test results to Bitrise.\n  You don't have to upload code signing files for this.\n  However, if you set a team for your project locally, in Xcode, then Xcode will ask for that team’s Developer certificate before running the test.\n\n  ### Configuring the Step\n  This Step has a default configuration that does not need to be modified, which means that if pre-defined tests are written correctly, they will work.\n  Here is a rundown of the inputs should you wish to modify them.\n  1. Add the path of your project in the **Project (or Workspace) path** input.\n  2. Add the scheme name in the **Scheme name** input. Please note the scheme has to be marked as shared in Xcode.\n  3. Add the device or simulator on which the app will run in the **Destination** input, for example, `platform=OS X,arch=x86_64`.\n  4. Set the **Should a clean Xcode build run before testing?** input to `yes` to run a clean build without cache.\n  5. Select `yes` in **Generate code coverage files?** input if you wish to get code coverage analysis of your tests.\n  6. If you wish to use xcpretty formatter for your xcodebuild as an output tool, select `xcpretty` in the **Output tool** input.\n  If this input is set to `xcodebuild`, the raw xcodebuild output gets printed.\n  7. Add extra options to the end of the `xcodebuild` call in the **Additional options for xcodebuild call** input.\n  Use multiple options separated by a space character, for example, `-xcconfig PATH -verboseAdditional`.\n  9. Set the **Disable indexing during the build** input to `yes` to speed up your build.\n\n  ### Troubleshooting\n\n  If your app does not have test targets defined, the primary workflow will be the only automatically created workflow and it will NOT include the **Xcode Test for Mac** Step.\n\n  ### Useful links\n  - [Getting started with MacOS apps](https://devcenter.bitrise.io/getting-started/getting-started-with-macos-apps/)\n  - [About code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Xcode Archive for Mac](https://www.bitrise.io/integrations/steps/xcode-archive-mac)\n  - [Deploy to iTunes Connect - Application Loader ](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2022-11-25T14:15:07.667839711Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 79dd28942cd5b2efbedecfe53f2c98cfd47b3ee4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj` or `.xcworkspace` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project (or Workspace) path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: CODE_SIGNING_ALLOWED='NO'\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.6.0/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode's `test` action for macOS app projects.\ndescription: |-\n  This Step runs your pre-defined tests, and the **Deploy to Bitrise.io** Step deploys your test results to Bitrise.\n  You don't have to upload code signing files for this.\n  However, if you set a team for your project locally, in Xcode, then Xcode will ask for that team’s Developer certificate before running the test.\n\n  ### Configuring the Step\n  This Step has a default configuration that does not need to be modified, which means that if pre-defined tests are written correctly, they will work.\n  Here is a rundown of the inputs should you wish to modify them.\n  1. Add the path of your project in the **Project (or Workspace) path** input.\n  2. Add the scheme name in the **Scheme name** input. Please note the scheme has to be marked as shared in Xcode.\n  3. Add the device or simulator on which the app will run in the **Destination** input, for example, `platform=OS X,arch=x86_64`.\n  4. Set the **Should a clean Xcode build run before testing?** input to `yes` to run a clean build without cache.\n  5. Select `yes` in **Generate code coverage files?** input if you wish to get code coverage analysis of your tests.\n  6. If you wish to use xcpretty formatter for your xcodebuild as an output tool, select `xcpretty` in the **Output tool** input.\n  If this input is set to `xcodebuild`, the raw xcodebuild output gets printed.\n  7. Add extra options to the end of the `xcodebuild` call in the **Additional options for xcodebuild call** input.\n  Use multiple options separated by a space character, for example, `-xcconfig PATH -verboseAdditional`.\n  9. Set the **Disable indexing during the build** input to `yes` to speed up your build.\n\n  ### Troubleshooting\n\n  If your app does not have test targets defined, the primary workflow will be the only automatically created workflow and it will NOT include the **Xcode Test for Mac** Step.\n\n  ### Useful links\n  - [Getting started with MacOS apps](https://devcenter.bitrise.io/getting-started/getting-started-with-macos-apps/)\n  - [About code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Xcode Archive for Mac](https://www.bitrise.io/integrations/steps/xcode-archive-mac)\n  - [Deploy to iTunes Connect - Application Loader ](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2023-07-12T09:22:46.638263696Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: 4893843c7f288d598d25bee4f5544a9f43ddaa81\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj`, `.xcworkspace` or `Package.swift` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project, Workspace or Package path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: CODE_SIGNING_ALLOWED='NO'\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/1.7.0/step.yml",
    "content": "title: Xcode Test for Mac\nsummary: Runs Xcode's `test` action for macOS app projects.\ndescription: |-\n  This Step runs your pre-defined tests, and the **Deploy to Bitrise.io** Step deploys your test results to Bitrise.\n  You don't have to upload code signing files for this.\n  However, if you set a team for your project locally, in Xcode, then Xcode will ask for that team’s Developer certificate before running the test.\n\n  ### Configuring the Step\n  This Step has a default configuration that does not need to be modified, which means that if pre-defined tests are written correctly, they will work.\n  Here is a rundown of the inputs should you wish to modify them.\n  1. Add the path of your project in the **Project (or Workspace) path** input.\n  2. Add the scheme name in the **Scheme name** input. Please note the scheme has to be marked as shared in Xcode.\n  3. Add the device or simulator on which the app will run in the **Destination** input, for example, `platform=OS X,arch=x86_64`.\n  4. Set the **Should a clean Xcode build run before testing?** input to `yes` to run a clean build without cache.\n  5. Select `yes` in **Generate code coverage files?** input if you wish to get code coverage analysis of your tests.\n  6. If you wish to use xcpretty formatter for your xcodebuild as an output tool, select `xcpretty` in the **Output tool** input.\n  If this input is set to `xcodebuild`, the raw xcodebuild output gets printed.\n  7. Add extra options to the end of the `xcodebuild` call in the **Additional options for xcodebuild call** input.\n  Use multiple options separated by a space character, for example, `-xcconfig PATH -verboseAdditional`.\n  9. Set the **Disable indexing during the build** input to `yes` to speed up your build.\n\n  ### Troubleshooting\n\n  If your app does not have test targets defined, the primary workflow will be the only automatically created workflow and it will NOT include the **Xcode Test for Mac** Step.\n\n  ### Useful links\n  - [Getting started with MacOS apps](https://devcenter.bitrise.io/getting-started/getting-started-with-macos-apps/)\n  - [About code signing](https://devcenter.bitrise.io/code-signing/code-signing-index/)\n\n  ### Related Steps\n  - [Xcode Archive for Mac](https://www.bitrise.io/integrations/steps/xcode-archive-mac)\n  - [Deploy to iTunes Connect - Application Loader ](https://www.bitrise.io/integrations/steps/deploy-to-itunesconnect-application-loader)\nwebsite: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsource_code_url: https://github.com/bitrise-steplib/steps-xcode-test-mac\nsupport_url: https://github.com/bitrise-steplib/steps-xcode-test-mac/issues\npublished_at: 2023-08-30T07:10:53.662507775Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-xcode-test-mac.git\n  commit: e887e1df63d673bdeebf53a48270f50d52bdced5\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- macos\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-xcode-test-mac\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      A `.xcodeproj`, `.xcworkspace` or `Package.swift` path, relative to\n      the Working directory (if specified).\n    is_required: true\n    title: Project, Workspace or Package path\n  project_path: $BITRISE_PROJECT_PATH\n- opts:\n    description: |\n      The Scheme to use.\n      **IMPORTANT**: The Scheme have to be marked as __shared__ in Xcode!\n    is_required: true\n    title: Scheme name\n  scheme: $BITRISE_SCHEME\n- destination: null\n  opts:\n    description: |\n      The Destination to use.\n\n      Read more in [Xcodebuild Destination Cheatsheet](http://www.mokacoding.com/blog/xcodebuild-destination-options/).\n\n      Example value: `platform=OS X,arch=x86_64`\n    is_required: false\n    title: Destination name\n- is_clean_build: \"yes\"\n  opts:\n    is_required: true\n    title: Should a clean Xcode build run before testing?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- generate_code_coverage_files: \"no\"\n  opts:\n    is_required: true\n    title: Generate code coverage files?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      If output_tool is set to xcpretty, the xcodebuild output will be prettified by xcpretty.\n      If output_tool is set to xcodebuild, the raw xcodebuild output will be printed.\n    is_required: true\n    title: Output tool\n    value_options:\n    - xcpretty\n    - xcodebuild\n  output_tool: xcpretty\n- opts:\n    description: |-\n      Options added to the end of the xcodebuild call.\n\n      You can use multiple options, separated by a space\n      character. Example: `-xcconfig PATH -verbose`\n    is_required: false\n    title: Additional options for xcodebuild call\n  xcodebuild_options: CODE_SIGNING_ALLOWED='NO'\n- disable_index_while_building: \"yes\"\n  opts:\n    description: |-\n      Could make the build faster by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command which will disable the indexing during the build.\n\n      Indexing is needed for\n\n      * Autocomplete\n      * Ability to quickly jump to definition\n      * Get class and method help by alt clicking.\n\n      Which are not needed in CI environment.\n\n      **Note:** In Xcode you can turn off the `Index-WhileBuilding` feature  by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.<br/>\n      In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag to the `xcodebuild` command.\n    summary: Could make the build faster by disabling the indexing during the build\n      run.\n    title: Disable indexing during the build\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      This input is __deprecated__, please __use change-workdir step__ instead.\n      Working directory of the step.\n      You can leave it empty to don't change it.\n    title: '[Deprecated] Working directory'\n  workdir: $BITRISE_SOURCE_DIR\noutputs:\n- BITRISE_XCODE_TEST_RESULT: null\n  opts:\n    title: Result of the tests. 'succeeded' or 'failed'.\n    value_options:\n    - succeeded\n    - failed\n"
  },
  {
    "path": "steps/xcode-test-mac/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-test-shard-calculation/0.1.0/step.yml",
    "content": "title: Xcode test shard calculation\nsummary: Calculates the test shards for your Xcode tests.\ndescription: |-\n  This step looks at the test bundle and calculates the test shards for your Xcode tests. It finds all of the tests and\n  divides them into the specified number of shards.\n\n  These shards can be used to run the tests in parallel, which can significantly speed up the testing process. Use the\n  [Xcode Test without building](https://www.bitrise.io/integrations/steps/xcode-test-without-building) step's `Test Selection`\n  input to specify which test shard information to use.\n\n  ### Related Steps\n  - [Xcode Test without building](https://www.bitrise.io/integrations/steps/xcode-test-without-building)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\npublished_at: 2025-03-11T14:43:19.494898+01:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation.git\n  commit: ac4c181d6d1920a87808ea9771eb47ebfea4d6d2\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\ninputs:\n- opts:\n    description: |-\n      The path of the test bundle.\n\n      The step supports the following formats:\n      - xcresrun\n      - xctestproducts\n\n      It will use the specified file to collect the built tests and generate the test shards.\n    is_required: true\n    summary: The path of the test bundle.\n    title: Product path\n  product_path: null\n- opts:\n    description: |-\n      The number of test shards to create.\n\n      The output folder will contain `shard_count` number of files, each containing the tests to run in that shard.\n    is_required: true\n    summary: The number of test shards to create.\n    title: Shard count\n  shard_count: null\n- opts:\n    description: |-\n      Defines the strategy to use when splitting the tests into shards\n\n      The available options are:\n      - `alphabetically`: The tests are sorted alphabetically and split into shards\n    is_required: true\n    summary: Defines the strategy to use when splitting the tests into shards\n    title: Shard calculation strategy\n    value_options:\n    - alphabetically\n  shard_calculation: alphabetically\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_TEST_SHARDS_PATH: null\n  opts:\n    summary: This folder contains the generated test shard information.\n    title: Test shards location\n"
  },
  {
    "path": "steps/xcode-test-shard-calculation/0.2.0/step.yml",
    "content": "title: Xcode test shard calculation\nsummary: Calculates the test shards for your Xcode tests.\ndescription: |-\n  This step looks at the test bundle and calculates the test shards for your Xcode tests. It finds all of the tests and\n  divides them into the specified number of shards.\n\n  These shards can be used to run the tests in parallel, which can significantly speed up the testing process. Use the\n  [Xcode Test without building](https://www.bitrise.io/integrations/steps/xcode-test-without-building) step's `Test Selection`\n  input to specify which test shard information to use.\n\n  ### Related Steps\n  - [Xcode Test without building](https://www.bitrise.io/integrations/steps/xcode-test-without-building)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\npublished_at: 2025-04-14T06:14:19.736587258Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation.git\n  commit: d997caee323a92b52e2fb9a79ef0ed253560d000\nproject_type_tags:\n- ios\n- macos\n- react-native\n- cordova\n- ionic\n- flutter\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\ninputs:\n- opts:\n    description: |-\n      The path of the test bundle.\n\n      The step supports the following formats:\n      - xcresrun\n      - xctestproducts\n\n      It will use the specified file to collect the built tests and generate the test shards.\n    is_required: true\n    summary: The path of the test bundle.\n    title: Product path\n  product_path: null\n- opts:\n    description: |-\n      Shard the provided test plan's test.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Shard the provided test plan's test.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      The number of test shards to create.\n\n      The output folder will contain `shard_count` number of files, each containing the tests to run in that shard.\n    is_required: true\n    summary: The number of test shards to create.\n    title: Shard count\n  shard_count: null\n- opts:\n    description: |-\n      Defines the strategy to use when splitting the tests into shards\n\n      The available options are:\n      - `alphabetically`: The tests are sorted alphabetically and split into shards\n    is_required: true\n    summary: Defines the strategy to use when splitting the tests into shards\n    title: Shard calculation strategy\n    value_options:\n    - alphabetically\n  shard_calculation: alphabetically\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_TEST_SHARDS_PATH: null\n  opts:\n    summary: This folder contains the generated test shard information.\n    title: Test shards location\n"
  },
  {
    "path": "steps/xcode-test-shard-calculation/0.2.1/step.yml",
    "content": "title: Xcode test shard calculation\nsummary: Calculates the test shards for your Xcode tests.\ndescription: |-\n  This step looks at the test bundle and calculates the test shards for your Xcode tests. It finds all of the tests and\n  divides them into the specified number of shards.\n\n  These shards can be used to run the tests in parallel, which can significantly speed up the testing process. Use the\n  [Xcode Test without building](https://www.bitrise.io/integrations/steps/xcode-test-without-building) step's `Test Selection`\n  input to specify which test shard information to use.\n\n  ### Related Steps\n  - [Xcode Test without building](https://www.bitrise.io/integrations/steps/xcode-test-without-building)\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\npublished_at: 2025-11-13T12:47:38.497230223Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation.git\n  commit: d9b767ffc49559b87e357f70af5fff10d2aa74d7\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- macos\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-shard-calculation\ninputs:\n- opts:\n    description: |-\n      The path of the test bundle.\n\n      The step supports the following formats:\n      - xcresrun\n      - xctestproducts\n\n      It will use the specified file to collect the built tests and generate the test shards.\n    is_required: true\n    summary: The path of the test bundle.\n    title: Product path\n  product_path: null\n- opts:\n    description: |-\n      Shard the provided test plan's test.\n\n      Leave this input empty to run the default Test Plan or Test Targets associated with the Scheme.\n\n      The input value sets xcodebuild's `-testPlan` option.\n    summary: Shard the provided test plan's test.\n    title: Test Plan\n  test_plan: null\n- opts:\n    description: |-\n      The number of test shards to create.\n\n      The output folder will contain `shard_count` number of files, each containing the tests to run in that shard.\n    is_required: true\n    summary: The number of test shards to create.\n    title: Shard count\n  shard_count: null\n- opts:\n    description: |-\n      Defines the strategy to use when splitting the tests into shards\n\n      The available options are:\n      - `alphabetically`: The tests are sorted alphabetically and split into shards\n    is_required: true\n    summary: Defines the strategy to use when splitting the tests into shards\n    title: Shard calculation strategy\n    value_options:\n    - alphabetically\n  shard_calculation: alphabetically\n- destination: platform=iOS Simulator,name=Bitrise iOS default,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n\n      In a CI environment, a Simulator device called `Bitrise iOS default` is already created.\n      It is a compatible device with the selected Simulator runtime, pre-warmed for better performance.\n\n      If a device with this name is not found (e.g. in a local dev environment), the first matching device will be selected.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Debugging\n    is_required: true\n    summary: Enable logging additional information for debugging.\n    title: Enable verbose logging\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- BITRISE_TEST_SHARDS_PATH: null\n  opts:\n    summary: This folder contains the generated test shard information.\n    title: Test shards location\n"
  },
  {
    "path": "steps/xcode-test-shard-calculation/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.1.0/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2022-06-20T09:14:46.883503+02:00\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 1cd3840a59ddb82a6a84a0d674bd952c93ce109e\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: null\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.2.0/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2022-06-20T12:37:24.281269186Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 01464c913d26ae4312ac17c1e9e82df3728e035b\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.2.1/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2022-07-29T13:23:47.978159146Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 869ae06354520c61f1515257ef6d23f9079ebc9d\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ndeps:\n  check_only:\n  - name: xcode\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.3.0/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2022-10-05T08:27:16.419020238Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: ab22bf298de83519c0b144f971c8d6efefecf596\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.3.1/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2023-07-26T14:54:34.145225611Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 6b35efe0e7afb34a0b9e2a995ef10a3b8966020b\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.4.0/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2025-01-28T07:48:12.504418236Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 0d19aeed5d22b60bb2789f9afc556ce416702e89\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- only_testing: null\n  opts:\n    category: Test Selection\n    description: |-\n      The step will execute only the listed tests.\n\n      The input value sets xcodebuild's `-only-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will execute only the listed tests.\n    title: Test identifier list to execute\n- opts:\n    category: Test Selection\n    description: |-\n      The step will skip the listed tests during execution.\n\n      The input value sets xcodebuild's `-skip-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will skip the listed tests during execution.\n    title: Test identifier list to skip\n  skip_testing: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.4.1/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2025-03-05T10:08:02.434369024Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: f6435d1d7ed2cb86258798d056d67659c5631fac\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- only_testing: null\n  opts:\n    category: Test Selection\n    description: |-\n      The step will execute only the listed tests.\n\n      The input value sets xcodebuild's `-only-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will execute only the listed tests.\n    title: Test identifier list to execute\n- opts:\n    category: Test Selection\n    description: |-\n      The step will skip the listed tests during execution.\n\n      The input value sets xcodebuild's `-skip-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will skip the listed tests during execution.\n    title: Test identifier list to skip\n  skip_testing: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.4.2/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2025-03-26T15:07:08.334288568Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 8be01953aa8941e7bc1048ca2873acff57cb90bc\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- only_testing: null\n  opts:\n    category: Test Selection\n    description: |-\n      The step will execute only the listed tests.\n\n      The input value sets xcodebuild's `-only-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will execute only the listed tests.\n    title: Test identifier list to execute\n- opts:\n    category: Test Selection\n    description: |-\n      The step will skip the listed tests during execution.\n\n      The input value sets xcodebuild's `-skip-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will skip the listed tests during execution.\n    title: Test identifier list to skip\n  skip_testing: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.5.0/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2025-10-20T08:52:35.936294614Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: f4b102282e6a73e105e74f8c3737e6c25a772481\nproject_type_tags:\n- ios\n- react-native\n- cordova\n- ionic\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- only_testing: null\n  opts:\n    category: Test Selection\n    description: |-\n      The step will execute only the listed tests.\n\n      The input value sets xcodebuild's `-only-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will execute only the listed tests.\n    title: Test identifier list to execute\n- opts:\n    category: Test Selection\n    description: |-\n      The step will skip the listed tests during execution.\n\n      The input value sets xcodebuild's `-skip-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will skip the listed tests during execution.\n    title: Test identifier list to skip\n  skip_testing: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/0.5.1/step.yml",
    "content": "title: Xcode Test without building\nsummary: Tests compiled bundles.\ndescription: Tests compiled bundles by running `xcodebuild test-without-building`\n  command.\nwebsite: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsource_code_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\nsupport_url: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building/issues\npublished_at: 2025-11-10T13:52:14.474917841Z\nsource:\n  git: https://github.com/bitrise-steplib/bitrise-step-xcode-test-without-building.git\n  commit: 336b5297e00524fce3da1508c19fe1d721006fc3\nproject_type_tags:\n- cordova\n- flutter\n- ionic\n- ios\n- kotlin-multiplatform\n- react-native\ntype_tags:\n- test\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/bitrise-step-xcode-test-without-building\ninputs:\n- opts:\n    is_required: true\n    summary: Test run parameters file, generated during the build-for-testing action.\n    title: xctestrun file path\n  xctestrun: $BITRISE_XCTESTRUN_FILE_PATH\n- destination: platform=iOS Simulator,name=iPhone 8 Plus,OS=latest\n  opts:\n    description: |-\n      Destination specifier describes the device to use as a destination.\n\n      The input value sets xcodebuild's `-destination` option.\n    is_required: true\n    summary: Destination specifier describes the device to use as a destination.\n    title: Device destination specifier\n- only_testing: null\n  opts:\n    category: Test Selection\n    description: |-\n      The step will execute only the listed tests.\n\n      The input value sets xcodebuild's `-only-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will execute only the listed tests.\n    title: Test identifier list to execute\n- opts:\n    category: Test Selection\n    description: |-\n      The step will skip the listed tests during execution.\n\n      The input value sets xcodebuild's `-skip-testing` option and you can enter multiple test identifiers separated by a newline.\n      The input field supports the same options as xcodebuild:\n      - Test target name only: `MyAppTests`\n      - Test target and test class name: `MyAppTests/MyAppTests`\n      - Test target, class and function name: `MyAppTests/MyAppTests/testExample`\n\n      The input value can be a filepath as well which contains the list of tests separated by a newline character.\n    summary: The step will skip the listed tests during execution.\n    title: Test identifier list to skip\n  skip_testing: null\n- opts:\n    category: Test Repetition\n    description: |-\n      Determines how the tests will repeat.\n\n      Available options:\n      - `none`: Tests will never repeat.\n      - `until_failure`: Tests will repeat until failure or up to maximum repetitions.\n      - `retry_on_failure`: Only failed tests will repeat up to maximum repetitions.\n      - `up_until_maximum_repetitions`: Tests will repeat up until maximum repetitions.\n\n      The input value together with Maximum Test Repetitions (`maximum_test_repetitions`) input sets xcodebuild's `-run-tests-until-failure` / `-retry-tests-on-failure` or `-test-iterations` option.\n    summary: Determines how the tests will repeat.\n    title: Test Repetition Mode (Available in Xcode 13+)\n    value_options:\n    - none\n    - until_failure\n    - retry_on_failure\n    - up_until_maximum_repetitions\n  test_repetition_mode: none\n- maximum_test_repetitions: \"3\"\n  opts:\n    category: Test Repetition\n    description: |-\n      The maximum number of times a test repeats based on the Test Repetition Mode (`test_repetition_mode`).\n\n      Should be more than 1 if the Test Repetition Mode is other than `none`.\n\n      The input value sets xcodebuild's `-test-iterations` option.\n    is_required: true\n    summary: The maximum number of times a test repeats based on the Test Repetition\n      Mode (`test_repetition_mode`).\n    title: Maximum Test Repetitions (Available in Xcode 13+)\n- opts:\n    category: Test Repetition\n    description: |-\n      If this input is set, tests will launch in a new process for each repetition.\n\n      By default, tests launch in the same process for each repetition.\n\n      The input value sets xcodebuild's `-test-repetition-relaunch-enabled` option.\n    summary: If this input is set, tests will launch in a new process for each repetition.\n    title: Relaunch Tests for Each Repetition (Available in Xcode 13+)\n    value_options:\n    - \"yes\"\n    - \"no\"\n  relaunch_tests_for_each_repetition: \"no\"\n- opts:\n    category: xcodebuild configuration\n    summary: Additional options to be added to the executed xcodebuild command.\n    title: Additional options for the xcodebuild command\n  xcodebuild_options: \"\"\n- opts:\n    category: Debugging\n    summary: JSON list of tests added to quarantine on Bitrise.io, quarantined tests\n      are excluded from test runs.\n    title: Quarantined tests\n  quarantined_tests: $BITRISE_QUARANTINED_TESTS_JSON\noutputs:\n- BITRISE_XCRESULT_PATH: null\n  opts:\n    summary: The result bundle path generated by `xcodebuild test-without-building`.\n    title: Test result bundle path\n- BITRISE_XCRESULT_ZIP_PATH: null\n  opts:\n    summary: The zipped result bundle path generated by `xcodebuild test-without-building`.\n    title: Zipped test result bundle path\n"
  },
  {
    "path": "steps/xcode-test-without-building/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/xcodebuild/0.0.1/step.yml",
    "content": "title: xcodebuild\nsummary: xcodebuild\ndescription: xcodebuild\nwebsite: https://github.com/chrisfuller/bitrise-step-xcodebuild\nsource_code_url: https://github.com/chrisfuller/bitrise-step-xcodebuild\nsupport_url: https://github.com/chrisfuller/bitrise-step-xcodebuild/issues\npublished_at: 2019-08-25T17:07:47.574407-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-xcodebuild.git\n  commit: dd1b9ce21d711702fdba61d43e573840b71080d6\nhost_os_tags:\n- osx\ntype_tags:\n- build\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The Xcode workspace.\n    is_expand: true\n    is_required: true\n    title: -workspace\n  xc_option_workspace: ${BITRISE_PROJECT_PATH}\n- opts:\n    description: |\n      The Xcode scheme.\n    is_expand: true\n    is_required: true\n    title: -scheme\n  xc_option_scheme: ${BITRISE_SCHEME}\n- opts:\n    description: |\n      The base SDK.\n    is_expand: true\n    is_required: true\n    title: -sdk\n    value_options:\n    - iphonesimulator\n  xc_option_sdk: iphonesimulator\n- opts:\n    description: |\n      The destination.\n    is_expand: true\n    is_required: true\n    title: -destination\n  xc_option_destination: platform=iOS Simulator,name=${SIMULATOR_DEVICE},OS=${SIMULATOR_OS_VERSION}\n- opts:\n    description: |\n      The actions.\n    is_expand: true\n    is_required: true\n    title: Actions\n  xcodebuild_actions: test\n- opts:\n    description: |\n      The raw xcodebuild output log.\n    is_expand: true\n    is_required: true\n    title: Log\n  raw_xcodebuild_output: ${BITRISE_DEPLOY_DIR}/raw-xcodebuild-output.log\n- opts:\n    description: |\n      The formatter to pipe raw xcodebuild output through.\n      Use `cat -u` if no formatting is desired.\n    is_expand: true\n    is_required: true\n    title: Formatter\n  xcodebuild_output_formatter: cat -u\n"
  },
  {
    "path": "steps/xcodebuild/0.0.2/step.yml",
    "content": "title: xcodebuild\nsummary: xcodebuild\ndescription: xcodebuild\nwebsite: https://github.com/chrisfuller/bitrise-step-xcodebuild\nsource_code_url: https://github.com/chrisfuller/bitrise-step-xcodebuild\nsupport_url: https://github.com/chrisfuller/bitrise-step-xcodebuild/issues\npublished_at: 2019-08-26T08:42:32.587878-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-xcodebuild.git\n  commit: 777f5be885d843396da5da5e8983b5656bc79184\nhost_os_tags:\n- osx\ntype_tags:\n- build\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The workspace.\n    is_expand: true\n    is_required: true\n    title: -workspace\n  xcodebuild_workspace: ${BITRISE_PROJECT_PATH}\n- opts:\n    description: |\n      The scheme.\n    is_expand: true\n    is_required: true\n    title: -scheme\n  xcodebuild_scheme: ${BITRISE_SCHEME}\n- opts:\n    description: |\n      The base SDK.\n    is_expand: true\n    is_required: true\n    title: -sdk\n    value_options:\n    - iphonesimulator\n  xcodebuild_sdk: iphonesimulator\n- opts:\n    description: |\n      The destination.\n    is_expand: true\n    is_required: true\n    title: -destination\n  xcodebuild_destination: platform=iOS Simulator,name=${SIMULATOR_DEVICE},OS=${SIMULATOR_OS_VERSION}\n- opts:\n    description: |\n      The actions.\n    is_expand: true\n    is_required: true\n    title: Actions\n  xcodebuild_actions: test\n- opts:\n    description: |\n      The raw output log.\n    is_expand: true\n    is_required: true\n    title: Log\n  raw_xcodebuild_output: ${BITRISE_DEPLOY_DIR}/raw-xcodebuild-output.log\n- opts:\n    description: |\n      The formatter to pipe raw output through.\n      Use `cat -u` if no formatting is desired.\n    is_expand: true\n    is_required: true\n    title: Formatter\n  xcodebuild_output_formatter: cat -u\noutputs:\n- XCRESULT_BUNDLE_PATH: null\n  opts:\n    description: The result bundle path.\n    title: Result Bundle Path\n"
  },
  {
    "path": "steps/xcodebuild/0.0.3/step.yml",
    "content": "title: xcodebuild\nsummary: Execute `xcodebuild`\ndescription: Execute `xcodebuild`\nwebsite: https://github.com/chrisfuller/bitrise-step-xcodebuild\nsource_code_url: https://github.com/chrisfuller/bitrise-step-xcodebuild\nsupport_url: https://github.com/chrisfuller/bitrise-step-xcodebuild/issues\npublished_at: 2019-09-03T02:32:18.046326-07:00\nsource:\n  git: https://github.com/chrisfuller/bitrise-step-xcodebuild.git\n  commit: b44797c2eced2e62115a32fa99797c0b89f737c5\nhost_os_tags:\n- osx\ntype_tags:\n- build\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      The workspace.\n    is_expand: true\n    is_required: true\n    title: -workspace\n  xcodebuild_workspace: ${BITRISE_PROJECT_PATH}\n- opts:\n    description: |\n      The scheme.\n    is_expand: true\n    is_required: true\n    title: -scheme\n  xcodebuild_scheme: ${BITRISE_SCHEME}\n- opts:\n    description: |\n      The base SDK.\n    is_expand: true\n    is_required: true\n    title: -sdk\n    value_options:\n    - iphonesimulator\n  xcodebuild_sdk: iphonesimulator\n- opts:\n    description: |\n      The destination.\n    is_expand: true\n    is_required: true\n    title: -destination\n  xcodebuild_destination: platform=iOS Simulator,name=${SIMULATOR_DEVICE},OS=${SIMULATOR_OS_VERSION}\n- opts:\n    description: |\n      The actions.\n    is_expand: true\n    is_required: true\n    title: Actions\n  xcodebuild_actions: test\n- opts:\n    description: |\n      The raw output log.\n    is_expand: true\n    is_required: true\n    title: Log\n  raw_xcodebuild_output: ${BITRISE_DEPLOY_DIR}/raw-xcodebuild-output.log\n- opts:\n    description: |\n      The formatter to pipe raw output through.\n      Use `cat -u` if no formatting is desired.\n    is_expand: true\n    is_required: true\n    title: Formatter\n  xcodebuild_output_formatter: cat -u\noutputs:\n- XCRESULT_BUNDLE_PATH: null\n  opts:\n    description: The result bundle path.\n    title: Result Bundle Path\n"
  },
  {
    "path": "steps/xcodebuild/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xcodegen/0.0.5/step.yml",
    "content": "title: Generate Xcode project\nsummary: |\n  This Bitrise step runs XcodeGen to generate a project.\ndescription: |\n  This Bitrise step runs XcodeGen to generate a project.\nwebsite: https://github.com/brandtdaniels/xcodegen-bitrise\nsource_code_url: https://github.com/brandtdaniels/xcodegen-bitrise\nsupport_url: https://github.com/brandtdaniels/xcodegen-bitrise/issues\npublished_at: 2019-11-07T08:41:31.184131-08:00\nsource:\n  git: https://github.com/brandtdaniels/xcodegen-bitrise.git\n  commit: d1904d7249a4eba3a0422c3bf46d6cf646f56cae\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: xcodegen\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: |\n      The path to the project spec file. Defaults to project.yml\n    is_expand: true\n    is_required: true\n    summary: The path to the project spec file.\n    title: The path to the project spec file\n  spec_path: $BITRISE_SOURCE_DIR/project.yml\n- opts:\n    description: The path to the directory where the project should be generated.\n      Defaults to the directory the spec is in. The filename is defined in the project\n      spec\n    is_expand: true\n    is_required: false\n    summary: The path to the directory where the project should be generated.\n    title: The path to the directory where the project should be generated\n  project_path: $BITRISE_SOURCE_DIR\n"
  },
  {
    "path": "steps/xcodegen/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xcparse/0.1.0/step.yml",
    "content": "title: xcparse\nsummary: |\n  Extract screenshots, attachments, code coverage, logs, & more from Xcode 11+ xcresult\ndescription: |\n  Extract screenshots, attachments, code coverage, logs, & more from Xcode 11+ xcresult\nwebsite: https://github.com/ChargePoint/bitrise-step-xcparse\nsource_code_url: https://github.com/ChargePoint/bitrise-step-xcparse\nsupport_url: https://github.com/ChargePoint/bitrise-step-xcparse/issues\npublished_at: 2019-12-06T13:53:38.578101-08:00\nsource:\n  git: https://github.com/ChargePoint/bitrise-step-xcparse.git\n  commit: bebc76ff386912e4cac4045220ad325d40dadaba\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\n- cordova\n- ionic\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  - name: ChargePoint/xcparse/xcparse\n  check_only:\n  - name: xcode\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- opts:\n    description: A `.xcresult` path, relative to the working directory (if specified).\n    is_expand: true\n    is_required: true\n    title: xcresult path\n  xcresult_path: $BITRISE_XCRESULT_PATH\n- extract_attachments: \"yes\"\n  opts:\n    description: If enabled, the attachments within the xcresult will be extracted.\n    title: Extract Attachments\n    value_options:\n    - \"yes\"\n    - \"no\"\n- extract_code_coverage: \"yes\"\n  opts:\n    description: If enabled, the code coverage files within the xcresult will be extracted.\n    title: Extract Code Coverage\n    value_options:\n    - \"yes\"\n    - \"no\"\n- extract_logs: \"yes\"\n  opts:\n    description: If enabled, the logs & diagnostics within the xcresult will be extracted.\n    title: Extract Logs\n    value_options:\n    - \"yes\"\n    - \"no\"\n- extract_screenshots: \"yes\"\n  opts:\n    description: If enabled, the screenshots within the xcresult will be extracted.\n    title: Extract Screenshots\n    value_options:\n    - \"yes\"\n    - \"no\"\n- export_to_deploy: \"yes\"\n  opts:\n    description: If enabled, all generated output will be exported into the ```BITRISE_DEPLOY_DIR```.\n    title: Export to BITRISE_DEPLOY_DIR\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_divide_by_model: \"no\"\n  opts:\n    category: Attachment Options\n    description: If enabled, divides attachments by model\n    title: Divide By Model?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_divide_by_os: \"no\"\n  opts:\n    category: Attachment Options\n    description: If enabled, divides attachments by OS\n    title: Divide By OS?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_divide_by_language: \"no\"\n  opts:\n    category: Attachment Options\n    description: If enabled, divides attachments by test language\n    title: Divide By Language?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_divide_by_region: \"no\"\n  opts:\n    category: Attachment Options\n    description: If enabled, divides attachments by test region\n    title: Divide By Region?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_divide_by_test_plan_config: \"no\"\n  opts:\n    category: Attachment Options\n    description: If enabled, divides attachments by test plan configuration\n    title: Divide By Test Plan Configuration?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_divide_by_test: \"no\"\n  opts:\n    category: Attachment Options\n    description: If enabled, divides attachments by test\n    title: Divide By Test?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- attachments_whitelist_activity_type: \"\"\n  opts:\n    category: Attachment Options\n    description: |-\n      Only extract attachments in the ```.xcresult``` whose activity type matches at least one of the provided activity type strings. If blank, all activity types are allowed.\n\n      Activity types can be found using verbose logging.  Below are a listing of common ones:\n\n      * ```com.apple.dt.xctest.activity-type.attachmentContainer```\n\n        Placeholder activity that contains an attachment, may contain user created screenshot\n      * ```com.apple.dt.xctest.activity-type.deletedAttachment```\n\n        Deleted attachment placeholder activity\n      * ```com.apple.dt.xctest.activity-type.internal```\n\n        Internal test step, may have automatic screenshot to show test progression\n      * ```com.apple.dt.xctest.activity-type.testAssertionFailure```\n\n        Step where the test failed in an assertion, may have failure screenshot\n      * ```com.apple.dt.xctest.activity-type.userCreated```\n\n        User created screenshot/attachment\n\n      **Note:** When an activity type string is provided which doesn't have a reverse-DNS style domain, it is assumed to be of ```com.apple.dt.xctest.activity-type.``` and the domain is automatically added.\n\n      So ```userCreated attachmentContainer``` would be equivalent to ```com.apple.dt.xctest.activity-type.userCreated com.apple.dt.xctest.activity-type.attachmentContainer```\n    title: Activity Type Whitelist\n- attachments_whitelist_test_status: \"\"\n  opts:\n    category: Attachment Options\n    description: |-\n      Only extract attachments in the ```.xcresult``` tied to tests that have a status that matches at least one of the provided status strings. If blank, all test statuses are allowed.\n\n      * ```Success```\n\n        Passing tests only\n      * ```Failure```\n\n        Failing tests only\n      * ```Success Failure```\n\n        Passing or failing tests only\n\n\n      Test status strings can be found by using verbose logging.\n    title: Test Status Whitelist\n- attachments_whitelist_uti: \"\"\n  opts:\n    category: Attachment Options\n    description: |-\n      Only extract attachments in the ```.xcresult``` that conform to at least one of the given UTIs. If left empty, all attachments, regardless of UTI conformance, are extracted.\n\n      Common attachment UTIs in xcresults are:\n      * ```public.image```\n\n        Screenshots\n      * ```public.plain-text```\n\n        Test failure debug descriptions\n\n      Read [this Apple documentation](https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/UTIRef/Articles/System-DeclaredUniformTypeIdentifiers.html#//apple_ref/doc/uid/TP40009259-SW1) for a list of publicly documented UTIs.\n    title: UTI Whitelist\n- opts:\n    category: Screenshot Options\n    description: If enabled, divides screenshots by model\n    title: Divide By Model?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  screenshots_divide_by_model: \"no\"\n- opts:\n    category: Screenshot Options\n    description: If enabled, divides screenshots by OS\n    title: Divide By OS?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  screenshots_divide_by_os: \"no\"\n- opts:\n    category: Screenshot Options\n    description: If enabled, divides screenshots by test language\n    title: Divide By Language?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  screenshots_divide_by_language: \"no\"\n- opts:\n    category: Screenshot Options\n    description: If enabled, divides screenshots by test region\n    title: Divide By Region?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  screenshots_divide_by_region: \"no\"\n- opts:\n    category: Screenshot Options\n    description: If enabled, divides screenshots by test plan configuration\n    title: Divide By Test Plan Configuration?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  screenshots_divide_by_test_plan_config: \"no\"\n- opts:\n    category: Screenshot Options\n    description: If enabled, divides screenshots by test\n    title: Divide By Test?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  screenshots_divide_by_test: \"no\"\n- opts:\n    category: Screenshot Options\n    description: |-\n      Only extract screenshots in the ```.xcresult``` whose activity type matches at least one of the provided activity type strings. If blank, all activity types are allowed.\n\n      Activity types can be found using verbose logging.  Below are a listing of common ones:\n\n      * ```com.apple.dt.xctest.activity-type.attachmentContainer```\n\n        Placeholder activity that contains an attachment, may contain user created screenshot\n      * ```com.apple.dt.xctest.activity-type.deletedAttachment```\n\n        Deleted attachment placeholder activity\n      * ```com.apple.dt.xctest.activity-type.internal```\n\n        Internal test step, may have automatic screenshot to show test progression\n      * ```com.apple.dt.xctest.activity-type.testAssertionFailure```\n\n        Step where the test failed in an assertion, may have failure screenshot\n      * ```com.apple.dt.xctest.activity-type.userCreated```\n\n        User created screenshot/attachment\n\n      **Note:** When an activity type string is provided which doesn't have a reverse-DNS style domain, it is assumed to be of ```com.apple.dt.xctest.activity-type.``` and the domain is automatically added.\n\n      So ```userCreated attachmentContainer``` would be equivalent to ```com.apple.dt.xctest.activity-type.userCreated com.apple.dt.xctest.activity-type.attachmentContainer```\n    title: Activity Type Whitelist\n  screenshots_whitelist_activity_type: \"\"\n- opts:\n    category: Screenshot Options\n    description: |-\n      Only extract screenshots in the ```.xcresult``` tied to tests that have a status that matches at least one of the provided status strings. If blank, all test statuses are allowed.\n\n      * ```Success```\n\n        Passing tests only\n      * ```Failure```\n\n        Failing tests only\n      * ```Success Failure```\n\n        Passing or failing tests only\n\n\n      Test status strings can be found by using verbose logging.\n    title: Test Status Whitelist\n  screenshots_whitelist_test_status: \"\"\n- opts:\n    category: Debug\n    description: You can enable verbose logging within xcparse to debug issues. All\n      xcresulttool commands and output will be shown when used.\n    title: Enable verbose logging?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- XCPARSE_ATTACHMENTS_PATH: null\n  opts:\n    description: This is the path of the test attachments zip.\n    title: The full test attachments zip path\n- XCPARSE_CODE_COVERAGE_PATH: null\n  opts:\n    description: This is the path of the test code coverage zip.\n    title: The full test code coverage zip path\n- XCPARSE_LOGS_PATH: null\n  opts:\n    description: This is the path of the test logs zip.\n    title: The full test logs zip path\n- XCPARSE_SCREENSHOTS_PATH: null\n  opts:\n    description: This is the path of the test screenshots zip.\n    title: The full test screenshots zip path\n- XCPARSE_VERSION: null\n  opts:\n    description: This is the version of xcparse used for extraction.\n    title: xcparse version\n"
  },
  {
    "path": "steps/xcparse/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/xctest-html-report/0.1.3/step.yml",
    "content": "title: Generate Xcode test HTML/JUnit report\nsummary: Generate Xcode-like HTML report for Unit and UI Tests\ndescription: Generate Xcode-like HTML report for Unit and UI Tests with XCTestHTMLReport\nwebsite: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsource_code_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsupport_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report/issues\npublished_at: 2019-05-24T10:28:01.338135+02:00\nsource:\n  git: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report.git\n  commit: 45b8b2c7462f0158c6067632794edcb19e28ac9e\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/BirmacherAkos/bitrise-step-xctest-html-report\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |-\n      The paths of the Xcode test generated .xctesresult files.\n\n      **Separated by a new line**\n\n      * $BITRISE\\_SOURCE\\_DIR/test.xctestresult\n      * $BITRISE\\_SOURCE\\_DIR/test\\_2.xctestresult\n      * ./test\\_3.xctestresult\n    is_required: true\n    summary: The paths of the Xcode test generated .xctesresult files.\n    title: Xcode test result (.xctesresult) paths\n  test_result_path: $BITRISE_XCRESULT_PATH\n- generate_junit: \"true\"\n  opts:\n    description: |\n      Provide JUnit XML output if enabled.\n    is_required: true\n    summary: Generate JUnit report?\n    title: Generate JUnit report?\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    description: |-\n      This directory will contain the generated test reports.\n\n      By default it's the `$BITRISE\\_DEPLOY_DIR`\n    is_required: \"true\"\n    summary: This directory will contain the generated test reports.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    description: |\n      You can enable the verbose logging for troubleshooting purposes.\n    is_required: true\n    summary: Enable verbose log?\n    title: Enable verbose log?\n    value_options:\n    - \"true\"\n    - \"false\"\n  verbose: \"false\"\noutputs:\n- XC_HTML_REPORT: null\n  opts:\n    summary: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n- XC_JUNIT_REPORT: null\n  opts:\n    summary: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n"
  },
  {
    "path": "steps/xctest-html-report/0.2.0/step.yml",
    "content": "title: Generate Xcode test HTML/JUnit report\nsummary: Generate Xcode-like HTML report for Unit and UI Tests\ndescription: Generate Xcode-like HTML report for Unit and UI Tests with XCTestHTMLReport\nwebsite: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsource_code_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsupport_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report/issues\npublished_at: 2019-11-17T17:23:13.834871+01:00\nsource:\n  git: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report.git\n  commit: 20d0ea8c9d9638bab2637a7e93642062a6091e16\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/BirmacherAkos/bitrise-step-xctest-html-report\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |-\n      The paths of the Xcode test generated .xctesresult files.\n\n      **Separated by a new line**\n\n      * $BITRISE\\_SOURCE\\_DIR/test.xctestresult\n      * $BITRISE\\_SOURCE\\_DIR/test\\_2.xctestresult\n      * ./test\\_3.xctestresult\n    is_required: true\n    summary: The paths of the Xcode test generated .xctesresult files.\n    title: Xcode test result (.xctesresult) paths\n  test_result_path: $BITRISE_XCRESULT_PATH\n- generate_junit: \"yes\"\n  opts:\n    description: |\n      Provide JUnit XML output if enabled.\n    is_required: true\n    summary: Generate JUnit report?\n    title: Generate JUnit report?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      This directory will contain the generated test reports.\n\n      By default it's the `$BITRISE\\_DEPLOY_DIR`\n    is_required: \"true\"\n    summary: This directory will contain the generated test reports.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- install_branch: develop\n  opts:\n    description: |\n      You can select from which branch do you want to install the XCTestHTMLReport.\n\n      **Master** for the stable version\n      **Develop** for the newest version\n    is_required: true\n    summary: Select from which branch should the step install the tool\n    title: Install branch of XCTestHTMLReport\n    value_options:\n    - develop\n    - master\n- opts:\n    description: |\n      You can enable the verbose logging for troubleshooting purposes.\n    is_required: true\n    summary: Enable verbose log?\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- XC_HTML_REPORT: null\n  opts:\n    summary: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n- XC_JUNIT_REPORT: null\n  opts:\n    summary: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n"
  },
  {
    "path": "steps/xctest-html-report/0.2.1/step.yml",
    "content": "title: Generate Xcode test HTML/JUnit report\nsummary: Generate Xcode-like HTML report for Unit and UI Tests\ndescription: Generate Xcode-like HTML report for Unit and UI Tests with XCTestHTMLReport\nwebsite: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsource_code_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsupport_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report/issues\npublished_at: 2019-11-22T16:06:06.142644+01:00\nsource:\n  git: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report.git\n  commit: 16ff4b78c7e8eb1d97c4e4ef9ddf7e3b05bb80dd\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/BirmacherAkos/bitrise-step-xctest-html-report\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- opts:\n    description: |-\n      The paths of the Xcode test generated .xctesresult files.\n\n      **Separated by a new line**\n\n      * $BITRISE\\_SOURCE\\_DIR/test.xctestresult\n      * $BITRISE\\_SOURCE\\_DIR/test\\_2.xctestresult\n      * ./test\\_3.xctestresult\n    is_required: true\n    summary: The paths of the Xcode test generated .xctesresult files.\n    title: Xcode test result (.xctesresult) paths\n  test_result_path: $BITRISE_XCRESULT_PATH\n- generate_junit: \"yes\"\n  opts:\n    description: |\n      Provide JUnit XML output if enabled.\n    is_required: true\n    summary: Generate JUnit report?\n    title: Generate JUnit report?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      This directory will contain the generated test reports.\n\n      By default it's the `$BITRISE\\_DEPLOY_DIR`\n    is_required: \"true\"\n    summary: This directory will contain the generated test reports.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- install_branch: develop\n  opts:\n    description: |\n      You can select from which branch do you want to install the XCTestHTMLReport.\n\n      **Master** for the stable version\n      **Develop** for the newest version\n    is_required: true\n    summary: Select from which branch should the step install the tool\n    title: Install branch of XCTestHTMLReport\n    value_options:\n    - develop\n    - master\n- opts:\n    description: |\n      You can enable the verbose logging for troubleshooting purposes.\n    is_required: true\n    summary: Enable verbose log?\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- XC_HTML_REPORT: null\n  opts:\n    summary: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n- XC_JUNIT_REPORT: null\n  opts:\n    summary: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n"
  },
  {
    "path": "steps/xctest-html-report/1.0.0/step.yml",
    "content": "title: Generate Xcode test HTML/JUnit report\nsummary: Generate Xcode-like HTML report for Unit and UI Tests\ndescription: Generate Xcode-like HTML report for Unit and UI Tests with XCTestHTMLReport\nwebsite: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsource_code_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report\nsupport_url: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report/issues\npublished_at: 2020-09-23T21:06:29.048917+02:00\nsource:\n  git: https://github.com/BirmacherAkos/bitrise-step-xctest-html-report.git\n  commit: a117b7f0da39c3fec27d17ee49b31718fd0d1514\nproject_type_tags:\n- ios\n- macos\n- react-native\n- flutter\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/BirmacherAkos/bitrise-step-xctest-html-report\nis_requires_admin_user: true\nis_always_run: true\nis_skippable: true\ninputs:\n- github_access_token: null\n  opts:\n    description: |-\n      Use this input to avoid Github rate limit issues.\n      See the github's guide: [Creating an access token for command-line use](https://help.github.com/articles/creating-an-access-token-for-command-line-use/).\n      __UNCHECK EVERY SCOPE BOX__ when creating this token. There is no reason this token needs access to private information.\n    is_sensitive: true\n    summary: Use this input to avoid Github rate limit issues for the XCTestHTMLReport\n      download\n    title: Github Personal Access Token\n- opts:\n    description: |-\n      The paths of the Xcode test generated .xctestresult files.\n\n      **Separated by a new line**\n\n      * $BITRISE\\_SOURCE\\_DIR/test.xctestresult\n      * $BITRISE\\_SOURCE\\_DIR/test\\_2.xctestresult\n      * ./test\\_3.xctestresult\n    is_required: true\n    summary: The paths of the Xcode test generated .xctestresult files.\n    title: Xcode test result (.xctestresult) paths\n  test_result_path: $BITRISE_XCRESULT_PATH\n- generate_junit: \"yes\"\n  opts:\n    description: |\n      Provide JUnit XML output if enabled.\n    is_required: true\n    summary: Generate JUnit report?\n    title: Generate JUnit report?\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |-\n      This directory will contain the generated test reports.\n\n      By default it's the `$BITRISE\\_DEPLOY_DIR`\n    is_required: \"true\"\n    summary: This directory will contain the generated test reports.\n    title: Output directory path\n  output_dir: $BITRISE_DEPLOY_DIR\n- opts:\n    description: |\n      The version of XCTestHTMLReport you want to use from https://github.com/TitouanVanBelle/XCTestHTMLReport/releases.\n      If the value is set to `latest`, the step will download to the latest XCTestHTMLReport version.\n    is_required: true\n    summary: Select which version to install\n    title: Version of the XCTestHTMLReport\n    value_options:\n    - develop\n    - master\n  version: latest\n- opts:\n    description: |\n      You can enable the verbose logging for troubleshooting purposes.\n    is_required: true\n    summary: Enable verbose log?\n    title: Enable verbose log?\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose: \"no\"\noutputs:\n- XC_HTML_REPORT: null\n  opts:\n    summary: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `HTML report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n- XC_JUNIT_REPORT: null\n  opts:\n    summary: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n    title: The path of the generated `JUnit report`. Which was exported to the output\\_dir\n      ( $BITRISE\\_DEPLOY\\_DIR by default )\n"
  },
  {
    "path": "steps/xctest-html-report/step-info.yml",
    "content": "maintainer: community\nremoval_date: \"2023-11-30\"\ndeprecate_notes: |\n This step is no longer maintained. To generate HTML reports from xcresult files use the new official Bitrise step: \"Generate Xcode test report html\" (https://devcenter.bitrise.io/en/testing/testing-ios-apps/viewing-xcode-test-results-in-rich-html-format.html).\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.1/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2019-08-28T12:22:24.518211+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 0d00bc6a35adcb022db1ef0702e232f7e9fbf005\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack sever. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: 0\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.11/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-06-03T00:13:16.305673+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 41745a4d6bd8acb8235bc4385312e339ede239a2\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.12/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-06-03T23:04:39.748349+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: f88e7ee12d46ac14ee1638cd438dae34aeef7645\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.13/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-06-21T12:00:31.522951+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 032ae70073e7d3d003e23958a55a9b66ac2f99d4\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.15/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-09-22T14:17:57.659286+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 8e7d936b89bc8ead34e5e6c4010f2054ddd189f3\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- browserstack_env_var: ENVIRONMENT_VARIABLE_NAME\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable name to be set while executing tests on Browserstack\n- browserstack_env_value: ENVIRONMENT_VARIABLE_VALUE\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable value to be set while executing tests on Browserstack\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.16/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-09-26T14:09:27.756657+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: d7f2d3a7d5a3b5dd354855e7f70eb22b8f2b7534\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- browserstack_env_var: ENVIRONMENT_VARIABLE_NAME\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable name to be set while executing tests on Browserstack\n- browserstack_env_value: ENVIRONMENT_VARIABLE_VALUE\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable value to be set while executing tests on Browserstack\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.17/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-10-18T16:10:17.633616+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 56c9621d953690fed91187f1fa26fc94028b1bba\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- browserstack_env_var: ENVIRONMENT_VARIABLE_NAME\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable name to be set while executing tests on Browserstack\n- browserstack_env_value: ENVIRONMENT_VARIABLE_VALUE\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable value to be set while executing tests on Browserstack\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.2/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2019-08-29T21:14:12.726885+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 34c134de044665835565df04d433ce796523dd83\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack sever. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: 0\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.5/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2019-09-06T15:46:01.896654+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: e5a2b259be20cedf5a27d2ffba4057b237c4fc6d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack sever. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.6/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2019-10-25T00:54:03.537572+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 85c1ddfc7a3ff8d41a758f0001db350913895c98\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack sever. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.8/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2019-11-25T16:13:32.922052+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 4dde3b296889f61aee1bfe1f551dc1c4a2c3217b\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/1.0.9/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-05-03T10:06:14.826348+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: b9a3c10ea34c34e84d4831f320c48c53f7d54d64\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/2.0.0/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-11-01T13:11:12.505238+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 740b6af5777a3afb62206447349f394e5d27c5cd\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- browserstack_env_vars: ENVIRONMENT_VARIABLES\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variables to be set while executing tests on Browserstack\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/2.0.1/step.yml",
    "content": "title: Browserstack iOS UI Test\nsummary: |\n  Execute XCUITests on Browserstack Platform with retry logic\ndescription: |\n  This step will help you to execute iOS UI Automation tests on Browserstack platform. Automatically manages device queue and retries failed tests and also reports test status.\nwebsite: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsource_code_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack\nsupport_url: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack/issues\npublished_at: 2020-12-13T12:13:18.728269+04:00\nsource:\n  git: https://github.com/satheeshkumarf/bitrise-step-executexcuitestonbrowserstack.git\n  commit: 296608d485334d4bc17739dc316373a79c232409\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- ios\n- macos\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: browserstack.sh\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- browserstack_app_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: IPA url of the app uploaded to Browserstack Server. You can use browserstack-upload\n      bitrise step to upload your ipa.\n    title: Browserstack ipa url\n- opts:\n    description: |\n      Sample file format:\n          SearchListingsTest/testXYZ=iPhone 6-11.2\n          SearchFilterTest/testABC=iPhone XS-12.1\n    is_expand: true\n    is_required: true\n    summary: Specifiy path to the file which contains your test and device details.\n      Use .txt file to specify your test name and device details separated by equal\n      to sign.\n    title: Test file path\n  tests_file_path: null\n- browserstack_xcuitest_url: null\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Build your XCUITests and publish it to Browserstack server. Specify the\n      test_url path returned from browserstack in this variable.\n    title: Browserstack xcuitest url\n- browserstack_username: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack username\n- browserstack_password: null\n  opts:\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    title: Browserstack access key\n- browserstack_local: \"false\"\n  opts:\n    is_expand: true\n    is_required: true\n    summary: Set this value to true for enabling testing on your private test environment.\n    title: Enable local testing feature of Browserstack\n    value_options:\n    - \"true\"\n    - \"false\"\n- browserstack_local_id: null\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify unique local connection name\n- browserstack_env_var_name: ENVIRONMENT_VARIABLE NAME\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable name to be set while executing tests on Browserstack\n- browserstack_env_var_value: ENVIRONMENT_VARIABLE VALUE\n  opts:\n    is_expand: true\n    is_required: false\n    title: Specify environemnt variable value to be set while executing tests on Browserstack\n- opts:\n    is_expand: true\n    is_required: true\n    summary: By default retry count is set as zero, which will not re-execute failed\n      tests. If you specify a value greater than zero, only the failed tests will\n      be re-executed to see if the issue was a random flakiness.\n    title: Retry count for failed tests\n  retry_count: \"0\"\n"
  },
  {
    "path": "steps/xcuitestbrowserstack/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/yarn/0.0.2/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/jonoirwinrsa/steps-yarn\nsource_code_url: https://github.com/jonoirwinrsa/steps-yarn\nsupport_url: https://github.com/jonoirwinrsa/steps-yarn/issues\npublished_at: 2016-10-20T13:25:54.991730369+02:00\nsource:\n  git: https://github.com/jonoirwinrsa/steps-yarn.git\n  commit: 9b65131340ace1399bee8b2916eb2d65b5714db7\nhost_os_tags:\n- osx-10.10\nproject_type_tags:\n- react-native\ntype_tags:\n- yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: Specify the command to run with `yarn`. For example `add`.\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `-dd -ll`\n    title: Arguments for running `yarn` commands\n"
  },
  {
    "path": "steps/yarn/0.0.3/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/jonoirwinrsa/steps-yarn\nsource_code_url: https://github.com/jonoirwinrsa/steps-yarn\nsupport_url: https://github.com/jonoirwinrsa/steps-yarn/issues\npublished_at: 2016-10-20T15:55:58.953051412+02:00\nsource:\n  git: https://github.com/jonoirwinrsa/steps-yarn.git\n  commit: 3fbb032b55af70bdd35ff37733e447692a14ef27\nhost_os_tags:\n- osx-10.11\nproject_type_tags:\n- ios\n- android\ntype_tags:\n- react-native\n- npm\n- yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `global`\n    title: Arguments for running `yarn` commands\n"
  },
  {
    "path": "steps/yarn/0.0.4/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/jonoirwinrsa/steps-yarn\nsource_code_url: https://github.com/jonoirwinrsa/steps-yarn\nsupport_url: https://github.com/jonoirwinrsa/steps-yarn/issues\npublished_at: 2017-02-15T12:28:39.004156417+02:00\nsource:\n  git: https://github.com/jonoirwinrsa/steps-yarn.git\n  commit: ec2279ecaf33360420509e7dd438cfe70300ea02\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `global`\n    title: Arguments for running `yarn` commands\n"
  },
  {
    "path": "steps/yarn/0.0.6/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/jonoirwinrsa/steps-yarn\nsource_code_url: https://github.com/jonoirwinrsa/steps-yarn\nsupport_url: https://github.com/jonoirwinrsa/steps-yarn/issues\npublished_at: !!timestamp 2018-03-29T18:29:32.102421429+02:00\nsource:\n  git: https://github.com/jonoirwinrsa/steps-yarn.git\n  commit: 85c5f339902370d52149b5150a486500c88ab72d\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `global`\n    title: Arguments for running `yarn` commands\n"
  },
  {
    "path": "steps/yarn/0.0.7/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/jonoirwinrsa/steps-yarn\nsource_code_url: https://github.com/jonoirwinrsa/steps-yarn\nsupport_url: https://github.com/jonoirwinrsa/steps-yarn/issues\npublished_at: !!timestamp 2018-03-29T18:41:37.136081535+02:00\nsource:\n  git: https://github.com/jonoirwinrsa/steps-yarn.git\n  commit: 919222b34e2d8567cb5c07ac8fcae2925dbc113d\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `global`\n    title: Arguments for running `yarn` commands\n"
  },
  {
    "path": "steps/yarn/0.0.8/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2018-10-31T16:02:24.695158334Z\nsource:\n  git: https://github.com/bitrise-community/steps-yarn.git\n  commit: 95f60fb059627f24ef5b4714bc9fbcd27be99ac1\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `global`\n    title: Arguments for running `yarn` commands\n"
  },
  {
    "path": "steps/yarn/0.1.0/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: Runs `yarn` with the given command and args.\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2019-10-15T10:35:20.751143473Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-yarn.git\n  commit: c5de117c0d4fa3f306e6e1e0fea8dd5d4794e011\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `react` or `-dev`\n    title: Arguments for running `yarn` commands\n- cache_local_deps: \"no\"\n  opts:\n    description: |-\n      Select if the contents of node_modules directory should be cached.\n\n      `yes`: Mark local dependencies to be cached.\n      `no`: Do not use cache.\n\n      All node_modules folders (recursively) located under the working directory will be cached.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Choose if debug logging is enabled.\n    is_required: true\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/yarn/0.1.1/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: \"\\nYarn is a package manager that is compatible with the npm registry.\n  Download your app's dependencies via yarn by using this Step.  \\n\\n### Configuring\n  the Step\\n\\nTo use the Step, you need to configure your dependencies in your `package.json`\n  file.\\n\\n1. Set a command in **The yarn command to run** input.\\n\\n   If you leave\n  the input blank, the Step will simply install your dependencies. You can find the\n  other available command in [yarn's documentation](https://yarnpkg.com/lang/en/docs/cli/).\\n\\n1.\n  Set the arguments in the **Arguments for running yarn commands** input.\\n\\n   You\n  can specify multiple arguments. Check out the available arguments for each command\n  in yarn's documentation.\\n\\nYou can also cache the contents of the node_modules\n  directory by setting the **Cache node_modules** input to `yes`.\\n\\n### Troubleshooting\\n\\nIf\n  the Step fails, run it again with verbose logging enabled. To do so, set the **Enable\n  verbose logging** input to `yes`. Doing so allows yarn to output more information\n  about the command you ran.\\n\\nMake sure your commands and arguments are correct,\n  and that your packages are correctly defined in the `package.json` file.\\n\\n###\n  Useful links\\n\\n[Getting started with React Native apps](https://devcenter.bitrise.io/getting-started/getting-started-with-react-native-apps/)\\n[Running\n  Detox tests on Bitrise](https://devcenter.bitrise.io/testing/running-detox-tests-on-bitrise/)\\n\\n###\n  Related Steps\\n\\n[Run Cocoapods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\\n[Run\n  npm command](https://www.bitrise.io/integrations/steps/npm)\"\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2020-01-14T14:50:57.321171007Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-yarn.git\n  commit: 52c2043e10bb241f0d520bc00b5927189dc4b98b\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `react` or `-dev`\n    title: Arguments for running `yarn` commands\n- cache_local_deps: \"no\"\n  opts:\n    description: |-\n      Select if the contents of node_modules directory should be cached.\n\n      `yes`: Mark local dependencies to be cached.\n      `no`: Do not use cache.\n\n      All node_modules folders (recursively) located under the working directory will be cached.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Choose if debug logging is enabled.\n    is_required: true\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/yarn/0.1.2/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: |2-\n\n  Yarn is a package manager that is compatible with the npm registry. Download your app's dependencies via yarn by using this Step.\n\n  ### Configuring the Step\n\n  To use the Step, you need to configure your dependencies in your `package.json` file.\n\n  1. Set a command in **The yarn command to run** input.\n\n     If you leave the input blank, the Step will simply install your dependencies. You can find the other available command in [yarn's documentation](https://yarnpkg.com/lang/en/docs/cli/).\n\n  1. Set the arguments in the **Arguments for running yarn commands** input.\n\n     You can specify multiple arguments. Check out the available arguments for each command in yarn's documentation.\n\n  You can also cache the contents of the node_modules directory by setting the **Cache node_modules** input to `yes`.\n\n  ### Troubleshooting\n\n  If the Step fails, run it again with verbose logging enabled. To do so, set the **Enable verbose logging** input to `yes`. Doing so allows yarn to output more information about the command you ran.\n\n  Make sure your commands and arguments are correct, and that your packages are correctly defined in the `package.json` file.\n\n  ### Useful links\n\n  [Getting started with React Native apps](https://devcenter.bitrise.io/getting-started/getting-started-with-react-native-apps/)\n  [Running Detox tests on Bitrise](https://devcenter.bitrise.io/testing/running-detox-tests-on-bitrise/)\n\n  ### Related Steps\n\n  [Run Cocoapods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2022-02-23T16:02:34.512861806Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-yarn.git\n  commit: 19f3fbd7f7f8f2b40a82344aca6475261ed5db29\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `react` or `-dev`\n    title: Arguments for running `yarn` commands\n- cache_local_deps: \"no\"\n  opts:\n    description: |-\n      Select if the contents of node_modules directory should be cached.\n\n      `yes`: Mark local dependencies to be cached.\n      `no`: Do not use cache.\n\n      All node_modules folders (recursively) located under the working directory will be cached.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Choose if debug logging is enabled.\n    is_required: true\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/yarn/0.1.3/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: |2-\n\n  Yarn is a package manager that is compatible with the npm registry. Download your app's dependencies via yarn by using this Step.\n\n  ### Configuring the Step\n\n  To use the Step, you need to configure your dependencies in your `package.json` file.\n\n  1. Set a command in **The yarn command to run** input.\n\n     If you leave the input blank, the Step will simply install your dependencies. You can find the other available command in [yarn's documentation](https://yarnpkg.com/lang/en/docs/cli/).\n\n  1. Set the arguments in the **Arguments for running yarn commands** input.\n\n     You can specify multiple arguments. Check out the available arguments for each command in yarn's documentation.\n\n  You can also cache the contents of the node_modules directory by setting the **Cache node_modules** input to `yes`.\n\n  ### Troubleshooting\n\n  If the Step fails, run it again with verbose logging enabled. To do so, set the **Enable verbose logging** input to `yes`. Doing so allows yarn to output more information about the command you ran.\n\n  Make sure your commands and arguments are correct, and that your packages are correctly defined in the `package.json` file.\n\n  ### Useful links\n\n  [Getting started with React Native apps](https://devcenter.bitrise.io/getting-started/getting-started-with-react-native-apps/)\n  [Running Detox tests on Bitrise](https://devcenter.bitrise.io/testing/running-detox-tests-on-bitrise/)\n\n  ### Related Steps\n\n  [Run Cocoapods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2023-11-20T14:54:57.936041726Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-yarn.git\n  commit: 07a231de216630978f1fedbdbc8219f590c7ac39\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `react` or `-dev`\n    title: Arguments for running `yarn` commands\n- cache_local_deps: \"no\"\n  opts:\n    description: |-\n      Select if the contents of node_modules directory should be cached.\n\n      `yes`: Mark local dependencies to be cached.\n      `no`: Do not use cache.\n\n      All node_modules folders (recursively) located under the working directory will be cached.\n    is_required: true\n    title: Cache node_modules\n    value_options:\n    - \"yes\"\n    - \"no\"\n- opts:\n    description: |\n      Choose if debug logging is enabled.\n    is_required: true\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/yarn/1.0.0/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: |2-\n\n  Yarn is a package manager that is compatible with the npm registry. Download your app's dependencies via yarn by using this Step.\n\n  ### Configuring the Step\n\n  To use the Step, you need to configure your dependencies in your `package.json` file.\n\n  1. Set a command in **The yarn command to run** input.\n\n     If you leave the input blank, the Step will simply install your dependencies. You can find the other available command in [yarn's documentation](https://yarnpkg.com/lang/en/docs/cli/).\n\n  1. Set the arguments in the **Arguments for running yarn commands** input.\n\n     You can specify multiple arguments. Check out the available arguments for each command in yarn's documentation.\n\n  ### Troubleshooting\n\n  If the Step fails, run it again with verbose logging enabled. To do so, set the **Enable verbose logging** input to `yes`. Doing so allows yarn to output more information about the command you ran.\n\n  Make sure your commands and arguments are correct, and that your packages are correctly defined in the `package.json` file.\n\n  ### Useful links\n\n  [Getting started with React Native apps](https://devcenter.bitrise.io/getting-started/getting-started-with-react-native-apps/)\n  [Running Detox tests on Bitrise](https://devcenter.bitrise.io/testing/running-detox-tests-on-bitrise/)\n\n  ### Related Steps\n\n  [Run Cocoapods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2026-01-29T12:20:48.057892151Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-yarn.git\n  commit: d5ec3cc386ebf6178b708579a61c52f83ccdb047\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-yarn\ndeps:\n  brew:\n  - name: node\n  - name: yarn\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `react` or `-dev`\n    title: Arguments for running `yarn` commands\n- opts:\n    description: |\n      Choose if debug logging is enabled.\n    is_required: true\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/yarn/2.0.0/step.yml",
    "content": "title: Run yarn command\nsummary: Runs `yarn` with the given command and args.\ndescription: |-\n  Yarn is a package manager that is compatible with the npm registry. Download your app's dependencies via yarn by using this Step.\n\n  This Step uses Corepack to automatically manage the Yarn version. The Yarn version is determined by the `packageManager` field in your `package.json` file or the `.yarnrc`/`.yarnrc.yml` configuration file.\n\n  ### Configuring the Step\n\n  To use the Step, you need to configure your dependencies in your `package.json` file.\n\n  1. (Recommended) Specify the Yarn version in your `package.json`:\n     ```json\n     {\n       \"packageManager\": \"yarn@4.1.0\"\n     }\n     ```\n     If not specified, Corepack will use its default Yarn version.\n\n  1. Set a command in **The yarn command to run** input.\n\n     If you leave the input blank, the Step will simply install your dependencies. You can find the other available command in [yarn's documentation](https://yarnpkg.com/lang/en/docs/cli/).\n\n  1. Set the arguments in the **Arguments for running yarn commands** input.\n\n     You can specify multiple arguments. Check out the available arguments for each command in yarn's documentation.\n\n  ### Troubleshooting\n\n  If the Step fails, run it again with verbose logging enabled. To do so, set the **Enable verbose logging** input to `yes`. Doing so allows yarn to output more information about the command you ran.\n\n  Make sure your commands and arguments are correct, and that your packages are correctly defined in the `package.json` file.\n\n  Note: This Step requires Corepack to manage Yarn versions. Corepack is bundled with Node.js from 14.19.0 and 16.9.0 until 24.x. For Node.js 25+, Corepack will be automatically installed via npm if not already present.\n\n  ### Useful links\n\n  [Corepack documentation](https://github.com/nodejs/corepack#readme)\n  [Getting started with React Native apps](https://devcenter.bitrise.io/getting-started/getting-started-with-react-native-apps/)\n  [Running Detox tests on Bitrise](https://devcenter.bitrise.io/testing/running-detox-tests-on-bitrise/)\n\n  ### Related Steps\n\n  [Run Cocoapods install](https://www.bitrise.io/integrations/steps/cocoapods-install)\n  [Run npm command](https://www.bitrise.io/integrations/steps/npm)\nwebsite: https://github.com/bitrise-community/steps-yarn\nsource_code_url: https://github.com/bitrise-community/steps-yarn\nsupport_url: https://github.com/bitrise-community/steps-yarn/issues\npublished_at: 2026-02-20T12:46:01.454612582Z\nsource:\n  git: https://github.com/bitrise-steplib/steps-yarn.git\n  commit: a88abac0ee3356ab4aec4a043d11eaaf7074defa\nexecutables:\n  darwin-amd64:\n    storage_uri: steps/yarn/2.0.0/bin/yarn-darwin-amd64\n    hash: sha256-a074a727d8694526fcf4f30cdf236d387307f47743389604fbdab20fd9010f93\n  darwin-arm64:\n    storage_uri: steps/yarn/2.0.0/bin/yarn-darwin-arm64\n    hash: sha256-1767a895c69fdc8bfac725d12689aee612fba6915a97f9d1bb652411013645f1\n  linux-amd64:\n    storage_uri: steps/yarn/2.0.0/bin/yarn-linux-amd64\n    hash: sha256-b57d5e51a786fec1714c6ae4c5a71f5320d2ae95a735b7401b18c5a1c7692723\n  linux-arm64:\n    storage_uri: steps/yarn/2.0.0/bin/yarn-linux-arm64\n    hash: sha256-862ac42c4e0755088f00d33636bade98599e6c88cac1ca205a4408ab562334d2\nhost_os_tags:\n- osx-10.11\ntype_tags:\n- dependency\ntoolkit:\n  go:\n    package_name: github.com/bitrise-steplib/steps-yarn\ndeps:\n  brew:\n  - name: node\nis_always_run: false\nis_skippable: false\ninputs:\n- opts:\n    description: |\n      Working directory of the step.\n      You can leave it empty to not change it.\n    title: Working directory\n  workdir: $BITRISE_SOURCE_DIR\n- command: null\n  opts:\n    description: |\n      Specify the command to run with `yarn`. For example `add`.\n      Leave it blank to install dependencies.\n    is_required: false\n    title: The `yarn` command to run\n- args: null\n  opts:\n    description: |-\n      Arguments are added to the `yarn` command. You can specify multiple arguments, separated\n      by a space character. For example `react` or `-dev`\n    title: Arguments for running `yarn` commands\n- opts:\n    description: |\n      Choose if debug logging is enabled.\n    is_required: true\n    title: Enable verbose logging\n    value_options:\n    - \"yes\"\n    - \"no\"\n  verbose_log: \"no\"\n"
  },
  {
    "path": "steps/yarn/step-info.yml",
    "content": "maintainer: bitrise\n"
  },
  {
    "path": "steps/zip-directory-and-export-its-path/1.0.2/step.yml",
    "content": "title: Zip Directory and Export its Path\nsummary: |\n  This step will zip a directory and then export the path as an environment variable\ndescription: |\n  This step will zip a directory and then export the path as an environment variable\nwebsite: https://github.com/danielmcconville/bitrise-step-zip-directory-and-export-its-path\nsource_code_url: https://github.com/danielmcconville/bitrise-step-zip-directory-and-export-its-path\nsupport_url: https://github.com/danielmcconville/bitrise-step-zip-directory-and-export-its-path/issues\npublished_at: 2018-11-22T09:02:52.779130017+10:30\nsource:\n  git: https://github.com/danielmcconville/bitrise-step-zip-directory-and-export-its-path.git\n  commit: 9b25fcdcaec3b54c9afbc9da92075cec3397826a\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: zip\n  apt_get:\n  - name: zip\nis_requires_admin_user: true\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- directory_to_zip: $BITRISE_DIRECTORY_TO_ZIP\n  opts:\n    description: |\n      Define the path to the directory you want zipped here.\n    is_expand: true\n    is_required: true\n    summary: Path to the directory to zip.\n    title: Path to the directory to zip.\n- include_directory: true\n  opts:\n    description: \"Set to true to include the parent directory in the zip file, false\n      if you \\njust want the files in the directory.\\n\"\n    is_expand: false\n    is_required: true\n    summary: If set to true, the zip file will include the parent directory.\n    title: Include the directory in the zip\n    value_options:\n    - \"true\"\n    - \"false\"\noutputs:\n- ZIP_FILE: null\n  opts:\n    description: |\n      This environment variable provdes the path to the zip file.\n    title: Path to the zip file\n"
  },
  {
    "path": "steps/zip-directory-and-export-its-path/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/zipalign-apk/0.2.0/step.yml",
    "content": "title: Zipalign APK\nsummary: |\n  Runs the zipalign Android build tool on a signed APK.\ndescription: |\n  Runs the zipalign Android build tool on a signed APK. Allows for page aligning all shared object files in an APK to ensure libraries are properly extracted after install. Fixes \"Failed to extract native libraries\" error caused by \"lib-xxxx.so is not page-aligned\" install error.\nwebsite: https://github.com/MCeley/bitrise-step-zipalign-apk\nsource_code_url: https://github.com/MCeley/bitrise-step-zipalign-apk\nsupport_url: https://github.com/MCeley/bitrise-step-zipalign-apk/issues\npublished_at: 2020-03-05T21:22:04.660953-05:00\nsource:\n  git: https://github.com/MCeley/bitrise-step-zipalign-apk.git\n  commit: cb7d991f752a8edb0f6bc431ea74d0e3fdb1834d\nhost_os_tags:\n- osx-10.10\n- ubuntu-16.04\ntype_tags:\n- utility\ntoolkit:\n  go:\n    package_name: github.com/MCeley/bitrise-step-zipalign-apk\ndeps:\n  brew:\n  - name: git\n  - name: wget\n  apt_get:\n  - name: git\n  - name: wget\nis_requires_admin_user: false\nis_always_run: false\nis_skippable: false\nrun_if: \"\"\ninputs:\n- bitrise_unaligned_apk_path: null\n  opts:\n    description: Usually `$BITRISE_APK_PATH` or `$BITRISE_SIGNED_APK_PATH`\n    is_expand: true\n    is_required: true\n    summary: The path of the APK that needs to be aligned.\n    title: Unaligned APK Path\noutputs:\n- BITRISE_ALIGNED_APK_PATH: null\n  opts:\n    summary: The path of the aligned APK.\n    title: Aligned APK Path\n"
  },
  {
    "path": "steps/zipalign-apk/step-info.yml",
    "content": "maintainer: community\n"
  },
  {
    "path": "steps/zscan-upload-plugin/1.0.3/step.yml",
    "content": "title: zScan Upload Plugin\nsummary: |\n  Bitrise plugin to upload to Zimperium zScan\ndescription: |\n  This plugin can be used to upload mobile applications to Zimperium (zScan) to be scanned for vulnerabilities. Using a plugin simplifies integrating mobile application security testing into CI/CD process and enables detection and remediation of vulnerabilities earlier in the application SDLC.\nwebsite: https://github.com/Zimperium/zscan-plugin-bitrise\nsource_code_url: https://github.com/Zimperium/zscan-plugin-bitrise\nsupport_url: https://github.com/Zimperium/zscan-plugin-bitrise/issues\npublished_at: 2025-04-01T11:32:49.636012-05:00\nsource:\n  git: https://github.com/Zimperium/zscan-plugin-bitrise.git\n  commit: d9d2aa6c5b3ff7f5a3e71eb77089d6a3a38f4012\ntype_tags:\n- test\ntoolkit:\n  bash:\n    entry_file: step.sh\ndeps:\n  brew:\n  - name: jq\n  - name: curl\n  apt_get:\n  - name: jq\n  - name: curl\nis_skippable: true\ninputs:\n- endpoint: https://ziap.zimperium.com\n  opts:\n    description: \"This is the base URL of your Zimperium console, e.g., `https://ziap.zimperium.com`.\n      \\nSee [Documentation](https://github.com/Zimperium/zscan-plugin-bitrise) for\n      more detail.\\n\"\n    is_expand: true\n    is_required: true\n    summary: Zimperium Console base URL.\n    title: Endpoint\n- client_id: null\n  opts:\n    description: |\n      Client ID part of the API Key created through the Authorization tab of your console.\n    is_expand: true\n    is_required: true\n    summary: Client ID part of the API Key.\n    title: Client ID\n- client_secret: null\n  opts:\n    description: \"Client Secret part of the API Key created through the Authorization\n      tab of your console. This input is marked as 'sensitive'.\\nAs such, only [Secrets](https://devcenter.bitrise.io/bitrise-cli/secrets/)\n      are accepted as values. \\n\"\n    is_expand: true\n    is_required: true\n    is_sensitive: true\n    summary: Client Secret part of the API Key.\n    title: Client Secret\n- file_path: null\n  opts:\n    description: |\n      The path to the binary to be uploaded for analysis. This must point to a valid mobile application, e.g., .ipa or .apk file.\n    is_expand: true\n    is_required: true\n    summary: The path to the binary\n    title: File Path\n- opts:\n    description: |\n      If set to true, the step will wait for an assessment report. Otherwise, the step will finish and the report can be obtained from the console.\n    is_expand: true\n    is_required: false\n    summary: Set to true to wait for an assessment report\n    title: Wait for Report\n    value_options:\n    - \"true\"\n    - \"false\"\n  wait_for_report: \"true\"\n- opts:\n    description: \"Specifies the format for the assessment report. For more information\n      on SARIF, \\nplease see [OASIS Open](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html).\\n\"\n    is_expand: true\n    is_required: false\n    summary: Format for the assessment report.\n    title: Report Format\n    value_options:\n    - json\n    - sarif\n  report_format: json\n- opts:\n    description: \"If the application is uploaded for the first time, it will be assigned\n      to the specified team.  This setting \\nhas no effect if the application is already\n      assigned to a team. To change team assignment, please use the Console.\\n\"\n    is_expand: true\n    is_required: false\n    summary: Team that the application should be assigned to.\n    title: Team Name\n  team_name: Default\noutputs:\n- ZSCAN_REPORT_PATH: null\n  opts:\n    description: \"Assessment report will be provided in the specified format. \\n\"\n    summary: Local path to the downloaded assessment report.\n    title: Path to the assessment report\n"
  },
  {
    "path": "steps/zscan-upload-plugin/step-info.yml",
    "content": "maintainer: community\n"
  }
]